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
{{ message }}
This repository has been archived by the owner on Mar 24, 2024. It is now read-only.
Tracing spans are getting dropped between when they're created and when they should be displayed in Jaeger's query interface. This causes obnoxious warnings:
Because parent spans can get dropped, traces can be much harder to interpret.
It's extremely unclear to me why this is happening; nothing I've been able to find on the topic applies to this scenario, as far as I can tell. Seemingly any span could be dropped, and it happens with essentially no load on any Jaeger components, making it unlikely it's a queuing problem.
The text was updated successfully, but these errors were encountered:
Tracing spans are getting dropped between when they're created and when they should be displayed in Jaeger's query interface. This causes obnoxious warnings:
Because parent spans can get dropped, traces can be much harder to interpret.
It's extremely unclear to me why this is happening; nothing I've been able to find on the topic applies to this scenario, as far as I can tell. Seemingly any span could be dropped, and it happens with essentially no load on any Jaeger components, making it unlikely it's a queuing problem.
The text was updated successfully, but these errors were encountered: