Why it matters
Incident detection matters because teams need a precise shared meaning for discovering that a service likely failed or degraded. 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, discovering that a service likely failed or degraded 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 detection 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 monitor failures on https://api.example.com/health. When observed behavior stops matching the definition of incident detection, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
Detection always equals a confirmed outage
That reading usually collapses distinct ideas into one slogan. Keep incident detection tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
Fajita detects candidate failures through monitors, then verifies before treating them as incidents.