> 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/monitoring/configure-checks.md).

# Configure checks

Add a monitoring check: the endpoint to probe, timeout, down threshold, regions, who gets alerted, and the optional link to a status page service.

A check probes one endpoint on a schedule and alerts your team when it goes down or comes back up. This page covers every setting on the check form; for what checks do and how up and down are decided, see [Monitoring](/next/basics/monitoring.md).

## Add a check

Go to **Monitoring** → **Checks** and click **Add check**. Any member with access to the Monitoring module can create and edit checks.

<figure><img src="https://4089725725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQG79S8GZWmqk3Plak6MO%2Fuploads%2Fgit-blob-f4a1436f5d4f9ddf19eca2f4ada5bd9d8a084983%2Fmonitoring-new-check-form.png?alt=media" alt="The New check form in the admin console, reached from Checks under Monitoring in the sidebar, with Name, URL to monitor, Response timeout, Down threshold, Monitoring regions, Notification recipients, and a Status page automation toggle, and a Create check button"><figcaption></figcaption></figure>

Fill in the form and click **Create check**:

* **Name**: a label for the checks list, for example "Webhooks EU HTTP check".
* **URL to monitor**: the protocol (HTTP, HTTPS, or TCP), the HTTP method for HTTP and HTTPS checks, and the host or URL to probe. Changing the protocol, method, or host later resets the check's recorded history.
* **Response timeout (secs)**: how long a probe waits before counting as failed, from 1 to 60 seconds.
* **Down threshold**: how many minutes the check must keep failing before it is reported as down, 5 by default. Use 0 to report on the first failed probe. This threshold also decides where Down periods start in the check's uptime history, and when a connected status page notice opens, so leave some margin before connecting a check to a status page.
* **Monitoring regions**: leave empty to probe from all regions, or pick US, EU, or both.
* **Notification recipients**: the team members alerted by email when the check changes state. At least one is required.
* **Status page automation**: switch on to link the check to a service on one of your status pages, so the check opens and resolves an incident notice on its own, and optionally to show the check's response times on that page. Pick the **Status page** and the **Service**, then tick **Display response time chart** if you want it. See [Connect checks to status pages](/next/monitoring/connect-checks-to-status-pages.md) for what happens on the page.

The check starts probing right away. It probes every minute, and its results appear on its own page shortly after; see [Understand check results](/next/monitoring/understand-check-results.md).

## Edit or remove a check

Open the check from the list and click **Edit check** to change any setting. There is no pause: a check probes and alerts until you remove it, which you do from the check page or from the menu on its row in the checks list. Removing a check deletes its history and, if it was connected to a status page, stops driving that service without changing the service's current status.