Support Nats java agent instrumentation

[pkgonan]

Is your feature request related to a problem? Please describe.

Nats is a very fast and scalable Pub/Sub messaging system that replaces WebSockets.

We are using Otel APM, but the metrics that communicate with Nats are not being exposed.

Therefore, we are requesting support for OTEL java agent instrumentation for Nats Client.

Reference

• https://github.com/nats-io/nats.java

Describe the solution you'd like

Development new java agent instrumentation for java nats client.

Describe alternatives you've considered

No response

Additional context

No response

[laurit]

Hey @pkgonan,

We likely won't have time and resources to implement this instrumentation ourselves, but we would find an external contribution welcome.

[wl2027]

@laurit It seems that this isuess has been open for a long time, it can be assigned to me, I will try my best to complete it.

[laurit]

@laurit It seems that this isuess has been open for a long time, it can be assigned to me, I will try my best to complete it.

sure, have fun

[AlixBa]

hey @wl2027 did you start anything on this topic? I'd like to work on the library instrumentation (not the agent part) if there is a basic structure available.

[AlixBa]

@laurit I am accumulating commits here, and I think I almost reach a point where it feels like the bare minimum is supported (publish, subscribe, jet stream excluded).

What would be the best for a review? All-in or split by block? Is there anything to do first as this would be a new module?

[laurit]

What would be the best for a review? All-in or split by block? Is there anything to do first as this would be a new module?

For review it is best to have a fully functional instrumentation so we could see what telemetry it creates and compare it with existing messaging instrumentations.

[wl2027]

hey @wl2027 did you start anything on this topic? I'd like to work on the library instrumentation (not the agent part) if there is a basic structure available.

I was too busy with work recently and missed this message. Since I had already completed part of the work before, I feel confused about the support for instrumentation starting from version 2.21.0, because NATS had already supported message headers passing in version 2.10.0

[AlixBa]

Then I guess we're not talking about the same thing. Unless I completely missed it, I don't see any instrumentation for this. I was referring to creating spans & traces for publication and subscriptions over NATS (with or without JetStreams).