Product update
📆 Automatically Schedule Postmortem Reviews Reviewing and learning about your incidents in a blameless way is critical to improving your incident management program. We are making scheduling postmortem review meetings even easier via a new Workflow task . Supports Google Calendar Dynamical
Product update
📟 Auto Create Incidents from Any Alert We are launching the ability to automatically create incidents from any alert source via Workflows. Monitoring tools - Datadog, Grafana, Nobl9, etc. Paging and alerting tools - PagerDuty, Opsgenie, VictorOps, etc. Ticketing and tracking tools - Zen
Product update
🧪 Terraform Provider for Rootly We are excited to introduce our long- awaited Terraform provider making infrastructure as code effortless . Engineering teams can now manage Rootly directly in code making distributed ownership of their service ownership even easier. No more needing to clic
Product update
🪂 Get Support From Rootly in Slack We are making accessing Rootly support and engineering team even easier. We are waving goodbye to support portals , Zendesk, and other methods. Anyone from within Slack can run /incident support to file a ticket (report bug, get help, etc.) with Rootly. A
Product update
🔖 Bookmark Anything in Incident Slack Channel We are introducing a new Workflow that allows you to bookmark any link, integration, or resource to the incident Slack channel. Customers can now append the most critical information at the top of incident channels making it immediately accessibl
Product update
🧞 Convert Existing Channels to Rootly Incidents Rootly provides the most comprehensive suite of onboarding tools to help companies rapidly adopt better incident management. As with the introduction of any tool, you won't always remember to use Rootly for new incidents due to muscle memory.
Product update
🔍 Incident Previews The vast majority of customers have a global Slack #incident / #outages / #warroom channel. This is where all incidents get posted for broader visibility . At a quick glance, we are making it now even easier to know whether or not its important to various stakeholders.
Product update
🔐 Custom Role-Based Access Control (RBAC) Rootly is already the most secure and enterprise-ready incident management platform on the market by a margin. Today, we are taking that further by introducing role-based access control (RBAC) to our customers. Why? Not all incident data or access is
Product update
🔔 Subscribe to Incidents We are introducing the ability to subscribe to incidents because staying in the loop is critical. But different audiences want to be updated differently. A couple of examples. Impacted Engineers - want to know every message sent because the details matter Leade
Product update
📜 Workflow Templates We are excited to introduce Workflow Templates to help you get started with Rootly even faster . This is just one of the ways we continue to a) provide the most powerful defaults out of the box but b) still allow for flexibility and configurations. Customers run hundreds o
Product update
✂️ Incident Variables and Snippets Incident variables such as {{ incident.severity }} are a way to quickly contextualize your communication without manual input . We are excited to launch 100+ incident variables that span across Rootly and it's integrations (e.g. Jira, Google Doc, etc.)
Product update
📮 Invite Responders to Incidents via Slack Incidents are best tackled collaboratively and looping in the right responders fast is critical. We've found today not only is it a manually intensive task but knowing who should be included is frustrating. We are introducing a new Workflow Task to auto
Product update
🦷 Severity Descriptions What's the difference between a SEV0 and SEV1? Most organizations at best have this defined in an internal doc buried away. However, that is not much use when you're under pressure and need to quickly create an incident. We are introducing dynamic severity description
Product update
🥡 Reopening Incidents We've all been there. Sometimes we get ahead of ourselves and close an incident too early before it's been resolved. Today, we are excited to introduce the ability to reopen incidents and continue right where you left off without missing a beat . Features : Accessibl
Product update
🛡️SOC 2 Type II Certified We are ringing in 2022 with our SOC 2 Type II (2) certification! We continue to be committed to our own privacy, governance, and security as our first priority to protect our customers. How is this different from SOC 2 Type I? Although SOC 2 Type I has it's benefit
Product update
⚙️ Trigger Workflows Anytime We are excited to release the ability to manually trigger Workflows independently and at anytime ! Workflows are the best way to automate your incident response and process. However, they rely on incident conditions being met (e.g. Started, Severity, Team, etc.).
Product update
💨 Making Incident Creation a Breeze Whenever customers adopt Rootly, our name quickly becomes synonymous with the easiest way to create incidents . Today, we are making incident creation even easier by introducing a new slash command /incident on Slack. /incident will function exactly the
Workflows
🔮 Workflows 2.0 - Next Gen Incident Automation We are excited to introduce the next generation of our Workflows feature to help automate the entire incident process in a consistent way! What has changed since Workflows 1.0? Well, now all integrations are supported by our simple but powerful
Product update
🍫 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 document
Product update
🏭 Slack Enterprise Grid & Multi-Workspace Ready We are excited to announce Rootly is the only incident management platform that is Slack Enterprise Grid ready. Our support for Slack Enterprise Grid means organizations with multiple workspaces can unify how they manage incidents. What
Product update
⚡Quick Start Shortcuts We are introducing a faster way to get started with Rootly. Whenever you type /rootly and hit enter, we will populate the most popular shortcuts to help you get started. The command is context aware and will show different results depending on what channel you are i
Product update
🤫 Shhh, Keep It Private (Incidents) We are excited to release the ability to create incidents as Private. Common use cases are for security or other sensitive incidents that you may not want broadcast to the entire company. Whenever a Private incident is triggered, we create a private channel,
Product update
🤑 Measuring Incident Cost We are introducing the ability to quantify incident cost . Our customers are looking for a way at quick glance see the estimated and aggregate cost of incidents. Although there are numerous variables that contribute to this calculation, we are starting with estimated re
Product update
🌐 Saying Hello to Rootly.com Our Rootly.io domain served us well but its time for a little change. Many of our eagle eyed customers might have noticed we rebranded to Rootly.com over the weekend. It took us a bit to get this domain but we are officially swapping over. But don't worry. If you've
On-call
📟 Paging on Autopilot, Stop Wondering Who is On-Call Alerting solutions like PagerDuty and Opsgenie are an integral part of our customers workflow. We are making it even easier to page the right people whenever you are tackling an incident, without wondering who is on-call. We are introducing a
Integrations
We 💛 Google Docs Many of our customers currently use Google Docs to write their postmortems. They enjoy the tooling for it's superior collaboration, ease of use, and familiarity as usually their entire company runs on it. However, when it comes to writing postmortems, although they prefer Google Do
Product update
Hi 👋 - welcome to our first Changelog where we will share exciting Rootly product updates on a regular basis. Stay up-to-date by subscribing to our newsletter below! 💌 Sharing Rootly with your Team Whether you're a team of 20 or 20,000, we want to make it even easier to introduce / onboard
