Notifications
Notifications and alerts let teams react to run evidence without living in the dashboard.
There are three related surfaces:
| Surface | What it does |
|---|---|
| In-app notifications | The bell and unread dots for run status, flaky/stable changes, and fired alerts. |
| Target Alerts | Target-local policies that watch functional or load metrics across recent runs. |
| Reports | Scheduled or manually generated health digests for an org or project scope. |
In-App Notifications
The app creates in-app notifications for events such as:
- run passed, failed, errored, or cancelled
- a test became flaky or stable
- an alert policy fired
The notification bell is org/project scoped. Opening a Target’s Alerts tab also clears the unread signal for that Target’s fired alerts.
Target Alerts
Alert policies live under a Target. They can watch:
- functional run health
- custom functional metrics
- load metrics such as p95, error rate, throughput, endpoint/scenario values, and plan-scoped signals
Alert policies can deliver to:
- Webhook
Reports
Reports are generated health digests. They can be org-wide or project-scoped, and schedules can push to email or webhook channels.
A Practical Setup
- Use Target Alerts for “wake me up when this Target regresses.”
- Use Reports for slower daily or weekly review.
- Keep in-app notifications as the quick triage surface for recent run state.
- Keep webhook channels signed and rotate secrets when a destination changes.
Related
Last updated on