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
The issue I am facing is that the span started within setTimeout gets associated with the parent span.
This is a problem when trying to identify things like requests that take a long time because now the request-response time also includes the span that was started without blocking the main request-response.
I think the correct solution is to pass parentSpan: null to startSpan, but wanted to confirm that that's the idiomatic way.
And if I do this, is there some sane way to still comment/leave a link to the parent span?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The issue I have is that some requests kick off background activities.
Think something like:
The issue I am facing is that the span started within
setTimeoutgets associated with the parent span.This is a problem when trying to identify things like requests that take a long time because now the request-response time also includes the span that was started without blocking the main request-response.
I think the correct solution is to pass
parentSpan: nulltostartSpan, but wanted to confirm that that's the idiomatic way.And if I do this, is there some sane way to still comment/leave a link to the parent span?
Beta Was this translation helpful? Give feedback.
All reactions