-
Notifications
You must be signed in to change notification settings - Fork 12.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
Tracing: Add more detail to HTTP Outgoing Request #64757
Conversation
As events rather than sub-spans, to save cluttering the view.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@bboreham I assume this one is fine for 9.5.0? (IE doesn't need to roll out into a patch). Let me know if you need a hand with the labelling to satisfy the checks |
No burning need to get it out, just something I thought would make an improvement. |
I found some instructions about labels in the 'Details' against CI checks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I have now pushed the commit turning off those extra attributes for headers. |
What is this feature?
Adds more detail to the span for outgoing HTTP calls from Grafana backend.
Why do we need this feature?
This lets you see in the tracing view the relative contribution of each step - DNS request, establishing the connection, sending data, etc.
Who is this feature for?
Engineers investigating performance of Grafana and backend systems.
Which issue(s) does this PR fix?:
NA
Special notes for your reviewer:
OpenTelemetry by default will generate a bunch of sub-spans for DNS lookup, etc., but I prefer to have them as events, to save cluttering the view.