Update (Sept 2023)

Superseded by #4843

Proposal (2022)

Creating top-level issue for Jaeger v2 based on OpenTelemetry collector.

This has already been discussed a couple of times:

• roadmap https://www.jaegertracing.io/roadmap/#Integration%20with%20OpenTelemetry%20collector
• two prototypes https://github.com/jaegertracing/jaeger/tree/v1.22.0/cmd/opentelemetry and https://github.com/jaegertracing/jaeger-otelcol. Docs https://www.jaegertracing.io/docs/1.20/opentelemetry/
• Many issue from: https://github.com/jaegertracing/jaeger/issues?q=is%3Aissue+opentelemetry+is%3Aclosed

I would like to bring the topic back as I think it is vital for the future success of Jaeger and staying relevant. Since we worked on v2 a couple of things changed, and therefore, I have created a new proposal on how v2 could be designed https://docs.google.com/document/d/1d7j956tDVYacKHF-l0JL9sVhpbYkt0JECDyGeup-olc/edit?usp=sharing and what is the impact on the ecosystem.

I would like to open this for discussion. If you are Jaeger user please upvote the issue if you would like the proposal including the breaking changes and impact on deployment helm/operator.