Skip to main content

​
How Rootly Works

Rootly provides a comprehensive incident management platform that streamlines your response process through automated workflows and intelligent coordination. Here’s how Rootly enhances your incident response:
  1. Incident Detection: Rootly integrates with various observability applications such as Datadog, Grafana, Sentry, etc. to alert teams when any abnormalities or potential issues arise.
  2. Paging and Notification: Upon potential issue detection, Rootly notifies the relevant stakeholders through various communication channels such as Slack, email, or SMS.
  3. Incident Triage: Upon being alerted, the incident is triaged to assess its severity and impact on the organization’s operations. Rootly provides a centralized interface to empower team members to efficiently collaborate and gather information about the potential incident.
  4. Incident Response: Rootly facilitates incident response efforts by automating manual tasks, which helps remove the cognitive load during system outages.
  5. Collaboration and Communication: Throughout the incident resolution process, Rootly serves as a hub for collaboration and communication among team members. It enables real-time communication, file sharing, and status updates, ensuring everyone stays informed and aligned on the incident response efforts.
  6. Resolution and Post-Incident Analysis: Once the incident is resolved, Rootly facilitates post-incident analysis to document root causes, lessons learned, and areas for improvement.
  7. Incident Analytics: Rootly captures all relevant incident information and provides insightful metrics to help teams interpret their incident data.

​
Incident Properties

Every incident created on Rootly can be characterized with a set of data properties. These properties can either be built-in or custom. Incident properties play a key role during incident management as they can
  • help categorize each incident (e.g. type = security, customer-facing, backend, etc.)
  • be used as run conditions for automations (e.g. create incident retrospective when status = resolved, notify leadership if severity = SEV0)
  • be used to gain insightful incident analytics (e.g. plot graph breaking down incidents by their impacted service)
You can read more about these properties on the dedicated page here.