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

July 13, 2023

Integrations

Rootly + Fivetran Data Connector Integration

Rootly + Fivetran Data Connector Integration

๐Ÿ”— Rootly + Fivetran Data Connector Integration

Incident data provides valuable insights into the health of your business. Rootly provides plenty of built-in, customizable metrics right in the web platform, but for organizations that want to dive even deeper into their data, we recommend using a data connector to pull your Rootly data right into your centralized data location.

The Fivetran Rootly connector is a fully managed data integration for delivering real-time, efficient data replication from Rootly to your destination of choice. The ELT connector extracts a deep level of data from the source, replicates and loads that data in your centralized data warehouse or data lake, represented in an easy-to-navigate schema, where your analysts can easily access and query it alongside the rest of your organization's critical information.

See this quick setup guide for instructions on how to set up this data connector.

๐ŸŒ New & Improved

๐Ÿ†• You can now use the Update a Google Doc task to update retrospective tasks and timelines in your own Google Doc templates
๐Ÿ†• Action items manually exported to Jira are now accessible directly from the Rootly web UI
๐Ÿ’… Optimized response time on Export to Ticketing feature for a better user experience
๐Ÿ’… Improved retrospective timelines by removing distracting events such as user joining a Slack channel
๐Ÿ’… Removed query text on snapshot graphs retrieved from New Relic for a cleaner display
๐Ÿ› Fixed issue with auto-adding two identical code snippets on the Send Slack Block task
๐Ÿ› Fixed issue with the Subject field not being able to be left empty on Update a Zendesk Ticket task

Previous post
Previous post
You are viewing the latestย post

๐Ÿ”’ Severity based incident permissions

๐Ÿค– AI Meeting Bot for Incident Bridges

๐Ÿ”„ Reordering Escalation Paths

๐Ÿ“ Alert Notes

๐Ÿšจ New Alert Sources: Checkly and New Relic

๐Ÿ”Š Configurable Alert Volume

๐Ÿ”” Notify Slack Channel of Shift Changes

๐Ÿ“ฆ Customizable Alert Description

๐Ÿคณ View Shifts, Create Overrides, and Escalate Alerts from Rootly Mobile

๐Ÿ˜… Alert Urgency

๐Ÿšจ New Alert Sources: Azure, CloudWatch, and Google Cloud

โ˜Ž๏ธ Live Call Routing

๐Ÿค‘ On-Call Pay Calculator

๐Ÿ’“ Heartbeats: Continuous System Monitoring

๐Ÿšจ Alert Grouping

๐Ÿค“ Smart Defaults for Google Meet & Zoom

๐Ÿงผ Redesigned Incident Announcement & Update Slack Blocks

๐Ÿ’… New Navigation Bar and Configuration UI

๐Ÿฅธ Sync On-Call Schedules with Slack User Groups

๐Ÿ•ต๏ธโ€โ™€๏ธ /rootly lookup: Find and Filter Recent Incidents in Slack

๐Ÿ‘ฏโ€โ™€๏ธ On-Call Shadowing

๐Ÿ”Œ Generic Webhook Alert Source

๐Ÿ”’ Lock Individual Workflows

๐Ÿฆโ€โฌ› Round Robin Escalation Policies

๐Ÿšจ Alert Sources