Why it matters
Monitor matters because teams need a shared, precise meaning for a configured check that runs on a schedule. 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 configured check that runs on a schedule 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 monitor is operational: it changes who gets notified, what customers see, or which metric a team reviews after an incident.
Practical example
Imagine a team running checks against https://api.example.com/health. When the observed behavior stops matching the definition of monitor, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
A monitor is the same thing as an incident
That reading usually collapses distinct ideas into one slogan. Keep monitor tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
In Fajita, a monitor is the configured check. Incidents are opened when verified failures continue. Start with create your first monitor.