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

Not to have more traces in the working #16

Open
1 of 2 tasks
Emily-Jiang opened this issue May 5, 2022 · 3 comments
Open
1 of 2 tasks

Not to have more traces in the working #16

Emily-Jiang opened this issue May 5, 2022 · 3 comments
Assignees

Comments

@Emily-Jiang
Copy link
Member

Emily-Jiang commented May 5, 2022

Description

As a:

  • Application user
  • Specification implementer

...I need to be able to:

choose when to use MicroProfile OpenTracing or MicroProfile Telemetry.
...which enables me to:
make my current applications that using MicroProfile OpenTracing continue working. I don't want to have both MicroProfile OpenTracing and MicroProfile Telemetry providing traces.

@Emily-Jiang
Copy link
Member Author

Do we want to support the scenario of having both MP Telemetry and MP OpenTracing enabled?

@pdudits
Copy link
Contributor

pdudits commented Jun 5, 2023

Supporting both is possible by using OpenTracing Shim in opentelemetry. The traces are not duplicated and should user want to retain particular export format or header propagation, they are free to do so by configuring appropriate OpenTelemetry components.

@Emily-Jiang
Copy link
Member Author

End users have to choose either to use MP OpenTracing or MP Telemetry. Microservices using MP Telemetry should work with another one using MP OpenTracing. A blog on this will be published in due course.

@Emily-Jiang Emily-Jiang self-assigned this Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants