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

opossum-prometheus

v0.4.0

Published

Prometheus metrics for opossum circuit breaker

Downloads

27,515

Readme

Prometheus Metrics for Opossum Circuit Breaker

Node.js CI Coverage Status Known Vulnerabilities

This module provides Prometheus metrics for opossum circuit breakers. To use it with your circuit breakers, just pass them in to the PrometheusMetrics constructor.

For each circuit breaker, the metrics are:

  • a prometheus counter for each event name
  • a prometheus summary for the events success, failed execution time.

Example:

  const CircuitBreaker = require('opossum');
  const PrometheusMetrics = require('opossum-prometheus');

  // create a couple of circuit breakers
  const c1 = new CircuitBreaker(someFunction);
  const c2 = new CircuitBreaker(someOtherFunction);

  // Provide them to the constructor
  const prometheus = new PrometheusMetrics({ circuits: [c1, c2] });

  //...
  // Provide other circuit breaker later
  const c3 = new CircuitBreaker(someOtherFunction3);
  prometheus.add([c3]);
  
  // Write metrics to the console
  console.log(await prometheus.metrics());

This module would typically be used in an application that can provide an endpoint for the Prometheus server to monitor.

The prometheusRegistry constructor parameter allows you to provide an existing prom-client registry. The metrics about the circuit will be added to the provided registry instead of the global registry. The default metrics will not be added to the provided registry.

const CircuitBreaker = require('opossum');
const PrometheusMetrics = require('opossum-prometheus');
const { Registry } = require('prom-client');

// Create a registry
const registry = new Registry();

// create a circuit
const circuit = new CircuitBreaker(functionThatMightFail);
const metrics = new PrometheusMetrics({ circuits: [circuit], registry: registry })

Options

The PrometheusMetrics constructor takes an options object as detailed below.

const options = {};
new PrometheusMetrics(options)

|Name |Description |Default | |--------------------------|------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| |circuits |A list or individual circuit breaker to create metrics for |No circuits | |registry |An existing registry to use for prometheus metrics |undefined - The default prometheus registry will be used and default system metrics will be collected| |exposePerformanceMetrics|Measure the performance of breakers and report them through the registry|true | |metricPrefix|Prefix for circuit breakers metrics name|any string |