website logo
⌘K
Help and Documentation
Introduction to Rootly
Quick Start Guide
Managing Incidents
Manage Action Items
Managing Users
Managing Teams
Status Pages
Timeline
Postmortems
Playbooks
Workflows
Alerts
Pulses
Metrics
API Reference
Webhooks
Liquid
Contacting Support
Integrations
Overview
Slack
Mattermost
PagerDuty
Opsgenie
VictorOps (Splunk On-Call)
Service Now
Nobl9
Jira
Jira ( On premise )
Confluence
Confluence ( On premise )
Google Docs
Notion
Quip
Dropbox Paper
Asana
Linear
Freshservice
Trello
Shortcut ( formerly Clubhouse )
Statuspage.io
Airtable
Zendesk
Zoom
Webex
Microsoft Teams
GoToMeeting
Google Meet
Twitter
GitHub
Gitlab
AWS Elastic Beanstalk
Heroku
Kubernetes
Datadog
Honeycomb
Backstage
New Relic
Looker
Grafana
Email
SMTP
Sentry
Rollbar
Zapier
API
Terraform
Pulumi
SSO (Okta, Azure, Auth0, etc.)
SCIM
Docs powered by archbee 
6min

Managing Incidents



Overview

Incident management is at the heart of how Rootly works. This page will describe the different ways you can create, manage, and resolve incidents with Rootly.

Incidents can be in one of three states at any given time:

  • STARTED - This is the default status for when new incidents are created.
  • MITIGATED - The incident is ongoing but immediate customer impact has stopped.
  • RESOLVED - The incident is resolved and a long-term or permanent fix has been implemented.

There are four main ways to easily create or modify an incident within Rootly.

  • Via the Rootly web UI.
  • Via Slack.
  • Via third-party services such as PagerDuty, VictorOps, and Opsgenie.
  • Via the API.
Updated 07 Dec 2022
Did this page help you?
Yes
No
UP NEXT
Managing Incident Roles
Docs powered by archbee 
TABLE OF CONTENTS
Overview