← back to overview
Log source went quiet (legacy)
? ? ? regime: resolving log_silence
labelwatch-host / labelwatch · 0 consecutive generations · since ?
Observed
Finding not found
Why this is not just a threshold alert
The service is up and the log transport is working, but no lines are arriving.
Why this matters
A log source that normally produces output has gone silent. Silence from a running service is itself a signal.
Next checks
log rotation service activity transport lag
new

Disk: 79.4% now, 79.4% 30 gens ago (stable) | Mem: 19.742975935491998 | CPU: 1.33

Pivots

All findings on this host · Transition history · Log observation history · Log exemplars (current)

SQL