Monitor VictoriaLogs with DumbMonit
The log database itself: lines ingested, lines it refuses, disk headroom before it turns read-only, errors.
DocumentationOfficial website: VictoriaLogs
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. Log database: ingestion, refused lines, disk headroom
Examples
- VictoriaLogs single-node
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 VictoriaLogs' own health
Nothing to install: check from the DumbMonit host that VictoriaLogs answers on its API port (9428 by default).
curl http://victorialogs.lan:9428/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 "victorialogs.lan" or "http://10.0.0.6:9428".
Heads-up. Free disk space is what to watch: below -storage.minFreeDiskSpaceBytes (10 MB by default) VictoriaLogs turns read-only and refuses every new log line. DumbMonit shows the headroom left and warns under 10%.