😅 Alert Urgency

Rootly plugs seamlessly into your observability stack, allowing you to connect a huge variety of Alert Sources to push alerts to Rootly and automatically page responders and declare incidents, no matter where they originate. While all alerts give you important insights into your system health, not all alerts require the same urgency of response. This is why we’ve introduced Alert Urgency. Alert Urgency refers to the level of immediacy with which an alert needs to be addressed, based on the potential impact and severity of the underlying issue it represents.

Rootly comes configured with three default Alert Urgencies: Low, Medium and High.

You can edit the titles and descriptions of these urgencies, or delete and add your own. When you create or edit an Alert Source, you can specify rules regarding alert urgency based on conditions from the incoming payload — for example, the alert’s title. You can also set a default urgency level for alerts from that source.

Just like Alert Sources, you can also configure alert urgency rules for Heartbeats and Live Call Routing. 

Alert urgencies can trigger different escalation paths, different user-level notification rules, and can be used to track impact and trends over time.

For full instructions to set up alert urgencies and a video demo, check out our Help Docs! 

🌝 New & Improved

🆕 Checkly is now available as a native alert source.

🆕 Added the ability to surface a “Delete Message” button through the Send Slack Message workflow action.

💅 Live Call Routing now supports toll-free and local Australian numbers.

💅 Terraform provider now supports escalation_level as a resource

🐛 Fixed issue with incoming CloudWatch alerts displaying the incorrect initial status.

🐛 Fixed intermittent issue with mitigated incidents not displaying on web UI.

🐛 Fixed issue with default severity values not being set when creating new incidents.

‍