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 29, 2025

Configuration

🏘️ Organization-Wide Alert Groups

🏘️ Organization-Wide Alert Groups

It’s important for on-call responders to be able to focus on investigating and escalating urgent alerts.

However, during a shift it’s challenging to stay focused when a responder is being flooded with alerts across many monitoring tools, usually alerting on the same issue. Alerts take longer to be investigated, escalations are delayed, and incidents aren’t created when they should, impacting your organization’s MTTA and MTTR.

Now, you can set your responders up for success by helping them cut through the noise and focus on investigating high-urgency alerts. Rootly’s Global Alert Groups allow you to define a single grouping rule for all of your teams and services once, ensuring that every responder across your organization can focus and drive faster incident response.

For example, you can define a single alert group that will group all incoming alerts across Rootly based on the team and payload of the alert.

What’s included?

With Rootly’s Global Alert Groups, you’re able to:

  1. Set conditions under which an Alert is eligible to be grouped together. For example, you can group alerts based on the service the alert is sent to, the team, or both.
  2. Create groups of alerts based on shared attributes. For example, alerts can be grouped together only if they’re sent to the same service, or if they’re sent to all services.
  3. Automatically group alerts together, allowing any status changes your responder makes on the initial alert to be updated on all the grouped alerts.

Use Rootly’s Global Alert Grouping feature to minimize alert fatigue with your responders, and drive faster incident response across your entire organization.

🌝 New & Improved

🆕 Rootly On-Call workflow action can now be configured to page out to multiple targets in a single run.

🆕 Added ability to sort schedules in Rootly alphabetically to help improve schedule management experience.

🆕 Added ability to sort Scheduled Maintenances for when they are scheduled for.

💅 Improved guidance flow for integrating into Slack Enterprise Grid.

🐛 Fixed Observers’ inability to see saved filter views on list of alerts and list of incidents pages.

🐛 Fixed intermittent issue with built-in retrospective steps not appearing as selectable options when adding a retrospective step.

🐛 Fixed issue with certain GitHub repositories not returned in repository dropdown menus.

Previous post
Previous post
You are viewing the latest post

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

Notion Projects Integration with Rootly

WhatsApp Integration

Manually Export Action Items to Ticketing Apps (Jira, Zendesk, Linear, and more)

Automated Dashboard Reports

GitHub Secret Scanning Partner

Request for Permission Upgrade

Rootly Joins AWS Marketplace

HashiCorp Vault Integration

Rootly Status Pages V2

Sub-Incidents

Rippling SSO Integration

View Who’s On-Call

Pause & Snooze Reminders

Postmortem Renamed to Retrospective

Sentry Integration

Merge Duplicate Incidents

Global Audit Log

Atlassian Data Center Integration for Jira and Confluence

Auto Create Incidents from Jira