Email and Telegram alerts

An alert at three in the morning for a disruption that already fixed itself isn't caution, it's noise. And noise has a very specific effect: by the third time, that notification gets ignored, and so does the real one, the important one, that eventually shows up for real.

The logic behind the alerts

A disruption only becomes a real incident after a number of consecutive failed checks that you decide on, not at the first isolated hiccup. You can set quiet hours where minor alerts wait until morning while critical ones still get through, and a repeat cadence in case the problem sticks around, so you don't forget it's still there but also don't get bombarded every five minutes.

A concrete case

On your own, with no pointless wake-up calls

You run your own online shop, and you probably don't want to be woken up for a twenty-second timeout that resolved on its own before you'd even opened your eyes. Raise the confirmation threshold to just two or three consecutive failed checks and that kind of noise nearly disappears, leaving behind, almost always, an alert that genuinely deserves attention.

As a team, with the right escalation

If there's a team involved instead, the same logic scales up: you can choose whether an alert goes out by email, to a shared Telegram channel, or both, so whoever's on call knows without refreshing the dashboard out of habit every five minutes. A shared channel also doubles as an informal record: anyone joining later can scroll back and understand what happened without having to ask around.

Fewer notifications, the right ones

The goal isn't to alert as much as possible, it's to alert at the right moment, with the right information, to the right person. An alert system that's too generous ends up ignored just as much as one that's silent: the threshold makes the difference, not the channel.