DumbMonit
Monitor Grafana Loki with DumbMonit
The log server itself: readiness, log lines it refuses and why, chunks that fail to reach storage, write-ahead log disk, request errors.
DocumentationOfficial website: Grafana Loki
Product descriptions are in English, as in the product. The page labels follow your language.
What DumbMonit watches
The log server itself: whether it is ready, which log lines it refuses and why, whether its chunks reach storage, and whether its write-ahead log still has disk.
Typical use. Log server: readiness, refused lines, flush failures
Examples
- Loki single binary
- Loki simple scalable
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
3100/TCPLoki HTTP API (default)
Setup steps: Let DumbMonit read Loki's own health
Nothing to install: check from the DumbMonit host that Loki answers on its HTTP port (3100 by default).
curl http://loki.lan:3100/readyLoki has no login of its own: only if a reverse proxy in front asks for one, pick Username / password (or Bearer token) below.
In DumbMonit, enter Loki's address, for example "loki.lan" or "https://logs.lan/loki" behind a reverse proxy.
With Loki split into components (simple scalable or microservices), add at least the write path.
Heads-up. Refused lines are the failure to watch: when Loki refuses a line (too old, over a rate or stream limit, too long), the sender usually drops the batch and Grafana only shows a gap in the logs.