Skip to main content
A monitor is a flow that runs automatically on a repeating schedule against your live production application. Instead of relying on user reports or manual spot-checks to find out when something breaks, a monitor catches failures the moment they happen and alerts you before your users — or your prospects — run into them. Every monitor gives you continuous, eyes-off assurance that a critical path in your application is working right now.

​
Schedule Options

When you create a monitor, you choose how frequently it runs. TYAN supports the following run frequencies:
  • Every 5 minutes — Maximum coverage for your highest-criticality flows, such as checkout or login
  • Every 15 minutes — Frequent checks for important but slightly less time-sensitive paths
  • Hourly — A solid default for most production monitors
  • Every 6 hours — Suitable for flows that are important but change infrequently
  • Daily — Low-frequency verification for stable, rarely-changing paths
  • Custom cron — Define any schedule using standard cron syntax for precise control over timing

​
Monitor Status

Each monitor in your dashboard displays a current status so you can assess the health of your production app at a glance:
  • Active — The monitor is running on schedule and all recent runs have passed. Your flow is healthy.
  • Paused — The monitor has been manually paused and is not running. No alerts will fire while a monitor is paused.
  • Failing — The most recent run failed. TYAN has already sent an alert and continues recording each run until the monitor passes again.
  • Degraded — The monitor is passing but recent runs are taking significantly longer than the established baseline, which may indicate a performance issue before it becomes an outright failure.

​
Alert Channels

TYAN sends alerts through the notification channels your team already uses. Supported channels are:
  • Slack — Post failure and recovery messages directly to a channel or DM. Configure which workspace and channel per monitor.
  • Email — Send failure notifications to one or more email addresses. Ideal for stakeholders who don’t use Slack.
  • Webhook — Fire a POST request to any URL when a monitor fails or recovers. Use this to integrate with PagerDuty, incident management tools, or your own internal systems.
Alerts fire on the first failure of each incident — you will not receive repeated notifications for every failing run of the same incident. When the monitor passes again, TYAN automatically sends a recovery notification so you always know when the issue resolved, without manually checking the dashboard.

​
Monitor History

Every monitor maintains a full run history so you can understand patterns and diagnose failures quickly. For each individual run, you can see:
  • Pass or fail — The outcome of the run and which specific step failed, if any
  • Duration — How long the entire flow took to execute, tracked over time to surface performance degradation
  • Screenshot on failure — An automatic screenshot captured at the exact step where the flow broke, giving you immediate visual context without needing to reproduce the failure manually
Use the run history to distinguish between a transient blip (a single failed run surrounded by passes) and a persistent outage (consecutive failures), and to identify the precise moment a regression was introduced.
Pausing a monitor stops all scheduled runs and silences all alerts for that flow. If you pause a monitor for maintenance or a deployment window, set a reminder to re-enable it before the window closes. A paused monitor provides no protection — breakages will go undetected until you turn it back on.

​
Integrations

Slack Integration

Connect TYAN to your Slack workspace to receive instant failure and recovery alerts in any channel.

Webhooks

Send monitor events to any endpoint to integrate with your incident response tools and internal systems.