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

November 23, 2021

Others

API and Infrastructure as Code Ready

API and Infrastructure as Code Ready

๐Ÿซ API First and Infrastructure as Code Ready

Our API is now stable and using OpenAPI Specification. This will allow you to programmatically control the platform.

As an API-first company, everything you can do in the UI can be done via our REST APIs without clicking around. View our documentation here.

Now, integrate into existing Infrastructure as Code workflows or build new ones with Rootly.

The use cases are endless. For example:

  • Create new incidents automatically from internal tools alerting (e.g. SLOs)
  • Export and offload incident metrics to your BI tool of choice
  • Automate updating services and creating new teams

Have a custom use case or integration in mind with our API? Reach out to support@rootly.io or on Slack and we'll help you build it.


๐ŸŒ New & Improved

  • ๐Ÿ†• Ability to specify which fields are required and optional at incident creation time on Slack, previously was only optional by default
  • ๐Ÿ†• Pinning messages to incident timeline displays who sent the message instead of who pinned
  • ๐Ÿ†• Ability to sort and reorder Workflows, making it easier to stay organized
  • ๐Ÿ†• Redesigned our own Rootly internal admin to make it easier to support customers
  • ๐Ÿ†• Built internal tools to support wiping demo data easily for customers that are done testing and moving over to production
  • ๐Ÿ’… Cleaned up how selecting marking incident as Mitigated and Resolved looks in Slack
  • ๐Ÿ’… Incident timeline now displays system messages coming from Rootly instead of who created the incident
  • ๐Ÿ’… Link incident variables to new documentation, stay tuned for V2 where you'll no longer need to leave Rootly to browse
  • ๐Ÿ› Fixed issue where scheduled maintenance windows would occasionally display as an active incident in UI only
  • ๐Ÿ› Fixed issue where action items created in Rootly sometimes did not get created in Linear
  • ๐Ÿ› Fixed issue where Zoom room links were not getting attached to incident notification emails
  • ๐Ÿ› Fixed issue in Pulses (used for deploy tracking) would occasionally display duplicates
Previous post
Previous post
You are viewing the latestย post

๐Ÿšจ Alert Sources

๐Ÿ”” Configurable On-Call Shift Reminders

๐Ÿ“„ Dynamic Forms

๐Ÿ” Granular Role-Based Access Control Settings for On-Call

โœ‰๏ธ Emails as an On-Call Alert Source

๐Ÿ—“๏ธ View Multiple On-Call Schedules Together

๐Ÿค Partial Shift Overrides in Rootly On-Call

๐Ÿ—๏ธ Terraform + API Support for Rootly On-Call

๐Ÿฆ‰ Rootly x Thena Integration

๐ŸŽฌ New Full Platform Tour on Rootly.com

๐Ÿ”ฆ Drop-down Search in Escalation Policy Builder

๐ŸฆŠ GitLab Integration

Update Custom Incident Fields Using Workflows

๐Ÿค– Ask Rootly AI (+ More New AI Features!)

Rootly AI Editor: Fix Typos, Grammatical Errors, and Wordy Text Instantly

๐Ÿ“Š Dashboard Sharing Permissions

โœ๏ธ Customize Your Wordbank for Automatic Incident Title Generation

๐Ÿง  Smart Defaults for Jira

๐Ÿ”Œ The Rootly Plugin for Zendesk

๐Ÿช„ Rootly Retrospectives

โšก Command Palette: Lightning Fast Navigation with a Single Keyboard Command

Rootly Terraformer: Seamlessly Bring Workflows From Rootlyโ€™s UI to Terraform

Smart Defaults for Slack Configuration

Rootly Rewind: Celebrating 2023 With Our Amazing Customers!

Search and Filter Available Actions for Workflows