# How do you catch a log source that quietly stopped sending before an audit does? — retained record

> Retained reddit record from reddit:sysadmin.

Canonical: https://highsignal.app/data/records/668f4a78f1ef9c76

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:sysadmin)  published 2026-10-09 12:23 ingested 2026-10-10 02:37

[original source ↗](https://www.reddit.com/r/sysadmin/comments/1x1jyn0/how_do_you_catch_a_log_source_that_quietly/)

## retained text



```
Hey all, how do you guys keep track of log sources going quiet? I was thinking about cases where the agent is still running and the host looks fine, but the collector hasnt received anything from it for days or weeks.

Another thing I've seen discussed is parsing issues after firmware updates. A field changes, the parser stops extracting it properly, and the events keep flowing through.

For those managing logs across lots of different devices, what checks do you use for this? Do you set up alerts based on each source's usual activity, watch for drops in log volume, or check whether important fields are still getting populated?

The tricky part seems to be accounting for devices that naturally go quiet overnight or only send events occasionally. Would be good to hear what approaches have worked well in larger environments
```



document fetched 2026-10-10 00:36 · canonical https://reddit.com/r/sysadmin/comments/1x1jyn0/how_do_you_catch_a_log_source_that_quietly
