Miterl Miterl
Back to all posts 日本語
April 1, 2026

Maintenance Window Best Practices to Prevent False Alerts

maintenance window uptime monitoring alert management

False Alerts During Maintenance Are Costing You Time

Every web agency has been there. You schedule a server migration or CMS update for a client site at 2 AM, and your monitoring tool floods Slack with alerts. By morning, your team is desensitized to notifications and slower to respond to real incidents. This is alert fatigue, and it is a serious operational risk.

Miterl's maintenance window feature lets you register planned downtime in advance so that alerts are automatically suppressed during that period.

What Is a Maintenance Window?

A maintenance window tells your monitoring system: "This downtime is planned." During the configured window, Miterl behaves as follows:

  • Monitoring checks continue to run as normal
  • Alert notifications are suppressed
  • If the site is still down when the window ends, an alert fires immediately

This means you never lose visibility. If maintenance runs longer than expected, you will know right away.

Best Practices for Configuration

1. Add Buffer Time Before and After

If your maintenance is scheduled from 11:00 PM to 1:00 AM, set the window from 10:50 PM to 1:15 AM. DNS propagation, cache invalidation, and CDN purges can cause brief downtime outside your exact maintenance period.

2. Automate via API

Integrate maintenance window creation into your CI/CD pipeline so no one forgets to set it.

# Create a maintenance window before deployment
curl -X POST https://api.miterl.com/v1/maintenance-windows \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "monitor_ids": ["mon_abc123", "mon_def456"],
    "starts_at": "2026-04-01T22:50:00+09:00",
    "ends_at": "2026-04-02T01:15:00+09:00",
    "reason": "Server migration"
  }'

This single API call eliminates the risk of manual oversight and keeps your deployment workflow clean.

3. Scope Windows to Specific Monitors

Apply the window only to the monitors under maintenance. Blanket suppression across all sites means you could miss a real outage on an unrelated client site.

4. Use Recurring Schedules

If a client has a weekly batch job every Wednesday at 3 AM, configure a recurring maintenance window instead of creating one manually each week.

{
  "schedule": {
    "type": "weekly",
    "day_of_week": 3,
    "starts_at": "03:00",
    "duration_minutes": 30,
    "timezone": "America/New_York"
  }
}

Set it once and never worry about it again.

Use Maintenance History for Client Reporting

Maintenance window history is visible in the Miterl dashboard. When a client asks about downtime in their monthly report, you can clearly distinguish planned maintenance from actual incidents. Planned downtime is automatically excluded from uptime calculations, giving you accurate SLA reports without manual adjustments.

Summary

Properly configured maintenance windows reduce false alerts, lower team stress, and give your clients clear accountability. With Miterl, you can automate the entire process through the API and integrate it directly into your deployment pipeline.

Check the documentation for detailed setup instructions. Try the feature yourself in the Playground, and see how other agencies use Miterl on the use cases page.

Back to all posts