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 Rootly.com
  • 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 [email protected] 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 Rootly.com
  • πŸ› Fixed issue where severity name occasionally rendered the slug instead of display name


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