You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to ask if OpenTelemetry support should be part of this library.
When a service A communicate through rabbitmq to service B, service A needs to propagate the "TraceID" and "SpanID" to service B to measure the time needed.
Hey there, by "support should be part of this library", I understand you would like to provide automatic instrumentation, something somewhat similar to e.g. Cassandra instrumentation?
Hi,
I would not add any exporter difference (eg. zipkin) as it is a component to be chosen by the dev team, rather only the propagator to inject TraceId, SpanId in the RabbitMQ headers.
I would avoid to add information to the payload as a checksum is needed in certain scenarios.
Hi,
I would like to ask if OpenTelemetry support should be part of this library.
When a service A communicate through rabbitmq to service B, service A needs to propagate the "TraceID" and "SpanID" to service B to measure the time needed.
I saw this issue which may help:
open-telemetry/opentelemetry-go-contrib#376
The text was updated successfully, but these errors were encountered: