Lab Test Alerts
Lab alerts are generated automatically when there's a significant change to a monitored page, or when a performance budget is breached.
Synthetic monitoring alerts can be sent by email, in Slack, or in Microsoft Teams.
When are lab alerts sent?
Lab test alerts are sent when a significant change is detected on a page or when a custom performance budget is breached.
You can configure alert criteria in the notification settings.
Lab Alerts are grouped based on when they are triggered. For example, if you run daily tests on 20 pages, a single alert message will be sent when all tests are complete.
Opening the notification settings
- Go to your project dashboard
- Select the Integrations tab
- Scroll down to Notification Triggers
- Click the gear icon next to the lab alert trigger
Alert categories and conditions
You can configure what changes should trigger a notification.
By default, you'll receive notifications when a budget is breached for the first time. Enable re-alert on consistent breaches to get a new message every time a test completes that breaches the budget.
DebugBear also has a set of automatic alerting rules that trigger when significant changes are detected on your page. You can adjust the sensitivity of these alerts, or disable them for certain categories.
Set up lab test notifications in Slack or Microsoft Teams
To get alerts in your chat tool, you need to add a notification channel and then select Lab Alerts during setup.
If you've already configured a channel, you can click Add Notification Trigger to set up a new trigger for lab alerts.
Automatic re-test before sending an alert
DebugBear tries to send notifications only when there was a real change on your website that you need to respond to.
If an analysis would result in a notification being sent, DebugBear may re-test before saving the result. This makes sure it's not just a one-off issue that can't be reproduced.
Muting notifications
You can mute notifications that aren't important to you.
