Not to have more traces in the working

eclipse / microprofile-telemetry

microprofile telemetry

Apache License 2.0

16 stars 16 forks source link

Not to have more traces in the working #16

Open Emily-Jiang opened 2 years ago

Emily-Jiang commented 2 years ago

Description

As a:

[x] 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 commented 2 years ago

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

pdudits commented 1 year ago

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 commented 10 months ago

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.