Why it matters
Monitoring interval matters because teams need a shared, precise meaning for how often a monitor runs its scheduled check. 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, how often a monitor runs its scheduled check 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 monitoring interval 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 every 60 seconds against https://api.example.com/health. When the observed behavior stops matching the definition of monitoring interval, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
Faster intervals always mean better reliability
That reading usually collapses distinct ideas into one slogan. Keep monitoring interval tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
Choose intervals in Fajita based on response needs and plan limits. See check intervals.