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

even though appropriate tracer object is created and registered globally, calling io.helidon.tracing.Tracer.global() results in DefaultTracer #9486

Closed
AshokVardhanM opened this issue Nov 12, 2024 · 3 comments
Assignees

Comments

@AshokVardhanM
Copy link

AshokVardhanM commented Nov 12, 2024

Even though appropriate tracer object is created and registered globally, calling io.helidon.tracing.Tracer.global() results in DefaultTracer

We have observed that OpenTelemetryProducer.java's init() method is being executed and both opentelemetry and helidon tracing tracer objects are created. Helidon tracing object is also registered globally via OpenTelemetryTracerProvider.java but when we try to call io.helidon.tracing.Tracer.global() it results in DefaultTracer object instead of appropriate tracer object.

Environment Details

  • Helidon Version: Helidon version 4.0.11
  • Helidon MP
  • JDK version: JDK 21
  • OS: All
  • Docker version (if applicable): NA

Problem Description

We are getting DefaultTracer object on executing io.helidon.tracing.Tracer.global() even when appropriate tracer object is created and registered globally via OpenTelemetryTracerProvider.java

This problem is continuously happening in the application shared/attached in this ticket.

Steps to reproduce

Start the application from the main class named "StreamsLongevityMain"
We can debug the flow and observe that OpenTelemetryProducer.java's init() method is executed first and then creates and registers the tracer object and then Tracer.global() results in DefaultTracer object.

@AshokVardhanM
Copy link
Author

seems like attachment is more than expected size and is not getting uploaded, please let me know on how to upload the project where the issue is observed.

@tjquinno
Copy link
Member

This might be the same as #9488.

@tjquinno tjquinno self-assigned this Nov 13, 2024
@tjquinno
Copy link
Member

Closing as duplicate of #9488.

@github-project-automation github-project-automation bot moved this from Triage to Closed in Backlog Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants