Package Exports
- zipkin-javascript-opentracing
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (zipkin-javascript-opentracing) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Zipkin-Javascript-Opentracing
Installation
Usage
Please see the examples in the examples/ directory.
Limitations
injecting and ejecting
We currently only support HTTP Headers. If you need your own mechanism, feel free to do a PR.
Also we assume that you only inject the HTTP Headers once, otherwise we will send multiple ClientSend annotations for you.
Flags
They are currently not supported, feel free to do a PR.
Follows From (zipkin)
FollowsFrom is not supported by openTracing, as far as I understand it.
Tags
Zipkin doesn't distinguish between logs and tags.
Additional options for starting a span
We need to know if this is a server or client to set the right annotations. Therefore we need the kind attribute to be set.
Example
All examples need to run zipkin on "localhost:9411". This is best achieved by a docker image.
docker run -d -p 9411:9411 openzipkin/zipkinIs the best method to achieve this.
Basic
To see how to use this library with only one service see examples/basic.
You can run the example with npm run example:basic.
Advanced
In order to see how different services may pick up spans and extend them, please see the advanced example at examples/advanced.
You can run the example with npm run example:advanced.
TODOS
- be able to set sampler
- investigate other easy win tags