I have a tool that I wrote, probably 5+ years ago. Runs once a week, collects data from a public API, translates it into files usable by the asterisk phone server.

I totally forgot about it. Checked. Yep, up to date files created, all seem in the right format.

Sometimes things just keep working.

[–] RustyNova@lemmy.world 52 points 2 months ago (10 children)

Meanwhile, had to debug a script that zipped a zip recursively, with the new data appended. The server had barely enough storage left, as the zip took almost 200GB (the data is only 3GB). I looked at the logs, last successful run: 2019

[–] adavis@lemmy.world 2 points 2 months ago (1 children)

Need some monitoring!

[–] RustyNova@lemmy.world 14 points 2 months ago (1 children)

Oh no need. The client didn't noticed anything in 6 years, and the reason why we had to check is because they wanted us to see if we could add this feature... That already existed.

[–] elvith@feddit.org 8 points 2 months ago (1 children)

My favorite part is, if you do some extensive analytics from time to time (e.g. to prepare an upgrade to a new major version) and as a side effect stumble upon some workflows/pipelines/scripts constantly failing (and alerting the process owner) every five minutes for... at least a few months already.

Then you go and ask the process owner and they're just like "yeah, we were annoyed by the constant error notification mails, so we mad a filter that auto deletes them"...

[–] greybeard@feddit.online 1 points 2 months ago

I feel like half my job is trying to stop false positives and other noise from hitting important places. Because false positives kill any chance true positives will be noticed/reacted to/processed.

load more comments (8 replies)

load more comments (12 replies)