Package Exports
- @opentelemetry/node
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 (@opentelemetry/node) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
OpenTelemetry Node
This module provides automated instrumentation and tracing for Node.js applications.
For manual instrumentation see the @opentelemetry/tracing package.
How does automated instrumentation work?
This package exposes a NodeTracerProvider
that will automatically hook into the module loader of Node.js.
For this to work, please make sure that NodeTracerProvider
is initialized before any other module of your application, (like http
or express
) is loaded.
OpenTelemetry comes with a growing number of instrumentation plugins for well know modules (see supported modules) and an API to create custom plugins (see the plugin developer guide).
Whenever a module is loaded NodeTracerProvider
will check if a matching instrumentation plugin has been installed.
Please note: This module does not bundle any plugins. They need to be installed separately.
If the respective plugin was found, it will be used to patch the original module to add instrumentation code. This is done by wrapping all tracing-relevant functions.
This instrumentation code will automatically
- extract a trace-context identifier from inbound requests to allow distributed tracing (if applicable)
- make sure that this current trace-context is propagated while the transaction traverses an application (see @opentelemetry/opentelemetry-context-base for an in-depth explanation)
- add this trace-context identifier to outbound requests to allow continuing the distributed trace on the next hop (if applicable)
- create and end spans
In short, this means that this module will use provided plugins to automatically instrument your application to produce spans and provide end-to-end tracing by just adding a few lines of code.
Creating custom spans on top of auto-instrumentation
Additionally to automated instrumentation, NodeTracerProvider
exposes the same API as @opentelemetry/tracing, allowing creating custom spans if needed.
Installation
npm install --save @opentelemetry/api
npm install --save @opentelemetry/node
# Install instrumentation plugins
npm install --save @opentelemetry/plugin-http
npm install --save @opentelemetry/plugin-https
Usage
The following code will configure the NodeTracerProvider
to instrument http
using @opentelemetry/plugin-http
.
const { NodeTracerProvider } = require('@/node');
// Create and configure NodeTracerProvider
const provider = new NodeTracerProvider({
plugins: {
http: {
enabled: true,
// You may use a package name or absolute path to the file.
path: '@/plugin-http',
// http plugin options
}
}
});
// Initialize the provider
provider.register()
// Your application code - http will automatically be instrumented if
// @opentelemetry/plugin-http is present
const http = require('http');
To enable instrumentation for all supported modules, create an instance of NodeTracerProvider
without providing any plugin configuration to the constructor.
const { NodeTracerProvider } = require('@opentelemetry/node');
// Create and initialize NodeTracerProvider
const provider = new NodeTracerProvider();
// Initialize the provider
provider.register()
// Your application code
// ...
Examples
See how to automatically instrument http and gRPC using node-sdk.
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.