Request for Permission Upgrade

⬆️ Request for Permission Upgrade

We are excited to announce the ability for Rootly users to request missing user permissions directly in Slack!

For example, users that have an Observer or Read-Only role that are limited from performing certain actions can request those privileges in a streamlined way. Otherwise they would have to find out who the admins are, message them, and the admin would then go into Rootly to promote that Observer to an User. Sounds like a lot of work in the middle of an incident!

  • Streamlined and Secure Request/Approval Process: Users seeking elevated privileges no longer have to find out who the admins are and ask if they can get their permissions upgraded. Admins no longer have to figure out what level of access to grant while still maintaining least privilege access. Rootly will calculate the correct level of access required for the attempted action, identify all eligible approvers, and submit the exact request.

  • Guided Permission Prompt: Generic errors are unclear and give no directions on what to do next when a user has insufficient permissions. They leave users confused and frustrated. The new feature eliminates this confusing layer by prompting users exactly what to do next in order to gain access to the action they’re trying to perform.

  • Single-Channel Communication: Users no longer have to contact their Rootly admins in separate channels when requesting for permission upgrades. They can initiate the request directly from Slack and maintain a single channel of communication.

Rootly already delivers the most enterprise-ready RBAC features but this is one of many in a suite of enhancements to come!

🌝 New & Improved

🆕 Added CONTAINS NONE OF condition in workflows
💅 Workflows runs now redirect user to details page
💅 Streamlined status page event publishing to only ask for event title during initial publication and not updates
💅 Improved token management process to help reduce token expiration occurrences for integrations
🐛 Addressed inconsistent favicons on main status page versus incident history page
🐛 Corrected Slack user tagging logic to map to Slack ID instead of Slack Username
🐛 Fixed inability to publish sub-incidents via Slack

Rootly Joins AWS Marketplace

☁️ Rootly Joins AWS Marketplace

We're thrilled to announce that Rootly is now available on the AWS Marketplace, providing the fastest and most streamlined way to purchase our incident management platform. In an economy where we need to do more with less, we are making the purchasing process a superpower for customers!

  • Simplified Procurement: With a few simple clicks, customers can now purchase Rootly directly through their AWS account, eliminating the need for separate procurement processes, additional vendor negotiations, and now unlocks the ability to utilize already committed cloud spend. This streamlined approach saves time and effort, making it more convenient for customers to get started with Rootly.

  • Integrated Billing and Invoicing: AWS Marketplace provides integrated billing and invoicing, allowing customers to manage their Rootly subscription alongside their other AWS services. This consolidated billing process simplifies financial management, making it easier for customers to keep track of their expenses and ensure seamless payments and accurate accounting.

  • Increased Flexibility: Customers now have the options to either procure Rootly from AWS Marketplace or work directly with the Rootly team for a bespoke plan. This flexibility allows customers to select the most suitable purchasing option based on their requirements and budget.

  • Enhanced Trust and Security: AWS Marketplace is renowned for its strong security measures and compliance standards. By offering Rootly on AWS Marketplace, we are able to leverage the ironclad security infrastructure of AWS, providing customers with an added layer of trust and confidence.

If you're interested in simplifying your purchase of Rootly, head over to our AWS Marketplace list page or reach out for more information.

🌝 New & Improved

🆕 Ability to convert a normal incident into a sub-incident of another incident
🆕 {{ incident.previous_attributes }} liquid variable added to enable references to previous property values
💅 Added ability to set Skip on Failure and Enabled field in workflow tasks configured via Terraform
💅 Enhanced /incident statuspage Slack command to display confirmation message on successful publishes
🐛 Fixed inability to filter alerts when attaching them to an incident
🐛 Corrected wrong link to HashiCorp Vault installation docs on Integrations page

HashiCorp Vault Integration

🔐 HashiCorp Vault Integration

One of the driving principles behind Rootly is configurability. We strive to maximize our product’s ability to be customized to different incident response procedures. A popular feature that enables this is the ability to call third party APIs directly from Rootly. This workflow task empowers our users to integrate with applications that don’t already have a native Rootly integration in an automated fashion.

However, it's important to put security first here. Majority of API endpoints our customers are calling would require the use of API keys. Exposing the actual key values would not be aligned with best practices.

To combat this, we are excited to announce our integration with HashiCorp Vault as a Premier Partner on their marketplace. With this integration, customers using Vault as their secret management system can now leverage the secrets defined in Vault within their Rootly workflows.

Rather than passing the actual value of the secret in the request header, simply reference the secret value using liquid incident variables.

If you are already using Vault, a quick installation is all you need to begin using your Vault secrets in Rootly workflows!

If you are interested in bringing Vault into your incident management stack, check out HashiCorp’s partners page on Rootly!

🌝 New & Improved

