Incidents

An incident is an unplanned event that disrupts normal operations and requires an organized response. In Batida, incidents are the central unit of your incident management workflow -- they track everything from initial detection to final resolution.

Why incident management matters

Without a structured process, teams waste time figuring out who is in charge, what is happening, and what to do next. Batida gives you a single place to declare incidents, assign ownership, track progress, and learn from what happened.

Key concepts

• Severity -- every incident has a priority level from SEV1 (critical) to SEV4 (low). Severity determines SLA targets, notification urgency, and escalation rules. Read more in Severity levels.

• Status -- incidents move through a defined lifecycle: Investigating → Identified → Monitoring → Resolved. Each transition is logged in the timeline. Read more in Incident lifecycle.

• Incident type -- classify incidents by category: technical, security, legal, compliance, PR, or executive. Types help with routing and postmortem analysis.

• Commander -- the person leading the incident response. The Commander coordinates responders, manages communication, and has authority to escalate. Read more in Assigning commanders.

• Responders -- team members who triage, investigate, and implement fixes. Responders are assigned based on the incident type and on-call schedule.

• Timeline -- a chronological log of every event: status changes, comments, role assignments, and external updates. Read more in Timeline & activity log.

Incident management flow

Alert detected or incident reported
  |
  v
Create incident (set severity, type, title)
  |
  v
Assign Commander and Responders
  |
  v
Investigating -> Identified -> Monitoring -> Resolved
  |
  v
Collect feedback and create postmortem

Where to go next

• Creating incidents -- learn how to declare a new incident.
• Incident lifecycle -- understand status transitions and role restrictions.
• Severity levels -- explore SEV1 through SEV4 definitions and SLA targets.
• Mock incidents -- practice your incident response with simulations.