Consolidate monitoring target stack
This commit is contained in:
@@ -1,5 +1,7 @@
|
||||
# Loki / Alloy
|
||||
|
||||
Status: abgeloester Altstand. Der zentrale Zielzustand ist `monitoring/` mit `monitoring-loki` und `monitoring-promtail`.
|
||||
|
||||
Internal logging stack for KalliLab CORE.
|
||||
|
||||
## Services
|
||||
@@ -7,6 +9,10 @@ Internal logging stack for KalliLab CORE.
|
||||
- `loki`: internal log store on `backend_net`, no Traefik route, `auth_enabled: false` because access is limited to internal Docker networking.
|
||||
- `alloy`: Docker log collector. It mounts `/var/run/docker.sock:ro` as a documented observability exception and forwards Docker container logs to Loki.
|
||||
|
||||
## Migration note
|
||||
|
||||
Do not run this stack in parallel with `monitoring/` unless you are deliberately comparing collectors during migration. After `monitoring-loki` and `monitoring-promtail` are live and Grafana can query logs, stop this Komodo stack and keep the files only as rollback reference.
|
||||
|
||||
## Host sync
|
||||
|
||||
Before first deploy, sync the checked-in config files to appdata:
|
||||
|
||||
Reference in New Issue
Block a user