Monitoring & alerts

Scheduled public-URL checks, app.unhealthy / app.recovered, top error paths

Ask your agent

Tell me whenever my app goes down.Read the guide at percher.app/docs/monitoring

Show me which parts of my app are failing.Read the guide at percher.app/docs/monitoring

How it works, with exact details

On paid plans, Percher checks your public URL from the platform API on a schedule and tells you when probes start failing. These are not independent external checks. This is distinct from crash diagnostics: the watchdog watches the container process; uptime monitoring watches whether the app is actually reachable from the internet (DNS, Caddy, TLS, 5xx). Both can fire for the same incident.

How often is my app checked?

Free — disabled (no scheduled probes)
Starter — every 5 minutes
Maker — every minute
Max — every 30 seconds

The probe fetches the app's primary URL (verified custom domain if any, otherwise the *.percher.run subdomain) with an 8-second timeout. HEAD requests fall back to GET for hosts that 405 on HEAD. 2xx or 3xx counts as up. Recognized private/password gate challenges (401/403) count as reachable; other 4xx, 5xx and network errors count as down.

When does an outage alert fire?

A single bad probe is not an outage. Three consecutive failures flip the app to down and fire app.unhealthy. A subsequent successful probe flips back to up and fires app.recovered — but only when the matching unhealthy was actually delivered (per channel, paired). A 15-minute cooldown gates re-firing during flapping. The current Health page shows the 30-day recorded-probe success percentage and current route latency. The uptime API also returns day/week/month rollups, recent probes, and outage intervals; those extra series are not all rendered in the dashboard yet.

What do the webhook payloads look like?

app.unhealthy:

{
  "type": "app.unhealthy",
  "id": "wh_abc123",
  "timestamp": 1735689600000,
  "data": {
    "appId": "app_xyz",
    "appName": "my-app",
    "url": "https://my-app.percher.run",
    "consecutiveFailures": 3,
    "statusCode": 502,
    "error": "bad gateway",
    "latencyMs": 8000
  }
}

app.recovered:

{
  "type": "app.recovered",
  "id": "wh_def456",
  "timestamp": 1735689900000,
  "data": {
    "appId": "app_xyz",
    "appName": "my-app",
    "url": "https://my-app.percher.run",
    "statusCode": 200,
    "latencyMs": 47
  }
}

Which routes are erroring? (per-route 5xx tracking)

The Analytics tab's Top error paths panel shows which routes returned 4xx/5xx, sorted by 5xx count, with errorRate% computed from the per-route request total. Aggregated daily from Caddy access logs and re-summed across the selected window. Bounded daily lists can omit paths, so multi-day rankings may be approximate. Updates every 15 minutes.