DumbMonit

IntegraçõesMétricas e registos

Monitorizar Prometheus exporter com o 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.

DocumentaçãoSite oficial: Prometheus

As descrições estão em inglês, como no produto. Os rótulos da página seguem o seu idioma.

O que o DumbMonit vigia

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.

Utilização típica. Any exporter (node_exporter, windows_exporter, cAdvisor, blackbox…): every series stored, graphed and usable in rules

Exemplos

  • node_exporter
  • windows_exporter
  • cAdvisor
  • blackbox_exporter

Como se liga

O que precisa

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

Não é preciso nenhuma conta.

Portas de rede a abrir

  • 9100/TCPMetrics page (HTTP, default for node_exporter)
Passos de configuração: 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.

Atenção. Metrics pages are usually unauthenticated: filter the port so that only the DumbMonit host reaches it.