Go to file
Dmitry Vasiliev 98d624f868
update cmd
2020-05-17 17:27:00 +03:00
.github/workflows try to fix 2020-05-17 16:51:42 +03:00
cmd kube friendly 2020-05-17 17:13:21 +03:00
merger update readme 2020-05-17 16:58:41 +03:00
.gitignore init 2020-05-17 16:30:52 +03:00
Dockerfile update cmd 2020-05-17 17:27:00 +03:00
example.yaml init 2020-05-17 16:30:52 +03:00
go.mod init 2020-05-17 16:30:52 +03:00
go.sum init 2020-05-17 16:30:52 +03:00
main.go fix build 2020-05-17 16:37:00 +03:00
README.md update cmd 2020-05-17 17:27:00 +03:00

prometheus-exporter-merger

Merges Prometheus metrics from multiple sources.

But Why?!

prometheus/prometheus#3756

To start the exporter:

prometheus-exporter-merger --config /config/prometheus-exporter-merger.yaml

Config example:

listen: :8080
scrap_timeout: 20s
sources:
  - url: http://127.0.0.1:8081/metrics
    labels:
      key1: value1
  - url: http://127.0.0.1:8082/metrics
    labels:
      key2: value2

Kubernetes

The prometheus-exporter-merger is supposed to run as a sidecar. By default, config must be available in the container by the path: /config/prometheus-exporter-merger.yaml.

...
  template:
    metadata:
      annotations:
        prometheus.io/scrape: "true"
        prometheus.io/port: "8080"
...
    spec:
      containers:
...
      - name: prometheus-exporter-merger
        image: vadv/prometheus-exporter-merger
        volumeMounts:
        - name: config
          mountPath: /config
...