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

Merge Duplicate Incidents

πŸ‘― Merge Duplicate Incidents

At Rootly, we advocate for everyone in the organization to be able to pull the fire alarm and declare incidents, not just engineers.

With everyone working concurrently and declaring incidents, its not uncommon to run into duplicate entries. Especially when the incident has a broad surface area of impact.

To help response teams reduce noise and effectively manage incidents, we are excited to introduce the ability to mark incidents as duplicates via the Web Platform or Slack (/incident duplicate).

Organizations no longer have to tiptoe around incident creation.

Marking duplicates during or after incident creation will also have downstream benefits - as the same issue will not be double-counted, resulting in more accurate metrics!

🌝 New & Improved

πŸ†• Introduced the ability to reference templates in workflow publish to status page tasks
πŸ’… Improved UX by pre-populating incident creation fields when incident is created from an alert
πŸ› Fixed Opsgenie escalation priority order
πŸ› Addressed issue with displaying incorrect resolution times in Slack
πŸ› Resolved inability to apply field positions in Terraform
πŸ› Corrected URL in private status page subscription email

Global Audit Log

πŸ“ Global Audit Log

Part of being enterprise-ready is enabling organizations with the ability to track changes made to their accounts.

We’re excited to introduce audit logging capabilities to Rootly!

No more guessing β€œhmm…when was this change made?” or asking β€œwho changed this?”. Now, you will be able to identify each update made to your account - along with meaningful details such as: author, changed content, time of change, etc.

🌝 New & Improved

πŸ†• Secret API keys can now be stored and used in HTTP Client workflows
πŸ†• Ability to extend a workflow by skipping a failed tasks
πŸ’… Multi-orgs can now provision each org from separate SSOs
πŸ’… More meaningful error messages to improve debugging experience in Slack
πŸ› Corrected elapsed time calculation on incident dashboards
πŸ› Reopening resolved incidents are now logged in the incident timeline

Atlassian Data Center Integration for Jira and Confluence

🏒 Atlassian Data Center Integration for Jira and Confluence

Also known as on-premise, server, or data center, customers using the self-hosted version of Atlassian can integrate Rootly directly with Jira and Confluence.

Maintain the security and control you need with self-hosted options but still be able to manage your action items (Jira) and write postmortems (Confluence) while leveraging Rootly. No compromises for enterprises or organizations with strict regulatory requirements.

Quickly get started by whitelisting Rootly IPs to enable access to your instance. Docs for Jira and Confluence.

🌝 New & Improved

πŸ†• API to allow programmatic retrieval of Users
πŸ’… Ability to attach action items and additional attributes to playbooks via Terraform
πŸ’… Removed β€œare you sure” pop-up on incident mitigation and resolution UI on Web
πŸ› Fixed issue where filtering by custom field in metrics charts weren’t working
πŸ› Fixed issue where updating playbooks were occasionally blocked by Cloudflare for some users
πŸ› Fixed issue where PDFs generated from metrics were empty files

Auto Create Incidents from Jira

🎟 Auto Create Incidents from Jira

We’re excited to announce that you can automatically declare incidents from Jira tickets.

Automatic Jira ticket creation has been one of the most heavily used workflows on Rootly. However, not all incident response operations run on the same procedures. Some teams might have existing processes that require issues to be reported directly in Jira first, but would still like to leverage Rootly to automatically spin up the necessary incident response process.

Teams can now listen for Jira events and decide to either programmatically declare incidents or manually triage them first, before kicking one off.

Getting started tutorial.

🌝 New & Improved

πŸ†• Ability to associate Rootly Services to PagerDuty Services to setup dynamic paging
πŸ†• Postmortem template and timeline in Notion is now cleaner, easier to read, and leverages native Notion elements
πŸ’… Incidents can now be filtered by kind
πŸ’… Workflows now supports IS SET, IS UNSET conditions
πŸ› Fixed issue where status page incident timeline ordering was not displaying in reverse chronological order

Sleuth Integration

πŸ”­ Sleuth Integration

