Smart Alerts
When metrics cross the line
Get notified when monitored metrics cross the lines you set: email digests and in-product signals today; additional channels per roadmap. Cooldowns and sensible defaults reduce fatigue from noisy deploys while still surfacing sustained problems. Alerts link scheduled test results to the engineers and account leads who fix production performance.
Why it matters
Less inbox noise, faster response, clear ownership.
Budget-driven
Thresholds from performance budgets define when an alert exists.
Multi-channel (where enabled)
Email today. Slack and webhooks are planned for tiers that include them.
Cooldowns by design
Repeat scheduled failures do not generate an endless notification thread.
From test result to notification
A test completes, we evaluate it against your budgets, and an alert record is created when something breaches. Organisation admins receive email today; wire Slack when your plan supports it.
Example thresholds: LCP, INP, CLS, performance score, aligned with Performance budgets.
Cooldown and resolution
| Stage | System behaviour |
|---|---|
| Open breach | Notify; start cooldown window |
| While failing | Suppress duplicate alerts until state changes |
| Passes budget | Resolve; ready to alert again on next breach |
What is coming
We are extending routing and analytics so large teams can steer noise away from the wrong inboxes. Until those ship, email plus in-product signals remain the backbone. On the roadmap: team routing, escalation rules, and alert analytics (frequency, time to resolve).