Product update
⏪ Rootly Rewind 2022 We are excited to wrap up the year with Rootly Rewind 2022. See how you performed by logging into Rootly.com. Available to all customers starting today. A few example statistics you can expect... Incidents with the most responders Estimated time saved from manual work Mon
Product update
💫 Trigger Workflow from Other Workflows Workflows in Rootly can be triggered a number of ways. Manually , API, alerts, or based on specific conditions. We are launching the ability to trigger workflows from other workflows. This provides granular control over exactly when specific workflows sho
Product update
🪡 Send Threaded Slack Messages via Workflows Incident channels can quickly grow noisy with messages as you collaborate on resolving incidents. To keep communications clean and focused , we are introducing the ability to send threaded Slack messages via workflows. By being able to pick the visib
Product update
✏️ Autocomplete for Incident Variables Incident variables has been one of the most popular ways to customize Rootly. We've made this easier by introducing our Incident Variable Explorer earlier in the year. Now we are launching the ability to autocomplete incident variables as you type with i
Action items
📚 Playbook Tasks We are excited to launch Playbook Tasks, a checklist of pre-populated tasks whenever an incident starts that matches a specific criteria (e.g. security, high severity, etc.). Consistency in incident response is everything. With playbook tasks, responders can work through a struc
Product update
🗂️ Workflow Groups and Folders Workflows sits at the heart of Rootly and allow companies to encode and automate their own unique incident management process into the tool. They can be created generically (e.g. creating incident channels , Zoom bridge), specific to teams, incident types, severity
Product update
🕹️ Optionally Create Incident Slack Channels Do all incidents deserve their own Slack channel for collaboration? Not necessarily. For example, incidents that have been previously resolved and are being backfilled , low severity incidents that don't require collaboration, etc. Previously, all inc
Product update
📄Backfill and Import Past Incidents Inevitably there will be incidents captured outside of Rootly , for example, an outage that lasted a few minutes that was automatically resolved due to self-healing that was in place. However, it is still important to track it for posterity . We are launching
Product update
🎓 Customizable Interactive Tutorials One of our largest investment areas is how we can help organizations drive better adoption of their incident management process. We are excited to launch our Interactive Tutorials that are customizable and designed to effectively teach users about Rootly an
Product update
🐛 Workflow Debugger We are excited to launch our Debug Workflows capability for all customers! If you've ever wondered why a workflow did not run and spent time debugging it, this is for you. This compares incident conditions against expected values against actual values and provides a pass or
Product update
🌾 Required, Default, and Customizable Fields We are introducing Form Fields that will allow you to customize what you capture whenever an incident is created, updated, mitigated, and resolved. Why? Incident response is unique across every organization and the data captured will vary dramatic
Integrations
⚡ Zapier Integration Rootly boasts the most extensible incident management platform with the most comprehensive 3rd party integration library, Open API , and capability to make external API via workflows. Today, we are excited to announce our integration with Zapier (5000+ no-code integrations
AI
🔧 Scheduled Maintenance Rootly serves as a single pane of glass for incidents and now scheduled maintenance events. A scheduled maintenance is a period of planned downtime communicated in advance. Like incidents, they share many of the same fields such as title, summary, service impact, and mo
AI
📥 Branded Emails and Custom SMTP Server As much as we love sending emails branded with Rootly (e.g. no-reply@rootly.com ), we think making it your own helps communication be even clearer. We are excited to launch the ability to integrate with your own SMTP server (e.g. alias@company.com ) and ha
On-call
We’ve built in gap finding functionality so that if you specify a schedule as needing 24/7 coverage, Rootly will auto-assign any gaps in coverage to the Schedule Owner, and notify them of the gap that was detected.
Product update
⛵ Incident Variable Explorer Since our launch of incident variables ( see changelog ), they have quickly become an integral part of Rootly. Customers leverage it today to build workflows, better automate communication, deep customization (e.g. rename incident title to Jira ticket number), and mo
Integrations
📡 Statuspage.io Integration - Component & Template Support We are excited to launch our Atlassian Statuspage.io integration with support for components and templates. Customers will be able to manage all communication updates to Statuspage without needing to leave Slack or fumble around with lo
Product update
🏖️ Sandbox Environments We are making testing your configurations, workflows, and integrations safer and easier with sandbox environments! A standalone instance of Rootly connected to a separate non-production Slack environment. An important consideration was ensuring you can seamlessly swit
Integrations
🍫 Rollbar Integration We are excited to announce our Rollbar integration, one of the world's most popular error tracking and notification software. For many of our customers, Rollbar is often detects errors related to incidents before anything else. Now with the Rollbar and Rootly integration,
Product update
📣 Beautiful Incident Timeline Pages We are excited to release beautiful incident timeline pages that can be easily shared across the organization . Why? Following along incidents can be noisy especially given the amount of collaboration required to debug the issue. Teams such as customer suppo
Product update
🧿 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 a
Metrics
📊 Customizable Incident Metrics We are excited to launch the industries most powerful reliability and incident insights . Previously, customers relied on a basic set of metrics that weren't editable. Now, customers can build beautiful custom dashboards and charts with data sliced the way they w
Integrations
📹 Microsoft Teams Integration We are excited to announce our video conferencing integration with Microsoft Teams. As we further our market leading position for enterprise readiness , organizations will now be able to collaborate over Teams for high bandwidth conversations as they tackle inciden
Integrations
🔑 Microsoft Azure AD (Active Directory) SSO Integration We are excited to be featured in the official Microsoft Azure AD application marketplace ! The vast majority of our customers leverage SSO and Rootly already, the most popular being Okta , Google, and Azure AD. With continued support for A
Integrations
🏟️ Backstage Integration - Service Catalog We are excited to announce our Backstage integration on the Backstage Plugin Marketplace . Backstage is a popular service catalog tool open sourced by Spotify and is used by companies such as Netflix, DoorDash, Hello Fresh, and 100's of others including
Integrations
🎟️ Linear Integration It's no secret that Rootly has a powerful integration with Linear and is leveraged by customers already. Today, we are formally launching in partnership with Linear on their integrations marketplace . Customers will be able to automatically create and track tickets such
Product update
🗄 Workflow Versioning Introducing Workflow Versioning, a detailed audit trail and history of all changes made to a given Workflow. Workflows are at the heart of Rootly. By making it easier to track changes made over time, teams will find Workflows even easier to manage and safely collaborate to
Product update
✍️ Incident Feedback Like organizations, your incident response process will evolve over time. We are making learning from incidents your superpower by closing the feedback loop. Excited to announce the ability to collect incident feedback and data on the incident process. This will help revea
Product update
⏲️ Retroactively Create Incidents and Modify Timestamps Declaring an incident the moment it actually starts may not always be possible. Sometimes we notice incidents hours or days later. This causes skewed timestamps that paint an inaccurate metrics picture . We are announcing the ability to ret
Product update
⚗️ Pulumi Provider for Rootly Hot on the heels of our API and Terraform provider, we are excited to launch our Pulumi provider! Support for Pulumi further helps Rootly build our lead for being the most developer friendly and Infrastructure as Code ready incident response platform. Pulumi
