> For the complete documentation index, see [llms.txt](https://docs.statuspal.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.statuspal.io/next/basics/monitoring.md).

# Monitoring

Monitoring runs scheduled health checks against your endpoints and notifies your team when something fails or recovers.

<figure><img src="/files/29lytS4zVxvUjLWo6wiW" alt="Monitoring checks list showing an HTTPS check for Admin console with a green up indicator"><figcaption></figcaption></figure>

## How it works

Each check probes an endpoint on a schedule. When a check fails, the configured **notification recipients** receive a direct alert. When it recovers, they're notified again. That's the baseline behavior for every check.

## Status page automation

Status page automation is an optional setting on each check. When enabled, the check is linked to a specific service on one of your status pages — and monitoring takes on the full incident lifecycle automatically:

**On failure:**

1. An incident is created and linked to the affected service
2. The service status is updated (e.g. to `major`)
3. A notice is posted on your status page
4. Subscribers are notified

**On recovery:**

1. The incident is automatically resolved
2. The service status is restored to `ok`
3. A recovery update is posted on the notice
4. Subscribers are notified of the recovery

## Setting up a check

Go to **Monitoring → Checks** and click **Add check**. Each check is configured with:

* **Name** — a label for the check (e.g. "Webhooks EU HTTP check")
* **URL to monitor** — the endpoint to probe, with your choice of protocol (HTTP, HTTPS, or TCP) and HTTP method
* **Response timeout** — how long to wait before treating the request as failed (1–60 seconds)
* **Monitoring regions** — run checks from the US, EU, or both
* **Notification recipients** — team members to alert directly when a check changes state
* **Status page automation** — enable to link the check to a status page service and activate the full automated incident lifecycle above