Using Ledge
DocsWhere alerts go, which events send them, how reminders work, and the difference between muting and ignoring.
Ledge sends alerts through notification policies. A policy is a set of channels with its own rules, and each site uses one or more policies.
Add channels in Settings → Integrations:
POST to your URL. Use the test button to check delivery.Every account starts with a policy called Default. New sites use it automatically. It has no channels at first, so nothing is sent until you add one.
A policy sets:
Tick Apply to all sites to use a policy everywhere, or choose policies per site. A site with several policies alerts through all of them. For example, one policy can send everything to your team's Slack, and another can email a client only when their site is down.
| Feature | Alert types |
|---|---|
| Health check | Unhealthy, Degraded, Healthy |
| Uptime | Down, Up, Performance change |
| SSL | Expiring, Renewed |
| Scheduled tasks | Missed, Recovered |
| Security | Advisories |
| Updates | Update runs, Repository disconnected |
| Backups | Failed |
Each problem sends one alert when it starts, then reminders on the policy's cadence until it's fixed. Healthy, Up, Recovered and Renewed are sent once, when the problem clears.
Mute a site from its bell menu while you're working on it: For 1 hour, For 1 day, Until a time you choose, or Indefinitely.
While a site is muted, monitoring keeps running and history is still recorded, but no alerts are sent, including recovery notices. If something is still wrong when the mute ends, you're alerted after the usual grace time.
Ignoring is for one known result you've decided to live with, not for the whole site:
Use mute for "not now" and ignore for "this one's fine".