Why it matters
Incident matters because teams need a precise shared meaning for a tracked period of degraded or failed service. Vague language turns incidents into arguments about words instead of fixes.
When everyone uses the same definition, alerts, status updates, and post-incident reviews stay aligned.
How it works
In practice, a tracked period of degraded or failed service shows up as a concrete signal you can measure or communicate. Operators define what good looks like, watch for deviations, and record what happened when expectations break.
The useful version of incident is operational: it changes who gets notified, what customers see, or which metric a team reviews after an incident.
Practical example
Imagine a team operating around api.example.com returning 503 after verification. When observed behavior stops matching the definition of incident, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
An incident is any failed monitor check
That reading usually collapses distinct ideas into one slogan. Keep incident tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
Fajita opens incidents after verification, not after every blip. See incident verification.