OpenTracing documentation Client Server #527
Replies: 5 comments
-
I got the client / publisher side of code working
Going to work on the server / subscriber side. |
Beta Was this translation helpful? Give feedback.
-
For subscriber will be this
This is for W3C header. Not B3 header. |
Beta Was this translation helpful? Give feedback.
-
@jek-bao-choo I'm not understanding what you are trying to accomplish here! What documentation in the NATS go client are you referring to (maybe a link to github?). What "context" are your referring to and what client/server to you mean read and inject from. Please give more information so I can help you. |
Beta Was this translation helpful? Give feedback.
-
@jek-bao-choo converted to discussion |
Beta Was this translation helpful? Give feedback.
-
We currently have a java reference for using Open Tracing - although it is dated and was written before we had headers, and so we used a binary carrier. https://github.com/nats-io/not.java I think this is a great idea - a .NET version of that reference architecture that uses the textMap carrier utilizing NATS headers. That being said, I think it would reside in be a separate repo + package rather than being here in NATS.Client assembly. |
Beta Was this translation helpful? Give feedback.
-
Does anyone have OpenTracing documentation on how to inject context at client and extract context at server?
The golang of nats has a documentation example. Wondering if we have one for nats.net?
If anyone of you have it, please share. I am happy to do PR to add it to the README.md here.
Beta Was this translation helpful? Give feedback.
All reactions