@opentelemetry/metrics

OpenTelemetry Metrics SDK

OpenTelemetry metrics allow a user to collect data and export it to a metrics backend like Prometheus.

Installation

npm install --save @opentelemetry/metrics

Usage

Counter

Choose this kind of metric when the value is a quantity, the sum is of primary interest, and the event count and value distribution are not of primary interest. Counters are defined as Monotonic = true by default, meaning that positive values are expected.

const { MeterRegistry } = require('@opentelemetry/metrics');

// Initialize the Meter to capture measurements in various ways.
const meter = new MeterRegistry().getMeter('your-meter-name');

const counter = meter.createCounter('metric_name', {
  labelKeys: ["pid"],
  description: "Example of a counter"
});

const labels = meter.labels({ pid: process.pid });

// Create a BoundInstrument associated with specified label values.
const boundCounter = counter.bind(labels);
boundCounter.add(10);

Gauge

Gauge metrics express a pre-calculated value. Generally, this kind of metric should be used when the metric cannot be expressed as a sum or because the measurement interval is arbitrary. Use this kind of metric when the measurement is not a quantity, and the sum and event count are not of interest. Gauges are defined as Monotonic = false by default, meaning that new values are permitted to make positive or negative changes to the gauge. There is no restriction on the sign of the input for gauges.

const { MeterRegistry } = require('@opentelemetry/metrics');

// Initialize the Meter to capture measurements in various ways.
const meter = new MeterRegistry().getMeter('your-meter-name');

const gauge = meter.createGauge('metric_name', {
  labelKeys: ["pid"],
  description: "Example of a gauge"
});

const labels = meter.labels({ pid: process.pid });

// Create a BoundInstrument associated with specified label values.
const boundGauge = gauge.bind(labels);
boundGauge.set(10); // Set to 10

See examples/prometheus for a short example.

Measure

Work in progress

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