Best Practices When Alerting On Issues

Check out the solution in the video Alerting Best Practices. We should consider the story of the Boy Who Cried Wolf: false alerts or annoying alerts train people to ignore them. The initial best practice for alerting is "do not create them" unless you must stop everything and solve the problem. However, if that means more than 100 alerts a day, you already have problems.

What's the first thing you think of when you get an alert? If it's not how to solve the issue, but whether the alert is noise or not noise, the problem is that you're training people to ignore the alert or to delay on the alert. Unfortunately, it's easy to email or text an alert and developers like the feeling of getting emails or alerts when they start, which ends up spamming people and training them to ignore the alerts.