If you're getting alerts for non-actionable events, you need to do a better job of tuning your monitors and alerts.
Alerts shouldn't be sent about anything that doesn't require an action.
Alerts shouldn't be sent about anything that doesn't require an action.
For example many remote locations have an on-site battery backup, which would supply power in an event of loosing commercial power. Those are actioned in terms of notifying field teams and deciding whether a specific location needs to be placed on a generator.
Imagine a hurricane disrupted commercial power grid and there are thousands of “site on battery” alerts; somewhere among them there is also an alert for OSPF down between two core switches.
Having a monitor with a large red warning saying “Link X at location Y is down!” - is a pretty effective way to not miss important notifications.
I mean playing devil’s advocate one might say “Then your alerts should have better filtering system with the important ones staying at the top of the page”... which is true. A lot of smart design features can render dashboards less relevant - however when there aren’t enough resources in a DevOps team to implement those solutions, a simple dashboard can go a long way!
In an ideal world, I agree. But sometimes an automated system can not perfeclty decide about the severity of an alert which leads to some alerts being ignofed, which is fine.
Alert fatigue is a big problem in the sysadmin/devops world.
I will have a look at the tool and have a play - I assume you can have multiple pages :-)
Would be cool to monitor the looks at GA " 1 2 3 4 5 …. Many" sites I have an interest in