Skip to content
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

Zipkin (and OpenTracing) tracing providers do not provide context propagation #8848

Open
tjquinno opened this issue Jun 5, 2024 · 0 comments
Labels
4.x Version 4.x bug Something isn't working P3 tracing
Projects

Comments

@tjquinno
Copy link
Member

tjquinno commented Jun 5, 2024

Environment Details

  • Helidon Version: 4.x
  • Helidon SE or Helidon MP
  • JDK version:
  • OS:
  • Docker version (if applicable):

Problem Description

The Jaeger and OpenTelemetry tracing providers both provide context propagation.

But neither the OpenTracing provider nor the Zipkin provider does so.

Addressing #8846 would allow the Zipkin provider to do propagation very similarly to how our OTel provider does. That change plus this one would put Zipkin on an equal footing with OTel and Jaeger as providers.

Given that OpenTracing is essentially retired we might not choose to invest the time to add propagation for it. But Zipkin probably should do propagation.

@tjquinno tjquinno added bug Something isn't working tracing 4.x Version 4.x labels Jun 5, 2024
@tjquinno tjquinno added this to Triage in Backlog via automation Jun 5, 2024
@m0mus m0mus added the P3 label Jun 6, 2024
@m0mus m0mus moved this from Triage to High priority in Backlog Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.x Version 4.x bug Something isn't working P3 tracing
Projects
Backlog
  
High priority
Development

No branches or pull requests

2 participants