DumbMonit

IntegrationsMetrics and logs

Monitor Prometheus exporter with DumbMonit

Any exporter that serves Prometheus metrics (node_exporter, windows_exporter, cAdvisor, blackbox_exporter…): every series is stored and can be graphed and used in threshold alerts.

DocumentationOfficial website: Prometheus

Product descriptions are in English, as in the product. The page labels follow your language.

What DumbMonit watches

Any exporter that serves the Prometheus text format: node_exporter, windows_exporter, cAdvisor, blackbox_exporter, smartctl_exporter, a database exporter, or one you wrote. DumbMonit reads its /metrics page on every check and stores each series, so it shows up in the explorer and the graphs and can be used in threshold rules.

Typical use. Any exporter (node_exporter, windows_exporter, cAdvisor, blackbox…): every series stored, graphed and usable in rules

Examples

  • node_exporter
  • windows_exporter
  • cAdvisor
  • blackbox_exporter

How it connects

What you need

  • Basic authFor an exporter behind basic authentication (web.config.file, or a reverse proxy).
  • Bearer tokenSent as "Authorization: Bearer …" on every read.

No account needed.

Network ports to open

  • 9100/TCPMetrics page (HTTP, default for node_exporter)
Setup steps: Point DumbMonit at the exporter
  1. Check that the exporter answers from the DumbMonit host.

    curl http://server.lan:9100/metrics
  2. In DumbMonit, enter the host and pick the exporter, or leave custom and give the port.

  3. Optional: restrict what is stored with Keep only or Ignore, to keep a large exporter within the series limit.

  4. Optional: if the exporter is on another site, choose a relay agent to read it from there.

Heads-up. Metrics pages are usually unauthenticated: filter the port so that only the DumbMonit host reaches it.