Monitoring

You can monitor APIs and tests continuously, with scheduled execution and alerting that tells you when something changes. Monitors keep running after release, so a regression or outage reaches you before it reaches a customer.

Who it’s for#

Teams that need ongoing confidence their APIs and critical flows keep working in production, not just at the moment they were last tested.

What it does#

• Continuous monitoring — keep APIs and tests under watch over time.
• Scheduled execution — run monitors on a schedule so checks happen without manual effort.
• Alerting — get notified when a monitor catches a problem.
• On-demand and lifecycle control — create monitors, run them on demand, and pause or resume them as needed.

How it works#

Create a monitor for an API or test, set it to run on a schedule, and let it execute on its own. For scheduling options, see scheduling and notifications. You can also run a monitor on demand, or pause and resume it when plans change.

Why it matters#

Most production problems are noticed first by customers. Continuous monitoring flips that: regressions and outages show up in your alerts so the team can respond before the support tickets start.