DumbMonit
IntegracionesMétricas y registros
Monitorizar Prometheus exporter con 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.
DocumentaciónSitio web oficial: Prometheus
Las descripciones están en inglés, como en el producto. Las etiquetas de la página siguen su idioma.
Qué vigila DumbMonit
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.
Uso habitual. Any exporter (node_exporter, windows_exporter, cAdvisor, blackbox…): every series stored, graphed and usable in rules
Ejemplos
- node_exporter
- windows_exporter
- cAdvisor
- blackbox_exporter
Cómo se conecta
Qué necesita
- Basic authFor an exporter behind basic authentication (web.config.file, or a reverse proxy).
- Bearer tokenSent as "Authorization: Bearer …" on every read.
No hace falta ninguna cuenta.
Puertos de red que abrir
9100/TCPMetrics page (HTTP, default for node_exporter)
Pasos de configuración: Point DumbMonit at the exporter
Check that the exporter answers from the DumbMonit host.
curl http://server.lan:9100/metricsIn DumbMonit, enter the host and pick the exporter, or leave custom and give the port.
Optional: restrict what is stored with Keep only or Ignore, to keep a large exporter within the series limit.
Optional: if the exporter is on another site, choose a relay agent to read it from there.
Ojo. Metrics pages are usually unauthenticated: filter the port so that only the DumbMonit host reaches it.