🆕 Added the ability to disable a specific task within a workflow
🆕 View on-call command can now be used in general channels, not just incident channels
🆕 Messages sent with Send Slack Message workflow task can be better highlighted with custom colours to draw more attention (e.g. red for reminders)
💅 Enhanced search capability on Team Members page to enable quick search by role and not just users
🐛 Fixed inability to save Config Default Role field on Team Settings page
🐛 Corrected UI display of calendar picker

Rootly Status Pages V2

📯 Rootly Status Pages V2

We're excited to announce V2 of our wildly popular and native Rootly Status Page that is now more configurable and enterprise-ready.

The best way to get real-time updates on incident and system statuses. Organizations can proactively communicate to customers (or internally) to eliminate duplicate support requests, accurately display system health, showcase system reliability, and provide full transparency.

  • Fully synced service health status. Rootly will automatically mark any impacted service, as long as they are attached to a live incident. No longer need to manually update.
  • Show impacted 3rd party components. You can tap into 100s of third party components to display the status of mission-critical tools your service relies on like Twilio, Datadog, and AWS, etc.
  • Automate via workflows. Ability to auto-publish based on the status of the incident or any other conditions. Supports pre-templated messages and incident variables.
  • Public and Private pages. You might not want to use the same status page for your public audience (customers) as your internal leadership (employees). Now you don’t have to.
  • Fit your brand. Organizations can match their page to fit their look and feel via custom domains, header/footer colors, logos, etc.
  • Display your uptime. Uptime for each system component over a configurable amount of time can be displayed to show system reliability.
  • Integrates directly with Import existing templates and subscribers directly from your account. Can run both Rootly Status Pages and at the same time without conflicts.
  • Publish directly from Slack. With the intuitive /incident statuspage Slack command. From Web navigate to Incidents > Status Page Timeline to update.
  • Unlimited subscribers. Supports email, phone, and RSS notification methods.

Get started by navigating to Rootly > Configuration > Status Page. Live for all customers!

🌝 New & Improved

🆕 Auto Assign Role from On-Call Rotation workflow task can now be configured to assign on-calls based on PagerDuty services (previously only escalation policies)
🆕 Alert workflows now support Update Action Item task
💅 Enhanced shortcut emojis to accept the same emoji but in all skin tones
💅 Sub-incidents have been added to Rootly retrospective templates
🐛 Expanded selectable date range on incident filter to extend past one year
🐛 Fixed alerts retrieval error on Attach Alerts form field


🔀 Sub-Incidents

Large scale incidents often impact multiple product areas and teams to varying degrees. Being able to break the incident into different workstreams can often help make managing them easier.

We’re excited to introduce the ability to create sub-incidents from parent incidents. Should you ever find yourself tackling a complex incident that requires it to be broken into smaller pieces, simply use the /rootly sub command in the incident Slack channel to or the button under /incident overview to declare a sub-incident. Alternatively, you can also create a sub incident through the Web Platform.

Like their parent counterparts, sub-incidents are also supported in workflows. To trigger tasks for sub-incidents, set the kind condition field to Sub Incident and your workflow will only run when the incident in reference is a sub-incident.

Once created, sub-incidents can be handled just like a regular incident. You’ll be able to reference its properties via the same incident/liquid variables and report on them in metrics.

GA today for all customers! You can visit our docs to learn more about sub-incidents.

🌝 New & Improved

🆕 Create as User field in Create a Zoom Room workflow task now accepts incident/liquid variables
🆕 Retrospectives created in Google Docs, Confluence, Notion, and Dropbox can now be be marked as draft
💅 List Alerts API & List Pulses API has been enhanced to be queried by source
💅 Slack User field in Invite to Slack Channel workflow task now accepts user inputs
🐛 Corrected permission-check error for Slack commands
🐛 Fixed display issue on linked Jira ticket for backfilled incidents

Rippling SSO Integration

🔑 Rippling SSO Integration

We are excited to officially partner with Rippling and launch our SSO/SCIM integration on the Rippling App Shop.

You can now easily provision Rootly access to your employees from Rippling - saving your administrators from having to manually add each person.

Rootly Single-Sign-On (SSO)
Connect Rootly with Rippling via SAML, so your users can access Rootly without having to key in their email/password combinations.

Auto Create & Remove Accounts in Rootly
Connect Rootly with Rippling to automatically create and remove user accounts when you onboard and offboard employees.

Check out our SSO Integrations page to get started!

🌝 New & Improved

🆕 Ability to export incidents are now tied to Incident Read role permission in RBAC
💅 Enhanced Add Action Item task to be able to assign to a role
💅 Custom fields mapping are now supported on Zendesk integration
🐛 Fixed inability to auto-invite assigned user in Auto Assign Role from On-Call Rotation workflow task
🐛 Corrected Firefox display error on datepickers
📝 Updated Zendesk integration doc to show required permissions

View Who’s On-Call

📞 View Who's On-Call

Knowing who is on-call is helpful beyond just paging someone during an incident. It's useful for knowing who to hand-off to, who you can ping on a team for potential issues, and more.

