Alerts Overview
Pulsar's alerting system notifies you when issues are detected with your monitored sites.
How Alerts Work
- A check detects an issue (HTTP failure, JS error, checkout failure)
- Pulsar creates an alert record
- Notifications are sent through configured channels
- Alert remains open until the issue is resolved or manually acknowledged
Alert Types
| Type | Trigger |
|---|---|
| Down | Site is unreachable or returns error status |
| Degraded | Response time exceeds threshold |
| JS Error | JavaScript error detected |
| Checkout Failed | Checkout flow step failed |
| Dependency Failing | A monitored third-party dependency serves an error, a stub, or a too-small response |
| Consent Violation | Consent Guard observed tracking requests firing without a consent decision |
| DNS Change | A monitored DNS record changed (NS/MX changes flagged as a possible hijack) |
| DNS Blocklist | A resolved IP was found on a DNS blocklist |
| Health Issue | A Magento health collector reported degraded/critical status |
| Security Advisory | A published CVE affects your store's Magento version (and no matching patch was detected) |
Incident-severity alerts (Down, Checkout Failed, Dependency Failing, Consent Violation, security compromises, and security advisories) always page instantly. Lower-severity alerts can roll into a daily digest depending on your channel's delivery mode.
Alert Lifecycle
Created → Notified → Resolved/Acknowledged
Created
When an issue is first detected, an alert is created.
Notified
Notifications are sent through all configured channels (email, Slack, Discord, etc.).
Resolved
The alert auto-resolves when:
- The site returns to healthy status
- It stays healthy for the configured number of consecutive checks (anti-flap confirmation; default 2)
Acknowledged
Manually acknowledge an alert to stop notifications while investigating.
Alert Deduplication
Pulsar prevents alert fatigue through intelligent deduplication:
- Multiple failures of the same type are grouped
- Notifications are only sent for new issues
- Resolved alerts include downtime duration
Notification Channels
Configure how you receive alerts:
| Channel | Use Case |
|---|---|
| Default, always-on alerting | |
| Slack | Team visibility, quick response |
| Discord | Team chat integration |
| PagerDuty | On-call escalation |
Muting Alerts
During maintenance windows, you can mute alerts:
- Open the site in Pulsar
- Click Mute in the toolbar
- Checks continue but alerts are suppressed
- Click Unmute when maintenance is complete
Muting is per-site. Use it during deployments or known maintenance.
Alert History
View past alerts for a site:
- Navigate to the site
- Click Alerts tab
- Filter by date range or status
How long historical data is retained depends on your plan (from 7 to 365 days).