npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

prometheus-middleware

v1.4.0

Published

Middleware to add an HTTP server to expose prometheus metrics.

Downloads

271

Readme

GitHub release GitHub license CI pipeline Opened issues Opened PR Code coverage Node version

Node.js simple middleware to expose Prometheus metrics

Purpose

Module to create an HTTP server to expose Prometheus metrics.
By default it:

  • runs an HTTP server to expose metrics
  • instantiates and returns a prom-client
  • patches http server to get request response time
  • allows to define custom metrics through prom-client

Compatibility

Supported and tested : >= 14.0

| Version | Supported | Tested | |:-------------:|:-------------:|:--------------:| | 16.x | yes | yes | | 18.x | yes | yes | | 20.x | yes | yes |

It works with different HTTP servers:

By default you can access your metrics on this endpoint: http://localhost:9350/metrics

In order to handle remote attack and to avoid high cardinality, the default behavior of this lib is to override the path label in case of HTTP code 404.

Installation

$ npm install prometheus-middleware --save

Usage

Basic

const APM = require('prometheus-middleware')
const apm = new APM()
apm.init()

Add a custom metric

const APM = require('prometheus-middleware')
const apm = new APM()
apm.init()
// ----------------
const counter = new apm.client.Counter({
  name: 'metric_name',
  help: 'metric_help',
})
// ----------------
counter.inc(); // Increment by 1
counter.inc(10); // Increment by 10

The metrics system is exactly the same as in prom-client librairy.

Configuration

The config is an JSON object which accepts the following property:

const APM = require('prometheus-middleware')
const apm = new APM({
  METRICS_ROUTE: "/metrics",
  PORT: 9350,
  PROM_CLIENT_CONF: {},
  HTTP_DURATION_BUCKETS: [0.01, 0.02, 0.05, 0.1, 0.2, 0.5, 1, 2]
  HTTP_SUMMARY_PERCENTILES: [0.5, 0.9, 0.95, 0.99]
  NORMALIZE_ENDPOINT: false,
})
apm.init()

Destroy the APM

If you use a graceful exit method or if you want to simply stop the APM, you should run:

const APM = require('prometheus-middleware')
const apm = new APM()
apm.init()

process.on('SIGTERM', () => {
  apm.destroy()
})

| Property | Default | Description | |:--------------------------|:----------------------------------------|:------------------------------------------------------------| | METRICS_ROUTE | /metrics | Route to expose the metrics | | PORT | 9350 | Port to listen metrics | | PROM_CLIENT_CONF | {} | Configuration of the prom-client lib | | HTTP_DURATION_BUCKETS | [0.01, 0.02, 0.05, 0.1, 0.2, 0.5, 1, 2] | List of values for HTTP request duration | | HTTP_SUMMARY_PERCENTILES | [0.5, 0.9, 0.95, 0.99] | List of values for HTTP request percentiles | | NORMALIZE_ENDPOINT | true | Normalize endpoint by occulting ids, and query parameters |

To see how to use the module you can refer to the example folder.

Debug

The agent use debug module in order not to pollute your logs. If you want to see all agent output just use DEBUG environment variable:

DEBUG=prometheus-middleware* node myApp.js

Test

$ npm test

Coverage report can be found in coverage/.