We are excited to partner with our friends at Sleuth to formally launch our joint integration!. Sleuth's Engineering Efficiency platform provides a complete and accurate view into DORA metrics, visibility into bottlenecks, and tools to automate workflows.

When failures occur, Sleuth’s native Rootly integration enables development teams to respond quickly and effectively. By viewing incidents through Sleuth’s deploy-centric lens, developers can immediately pinpoint which specific changes caused those incidents so they can act quickly to resolve them (e.g. by rolling back, deploying a hot fix, etc.). With this integration, customers can:

  • Configure one or more Rootly integrations, each with its own unique set of incident filter criteria, and map those integrations to specific projects in Sleuth, allowing teams to cut through the noise and zero in on the incidents that matter to them.
  • View in real-time how incidents are impacting change failure rate and mean time to recovery metrics for specific projects and teams.
  • Remediate incidents quickly and effectively to deliver the best possible experience to their customers and stakeholders

🎀 Dylan Etkin, CEO, Sleuth

β€œIn our continuous effort to meet customers where they are, we’re excited to provide this native integration with Rootly that allows engineering teams to understand in realtime how incidents are impacting two of their key DORA stability metrics: change failure rate and mean time to recovery. With this exciting new addition to our rich library of integrations spanning issue trackers, code repos, CI/CD platforms, and observability tools, we’re even better able to provide our customers with a 360-degree view of their development workflow and opportunities to improve it.”

🌝 New & Improved

πŸ†• Ability to re-escalate to additional PagerDuty services even if previously paged a different one
πŸ†• Shiny new G2 badges on for Winter 2023
πŸ’… Zapier directly embedded into Rootly > Integrations
πŸ’… security section updated with additional enterprise-readiness details
πŸ’… CSV export will be emailed directly to that of the requester
πŸ’… PagerDuty tokens are automatically refreshed, removing the need to ever reintegrate
πŸ’… Improved error messaging if using /incident convert to turn existing channels into Rootly incidents were to fail
πŸ’… Countless infrastructure improvements primarily focused around Slack
πŸ› Fixed issue where action items on the Web Platform had unnecessary labels
πŸ› Fixed issue where Pulses were timing out due to large payloads

Multi-Organization and Workspace Support

🏘 Multi-Organization and Workspace Support

We are excited to launch the ability to have multiple organizations and workspaces of Rootly under the same roof and license.

Why? Companies and enterprises are not one dimensional in their needs. They are comprised of multiple departments, sibling organizations, acquisitions, and all of whom might have wide ranging requirements when it comes to how incidents are managed.

By having separate workspaces, organizations, and instances of Rootly, this unlocks the ability to not step on each others toes. For example, the NOC department will likely handle incidents differently from the rest of the company. The sister company that was acquired that will remain separate from the parent org has different tools they'd like to use. The SRE team that has a sandbox environment to experiment with new processes before rolling to production.

Use the same Slack workspace across all of your Rootly organizations! Upon incident creation, users will be asked to select which organization they would like to create their incident in (see header image).

Regardless of your organizational complexity, the UX for responders is simple and intuitive.

  • Be part of and switch between multiple organizations within the Web Platform without needing to logout
  • Support for multiple domains
  • Plug in the same or different integrations as needed (e.g. company uses the same Jira but different PagerDuty accounts)
  • User and usage is counted towards a single license

Existing users - to setup a new organization, contact your account team via Slack or Once enabled, on the Web Platform > Profile > Switch Organization. The ability to switch organizations on Slack will appear after you've integrated the same Slack workspace across multiple Rootly organizations automatically.

🌝 New & Improved

πŸ†• API endpoints to mark the incident as started, mitigated, resolved, and canceled
πŸ†• Default postmortem timeline is in chronological order and incident timeline is in reverse chronological order (most recent first)
πŸ’… Infrastructure improvements to how we handle webhooks
πŸ’… Significant infrastructure improvements around increasing test coverage
πŸ’… Incidents deleted by accident can be recovered by requesting to or in your teams shared Slack channel with Rootly
πŸ› Fixed issue where form fields where not being respected on the Web Platform when disabled
πŸ› Fixed issue where some Slack redirect links were incorrect

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