Incident management
Incident response connected to the services that failed.
SenalOps opens incidents from monitor failures, telemetry SLO burn alerts, and correlated service signals. Teams can route by service, team, and severity, suppress planned maintenance, assign incident command, acknowledge incidents, add responder notes, correlate deployments, resolve manually, and publish AI-assisted post-incident reviews with action items.
Routing and escalation
Primary and secondary channels, severity filters, delivery logs, and maintenance suppression.
Reviews and follow-through
Incident timelines, AI-assisted summaries, root cause drafts, action items, and published reviews.
Incident command
Severity, commander assignment, communications channel, acknowledgement, and response ownership in one record.
Change correlation
Verified GitHub webhooks connect deployments, releases, pushes, and workflow runs to nearby incidents.
The incident lifecycle in SenalOps
- Open: SenalOps detects a confirmed failure or reliability breach and opens an incident on the affected service.
- Acknowledged: a responder accepts ownership, which stops secondary escalation.
- Investigate: responders add notes, findings, mitigation steps, and decisions to the timeline.
- Resolved: the incident is resolved manually or closes automatically once recovery conditions are met.
- Review: the team publishes a post incident review with timeline, impact, root cause, and action items.
Context responders get in every incident
Each incident shows the affected service, linked monitors, current service health, dependency context for upstream causes and downstream impact, SLO burn and telemetry context, related incidents, and recent deployments from mapped GitHub repositories. Plain language summaries help the first responder triage quickly.
FAQ
Incident management questions
How does SenalOps handle incident response?
SenalOps opens service incidents from monitor failures, telemetry SLO breaches, and correlated signals. Incidents include event timelines, incident command fields, acknowledgements, notes, manual resolution, escalation routing, secondary escalation, maintenance suppression, delivery logs, deployment correlation, and AI-assisted post-incident reviews with action items.
How are alerts delivered?
Alerts can be delivered through email, Slack, webhooks, SMS, and WhatsApp depending on the plan and channel configuration. Routing policies can target services, teams, severities, primary channels, and secondary escalation delays.
What happens when a responder acknowledges an incident?
Acknowledging an incident records who owns the response and stops secondary escalation from treating the incident as unattended. Responders can then add notes, update severity and incident command, and resolve the incident once customer impact has ended.
How do maintenance windows affect alerts?
Maintenance windows suppress expected alert noise during planned work, so scheduled deploys and migrations do not page the on call team. Delivery logs still record what happened for later review.
How do AI assisted post incident reviews work?
SenalOps drafts a review from the incident timeline, dependency, SLO, deployment, and correlation evidence. The draft covers summary, impact, probable root cause, what went well, what could improve, and suggested action items. If AI is not configured, SenalOps writes an evidence based draft instead so the workflow still works.
Can SenalOps connect deployments to incidents?
Yes. Verified GitHub webhooks bring deployments, releases, pushes, and workflow runs into SenalOps. When a mapped repository changes near the start of an incident, that change appears in the incident context.