Keep It Private (Incidents)

🀫 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, silence notifications, and hide it in the Web Dashboard.

We give you a powerful suite of features to configure and control access. We also ensure Private and Public incidents can co-exist seamlessly.

  • Create Private incidents from Web or Slack
  • On a per incident basis, choose if you want to create incident as Private
  • Only Rootly admins can see or access on Web Dashboard
  • Spins up private incident channel on Slack
  • Notifications to your global #incidents channel are muted
  • Any Private incidents are tagged with πŸ”’ Private

In Action

🌝 New & Improved

  • πŸ†• New Task in Workflows that allows you to rename your incident channel on Slack
  • πŸ†• Use your Jira ticket number/slug as your incident channel title in Slack - syntax {{incident.jira_issue_url | split: "/" | last}}
  • πŸ†• New coat of paint on with detailed walk-through video
  • πŸ†• New Task in Workflows that allows you to change incident states (e.g. auto resolve incident if inactivity for 24hrs)
  • πŸ’… Zoom integration no longer relies on a user credentials to start the meeting
  • πŸ’… Beta features get an appropriate (beta) tag to give customers a heads up
  • πŸ’… Any time selector now includes UTC such as organizational timezone
  • πŸ’… Cleaned up Google Meet UI in Slack to reduce visual clutter
  • πŸ’… Auto resolve setting migrated out of organizational settings and into Workflows
  • πŸ› Fixed issue where duplicate title names could not be used for Workflow names
  • πŸ› Fixed issue where scheduled maintenance would incorrectly display warning message to resolve incident
  • πŸ› Fixed issue where auto archive Slack channels occasionally didn't work
  • πŸ› Fixed issue where Workflows occasionally did not repeat themselves
  • πŸ› Fixed issue where action items did not want to be created as Jira subtasks for some customers

Measuring Incident Cost

πŸ€‘ 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 revenue loss.

This will look at your average cost per minute multiplied by duration of the incident.

  • Enabled optionally in Organization Settings where you can configure variables
  • Displayed in both Metrics tab and on each individual incident in
  • Calculation can be based on time to mitigation and/or resolution
  • Shows aggregate view (e.g. average cost per month) and per incident basis
  • Export metrics out via CSV, JSON, API, or contact for custom export builds
  • Coming soon - time tracking and developer productivity costs, stay tuned!

In Action

🌝 New & Improved

  • πŸ†• If you import services via PagerDuty, we now run a daily sync to see if more were added, we also check for duplicates
  • πŸ†• Marking an incident on Rootly as resolved also are reflected in PagerDuty
  • πŸ†• Auto scrolling added to all pages such as services to make drag and drop easier
  • πŸ†• When starting to type /rootly the suggested text includes popular commands such as new, update, resolve, and help
  • πŸ’… Organizations with lots of spaces in Confluence now load faster when integrating for the first-time
  • πŸ’… We persist the user and remember who you selected last to make editing team memberships easier
  • πŸ’… Rebranding Genius Workflows to just Workflows to provide greater clarity around what it does
  • πŸ’… PagerDuty modal in Slack now better renders all users, especially for organizations that have hundreds to thousands
  • πŸ’… After running /rootly connect we now automatically redirect users back to Slack
  • πŸ’… Reduced visual clutter inside of Slack by removing unnecessary emojis (there is a thing as too much!)
  • πŸ’… Cleaned up how Google Docs is displayed in Slack
  • πŸ› Fixed issue where pinning events and messages to timeline were delayed
  • πŸ› Fixed typos a few typos inside of Slack and integrations
  • πŸ› Fixed issue in Confluence when changing the space key did not dynamically update list of pages
  • πŸ› Fixed issue where some icons were broken after the switch to
  • πŸ› Fixed issue where severity name occasionally rendered the slug instead of display name

Saying Hello to

🌐 Saying Hello to

Our domain served us well but its time for a little change. Many of our eagle eyed customers might have noticed we rebranded to 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 shared links internally and with your customers, they will continue to redirect.

Now that is out of the way, exciting and long awaited features below! πŸ‘‡

🌝 New & Improved

  • πŸ†• Ability to re-order any component (severity, service, role, etc.) inside of Rootly. Now you can display what comes up first!
  • πŸ†• Introduced a new events system for handling callbacks with third party integrations that dramatically improves reliability
  • πŸ†• Made clearer in Slack that if you have more than 2 roles that there are more to be assigned
  • πŸ’… Refactored Confluence and Google Doc to generate prettier docs by default
  • πŸ’… Pinning items to incident timeline are based on when the message occurred instead of when it was pinned
  • πŸ’… Create incidents on Web without needing to attach a severity, all fields are now optional similar to Slack
  • πŸ’… Organizations with over 500+ PagerDuty/Opsgenie users now load faster in Slack when needing to manually escalate
  • πŸ’… New /rootly tutorial guidance for updating the incident summary
  • πŸ’… Pinning long messages with line breaks to incident timeline are formatted appropriately instead of one long string
  • πŸ› Fixed issue where using Functionalities weren't triggering playbooks consistently
  • πŸ› Fixed issue where postmortems written in Rootly occassionally didn't save correctly
  • πŸ› Fixed issue where our Workflows weren't checking conditions were satisfied after incident was resolved

