digiDocs/Services/Website_Monitoring.md
Joey King e616199b9d
Some checks failed
Regenerate Documentation Index / regenerate-index (push) Failing after 1s
Remove stale reference to Website_Status.md (moved to private repo)
2026-02-19 15:31:39 +00:00

41 lines
1.7 KiB
Markdown

# Website Monitoring
**Last Updated:** 2026-02-19
## What We Monitor
digiBandit monitors client websites for availability and traffic health using a two-layer approach:
1. **Traffic Analysis** - We track visitor patterns using privacy-friendly analytics. When a site that normally receives regular traffic suddenly drops to zero, that's often an early warning sign of a problem (broken pages, SSL issues, CDN problems, DNS failures).
2. **HTTP Health Checks** - When a traffic anomaly is detected, we automatically verify the site is reachable. This confirms whether the issue is a real outage or just a quiet day.
## How Alerts Work
When our system detects a potential issue:
- The site's traffic pattern is compared against its 7-day baseline
- If traffic has dropped to zero on a site that normally gets visitors, an HTTP check runs
- If the HTTP check also fails, the team is alerted immediately
- We investigate and begin remediation, often before anyone notices the site is down
## What Triggers an Alert
| Condition | Action |
|-----------|--------|
| Normal traffic, site responds | No action needed |
| Low-traffic site (< 5 visitors/day) | Monitored but excluded from anomaly alerts |
| Traffic drop + site responds | Flagged as warning, investigated |
| Traffic drop + site unreachable | Alert sent to team, immediate investigation |
## Check Frequency
| Check Type | Frequency | Coverage |
|------------|-----------|----------|
| Traffic analysis | Every 4 hours | All client websites with analytics |
| HTTP health checks | On-demand (when anomaly detected) | Flagged sites only |
| Infrastructure monitoring | Every 5 minutes | digiBandit internal services |
## Questions?
Contact digiBandit at (506) 404-0055 or through your usual support channel.