Suites
A suite groups monitors that together make up one service or user journey — for example, Checkout journey with the cart API, the payment API and the checkout browser test. A suite has its own state, alerts and runs, so you can view, run and be alerted about the whole journey at once.
Suites are listed under Synthetics → Suites, with their State, number of Monitors, Critical members, Uptime, Labels and Description.
Creating a Suite
Click New suite:
| Field | Description |
|---|---|
| Name | e.g. Checkout journey |
| Description | What the suite covers |
| Enabled | A disabled suite is paused: not evaluated, no alerts |
| Labels | Key/value labels for filtering |
| Monitors | Pick members from Available monitors (search by name, filter by type or key:value label). Each member is Critical (counts toward the suite's state) or Ignored (shown, not counted). Up to 300 members |
| DOWN threshold | Share of the critical monitors that must be down for the suite to be down. Default 50% |
| Minimum failure duration | How long the suite must be down before it alerts (0–1440 minutes, 0 = at once) |
| Notify channels, Priority, Message | Where the suite's alert goes, its priority and its message |
| Viewer access to this suite | Who else can see the suite |
Click Create suite.
A monitor can belong to several suites, and keeps its own alerts.
Suite Details
| Element | Description |
|---|---|
| State tiles | Evaluated, Up, Critical down, Degraded, No data, Paused, Monitors, Uptime 24 h |
| State timeline | The suite's state over time |
| Members | Each monitor with its type, role, state, last run and 24-hour uptime |
| Recent suite runs | Each Run suite, with every member's result |
| Alert events | The suite's alerts, with when they fired, their duration and status |
Actions:
- Run suite — runs every member once, as a batch (see CI batches).
- Add to downtime — creates a maintenance window for the suite.
- Edit, Access and Delete suite.