Dht-prometheus NPM

DHT Prometheus

A bridge to scrape Prometheus metrics from self-registering services, all using direct, end-to-end encrypted peer-to-peer connections (not http).

Service discovery is done with a decentralised hash table (HyperDHT). This means that both this service and the clients it scrapes can live behind a firewall and need no reverse proy nor DNS entries.

An advantage is the small amount of configuration required. Clients register themselves with the DHT-Prometheus service, so no manual list of targets needs to be maintained. All a client needs to register itself, is the DHT-Prometheus service's public key, and a shared secret.

Deployment

DHT-Prometheus is meant to be deployed alongside Prometheus. It manages a single targets.json file referenced from the main prometheus configuration (See prometheus/prometheus.yml for an example).

The DHT-prometheus service fulfils two complementary roles:

It maintains a targets.json file with aliases to all services which Prometheus should scrape.
It provides an HTTP server which receives Prometheus requests and forwards them to the DHT-prom clients.

Run

Configuration is done through environment variables:

DHT_PROM_KEY_PAIR_SEED: 32-byte seed passed to HyperDHT.keyPair(), set as hex or z32. Set this to have a consistent public key (otherwise random, which is only useful for tests).
DHT_PROM_SHARED_SECRET: 32-byte secret key, set as hex or z32.
DHT_PROM_LOG_LEVEL: defaults to info
DHT_PROM_HTTP_PORT: port where the http server listens. Defaults to a random port.
DHT_PROM_HTTP_HOST: host where the http server listens. Defaults to 127.0.0.1

Docker

docker run --network host --env DHT_PROM_SHARED_SECRET=<A 64 character hex string> --mount type=bind,source=/etc/prometheus/config/prometheus-dht-targets,destination=/home/dht-prometheus/prometheus

The intent is for the prometheus service to read its config from a read-only bind mount to /etc/prometheus/config, and for its config file to reference ./prometheus-dht-targets/targets.json

Note: /etc/prometheus/config/prometheus-dht-targets should be writable by the container's user.

Note: --network=host is optional, but HyperDHT holepunching can struggle using the default bridge network, particularly for LAN and localhost connections.

CLI

Install:

npm i -g dht-prometheus

Run:

DHT_PROM_PROMETHEUS_TARGETS_LOC=path/to/prometheus/targets.json DHT_PROM_HTTP_PORT=30000 DHT_PROM_SHARED_SECRET=<A 64 character hex string> dht-prometheus