Package Exports
- @opentelemetry/sdk-metrics
- @opentelemetry/sdk-metrics/build/esm/index.js
- @opentelemetry/sdk-metrics/build/esnext
- @opentelemetry/sdk-metrics/build/esnext/index.js
- @opentelemetry/sdk-metrics/build/src/export/AggregationSelector
- @opentelemetry/sdk-metrics/build/src/export/AggregationSelector.js
- @opentelemetry/sdk-metrics/build/src/index.js
- @opentelemetry/sdk-metrics/package.json
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/sdk-metrics) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
OpenTelemetry Metrics SDK
This module contains the Metrics SDK of opentelemetry-js.
Used standalone, this module provides methods for manual instrumentation of code, offering full control over recording metrics for client-side JavaScript (browser) and Node.js.
It does not provide automated instrumentation of known libraries or host environment metrics out-of-the-box.
Installation
npm install --save @opentelemetry/api
npm install --save @opentelemetry/sdk-metrics
Usage
The basic setup of the SDK can be seen as followings:
const opentelemetry = require('@opentelemetry/api');
const { MeterProvider } = require('@opentelemetry/sdk-metrics');
// To create an instrument, you first need to initialize the Meter provider.
// NOTE: The default OpenTelemetry meter provider does not record any metric instruments.
// Registering a working meter provider allows the API methods to record instruments.
opentelemetry.metrics.setGlobalMeterProvider(new MeterProvider());
// To record a metric event, we used the global singleton meter to create an instrument.
const counter = opentelemetry.metrics.getMeter('default').createCounter('foo');
// record a metric event.
counter.add(1, { attributeKey: 'attribute-value' });
In conditions, we may need to setup an async instrument to observe costly events:
// Creating an async instrument, similar to synchronous instruments
const observableCounter = opentelemetry.metrics.getMeter('default')
.createObservableCounter('observable-counter');
// Register a single-instrument callback to the async instrument.
observableCounter.addCallback(async (observableResult) => {
// ... do async stuff
observableResult.observe(1, { attributeKey: 'attribute-value' });
});
// Register a multi-instrument callback and associate it with a set of async instruments.
opentelemetry.metrics.getMeter('default')
.addBatchObservableCallback(batchObservableCallback, [ observableCounter ]);
async function batchObservableCallback(batchObservableResult) {
// ... do async stuff
batchObservableResult.observe(observableCounter, 1, { attributeKey: 'attribute-value' });
}
Views can be registered when instantiating a MeterProvider
:
const meterProvider = new MeterProvider({
views: [
// override the bucket boundaries on `my.histogram` to [0, 50, 100]
{
aggregation: {
type: AggregationType.EXPLICIT_BUCKET_HISTOGRAM,
options: {
boundaries: [0, 50, 100]
}
},
instrumentName: 'my.histogram'
},
// rename 'my.counter' to 'my.renamed.counter'
{ name: 'my.renamed.counter', instrumentName: 'my.counter'}
]
})
Example
See examples/prometheus for an end-to-end example, including exporting metrics.
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 in GitHub Discussions
License
Apache 2.0 - See LICENSE for more information.