Zipkin like tracing about prometheus-nats-exporter HOT 6 CLOSED

I agree having Zipkin like tracing would sure be helpful especially for troubleshooting scenarios.
e.g. the trace of message
publishing ----> [NATS Streaming] -----> n-Consumers
can help me tell if there are any consumers or not for a particular message.

However, I suppose might be other possibilities to get similar information.

from prometheus-nats-exporter.

Would you mind explaining your use case further? Are you suggesting zipkin integration into the NATS server or NATS streaming server?

from prometheus-nats-exporter.

Sure,
Thanks for replying back.
I would like the tracing of a request throughout my application, So that I could know what flow has a request taken through the microservices application which could include information also on what NATS subjects were visited.
Also it would be great if we would trace NATS requests per subject like throughout, How many failed etc.

from prometheus-nats-exporter.

Closing for now. For zipkin like tracing can check: https://github.com/nats-io/not.go

from prometheus-nats-exporter.

Seems like https://github.com/nats-io/not.go is not maintained anymore. Tried this in Java and Maven dependency is not available anymore.

from prometheus-nats-exporter.

We are working on this as part of nats-surveyor where it will support tracing across imports. Some detail:

• ADR https://github.com/nats-io/nats-server/blob/master/doc/adr/0003-distributed-tracing.md
• full multi component overview https://gist.github.com/ripienaar/81dcd435b9bcb34419a7caec8e52c2b8

from prometheus-nats-exporter.