-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Add OpenTelemetry tracing and metrics support #8999
Conversation
f9e52d8
to
fb6faef
Compare
Would be great to get this PR merged. |
e324bd3
to
50669a4
Compare
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 👽
825a049
to
b799956
Compare
* Support OpenTelemetry tracing * Support OpenTelemetry metrics * Handle trace propagation
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 👌
@tomMoulard thanks a lot for the PR, I am trying to deploy this in my k8 cluster where otel collector is running like a daemonset, not sure how to pass in the node ip to the command line args ?
|
also if we are using aws xray as tracing backend, how can we change the trace id to xray specific ID ? for instance in our downstream services we use https://www.npmjs.com/package/@opentelemetry/id-generator-aws-xray |
Hello @jayasai470, Closed PRs are not a place to have discussions. Feel free to open a topic on Traefik's community forum. |
Thanks for letting me know, have created one https://community.traefik.io/t/traefik-opentelemetry/16994 |
What does this PR do?
This PR adds support OpenTelemetry traces and metrics.
Motivation
To have more tracing and metrics backends.
Fixes #6374
Fixes #8231
More
Additional Notes
TODO: Handle W3C Trace Context propagation #8231