Ana içeriğe geç
Versiyon: 1.0.6

Exclusion Rules

Define time windows during which alert notifications are suppressed, preventing false alarms during planned maintenance or deployments.

What are Exclusion Rules?​

Exclusion rules let you schedule periods when a monitor's failures will not trigger alerts or count against uptime KPIs. Checks continue to run during exclusion windows — data is still collected — but the alerting engine treats failures as expected and suppresses notifications.

Creating an Exclusion Rule​

  1. Navigate to HealthCheck → Dashboard.
  2. Click a monitor to open its report page.
  3. Select the Exclusion tab.
  4. Click Add Exclusion.

Add Exclusion Rule

Exclusion Fields​

FieldDescription
NameA descriptive label (e.g., "Weekly Deployment Window")
Start Date/TimeWhen the exclusion begins
End Date/TimeWhen the exclusion ends
RecurrenceOne-time, Daily, Weekly, or Monthly
DescriptionOptional notes about the maintenance activity
  1. Select start and end times using the calendar picker.
  2. Choose a Recurrence pattern if the maintenance repeats on a schedule.
  3. Click Save to create the exclusion.

Recurrence Patterns​

PatternBehavior
One-TimeApplies once at the scheduled date/time, then expires
DailyRepeats every day at the same time window
WeeklyRepeats on the same day of the week
MonthlyRepeats on the same day of the month
bilgi

Recurring exclusions continue indefinitely until you delete or modify them. Review recurring rules periodically to remove exclusions that are no longer needed.

Managing Exclusion Rules​

Viewing Exclusions​

All exclusion rules for a monitor are listed in the Exclusion tab on the monitor report page. Each entry shows the name, time window, recurrence pattern, and status (upcoming, active, expired).

Editing an Exclusion​

  1. Click the Edit icon next to the exclusion rule.
  2. Modify the time window, recurrence, or description.
  3. Click Save to apply changes.

Deleting an Exclusion​

  1. Click the Delete icon next to the exclusion rule.
  2. Confirm the deletion in the dialog.
uyarı

Deleting an active exclusion immediately re-enables alerting. If the monitor is currently failing, alerts will be sent as soon as the exclusion is removed.

Best Practices​

  • Name exclusions descriptively — Use names like "Bi-weekly DB migration" instead of "Maintenance" so the team understands the context.
  • Keep windows tight — Only cover the actual maintenance duration. Overly broad windows hide real issues that occur outside the planned work.
  • Use recurring rules for regular maintenance — If your team deploys every Tuesday at 2 AM, create a weekly recurring exclusion instead of adding a new one-time rule each week.
  • Review expired exclusions — Clean up one-time exclusions after they expire to keep the list manageable.
  • Coordinate with your team — Notify stakeholders when exclusion windows are active so they know that alerts are suppressed and monitoring data may show expected failures.

Next Steps​