Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
OpenTracing compatibility (question)
See original GitHub issueOpenTracing website proclaims that Zipkin is one of the supported implementations. However, the interface of the tracer provided by zipkin does not seem to be any close to the official Javascript OpenTracing API and it fails with the TypeError: Uncaught error: tracer.startSpan is not a function.
Am I missing something fundamental (quite possible), or is openzipkin/zipkin-js indeed incompatible with OpenTracing API? In the latter case, is there either a plan to provide compatibility with OpenTracing API (and/or willingness to accept pull requests which would provide it), or some other zipkin tracer implementation that would be compatible wityh OpenTracing API?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thank you for the alert 😃 Awesome to see the typescript conversion, might be a good idea to move DanielMSchmidt/zipkin-javascript-opentracing also to typescript 🤔
https://github.com/DanielMSchmidt/zipkin-javascript-opentracing provide a wrapper for OpenTracing API.