-
Notifications
You must be signed in to change notification settings - Fork 465
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Backwards rendering of CHILD_OF vs. FOLLOWS_FROM #1802
Comments
typically child-of should take precedence over follows-from links. |
@yurishkuro, I would consider making a PR with a fix if I could get a rough pointer into the code base where the adjustments are most likely to be needed. (I'm just completely unfamiliar with this codebase.) |
Unfortunately, I am not that intimately familiar with the UI code either. My typical approach is to look at some UI labels in the screen of interest, find them in the code, and walk upwards. In theory, there can be several solutions to this problem:
|
What happened?
When creating a new span with a single link to a
followed
span in the same trace, the UI renders the new span as if thefollowed
span were actually theparent
span, and renders a link icon for the trueparent
of the new span. In other words, the UI seems to flip the meaning ofCHILD_OF
andFOLLOWS_FROM
when rendering, even though the references are correctly expressed in the trace.Steps to reproduce
followed
andparent
parent
and specify one link to thefollowed
spanfollowed
with a link toparent
instead of the other way round.Expected behavior
I expected child spans to be rendered beneath their parent, not beneath a linked span.
Relevant log output
No response
Screenshot
Additional context
Hopefully the annotated screen shot depicts the issue clearly.
The red-circled span shows a parent spanID ending in
dc34
and a follows-from spanId ending inde6f
. Yet the red-circled span namedremote_client::send_response
is rendered as if the parent is the follows-from span ofde6f
.Jaeger backend version
v1.49.0
SDK
https://crates.io/crates/opentelemetry_sdk
OTEL Rust SDK -> [OTLP] -> Jaeger-all-in-one
Pipeline
OTEL Rust SDK -> OTLP -> Jaeger-all-in-one
Stogage backend
Jaeger all-in-one
Operating system
Linux
Deployment model
Docker
Deployment configs
No response
The text was updated successfully, but these errors were encountered: