OpenTelemetry API for JavaScript
Note: This is an experimental package under active development. New releases may include breaking changes.
This package provides everything needed to interact with the unstable OpenTelemetry Metrics API, including all TypeScript interfaces, enums, and no-op implementations. It is intended for use both on the server and in the browser.
Beta Software - Use at your own risk
The metrics API is considered alpha software and there is no guarantee of stability or long-term support. When the API is stabilized, it will be made available and supported long-term in the @opentelemetry/api
package and this package will be deprecated.
Quick Start
To get started you need to install the SDK and instrumentations, create a MeterProvider, and register it with the API.
Install Dependencies
$
$ npm install \
@opentelemetry/api-metrics \
@opentelemetry/sdk-metrics \
@opentelemetry/exporter-prometheus
Note: this example is for node.js. See examples/tracer-web for a browser example.
Initialize the SDK
Before any other module in your application is loaded, you must initialize the global tracer and meter providers. If you fail to initialize a provider, no-op implementations will be provided to any library which acquires them from the API.
To collect traces and metrics, you will have to tell the SDK where to export telemetry data to. This example uses Jaeger and Prometheus, but exporters exist for other tracing backends. If you're not sure if there is an exporter for your tracing backend, contact your tracing provider.
Metrics
const api = require("@opentelemetry/api-metrics");
const { MeterProvider } = require("@opentelemetry/sdk-metrics");
const { PrometheusExporter } = require("@opentelemetry/exporter-prometheus");
const exporter = new PrometheusExporter({ startServer: true });
const meterProvider = new MeterProvider();
meterProvider.addMetricReader(exporter);
api.metrics.setGlobalMeterProvider(meterProvider);
Version Compatibility
Because the npm installer and node module resolution algorithm could potentially allow two or more copies of any given package to exist within the same node_modules
structure, the OpenTelemetry API takes advantage of a variable on the global
object to store the global API. When an API method in the API package is called, it checks if this global
API exists and proxies calls to it if and only if it is a compatible API version. This means if a package has a dependency on an OpenTelemetry API version which is not compatible with the API used by the end user, the package will receive a no-op implementation of the API.
Advanced Use
API Methods
If you are writing an instrumentation library, or prefer to call the API methods directly rather than using the register
method on the Tracer/Meter Provider, OpenTelemetry provides direct access to the underlying API methods through the @opentelemetry/api-metrics
package. API entry points are defined as global singleton objects trace
, metrics
, propagation
, and context
which contain methods used to initialize SDK implementations and acquire resources from the API.
const api = require("@opentelemetry/api-metrics");
api.metrics.setGlobalMeterProvider(meterProvider);
api.metrics.getMeterProvider();
api.metrics.getMeter(name, version);
Useful links
License
Apache 2.0 - See LICENSE for more information.