Well the thing is alerts are indeed for actionable events. For example many remote locations have an on-site battery backup, which would supply power in an eve

Well the thing is alerts are indeed for actionable events. 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!