Setting Up Alerts
Learn how to create alert rules to get notified when metrics cross your thresholds.
Alerts notify you when something needs attention. Set up rules for any metric and receive notifications through email and in-app alerts.
Creating an Alert
Step 1: Navigate to Alerts
- Go to your domain's dashboard
- Click Alerts in the sidebar
- Click Create Alert
Step 2: Configure the Rule
| Field | Description |
|---|---|
| Name | Descriptive name for the alert |
| Module | Which monitoring type (RUM, Uptime, etc.) |
| Metric | Specific metric to monitor |
| Condition | Comparison operator |
| Threshold | Value that triggers the alert |
| Window | Time period to evaluate |
| Severity | Info, Warning, or Critical |
Step 3: Set Notification Channel
Choose how to receive alerts:
- In-app notifications (always enabled)
- Email notifications (optional, toggle per alert)
Step 4: Save and Activate
Click Create Alert to activate your rule.
Alert Configuration
Modules
Choose which monitoring type to create alerts for:
| Module | Configuration |
|---|---|
| RUM | Custom metrics: LCP, CLS, INP, TTFB, FCP (p75 values), Error Rate |
| CrUX | Custom metrics: LCP, CLS, INP, TTFB with URL/Origin and device filter |
| Synthetic | Custom metrics: LCP, CLS, TBT, TTI, FCP, SI, TTFB, Network Requests with URL and evaluation window |
| Uptime | Predefined alerts: Site down/up, SSL expiry, domain expiry |
| Robots.txt | Predefined alerts: Syntax errors, sitemap blocking, file changes |
| Google Search Console | Percentage-change metrics: Clicks, Impressions, CTR, Discover, News |
| Indexing | Percentage-change metrics: page counts per coverage state |
| Web Analytics | Percentage-change metrics: Visitors, Sessions, Pageviews, Bounce Rate, and more |
| Google Analytics | Percentage-change metrics: Users, Sessions, Engagement Rate, and more |
Predefined Alerts (Uptime & Robots.txt)
For Uptime and Robots.txt modules, select from predefined alert types:
Uptime Alerts:
- Site is down
- Site is up (recovery)
- SSL will expire in 14/7 days
- Domain will expire in 14/7 days
Robots.txt Alerts:
- Robots.txt file changed
- Robots.txt has syntax errors
- Robots.txt blocks sitemap URLs
Device Filter (RUM, CrUX & Synthetic)
For RUM, CrUX, and Synthetic alerts, you can filter by device type:
| Device | Description |
|---|---|
| Any | Combined data from all devices |
| Phone | Mobile devices only |
| Desktop | Desktop computers only |
Evaluation Window (Synthetic Only)
For Synthetic alerts, choose how many recent tests to evaluate:
| Window | Description |
|---|---|
| Last test only | Alert on single test result |
| Average of last 3 | Smoother, reduces noise |
| Average of last 5 | More stable baseline |
| Average of last 10 | Most stable, slower to react |
Conditions (Custom Alerts)
For RUM, CrUX, and Synthetic modules, configure threshold conditions:
| Operator | Description |
|---|---|
> | Greater than |
< | Less than |
>= | Greater than or equal |
<= | Less than or equal |
= | Equals |
!= | Not equals |
changed | Value changed (Uptime and Robots.txt boolean metrics only) |
For Google Search Console, Indexing, Web Analytics, and Google Analytics, alerts compare the current period against the previous one using percentage-change operators:
| Operator | Description |
|---|---|
| Decreased by more than (%) | Metric dropped by more than X% vs. the previous period |
| Increased by more than (%) | Metric rose by more than X% vs. the previous period |
| Anomaly (std. deviations) | Metric deviates from its rolling average by more than N standard deviations |
These operators require a comparison window (1, 3, 7, 14, or 28 days).
Severity Levels
| Level | When to Use |
|---|---|
| Info | Non-urgent, good to know |
| Warning | Needs attention soon |
| Critical | Immediate action required |
Example Alerts
Site Down Alert (Predefined)
Select from Uptime module:
- Alert Type: Site is down
- Severity: Critical (preset)
- Email: Enabled
Poor LCP Alert (Custom)
| Setting | Value |
|---|---|
| Module | RUM |
| Metric | LCP p75 |
| Condition | > |
| Threshold | 2500 (ms) |
| Severity | Warning |
SSL Expiring Soon (Predefined)
Select from Uptime module:
- Alert Type: SSL will expire in 14 days
- Severity: Warning (preset)
- Email: Enabled
CrUX Performance Alert (Custom)
| Setting | Value |
|---|---|
| Module | CrUX |
| Metric | LCP p75 |
| URL/Origin | Origin (all URLs) |
| Device | Any |
| Condition | > |
| Threshold | 2500 (ms) |
| Severity | Warning |
Synthetic Monitoring Alert (Custom)
| Setting | Value |
|---|---|
| Module | Synthetic |
| Metric | LCP |
| URL | Homepage |
| Device | Any |
| Evaluation Window | Average of last 5 |
| Condition | > |
| Threshold | 2500 (ms) |
| Severity | Warning |
Managing Alerts
View All Alerts
See all configured alerts at Domain → Alerts:
- Alert name
- Module badge
- Enabled/disabled toggle
Edit an Alert
- Click the alert row
- Modify settings in the modal
- Click Update Rule
Disable an Alert
Toggle the switch next to any alert to enable or disable it without deleting.
Delete an Alert
- Click the trash icon next to the alert
- Confirm deletion
Quick Setup
For new domains, use Create essential alerts with one click to set up recommended alerts across every module. This creates alerts for:
- RUM: LCP, CLS, INP (p75 thresholds)
- CrUX: LCP, CLS, INP (Origin, any device)
- Synthetic: LCP, CLS (Home URL, average of last 5)
- Uptime: Site down/up, SSL expiry (14/7 days), Domain expiry (14/7 days)
- Robots.txt: Syntax errors, sitemap blocking, file changed
- Google Search Console: Clicks and Impressions dropped > 30% (7-day)
- Indexing: Indexed pages dropped > 15% (7-day)
- Web Analytics: Visitors dropped > 30% (7-day)
- Google Analytics: Users dropped > 30% (7-day)
Best Practices
Start with Critical Alerts
Begin with the most important alerts:
- Site down
- SSL expiring
- Critical performance thresholds
Avoid Alert Fatigue
Too many alerts lead you to ignore them:
- Use appropriate thresholds
- Set reasonable evaluation windows
- Group related alerts
Test Your Alerts
Verify alerts work:
- Create a test alert with a low threshold
- Confirm notification is received
- Delete the test alert
Use Severity Appropriately
Reserve Critical for truly urgent issues:
- Site completely down
- Security issues
- Revenue-impacting problems
Review and Refine
Periodically review your alerts:
- Are you getting too many?
- Did you miss important issues?
- Are thresholds still appropriate?