CODEWITHSUNDEEP
quarkusactivemq-artemisopen-telemetry
Timz
Timz

Reputation: 461

OpenTelemetry: Context propagation using messaging (Artemis)

I wrote some micro-services using Quarkus that communicate via Artemis. Now I want to add OpenTelemetry for tracing purpose.

What I already tried is to call service B from service A using HTTP/REST. Here the trace id from service A is automatically added to the header of the HTTP request and used in service B. So this works fine. In Jaeger I can see the correlation.

But how can this be achieved using Artemis as messaging system? Do I have to (manually) add the trace id from service A into the message and read it in service B to setup somehow the context (don't know whether this is possible)? Or is there possibly an automatism like for HTTP requests?

I would appreciate any assistance. I have to mention at this point that I have little experience with tracing so far.

Upvotes: 0

Views: 723

Answers (1)

Bruno Baptista
Bruno Baptista

Reputation: 441

There is no quarkus, quarkiverse extension or smallrye lib that provides integration with Artemis and OpenTelemetry, yet.

Also, OpenTelemetry massaging spec is being worked at the moment, because the correct way to correlate sent, received messages and services is under definition at the OTel spec level.

However, I had exactly the same problem as you and did a manual instrumentation that you can use as inspiration: quarkus-observability-demo-activemq

It will correlate the sent service as parent of receiving end.

Upvotes: 1

Related Questions