But today there is a tedious process involved on how you'd figure that out.

  1. Navigate out of Slack
  2. Digging up your login for your paging solution
  3. Determining which service or policy you want to check
  4. Locate the person assigned to the specific time slot
  5. Navigate back to Slack
  6. Find person and contact them

Not exactly the most efficient process...

With the new Who's On-Call feature, Rootly will fetch and display your PagerDuty, Opsgenie, or VictorOps on-call schedules, without you having to leave Slack!

Just key in the /incident oncall command, in or outside of an incident channel, and select a Service or Schedule to check. Rootly will also present you with the on-call user at each escalation level.

Users have the ability to directly escalate from there without leaving the modal. Available to all customers starting today!

🌝 New & Improved

🆕 Introduced new endpoint to delete a user via API
🆕 Out-of-box form field names can now be set to custom values
💅 Expanded incident search logic to search beyond incident title
💅 Enhanced global audit log to includes export events
🐛 Add Action Item workflow task can correctly accept incident / liquid variables
🐛 Filtering capability on Incidents page have been fixed to return all matches

Pause & Snooze Reminders

💤 Pause & Snooze Reminders

Alert fatigue is real! Teams set up reminders with the best of intentions - to ensure nothing slips through the cracks. However, too much notification can cause unintended distractions for response teams.

To help teams reduce unwanted interruptions, we introduced the ability to pause and snooze reminder workflows. Now, teams can quiet down the reminders with just a few clicks directly from Slack. No more need to disable/re-enable workflows - which can be tedious and error prone.

If you want a reminder to go on break for the next 2 hours, simply hit the Snooze button and set the duration to 2 hours.

If you want to halt the reminder indefinitely, a single click of the Pause button will keep it quiet until you choose to restart it.

To get started, customers can leverage a new workflow task called Send Slack Reminder or modify their existing Send Slack Message task with the new actions.

Checkout this short video to learn about how to pause and snooze reminders!

🌝 New & Improved

🆕 Position parameter introduced as a team attribute in Terraform to enable customizable list order
🆕 Enabled dependency linkage between Asana tasks in different projects
💅 When creating new incidents, private incidents are no longer suggested as related incidents
💅 Updated List Incidents API to be able to filter by last updated_at time
💅 Enhanced Trigger Workflow task to only run if conditions of the ensuing workflow are met
🐛 Corrected run logic on workflows with inactivity conditions
🐛 Fixed issue with header fields incorrectly populating in Notion

Postmortem Renamed to Retrospective

💀 Postmortem Renamed to Retrospective

The term postmortem comes with the unwanted negative connotation of death and implies a single root cause. At Rootly, we don’t view each resolved incident as dead, but rather as an opportunity to learn and continuously improve.

To better align this approach, we’ve decided to rebrand Postmortem to Retrospective.

Traditionally, postmortems were conducted following major incidents, with the focus on identifying root-causes and how to avoid future occurrences. That’s a great start, however, we believe it would be even better to expand the coverage to all incidents and include discussions on what went well, what didn't go well, contributing factors, and what might we do differently next time.

You will find references to postmortems change to retrospectives within your Rootly app. However, all existing configurations remain the same!

If you’d like to learn more about best practices around retrospectives, please reach out to your Rootly team on Slack!

🌝 New & Improved

🆕 Workflow now supports conditions for specific Incident Roles
💅 Rootly API keys are now prefixed with rootly_ to improve key management
💅 Added pin to channel option to Send Slack Message / Send Slack Blocks workflow task to enable auto-pinning
💅 Timeline now shows the previous severity when a change in severity occurs
🐛 Default role on New Invitation page now matches value set in Team Settings page

Sentry Integration

📈 Sentry Integration

Issues can arise anytime and anywhere. A reliable monitoring system paired with an efficient incident management platform is key in keeping your application running smoothly. We are excited to announce our partnership with our friends at Sentry!

Sentry is a developer-first monitoring platform, designed to provide valuable insights to help fastrack your effort in identifying the issue root-cause.

WIth Sentry integrated, you’ll be able to receive Sentry alerts in Rootly and create incidents off of them - ensuring a prompt and efficient incident declaration process.

  • Ingest alerts created by Sentry into Rootly (Web or Slack) with all relevant metadata
  • Triage Sentry alerts in Rootly and create an incident with human in the loop
  • Automatically create incidents in Rootly is Sentry alerts exceed a defined threshold

If you already use Sentry, all that’s left to do is installing it in Rootly to get started.

See why Rootly was featured as the integration of the month on the Sentry integration marketplace:

🌝 New & Improved

🆕 Introduced Audit Log API to programmatically retrieve global audit log
💅 Enabled the use of Datadog templates for auto creating notebooks in Datadog
🐛 Restored guidance text when selecting Severities in Slack
🐛 Fixed 404-error on Fetch Gitlab Commits workflow task
🐛 Fixed 500-error on Incident Variable Explorer page

Rootly helps you respond to incidents faster as a team and learn to prevent them in the future.