Why it matters
Error rate matters because teams need a precise shared meaning for the share of requests that fail within a period. 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, the share of requests that fail within a period 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 error rate 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 2% of checkout API calls returning 5xx. When observed behavior stops matching the definition of error rate, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
Error rate is the same as uptime percentage
That reading usually collapses distinct ideas into one slogan. Keep error rate tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
Define which statuses count as errors before comparing periods.