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 20, 2022

Others

Manage Workflows via API, Terraform, and Pulumi

Manage Workflows via API, Terraform, and Pulumi

๐Ÿงฟ Manage Workflows via API, Terraform, & Pulumi

Rootly is the only enterprise-ready incident management platform that supports IaC via API, Terraform, and Pulumi.

Today, we are taking that one level further and enabling customers to manage workflows via API, Terraform, and Pulumi.

Workflows are at the heart of what makes Rootly able to be customized to encode each organizations individual incident processes.

Previously, managing these workflows (e.g. automatically create Jira ticket for on security board, invite infra team if SEV0, etc.) had to be done in our Web platform. This was manual and didn't align with how organizations were already leveraging IaC.

With the ability to now manage workflows through providers like Terraform, individual departments and teams can own workflow configuration without click-ops.

API

  • Docs with workflows support: here
  • Previous changelog release notes: here

Terraform

  • Docs with workflows support: here
  • Previous changelog release notes: here

Pulumi

  • Docs with workflows support: here
  • Previous changelog release notes: here


๐ŸŒ New & Improved

  • ๐Ÿ†• Scheduled maintenance can be created from Slack using /incident maintenance, previously only available on Web platform
  • ๐Ÿ†• Assigning action items to others easier in Slack by right clicking and selecting ๐Ÿ‘‰ assign a user/team
  • ๐Ÿ’… Improvements to make tasks associated with playbooks more robust
  • ๐Ÿ’… General refactoring on our data model and configurations that improves overall loading and saving speeds
  • ๐Ÿ’… Adding action items on Web platform no longer require a refresh to populate
  • ๐Ÿ› Fixed issue where filters on alerts were not working for environments and services
  • ๐Ÿ› Fixed issue where export to CSV and JSON did not specify the title of the custom field
  • ๐Ÿ› Fixed issue where updating the organization page rendered a 500 despite data always being saved
Previous post
Previous post
You are viewing the latestย post

โฒ๏ธ Acknowledge, Snooze, and Escalate Alerts

๐Ÿ”’ 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