DumbMonit

IntegrazioniDatabase e messaggistica

Monitorare InfluxDB con DumbMonit

The time series database: health and readiness, uptime, memory, file descriptors and server errors, for InfluxDB 2 and 3.

DocumentazioneSito ufficiale: InfluxDB

Le descrizioni sono in inglese, come nel prodotto. Le etichette della pagina seguono la tua lingua.

Cosa controlla DumbMonit

InfluxDB 2 and 3: health and readiness, uptime, memory, file descriptors and server errors.

Uso tipico. InfluxDB 2 and 3: health, readiness, uptime, memory, server errors

Esempi

  • InfluxDB 2.x
  • InfluxDB 3 Core
  • InfluxDB 3 Enterprise

Come si collega

Cosa serve

  • API tokenSent as a bearer token. InfluxDB 3 needs it on /health; InfluxDB 2 does not.

Nessun account necessario.

Porte di rete da aprire

  • 8086/TCPInfluxDB 2 API (default port)
  • 8181/TCPOnly for InfluxDB 3, whose default port is 8181
Passaggi di configurazione: Let DumbMonit read InfluxDB's health
  1. InfluxDB 2: nothing to create, /health, /ready and /metrics are open. Leave the credential on No authentication.

  2. InfluxDB 3 asks for a token on /health and /metrics by default: paste a token as API token, or start the server with --disable-authz health,ping,metrics.

  3. In DumbMonit, enter the server address, for example influx.lan, with the port 8086 for InfluxDB 2 or 8181 for InfluxDB 3.

  4. Tick HTTPS if the server, or the reverse proxy in front of it, serves TLS.

Attenzione. InfluxDB 3 answers 401 on /health without a token unless it runs with --disable-authz. The token is only used to read health and metrics.