Hi all,<p>I worked for a company more than 1 year which most of our stack is using Node.js architected in micro-service way.<p>I found difficulty on finding the best way for tracing context and error (distributed tracing) to detect issue faster. Anyone has experienced this too and been willing to share the way for dealing with this in production system?<p>P.S: I believe most people usually passing context in function call and combine it with open tracing. But I'm not sure if there are any better ways than that in Node.js. Example of distributed tracing in Golang: https://www.youtube.com/watch?v=nm2A80PfYww
In JS you use (if using zipkin) <a href="https://github.com/openzipkin/zipkin-js/tree/master/packages/zipkin-context-cls" rel="nofollow">https://github.com/openzipkin/zipkin-js/tree/master/packages...</a>. If you have further questions, feel free to come to <a href="https://gitter.im/openzipkin/zipkin" rel="nofollow">https://gitter.im/openzipkin/zipkin</a> and people will help you with more details.
> I believe most people usually passing context in function call and combine it with open tracing.<p>What about that is not working for you? I haven't used Node at all but I imagine it would work about the same as described in the video you linked.