-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
FOLLOWS_FROM breaks nesting #3785
Comments
Q1: if you reorder the span references in this span such that CHILD_OF comes in first, would the UI display it correctly then? Q2: was this trace JSON originally loaded from the Jaeger backend, or composed by some other means? I seem to recall we had logic in the backend to reorder the references such that we have the true "parent" reference comes first in the list, which is what might be tripping the UI. |
A1: Indeed it works correctly if A2: It came from Jaeger backend. |
I'm not seeing anything that would place I'm happy to open a PR if you agree with this approach. |
yes, I would do it in the query path of the backend (as an adjuster) |
I opened #3786 |
Describe the bug
Here's a correctly nested span of
foo
:And here it is if it had a
FOLLOWS_FROM
relation to another trace:Here
resize
comes first and you can't collapsefetch_original
anymore.To Reproduce
Use the following trace:
Trace JSON
The problematic reference is:
Expected behavior
FOLLOWS_FROM
adds an icon and doesn't change nesting or ordering.Version (please complete the following information):
The text was updated successfully, but these errors were encountered: