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

async-prometheus-client

v2.0.1

Published

Prometheus client, with support for horizontal scaling w/o a PushGateway

Downloads

459

Readme

Async Node.JS Prometheus Client

Build Status codecov

This library was built to allow for asynchronous metric tracking. This mostly just means that it was built in order to use Redis as a registry.

The specific use case this was created for, was tracking metrics on Zeit.co's Now v2 platform, without using a PushGateway.

How does it work?

Normally, NodeJS process are long running, and share memory. With the advent of serverless frameworks and technologies, NodeJS apps are starting to scale across multiple processes and "servers". This can be problematic for metric tracking and Prometheus, as you need to set it up to scrape a particular endpoint. You might not always know what the direct endpoint is!

Some might suggest using a PushGateway, but this comes with its own list of problems to solve.

This solution was heavily inspired (pretty much a clone) from the PHP library.

Usage

Create your registry:
import {Registry, RedisAdapter} from 'async-prometheus-client'
import {createClient} from 'redis';

// By default, this will use an In Memory registry
const registry = Registry.getDefault();
// Or, a Redis one!
const registry = new Registry(new RedisAdapter(createClient()));
Create some metrics
const counter = registry.getOrRegisterCounter({
    namespace: 'test',
    name: 'some_counter',
    help: 'it increases',
    labels: ['type'],
});
await counter.inc('blue');
await counter.incBy(3, 'green');

const gauge = registry.getOrRegisterGauge({
    namespace: 'test',
    name: 'some_gauge',
    help: 'it sets',
    labels: ['type'],
})
await gauge.set(2.5, ['blue']);
await gauge.inc(['green']);

const histogram = registry.getOrRegisterHistogram({
    namespace: 'test',
    name: 'some_histogram',
    help: 'it observers',
    labels: ['type'],
    buckets: [0.1, 1, 2, 3.5, 4, 5, 6, 7, 8, 9],
})
histogram.observe(3.5, ['blue']);
Expose the metrics
import {Renderer} from 'async-prometheus-client';

app.get('/metrics', async (req, res) => {
    res.set('Content-Type', Renderer.MIME_TYPE);
    
    res.send(await Renderer.render(registry));
})