JSPM

  • Created
  • Published
  • Downloads 212123
  • Score
    100M100P100Q197841F
  • License MIT

express middleware with popular prometheus metrics in one bundle

Package Exports

  • express-prom-bundle

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 (express-prom-bundle) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

build status Coverage Status license NPM version

express prometheus bundle

Express middleware with popular prometheus metrics in one bundle. It's also compatible with koa v1 (see below).

Internally it uses prom-client. See: https://github.com/siimon/prom-client

Included metrics:

  • up: normally is just 1
  • http_request_duration_seconds: http latency histogram labeled with status_code, method and path

Please not version 2.x is NOT compatible with 1.x

Install

npm install express-prom-bundle

Usage

const promBundle = require("express-prom-bundle");
const metricsMiddleware = promBundle({/* options */ });
const app = require("express")();

app.use(metricsMiddleware);
app.use(/* your middleware */);
app.listen(3000);

ALERT!

The order in wich the routes are registered is important, since only the routes registered after the express-prom-bundle will be measured

You can use this to your advantage to bypass some of the routes. See the example below.

Options

  • buckets: buckets used for http_request_seconds histogram
  • includeMethod: include HTTP method (GET, PUT, ...) as a label to http_request_duration_seconds
  • includePath: include URL path as a label (see below)
  • normalizePath: boolean or function(req) - path normalization for includePath option
  • excludeRoutes: array of strings or regexp specifying which routes should be skipped for http_request_duration_seconds metric. It uses req.path as subject when checking
  • autoregister: if /metrics endpoint should be registered. (Default: true)
  • whitelist, blacklist: array of strings or regexp specifying which metrics to include/exclude

More details on includePath option

The goal is to have separate latency statistics by URL path, e.g. /my-app/user/, /products/by-category etc.

Just taking req.path as a label value won't work as IDs are often part of the URL, like /user/12352/profile. So what we actually need is a path template. The module tries to figure out what parts of the path are values or IDs, and what is an actual path. The example mentioned before would be normalized to /user/#val/profile and that will become the value for the label.

You can override this magical behavior and define your own function by providing an optional callback using normalizePath option.

For more details:

express example

setup std. metrics but exclude up-metric:

"use strict";

const express = require("express");
const app = express();
const promBundle = require("express-prom-bundle");


// calls to this route will not appear in metrics
// because it's applied before promBundle
app.get("/status", (req, res) => res.send("i am healthy"));

app.use(promBundle({
    includePath: true,
    excludeRoutes: ["/foo"]
}));

// this call will NOT appear in metrics, because it matches excludeRoutes
app.get("/foo", (req, res) => res.send("bar"));

// calls to this route will appear in metrics
app.get("/hello", (req, res) => res.send("ok"));

app.listen(3000);

See an advanced example on github

koa v1 example

const promBundle = require("express-prom-bundle");
const koa = require("koa");
const c2k = require("koa-connect");
const metricsMiddleware = promBundle({/* options */ });

const app = koa();

app.use(c2k(metricsMiddleware));
app.use(/* your middleware */);
app.listen(3000);

Changelog

  • 2.0.0

  • 1.2.1

    • upgrade prom-client to 6.1.2
    • add options: includeMethod, includePath, keepDefaultMetrics

License

MIT