Changelog

Auto Create Incidents from Any Alert

📟 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

Auto Create Incidents from Any Alert
On this page

📟 Auto Create Incidents from Any Alert

We are launching the ability to automatically create incidents from any alert source via Workflows.

Editor’s note: Atlassian is retiring Opsgenie, with end-of-life scheduled for April 2027—factor a migration path into any evaluation.

  • Monitoring tools - Datadog, Grafana, Nobl9, etc.
  • Paging and alerting tools - PagerDuty, Opsgenie, VictorOps, etc.
  • Ticketing and tracking tools - Zendesk, Asana, etc.

Customers can configure a Workflow to ingest specific alerts from various external tooling and set a task to automatically kick-off incidents, regardless of source. This will spin up an incident channel on Slack, invite responders, start a Zoom, and/or whatever was configured.

Why did we build this? Because incidents can stem from many different sources such as programmatically, human detected, and more.

Rootly is the single aggregation point for all types of incidents and that can be created and managed consistently every time.

What else shipped
  • 🆕 Design overhaul for timeline in Web platform to improve navigation and readability
  • 🆕 Auto-assign Reporters and Assignee to Jira tickets in Workflows, e.g. {{ incident.creator.email }}
  • 🆕 Automatically record to cloud or local for Zoom bridges created with Workflows
  • 🆕 Conditions in Workflows for set and unset (e.g. run Workflow A if Service is blank)
  • 💅 Ability to unsubscribe from status page updates
  • 💅 Datadog snapshots and dashboards posted into the incident channel by Rootly link back to Datadog
  • 💅 Running /incident list displays incident titles alongside their status
  • 💅 UI improvements to https://rootly.com/blog