Package Exports
- jaeger-client
- jaeger-client/dist/src/metrics/metrics
- jaeger-client/dist/src/metrics/noop/metric_factory
- jaeger-client/dist/src/reporters/udp_sender
- jaeger-client/dist/src/samplers/remote_sampler
- jaeger-client/dist/src/thrift
- jaeger-client/dist/src/util
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 (jaeger-client) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Jaeger Bindings for Javascript OpenTracing API
This is a client side library that implements Javascript OpenTracing API, with Zipkin-compatible data model.
This project is currently WIP and not ready for use. Do not use it until this notice goes away.
Contributing
Please see CONTRIBUTING.md.
Debug Traces (Forced Sampling)
Programmatically
The OpenTracing API defines a sampling.priority standard tag that
can be used to affect the sampling of a span and its children:
span.setTag(opentracing_tags.SAMPLING_PRIORITY, 1);Via HTTP Headers
Jaeger Tracer also understands a special HTTP Header jaeger-debug-id,
which can be set in the incoming request, e.g.
curl -H "jaeger-debug-id: some-correlation-id" http://myhost.comWhen Jaeger sees this header in the request that otherwise has no tracing context, it ensures that the new trace started for this request will be sampled in the "debug" mode (meaning it should survive all downsampling that might happen in the collection pipeline), and the root span will have a tag as if this statement was executed:
span.setTag("jaeger-debug-id", "some-correlation-id");This allows using Jaeger UI to find the trace by this tag.