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

hyper-instrument

v1.0.0

Published

Instrument services in the hypercore ecosystem

Downloads

113

Readme

Hyper Instrument

Instrument services in the Hypercore ecosystem.

Supports the metrics of

The service registers itself with a DHT Prometheus instance, which scrapes the metrics at regular intervals.

A Grafana dashboard visualising all metrics is available (source).

Install

npm i hyper-instrument

Usage

const instrument = require('hyper-instrument')
const Hyperdht = require('hyperdht')

const scraperPublicKey = // Public key of the metrics scraper
const scraperSecret = // Secret of the metrics scraper
const prometheusAlias = // unique alias identifying this instance
const prometheusServiceName = // the name of the service

const dht = new Hyperdht()

const dhtPromClient = instrument({
  dht,
  scraperPublicKey,
  scraperSecret,
  prometheusAlias,
  prometheusServiceName
})

// You can add additional metrics
new dhtPromClient.promClient.Gauge({
  name: 'my_custom_metric',
  help: 'my custom metric help',
  collect () {
    return 1 // dummy metric
  }
})

// start the scraping
await dhtPromClient.ready()

API

const dhtPromClient = instrument(params)

Set up instrumentation.

Returns a DHT-Prom client instance.

It is possible to add additional metrics by adding them to dhtPromClient.promClient, which is a Prom-client instance.

Run await dhtPromClient.ready() to start the scraping.

params must include:

  • scraperPublicKey: public key of the DHT-Prometheus scraper (hex, z32 or buffer)
  • scraperSecret: secret of the DHT-Prometheus scraper (hex, z32 or buffer)
  • prometheusAlias: string uniquely identifying this instance to the scraper
  • prometheusServiceName: string containing the name of the service

params must also include exactly one of

  • dht: a HyperDHT instance
  • swarm: a Hyperswarm instance

The passed-in swarm/dht will be instrumented. It will also be used to connect with the scraper.

You should pass in swarm if your service operates at Hyperswarm level, since Hyperswarm extends HyperDHT (the Hyperswarm metrics include all HyperDHT metrics).

Optionally, params can also include:

  • corestore: a Corestore instance. Passing in a Corestore will set up hypercore-stats instrumentation