Move to OpenTelemetry

[Alvise88]

Dagger use OpenTracing to export traces, OpenTelemetry is considered the new version of both OpenTracing and OpenCensus

Getting started
Migration guide
Example

[aluzzardi]

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 :)

moby/buildkit#2152

I'll add this to our roadmap. Would you be interested in contributing this change?

[Alvise88]

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 :)

moby/buildkit#2152

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

[Alvise88]

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:

1. http://host.docker.internal:14268/api/traces (at least docker 20)
2. http://localhost:14268/api/traces

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)