DumbMonit

IntégrationsMétriques et journaux

Surveiller Prometheus exporter avec 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.

DocumentationSite officiel : Prometheus

Les descriptions des produits sont en anglais, comme dans le produit. Les libellés de la page suivent votre langue.

Ce que DumbMonit surveille

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.

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

Exemples

  • node_exporter
  • windows_exporter
  • cAdvisor
  • blackbox_exporter

Comment il se connecte

Ce qu'il faut

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

Aucun compte nécessaire.

Ports réseau à ouvrir

  • 9100/TCPMetrics page (HTTP, default for node_exporter)
Étapes de mise en place: 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.

À savoir. Metrics pages are usually unauthenticated: filter the port so that only the DumbMonit host reaches it.