DumbMonit
IntégrationsMétriques et journaux
Surveiller Grafana Loki avec DumbMonit
The log server itself: readiness, log lines it refuses and why, chunks that fail to reach storage, write-ahead log disk, request errors.
DocumentationSite officiel : Grafana Loki
Les descriptions des produits sont en anglais, comme dans le produit. Les libellés de la page suivent votre langue.
Ce que DumbMonit surveille
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.
Usage typique. Log server: readiness, refused lines, flush failures
Exemples
- Loki single binary
- Loki simple scalable
Comment il se connecte
Ce qu'il faut
- Username / passwordSent as HTTP basic authentication.
- Bearer tokenSent as "Authorization: Bearer …" on every request.
Aucun compte nécessaire.
Ports réseau à ouvrir
3100/TCPLoki HTTP API (default)
Étapes de mise en place: 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.
À savoir. 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.