Back to Changelog
Back to Changelog

November 19, 2024

On-Call

🚨 New Alert Sources: Checkly and New Relic

🚨 New Alert Sources: Checkly and New Relic

Since launching Alert Sources, we’ve been committed to expanding our integrations to seamlessly bring alerts from your favorite tools into Rootly. This week, we’re excited to introduce two new native alert sources designed to enhance your monitoring workflows:

Checkly: a monitoring platform built for developers, combining end-to-end browser checks with API monitoring to ensure your web apps and APIs are performing flawlessly. Integrating Checkly with Rootly means your team can immediately respond to issues as soon as they’re detected, keeping your services running smoothly.

New Relic: offers a powerful observability platform that unifies logs, metrics, and traces, providing deep insights into the health and performance of your applications. With Rootly integration, New Relic alerts flow directly into your incident management workflow, enabling faster detection, response, and resolution of issues.Once set up, any alert triggered in Checkly or New Relic will automatically create an alert in Rootly, ensuring incidents are captured and actioned without delay.

To set up any of these alert sources, head to On-Call > Alert Sources > + Add Alert Source and type in the tool you’re looking for. Each native Alert Source has in-app setup instructions so no need to hunt for documentation.

🌝 New & Improved

🆕 The same team can now be paged multiple times when escalating to Opsgneie. Opsgenie only allows the same team to be paged once per incident. This new feature will allow teams to bypass that restriction and re-page the same team for the same Rootly incident.

🆕 Teams can now see and track Partially Completed workflows. Previously, workflow runs were only shown as either Completed or Failed.

💅 Added informational text to warn users that on-call schedules synced to a calendar sync to a  frequency set in the user’s calendar app.

💅 Improved UI for item filters. Now selected values will be displayed at the top of the filter dropdown to inform users of the already-selected values.

🐛 Fixed sort logic on action items displayed in Slack to ensure they are displayed in the order in which they are created in.

🐛 Fixed issue with Mark as In Triage field auto unchecking itself when another field edited on a Dynamic Form.

Previous post
Previous post
You are viewing the latest post

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

Notion Projects Integration with Rootly

WhatsApp Integration

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

Automated Dashboard Reports