Paging on Autopilot, Stop Wondering Who is 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 new Task inside of our Automated Genius Workflow where you can automatically page people, team, or escalation policy depending on the condition of an incident. Some example use cases are page Infrastructure whenever a postgres-db incident occurs or page IMOC for every incident.

  • Works with any alerting solution such as PagerDuty and Opsgenie
  • Removes cognitive overhead and burden of wondering who to page during an incident as its automated
  • Easy to configure with drag and drop editor in seconds
  • No more wondering or fumbling with who has access to PagerDuty or Opsgenie logins

In Action

🌝 New & Improved

  • πŸ†• New configurations for incident creation module on Web that can now mirror Slack
  • πŸ†• All incident titles are assigned incremental numbers (e.g. #771) to more easily identify especially when duplicate sounding titles, similar to Jira
  • πŸ†• Ability to require users to connect their Slack accounts at sign up with new setting in Slack integration, no need for /rootly connect
  • πŸ†• Genius Workflow output in Slack is refactored to be less chatty to put more emphases on the output instead
  • πŸ’… Improved UI navigation to Integrations is more accessible
  • πŸ’… Added option to assign myself in top of roles drop down on Slack instead of searching for your own name
  • πŸ’… Updated welcome email template that better guides users to install Rootly and declare their first incident
  • πŸ’… Genius Workflow output on timeline is much cleaner looking
  • πŸ’… Better support rendering code snippets in incident timeline when pinned on Slack
  • πŸ› Fixed issue where status page timestamps were duplicated
  • πŸ› Fixed issue where sometimes Jira tickets were inconsistently created
  • πŸ› Fixed issue where some users experienced slower updates in the Slack overview message

We πŸ’› Google Docs

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 Docs, it's largely a manual process.

We are introducing our integration with Google Docs to automatically generate your postmortem after the incident is resolved. By enabling your Google Docs integration, Rootly will:

  • Create a Google Doc under you desired Drive folder
  • Populate the doc with a postmortem template as defined inside of Rootly (e.g. 5 whys)
  • Populate incident metadata (e.g. incident title, severity, services impacted, resolution time, etc.)
  • Generate incident timeline, no more copy-pasting from Slack!
  • Disable native Rootly Dashboard postmortem experience and instead point users to Google Docs

In Action

🌝 New & Improved

  • πŸ†• Added a brand new Resources tab on the Rootly website. Everything from the hottest SRE jobs to our incident management blog!
  • πŸ†• Added a Genius Workflow task for auto archiving incident Slack channels
  • πŸ†• Export your incidents as a CSV
  • πŸ†• Added copy to clipboard option for postmortem timeline and incident data
  • πŸ†• After incident is resolved, users are prompted to edit their postmortem more explicitly
  • πŸ’… Improved load times on Rootly Dashboard
  • πŸ’… Improved reliability of PagerDuty integration that includes multiple redundancies
  • πŸ’… Zoom, Google Meet, and other video conferencing options are globally turned on/off instead of per incident
  • πŸ› Fixed issue where you could not unassign a user from an incident role in Slack
  • πŸ› Fixed typos in /rootly tutorial guide and in the Rootly Dashboard
  • πŸ› Fixed bug where /rootly tutorial would not work for Slack users who had not linked their Rootly accounts yet
  • πŸ› Fixed duplicate tags for key:value pairs that would occasionally pop up

πŸ’Œ Sharing Rootly with your Team

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 your organization to Rootly based on a few guiding principles:

  • Reduce work needed to teach others of a new tool
  • Accelerate adoption via self-service
  • Customizable towards your organization

We are introducing a new Slack command /rootly tutorial that as the name states is a guided and interactive tutorial of Rootly.

  • Comprehensive - takes all users from account setup, creating incidents, and finding help
  • Accessible - command can be ran anywhere regardless if you have a Rootly account
  • Beautiful - thoughtfully designed to be delightful to use and interact with
  • Customizable - anywhere you want to provide additional context, we can link back to your internal docs on Confluence, Google Docs, etc.

In Action

Rootly Tutorial

🌝 New & Improved

  • πŸ†• This Changelog you are reading, thank you!
  • πŸ†• Support for additional incident milestones such as MTTA and MTTD.
  • πŸ†• Export incidents and metrics as CSV
  • πŸ†• Incident milestones (MTTA/D/M/R) and timeline in postmortems will reflect your local timezone
  • πŸ†• Supporting the ability to run Genius Workflows on a delay (e.g remind Slack channel to update postmortem 2 days incident is resolved)
  • πŸ’… We migrated our documentation to hosted by Archbee (YC S21) to make it easier to find what you need
  • πŸ’… You can decide what incident updates you want to broadcast to your global #incidents #war-room channels
  • πŸ’… Can multi-select incident conditions such as incident type, services, environments, etc.
  • πŸ› Fixed issue where the timer on Genius Workflows were slightly inaccurate
  • πŸ› Fixed issue where pinning Slack messages that contained a hyperlink didn't show up
  • πŸ› De-duplicate showing the same participant in incidents if the same user was assigned to multiple roles

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