Business severity
A Broken Checkout Is Not the Same as a Broken Blog Image
Most monitoring tools treat every page the same. Sitewatch adjusts incident severity based on business importance — a medium issue on your client's checkout page (marked "critical") becomes high severity and bypasses quiet hours. The same issue on a blog page stays medium. Your team gets woken up for revenue emergencies, not cosmetic issues.
- Severity adjusted by page importance — critical pages escalate automatically
- Critical pages bypass quiet hours so revenue issues never wait until morning
- Reduces alert noise for low-importance pages — fewer interruptions, better focus
Severity escalated — Critical page
Medium → High (escalated by business importance)
/checkout — Business importance: Critical
Recent activity
- Issue detected — medium severity3:12 AM
- Page importance checked — Critical3:12 AM
- Severity escalated to High3:12 AM
- Quiet hours bypassed — critical page3:12 AM
- Alert sent to 3 channels3:12 AM
Why business severity scoring
Not every broken page deserves the same response
Severity adjusted by importance
A medium issue on a critical page becomes high severity. A medium issue on a blog page stays medium. Alerts reflect real business impact.
Critical pages bypass quiet hours
When a critical page has an incident, quiet hours are overridden automatically. Revenue-impacting issues never wait until morning.
Reduces alert noise
Low-importance pages generate lower-priority alerts. Your team focuses on what matters instead of chasing cosmetic issues on blog posts.
No configuration per incident
Set the importance level once per page. Sitewatch handles the severity adjustment automatically every time an issue is detected.
Works with all failure types
Broken links, missing assets, SSL errors, performance regression — severity scoring applies to every detection rule, not just specific issue types.
Business-aware, not just technical
Most monitoring tools treat every page equally. Sitewatch adjusts incident severity based on the business importance of the affected page — so your response matches the real-world impact.
4
Importance levels
Yes
Quiet hour bypass
All
Plans supported
How it works
From page importance to business-aware severity in four steps
Set page importance
Tag each monitored page as critical, high, normal, or low. This tells Sitewatch how important that page is to your business.
Incident detected
Sitewatch detects an issue on one of your monitored pages — a broken asset, SSL error, performance regression, or any other failure.
Severity weighted by importance
The raw severity is adjusted based on the page's business importance. A medium issue on a critical page is escalated to high severity.
Critical pages bypass quiet hours
If the affected page is marked critical, quiet hours are overridden. Your team is alerted immediately, even at 3 AM.
The difference
Flat severity vs. business severity
| Feature | Flat severity | Business severity |
|---|---|---|
| How severity is determined | Based on issue type alone — every page treated equally | Issue type weighted by page business importance |
| Quiet hours behavior | All alerts suppressed during quiet hours | Critical pages bypass quiet hours automatically |
| Alert noise | Same urgency for blog and checkout | Low-importance pages generate lower-priority alerts |
| Business context | None — just technical severity | Every alert reflects the business impact of the affected page |
How severity is determined
Quiet hours behavior
Alert noise
Business context
FAQ
Frequently asked questions
When Sitewatch detects an issue, it checks the business importance level of the affected page. If the page is marked as critical or high, the severity is escalated automatically. A medium issue on a critical page becomes a high-severity incident.
There are four levels: critical, high, normal, and low. You assign one level per monitored page. Critical is for pages like checkout and login where downtime directly impacts revenue. Low is for pages like blog posts where issues are less urgent.
Yes. Severity scoring applies before alerts are sent, so every channel — Slack, email, SMS, webhooks — receives the escalated severity. There is no need to configure per-channel rules.
Yes. Every plan that supports critical page monitoring includes business severity scoring. The number of pages you can monitor depends on your plan (1 on Free, 5 on Starter, 25 on Pro).
If an incident affects a page marked as critical, quiet hours are bypassed and the alert is sent immediately. For pages marked high, normal, or low, quiet hours are respected as usual.
Explore more