Schedules

Monitor schedules let you control when health checks run. By default, monitors check continuously at their configured interval. Schedules add the ability to restrict checks to specific time windows.

Why use schedules

Continuous monitoring is the right choice for most production services. Schedules are useful when:

• A service only runs during business hours and is expected to be offline at night.
• You want to avoid alert noise during planned maintenance windows.
• A staging environment is only active during work hours.
• Certain endpoints have known downtime periods that should not trigger incidents.

How schedules work

When a schedule is applied to a monitor, BlameTrail only runs health checks during the defined time windows. Outside those windows, the monitor is effectively paused — no checks are executed and no incidents are created.

If a monitor has an active incident when its schedule window closes, the incident remains open. It will be evaluated again when the next scheduled window begins.

Creating a schedule

1. Navigate to the Schedules page.
2. Click Create Schedule.
3. Define the time windows when the monitor should be active:
   • Days — Select which days of the week the schedule applies to.
   • Start time — When checks should begin.
   • End time — When checks should stop.
   • Timezone — The timezone for the start and end times.
4. Click Save.

Managing schedules

From the Schedules page, you can:

• Edit a schedule to adjust time windows.
• Delete a schedule to remove it. Monitors previously using the deleted schedule revert to continuous checking.

Default behavior

Monitors without a schedule check continuously at their configured interval, 24 hours a day, 7 days a week. This is the recommended setup for production services where downtime at any hour should be detected.