-
Notifications
You must be signed in to change notification settings - Fork 627
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
Move to OpenTelemetry #735
Comments
Thanks @Alvise88! We originally used OpenTracing because that's what BuildKit uses, but they actually added support for OpenTelemetry just 2 weeks ago so we can migrate now :) I'll add this to our roadmap. Would you be interested in contributing this change? |
Ok, i will do it in the next few days |
I created a new branch fo this issue: https://github.com/Alvise88/dagger/tree/move-to-opentelemetry Instead of JAEGER_TRACE you have to use OTEL_EXPORTER_JAEGER_ENDPOINT, it can be:
What do you think ? Do you have any suggestions to improve what I have done ? @aluzzardi The pull request is failed due to buildkit mismatch (there is no buildkit tagged with opentelemetry, but only master) |
Dagger use OpenTracing to export traces, OpenTelemetry is considered the new version of both OpenTracing and OpenCensus
Getting started
Migration guide
Example
The text was updated successfully, but these errors were encountered: