Why it matters
Component group matters because teams need a precise shared meaning for a collection of related status-page components shown together. 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 collection of related status-page components shown together 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 component group 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 group containing API, Dashboard, and Auth. When observed behavior stops matching the definition of component group, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
Groups replace individual component status
That reading usually collapses distinct ideas into one slogan. Keep component group tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
Groups improve scanning; each component should still have its own state.