> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.tester.army/run/llms.txt.
> For full documentation content, see https://docs.tester.army/run/llms-full.txt.

# Production Monitoring

Production Monitoring execute tests at a fixed time, on repeat. Use them for nightly smoke checks, regression catching, or monitoring key flows outside of PR activity.

## Set up Production Monitoring

1. Open **Project → Tests** tab.
2. Click the **Triggers** button.
3. Click **New Production Monitoring**.
4. Set:
   * **Frequency**: Hourly, Daily, or Weekly
   * **Time and timezone**
   * **Day of week** (weekly only)
   * **Test group** to execute - each production monitor runs a test group you've already [created](/get-started/quick-start)
5. Save.

![Production Monitoring configuration](https://files.buildwithfern.com/testerarmy.docs.buildwithfern.com/29f2bcf48de3427ef0affc99281255b4093d037e49b8875dc082ec3903da7e0e/docs/assets/docs/production-monitoring.png)

## Failure notifications

If any test in a monitored run fails, you'll receive an email notification so you can act on it right away. You can also get failure alerts in [Slack](/integrations/slack) by connecting your workspace.

## Tips

Keep each monitor focused. A monitor that tries to test login, billing, and settings in one go is harder to act on when it fails. Split those into separate groups instead.