The real cost of ignoring alerting

This is cheap to get right at the start and expensive to retrofit. Nobody bills you for neglecting alerting. The cost shows up somewhere else.

Cloud work rewards teams who automate early and punishes teams who click through consoles. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

Where the cost lands

• Time spent on work that should not have been necessary
• Enquiries that quietly never arrive
• An alert nobody acts on trains everyone to ignore alerts
• Rework, once the problem is finally visible

Page on symptoms customers feel, not on every anomaly. In practice this is a scheduling problem more than a technical one. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.

A reasonable first step

Every alert should link to what to do about it. In practice this is a scheduling problem more than a technical one. It rarely shows up as a line item, which is exactly why it slips.

In practice

The bill is a design document: it tells you exactly what your architecture actually does. Three things worth confirming about alerting before you move on:

• Someone can say what the current setup is without going to look
• An alert nobody acts on trains everyone to ignore alerts — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If any of that sounds like a description of your current setup, it is fixable.