Escalation, Scheduled Actions, and Smarter Auto-Fix: Level Up Your Monitoring

Uptime monitoring is only as good as the actions it triggers. We've added three features that make your setup more flexible and easier to operate: escalation by duration, scheduled actions, and multi-trigger auto-actions. Together they help you avoid alert fatigue, integrate with incident tools, and run the right fix for each kind of failure.

Escalation by duration

When a site goes down, you usually get an alert right away. But if the outage drags on, you may want a second, stronger signal—for example, to wake an on-call engineer or to open a ticket in PagerDuty or Opsgenie. Escalation by duration does exactly that: after the site has been down for a configurable number of minutes (e.g. 15), we send an extra POST request to a dedicated escalation webhook. The payload includes how long the site has been down, the cause code, and a short summary, so your incident system can prioritize and route the alert. You set the threshold and URL per website under Edit website → Settings in the "Escalation by duration" section.

Scheduled actions

Not every automation should run only when something breaks. Scheduled actions run on a fixed schedule—daily at a given time or weekly on a chosen day—and can call a webhook or run an SSH command. Use them to ping a health endpoint, trigger a backup, warm caches, rotate logs, or run any recurring task. Add and manage them per website under the Edit website → Scheduled tab. The system evaluates due actions every minute, so your cron-style jobs run reliably without touching server crontabs.

Multi-trigger auto-actions

Auto-Fix (SSH actions and webhooks) already let you react automatically when downtime is detected. Now you can narrow when each action runs by choosing one or more failure causes. For example: run "restart Nginx" only when the cause is server error (5xx) or timeout; run "redeploy" only when required keyword is missing; run "notify DNS team" only on DNS resolution failed. In Edit website → Auto-Actions, use the "When this happens" multi-select to pick the causes that should trigger that action. Leave all unchecked to run on any downtime. This keeps recovery scripts targeted and reduces unnecessary runs and noise.

Combined, escalation, scheduled actions, and multi-trigger auto-actions give you finer control over alerts and automation—so you can respond faster and keep your monitoring stack easier to maintain.