You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
INTERNAL span kind should be used to instrument some internal functions/operations within application process.
Workers are technically a remote service, so I believe they should produce SERVER spans.
Overall, such inconsistency results in Elastic APM incorrectly "drawing" such spans on a timeline, because the timestamps of worker traces differ from client/backend traces, since they are sent in different times.
Yah, I think it'd be reasonable to make this configurable. Workers can behave a lot of different ways. I'll see if I can expose this as an option for now, though that may change in the future.
Hi,
I have a question regarding
SpanKind
which is set toINTERNAL
now.As per docs:
INTERNAL
span kind should be used to instrument some internal functions/operations within application process.Workers are technically a remote service, so I believe they should produce
SERVER
spans.Overall, such inconsistency results in Elastic APM incorrectly "drawing" such spans on a timeline, because the timestamps of worker traces differ from client/backend traces, since they are sent in different times.
The current workaround for me looks like this:
Is there possibility to change this default span kind or give possibility to override it on API level?
The text was updated successfully, but these errors were encountered: