For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Discord
DocsAPI Reference
DocsAPI Reference
  • Get Started
    • Welcome
    • Introduction
    • Quick Start
  • Run
    • Run Videos
    • Run Mode
    • Viewport Size
    • Preparation Test
    • Pull Request Testing
    • Production Monitoring
    • Group Webhooks
    • Run Troubleshooting
  • Auth
    • Test Credentials
    • API Keys
    • Agent Mail Inboxes
    • HTTP Basic Auth
    • Auth Troubleshooting
  • Mobile
    • Overview
    • App Uploads
    • Expo EAS
    • GitHub Actions
  • Integrations
    • Vercel
    • Coolify
    • Custom Infrastructure
    • Slack
    • Discord
    • Email
  • Guides
    • Testing Staging Environment
  • CLI
    • Getting Started
    • Local Development
    • Agentic Usage
  • AI
    • LLMs
LogoLogo
Discord
On this page
  • Set up Production Monitoring
  • Failure notifications
  • Tips
Run

Production Monitoring

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Pull Request Testing

Next

Group Webhooks

Built with

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.

Disabled tests in the selected group are skipped. You can still run a disabled test manually from its test page.

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
  5. Save.

Production Monitoring configuration

Failure notifications

If any test in a monitored run fails, TesterArmy sends a failure summary to connected chat providers such as Slack or Discord. If no chat provider delivers, you’ll receive an email notification so you can act on it right away.

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.