node package manager
Share your code. npm Orgs help your team discover, share, and reuse code. Create a free org »


Prometheus client for node.js Build Status Build status

A prometheus client for node.js that supports histogram, summaries, gauges and counters.


See example folder for a sample usage. The library does not bundle any web framework, to expose the metrics just return the metrics() function in the registry.

Usage with Node.js's cluster module

Node.js's cluster module spawns multiple processes and hands off socket connections to those workers. Returning metrics from a worker's local registry will only reveal that individual worker's metrics, which is generally undesirable. To solve this, you can aggregate all of the workers' metrics in the master process. See example/cluster.js for an example.

Default metrics use sensible aggregation methods. Custom metrics are summed across workers by default. To use a different aggregation method, set the aggregator property in the metric config to one of 'sum', 'first', 'min', 'max', 'average' or 'omit'. (See lib/metrics/version.js for an example.)

If you need to expose metrics about an individual worker, you can include a value that is unique to the worker (such as the worker ID or process ID) in a label. (See example/server.js for an example using worker_${} as a label value.)

Metrics are aggregated from the global registry by default. To use a different registry, call client.AggregatorRegistry.setRegistries(registryOrArrayOfRegistries) from the worker processes.



All metric types has 2 mandatory parameters, name and help.

Default metrics

There are some default metrics recommended by Prometheus itself. To collect these, call collectDefaultMetrics

NOTE: Some of the metrics, concerning File Descriptors and Memory, are only available on Linux.

In addition, some Node-specific metrics are included, such as event loop lag, active handles and Node.js version. See what metrics there are in lib/metrics.

collectDefaultMetrics takes 1 options object with 2 entries, a timeout for how often the probe should be fired and a registry to which metrics should be registered. By default probes are launched every 10 seconds, but this can be modified like this:

const client = require('prom-client');
const collectDefaultMetrics = client.collectDefaultMetrics;
// Probe every 5th second.
collectDefaultMetrics({ timeout: 5000 });

To register metrics to another registry, pass it in as register:

const client = require('prom-client');
const collectDefaultMetrics = client.collectDefaultMetrics;
const Registry = client.Registry;
const register = new Registry();
collectDefaultMetrics({ register });

You can get the full list of metrics by inspecting client.collectDefaultMetrics.metricsList.

collectDefaultMetrics returns an identification when invoked, which is a reference to the Timer used to keep the probes going. This can be passed to clearInterval in order to stop all probes.

NOTE: Existing intervals are automatically cleared when calling collectDefaultMetrics.

const client = require('prom-client');
const collectDefaultMetrics = client.collectDefaultMetrics;
const interval = collectDefaultMetrics();
// ... some time later

NOTE: unref is called on the interval internally, so it will not keep your node process going indefinitely if it's the only thing keeping it from shutting down.

Stop polling default metrics

To stop collecting the default metrics, you have to call the function and pass it to clearInterval.

const client = require('prom-client');
// Clear the register


Counters go up, and reset when the process restarts.

const client = require('prom-client');
const counter = new client.Counter({ name: 'metric_name', help: 'metric_help' });; // Inc with 1; // Inc with 10

A counter can be reset manually. This removes the label-values combinations and initializes to 0.

counter.reset();; // Inc with 1 starting from 0


Gauges are similar to Counters but Gauges value can be decreased.

const client = require('prom-client');
const gauge = new client.Gauge({ name: 'metric_name', help: 'metric_help' });
gauge.set(10); // Set to 10; // Inc with 1; // Inc with 10
gauge.dec(); // Dec with 1
gauge.dec(10); // Dec with 10

A gauge can be reset manually. This removes the label-values combinations and initializes to 0.

gauge.reset();; // Inc with 1 starting from 0

There are some utilities for common use cases:

gauge.setToCurrentTime(); // Sets value to current time
const end = gauge.startTimer();
xhrRequest(function(err, res) {
    end(); // Sets value to xhrRequests duration in seconds


Histograms track sizes and frequency of events.


The defaults buckets are intended to cover usual web/rpc requests, this can however be overriden.

const client = require('prom-client');
new client.Histogram({ name: 'metric_name', help: 'metric_help', buckets: [ 0.10, 5, 15, 50, 100, 500 ] });

You can include all label names as a property as well.

const client = require('prom-client');
new client.Histogram({ name: 'metric_name', help: 'metric_help', labelNames: [ 'status_code' ], buckets: [ 0.10, 5, 15, 50, 100, 500 ] });


const client = require('prom-client');
const histogram = new client.Histogram({ name: 'metric_name', help: 'metric_help' });
histogram.observe(10); // Observe value in histogram

Utility to observe request durations

const end = histogram.startTimer();
xhrRequest(function(err, res) {
    end(); // Observes the value to xhrRequests duration in seconds

A Histogram can be reset manually. This removes the label-values combinations and reinitializes the observations.



Summaries calculate percentiles of observed values.


The default percentiles are: 0.01, 0.05, 0.5, 0.9, 0.95, 0.99, 0.999. But they can be overriden like this:

const client = require('prom-client');
new client.Summary({ name: 'metric_name', help: 'metric_help', percentiles: [ 0.01, 0.1, 0.9, 0.99 ] });

Usage example

const client = require('prom-client');
const summary = new client.Summary({ name: 'metric_name', help: 'metric_help' });

Utility to observe request durations

const end = summary.startTimer();
xhrRequest(function(err, res) {
    end(); // Observes the value to xhrRequests duration in seconds

A Summary can be reset manually. This removes the label-values combinations and reinitializes the observations.



All metrics can take a labelNames property in the configuration object. All labelNames that the metric support needs to be declared here. There are 2 ways to add values to the labels

const client = require('prom-client');
const gauge = new client.Gauge({ name: 'metric_name', help: 'metric_help', labelNames: [ 'method', 'statusCode' ] });
gauge.set({ method: 'GET', statusCode: '200' }, 100); // 1st version, Set value 100 with method set to GET and statusCode to 200
gauge.labels('GET', '200').set(100); // 2nd version, Same as above

It is also possible to use timers with labels, both before and after the timer is created:

const end = startTimer({ method: 'GET' }); // Set method to GET, we don't know statusCode yet
xhrRequest(function(err, res) {
    if (err) {
        end({ statusCode: '500' }); // Sets value to xhrRequest duration in seconds with statusCode 500
    } else {
        end({ statusCode: '200' }); // Sets value to xhrRequest duration in seconds with statusCode 200
Default Labels (segmented by registry)

Static labels may be applied to every metric emitted by a registry:

const client = require('prom-client');
const defaultLabels = { serviceName: "api-v1" };

This will output metrics in the following way:

# HELP process_resident_memory_bytes Resident memory size in bytes.
# TYPE process_resident_memory_bytes gauge
process_resident_memory_bytes{serviceName="api-v1"} 33853440 1498510040309

Default labels will be overridden if there is a name conflict.

register.clear() will clear default labels.


Counter and gauge metrics can take a timestamp argument after the value argument. This argument must be a Date or a number (milliseconds since Unix epoch, i.e. 1970-01-01 00:00:00 UTC, excluding leap seconds).

gauge.set(100, 1485531442231); // Set gauge value and timestamp as milliseconds since Unix epoch
gauge.set(100,; // Set gauge value and timestamp as milliseconds since Unix epoch
gauge.set(100, new Date()); // Set gauge value and timestamp as Date
gauge.set({ method: 'GET', statusCode: '200' }, 100, new Date()); // Set gauge value and timestamp with labels
gauge.labels('GET', '200').set(100, new Date()); // Same as above, new Date()); // Increment counter with timestamp

Multiple registries

By default, metrics are automatically registered to the global registry (located at require('prom-client').register). You can prevent this by setting last parameter when creating the metric to false (depending on metric, this might be 4th or 5th parameter).

Using non-global registries requires creating Registry instance and adding it inside registers inside the configuration object. Alternatively you can pass an empty registers array and register it manually.

Registry has a merge function that enables you to expose multiple registries on the same endpoint. If the same metric name exists in both registries, an error will be thrown.

const client = require('prom-client');
const registry = new client.Registry();
const counter = new client.Counter({name: 'metric_name', help: 'metric_help', registers: [ registry ]});
const histogram = new client.Histogram({name: 'metric_name', help: 'metric_help', registers: [ ]});
const mergedRegistries = client.Registry.merge([registry, client.register]);

If you want to use multiple or non-default registries with the Node.js cluster module, you will need to set the registry/registries to aggregate from:

const AggregatorRegistry = client.AggregatorRegistry;
// or for multiple registries:
AggregatorRegistry.setRegistries([registry1, registry2]);


You can get all metrics by running register.metrics(), which will output a string for prometheus to consume.

register.metrics() takes an optional object with a timestamps field. Setting this to false will strip timestamps from the string.

Getting a single metric for Prometheus displaying

If you need to output a single metric for Prometheus, you can use register.getSingleMetricAsString(*name of metric*), it will output a string for Prometheus to consume.

Getting a single metric

If you need to get a reference to a previously registered metric, you can use register.getSingleMetric(*name of metric*).

Removing metrics

You can remove all metrics by calling register.clear(). You can also remove a single metric by calling register.removeSingleMetric(*name of metric*).

Resetting metrics

If you need to reset all metrics, you can use register.resetMetrics(). The metrics will remain present in the register and can be used without the need to instantiate them again, like you would need to do after register.clear().

Cluster metrics

You can get aggregated metrics for all workers in a node.js cluster with register.clusterMetrics(). This method both returns a promise and accepts a callback, both of which resolve with a metrics string suitable for Prometheus to consume.

    .then(metrics => { /* ... */ })
    .catch(err => { /* ... */ });
// - or -
register.clusterMetrics((err, metrics) => {
    // ...


It is possible to push metrics via a Pushgateway.

Note that timestamps will be stripped before the metrics are pushed, since pushgateway >= 0.4 does not accept timestamps.

const client = require('prom-client');
let gateway = new client.Pushgateway('');
gateway.pushAdd({ jobName: 'test' }, function(err, resp, body) { }); //Add metric and overwrite old ones
gateway.push({ jobName: 'test' }, function(err, resp, body) { }); //Overwrite all metrics (use PUT)
gateway.delete({ jobName: 'test' }, function(err, resp, body) { }); //Delete all metrics for jobName
//All gateway requests can have groupings on it
gateway.pushAdd({ jobName: 'test', groupings: { key: 'value' } }, function(err, resp, body) { });
//It's possible to extend the Pushgateway with request options from nodes core http/https library
gateway = new client.Pushgateway('', { timeout: 5000 }); //Set the request timeout to 5000ms


For convenience, there are 2 bucket generator functions - linear and exponential.

const client = require('prom-client');
new client.Histogram({
    name: 'metric_name',
    help: 'metric_help',
    buckets: client.linearBuckets(0, 10, 20) //Create 20 buckets, starting on 0 and a width of 10
new client.Histogram({
    name: 'metric_name',
    help: 'metric_help',
    buckets: client.exponentialBuckets(1, 2, 5) //Create 5 buckets, starting on 1 and with a factor of 2

The content-type prometheus expects is also exported as a constant, both on the register and from the main file of this project, called contentType.

Garbage Collection

To avoid dependencies in this module, GC stats are kept outside of it. If you want GC stats, you can use