Get Rootly's Incident Communications Playbook

Don't let an incident catch you off guard - download our new Incident Comms Playbook for effective incident comms strategies!

By submitting this form, you agree to the Privacy Policy and Terms of Use and agree to sharing your information with Rootly and Google.

Back to Changelog
Back to Changelog

January 10, 2025

On-Call

⏲️ Acknowledge, Snooze, and Escalate Alerts

⏲️ Acknowledge, Snooze, and Escalate Alerts

Strengthen your incident response by helping your responders stay on top of open alerts with Rootly’s latest Alert Timeout, Snooze, and Escalate features.

Once a responder has acknowledged an alert, Rootly will snooze the alert while the responder investigates. After a period of time, Rootly will re-page the same responder, reminding them that the alert is still open and needs to be investigated.

Why it matters

How do you make sure a responder hasn’t fallen back asleep? In the middle of the night or during a busy day, alerts may be forgotten about and remain open when an urgent incident should’ve be spun up. By re-paging your responders:

  • You’ll have confidence that your team’s alerts are being evaluated and triaged by paging responders
  • Minimize stale alerts that should’ve resulted in an escalation, or an incident
When an alert is acknowledged by a responder, Rootly will re-page the responder based on the snooze timeout period.

With Rootly, never leave a critical alert open and without investigation again!

To get started, visit your Alerts page in your Rootly admin. Turn the ‘Retrigger acknowledged alert’ toggle on to begin re-paging responders after an alert is acknowledged.

🌝 New & Improved

🆕 Added the ability to schedule Google Calendar events to specific calendars.

🆕 Added API and Terraform support for enabling services and teams to allow email-triggered alerts.

💅 Added the ability to filter Rootly members list by Incident Response Role and On-Call Role.

💅 Page Rootly On-Call workflow action has been updated to allow quick simpler confirmation to page All Attached Services/Teams, Newly Attached Services/Teams, and First Attached Services/Teams.

🐛 Fixed display issue where 3rd party ad-ons (e.g. 1Password, Grammarly, etc.) partially blocking field inputs. 

🐛 Fixed incorrect display of error message on resource edit pages.

Previous post
Previous post
You are viewing the latest post

Incident Timeline Comments: Add Context and Move from Conversation to Action Seamlessly

Introducing: Rootly x ClickUp! Our New Integration for Seamless Collaboration and Task-Tracking

The New and Improved Home Dashboard

Guided Onboarding Flow for New Rootly Users

Fields List View and More UX Improvements for Forms & Form Fields

Bulk Actions for Incidents and Workflows

Share and Set Permissions for Rootly Metrics Dashboards

Bulk Edit Task and Follow-up Action Items

Create Fully Custom Slack Forms Using Our New Form Builder

Specify Public vs Internal Incident Titles on Your Rootly Status Pages

Integrate with Multiple Instances of Jira and Confluence

Auto map any user from PagerDuty and Jira to Rootly incidents with new user lookup

Customize Your Incident Overview Banner in Slack

Improved Confluence Retrospective Templates

Workflows Can Now Automatically Update Previously Posted Slack Messages

Automate Component Status Updates on Statuspage.io

Rootly Joins the Vendr+ Marketplace

Assign Multiple Users to the Same Incident Role

Incident Triage: Investigate Potential Incidents Faster

Rootly + Fivetran Data Connector Integration

Less Noise, More Flexibility: New Slack Notification & Emoji Options

SCIM Group Support: Access Control Made Easy at Enterprise Scale

Integrate With External Systems via HTTP Client

Custom Google Doc Permissions

Advanced Slack Customization via Slack Blocks