Rootly

Rootly organizes incident management around Incidents. Incidents have severity, type, status, and sub-status. Playbooks and Workflows automate response; Dashboards show metrics. Post mortems and retrospectives track learnings.

Data Model

• Incidents — operational incidents; have severity, type, status, events, action items.
• Incident Types — categories (e.g., outage, security).
• Severities — impact levels.
• Sub Statuses — fine-grained status within an incident.
• Playbooks — runbooks for incident response.
• Workflows — automation with tasks; grouped by Workflow Groups.
• Services — systems monitored; link to incidents.
• Teams — on-call teams.
• Users — people; have roles, notification rules.
• Dashboards — panels with metrics.
• Status Pages — public incident status.
• Form Sets / Form Fields — custom data collection.
• Post Mortems — incident retrospectives.
• Roles, Permission Sets — access control.

Gotchas

• Incident-centric: Action items, events, and sub-statuses are child resources of an incident. Obtain incident_id first.