❌

Normal view

At what point does monitoring become so noisy that engineers stop trusting it?

You add alerts because you want to catch problems early.

CPU spikes. Memory usage. Failed requests. Slow queries. Queue delays.

Eventually, the team starts receiving notifications throughout the day.

Some are important. Most aren't.

And that's when a dangerous habit develops: people start assuming the next alert probably doesn't matter either.

I'm curious how teams deal with this.

Have you ever deliberately removed a large number of alerts to make monitoring more useful?

How do you decide which alerts deserve to interrupt an engineer and which should just be visible on a dashboard?

submitted by /u/djgoel123 to r/devops
[link] [comments]
❌