Fight Alert Fatigue

output_TAyP7X

How to Win the Alert Fatigue Battle IT engineers and DevOps teams cannot help but experience alert fatigue when they receive after-hour alerts lacking context or relevance. Messages come in, for example, telling the engineer on-call that disk space is used up. Does this mean 60% used up or 100% used up? Or an after-hours message might come in alerting to a downed server. Which server? Did the back-up server come on-line as a result? The remedy then is to implement an IT alerting system that differentiates high priority alerts and allows for messaging with attachments. Lack of context can cause significant frustration among engineers as well as alert fatigue. Impact of Alert fatigue Companies shouldn’t downplay the impact of alert fatigue. There are also significant financial implications for companies if they have stressed out, unhappy, sleep deprived engineers. For example, engineers who are feeling the stress of alert fatigue are […] Read more »

7 Ways DevOps Can Avoid Alert Fatigue

7 ways to avoid alert fatigue

Being on-call doesn’t have to mean you’re always tired The introduction of monitoring into the DevOps world means alerts will occur 24/7. As such, there will be alert fatigue in DevOps. Monitoring needs alerts in order to be effective but the issue is that while our technology is 24/7, humans cannot work in a similar fashion. Clearly, 24/7 alerts need to be better calibrated with human physiological realities in order to avoid alert fatigue. The remedy then is to implement an IT alerting system that differentiates high priority alerts and allows for messaging with attachments. Alert fatigue in DevOps The traditional setup of IT and DevOps is such that email is the main form of relating issues such as deployment problems or server problems. If software fails to deploy correctly, an email goes to a designated engineer. Similarly, if a server experiences a power surge, an email is sent. Monitoring […] Read more »