Files
infrastructure/llm-server/monitoring
spektr 888c1a294c GNMON-001 M3.5+M3.6: Log-Browser, Alerts-Ansicht, Alloy-Journal-Pipeline repariert
Logs-Seite mit Quelle-Filter, Zeilen-Suche und Live-Tail (3-s-Takt);
Alerts-Seite listet aktive Alerts mit Severity-Farben. Neue Clients:
LokiClient (query_range, Label-Values) und AlertmanagerClient (v2).
Journal-Pipeline: der dokumentierte relabel_rules-Handoff am
loki.source.journal uebertraeg __journal_* in v1.21.3/User-Scope nicht
in stabile Labels (verifiziert); Ersatz format_as_json +
loki.process (stage.json/labels/output) extrahiert unit, user_unit,
syslog_identifier, priority deterministisch. Expliziter Journal-Pfad
notwendig (User-Scope oeffnet sonst nur das User-Journal), als
Inventory-Variable parametrisiert. Fünf Befunde in GNMON-000.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
2026-11-04 17:47:37 +01:00
..

Monitoring workload

Host-wide monitoring on ghostnet-ki: system metrics (CPU, RAM, disk, GPU utilization, VRAM) collected by a host-side metrics collector and visualised by a dashboard container. The workload is separated from the encoding and LLM workloads; the dashboard currently shows the encoding pipeline and is extensible to LLM metrics.

Architecture and decisions are documented under ../../docs/platform/llm-server/monitoring/. The executable Ansible control project under ansible/ entsteht mit der Implementierung.