Hyper Instrument

Instrument services in the Hypercore ecosystem.

Supports both the Node.js and bare runtimes.

Supports the metrics of

- hypercore-stats
- hyperswarm-stats
- hyperdht-stats

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
`

Versions

- V1 works for Hypercore V10 and Corestore V6. It has a different API, so make sure to look at the V1 README.
- V2 works for Hypercore v11 and Corestore v7

Usage

`
const HyperInstrument = require('hyper-instrument')
const Hyperdht = require('hyperdht')
const { version } = require('./package.json') // version of your own module

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 instrumentation = new HyperInstrument({
dht,
scraperPublicKey,
scraperSecret,
prometheusAlias,
prometheusServiceName,
version
})

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

// If you want to see instrumentation-related logs:
instrumentation.registerLogger()

// start the scraping
await instrumentation.ready()
`

API

#### const instrumentation = new HyperInstrument(params)

Set up instrumentation by registering the default metrics and creating a DHT-Prom client instance.

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

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
- moduleVersions: a list of package names for which to expose the version number as a metric. Defaults to the core datastructure and networking libraries.

#### instrumentation.promClient

The Prom Client instance.

#### instrumentation.dhtPromClient

The DHT Prom Client instance.

#### await instrumentation.ready()

Start the metrics scraping.

#### await instrumentation.close()

Stop the metrics scraping.

#### registerLogger(logger=console)

Register a logger, so it logs info about the instrumentation (for example when it successfully registers with the scraper). logger can be a pino instance, or console` (default).