Logical-decoding Promethus Metric Reverse Proxy
A prebuilt docker container is hosted on Github Packages:
docker run -it -p 9998:9998 -v /reverse_exporter.yml:/config/reverse_exporter.yml ghcr.io/wrouesnel/reverse_exporterOr you can build your own:
docker build -t reverse_exporter .
docker run -p 9998:9998 -v /myconfig.yml:/config/reverse_exporter.ymlThis exporter is designed for appliance-like container environments where multiple Prometheus exporters should be presented as a single "instance" to a Prometheus server.
The reverse_exporter logically decodes its target exporters on each scrape, allowing them to be
presented as unique metrics to Prometheus. It appends a new field (enforced to be unique) of exporter_name
to each metric so name-colliding metrics from internal exporters can be differeniated (i.e. since most Prometheus
exporters export their own process information as a part of their metrics).
tl;dr It's how you get /metrics to work with a fat container.
- Combine and merge multiple exporters into a single
/metricsendpoint - Append and override metric labels on all reverse proxied metrics
- Support exposing metrics from static files on disk
- Support intelligent on-scrape dynamic metrics from scripts (multiple scrapes are queued to single script execution preventing overloading)
- Support periodic (cron-like) dynamic metrics from scripts
- TLS support.
- Authentication support via HTTP basic auth and/or TLS client-certificates.
Run docker-compose up in the root of the repository to build and start a
reverse_exporter combining the metrics of a Prometheus instance with a
node_exporter.
Browse to http://127.0.0.1:9998/metrics to view the results.
See example.config.yml for a config file including all parameters used in
some way.
To get started with the repository run go run mage.go autogen to configure
your repositories build hooks.
To build a binary for your current platform run go run mage.go binary