Monitor VictoriaMetrics with DumbMonit
The time series database itself: ingestion, samples it refuses, disk headroom before it turns read-only, slow inserts and active series.
DocumentationOfficial website: VictoriaMetrics
Product descriptions are in English, as in the product. The page labels follow your language.
What DumbMonit watches
The time series database and the log database themselves: whether they accept what they are sent, how much disk is left before they stop accepting anything, and what they refuse.
Typical use. Time series database: ingestion, refused samples, disk headroom
Examples
- VictoriaMetrics single-node
- Prometheus long-term storage
How it connects
What you need
- Username / passwordSent as HTTP basic authentication.
- Bearer tokenSent as "Authorization: Bearer …" on every request.
No account needed.
Network ports to open
8428/TCPVictoriaMetrics HTTP API (default)9428/TCPVictoriaLogs HTTP API (default)
Setup steps: Let DumbMonit read VictoriaMetrics' own health
Nothing to install: check from the DumbMonit host that VictoriaMetrics answers on its API port (8428 by default).
curl http://victoriametrics.lan:8428/healthIf it runs with -httpAuth.username and -httpAuth.password, pick Username / password below; behind vmauth or a proxy that expects a bearer token, pick Bearer token.
In DumbMonit, enter the server address, for example "victoriametrics.lan" or "http://10.0.0.5:8428".
Heads-up. Free disk space is what to watch: below -storage.minFreeDiskSpaceBytes (100 MB by default) VictoriaMetrics turns read-only and refuses every new sample. DumbMonit shows the headroom left and warns under 10%.