> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testbrick.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitors

> Run tests on a schedule and hear about it the moment they break

# Monitors

A monitor runs a group of tests on a schedule — every few minutes, hourly or daily — and tells you when one breaks and when it's fixed. Browser tests and API flows can share one monitor.

Open **Monitors** at the top of the dashboard to see every monitor in the project, how healthy each one is, and the project's uptime over the last 7 days.

## Create a monitor

<Steps>
  <Step title="Pick the tests">
    Click **New monitor** and tick the tests it should run. **Select all in folder** picks a whole folder at once.

    <img src="https://mintcdn.com/testbrick/_9wt3b4mC622fMK-/images/monitor-pick-tests.png?fit=max&auto=format&n=_9wt3b4mC622fMK-&q=85&s=33f79b5325e746ee76d2410ef8a3727c" alt="Pick tests for a monitor" width="672" height="343" data-path="images/monitor-pick-tests.png" />
  </Step>

  <Step title="Choose how often and who hears about it">
    * **How often** — every 5, 10, 15 or 30 minutes, hourly, or daily at noon. How often you can run depends on your plan.
    * **Where** — email (to your account address) and, if connected, a Slack channel
    * **What** — which messages to send (see below)

          <img src="https://mintcdn.com/testbrick/_9wt3b4mC622fMK-/images/monitor-schedule-alerts.png?fit=max&auto=format&n=_9wt3b4mC622fMK-&q=85&s=43224cca237f5582e17e0d89f9882a00" alt="Schedule and alerts" width="672" height="813" data-path="images/monitor-schedule-alerts.png" />

    If a test hasn't passed recently, you'll see a warning — you may get an alert on the first run.
  </Step>

  <Step title="Turn monitoring on">
    Click **Turn monitoring on**. The first run starts on the next scheduled time.
  </Step>
</Steps>

## What you're told

| Message | When |
| - | - |
| **Breaks and recoveries** | The moment a test goes red, and when it's green again |
| **Daily standup** | Once a day at the time you pick: what passed, anything that blipped, what fixed itself (Slack) |
| **Every run** | A short line per run, pass or fail — best in its own quiet Slack channel |
| **Weekly recap** | Mondays: the week's pass rate and the flakiest test |

Every alert links to the failed run, which opens with [why it failed](/ui-testing/running-tests#why-it-failed).

## Managing monitors

From the Monitors page you can search and filter monitors, pause and resume them, change their tests or schedule, and see each one's pass rate over the last 7 days.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.