@opentelemetry/scope-async-hooks

OpenTelemetry AsyncHooks-based Scope Manager

This package provides async-hooks based scope manager which is used internally by OpenTelemetry plugins to propagate specific scope between function calls and async operations. It only targets NodeJS since async-hooks is only available there.

What is a ScopeManager ?

The definition and why they exist is available on the readme of the scope-base package.

Implementation in NodeJS

NodeJS has a specific API to track async scope: async-hooks, it allows to track creation of new async operation and their respective parent. This package only handle storing a specific object for a given async hooks context.

Limitations

Even if the API is native to NodeJS, it doesn't cover all possible cases of scope propagation but there is a big effort from the NodeJS team to fix those. That's why we generally advise to be on the latest LTS to benefit from performance and bug fixes.

There are known modules that break scope propagation (some of them are listed there), so it's possible that the scope manager doesn't work with them.

Prior arts

Context propagation is a big subject when talking about tracing in NodeJS, if you want more informations about that here are some resources:

• https://www.npmjs.com/package/continuation-local-storage (which was the old way of doing context propagation)
• Datadog's own implementation for their Javascript tracer: here
• OpenTracing implementation: here
• Discussion about context propagation by the NodeJS diagnostics working group: here

Useful links

• For more information on OpenTelemetry, visit: https://opentelemetry.io/
• For more about OpenTelemetry JavaScript: https://github.com/open-telemetry/opentelemetry-js
• For help or feedback on this project, join us on gitter

License

Apache 2.0 - See LICENSE for more information.

Changelog

0.3.3

Released 2020-01-22

:rocket: (Enhancement)

• opentelemetry-core, opentelemetry-exporter-collector, opentelemetry-exporter-zipkin, opentelemetry-node, opentelemetry-plugin-dns, opentelemetry-plugin-document-load, opentelemetry-plugin-grpc, opentelemetry-plugin-http, opentelemetry-plugin-https, opentelemetry-plugin-ioredis, opentelemetry-plugin-mongodb, opentelemetry-plugin-mysql, opentelemetry-plugin-postgres, opentelemetry-plugin-redis, opentelemetry-plugin-xml-http-request, opentelemetry-shim-opentracing, opentelemetry-tracing, opentelemetry-types, opentelemetry-web
  • #582 Named Tracers / Tracer Registry
• opentelemetry-node, opentelemetry-plugin-postgres
  • #662 feat: add pg-pool to default list of instrumented plugins
  • #708 Simplify and speed up trace context parsing
• opentelemetry-metrics
  • #700 implement named meter

:sparkles: (Feature)

• opentelemetry-propagator-jaeger
  • #701 add jaeger http trace format
• opentelemetry-exporter-stackdriver-trace
  • #648 Stackdriver Trace exporter

:books: (Refine Doc)

• #673 chore(getting-started): Added a TypeScript version for Getting Started Guide

:bug: (Bug Fix)

• opentelemetry-plugin-ioredis
  • #714 fix: return module exports from ioredis