Alerts & Incidents

How incidents work

When a monitor fails, Blind Spot opens an incident and alerts every eligible channel. When the monitor recovers, the incident closes and a recovery alert is sent.

Routing rules

• Default: all channels receive all severities.
• Custom: route alerts per monitor and severity to trim noise.
• Reminders: if an incident stays unresolved, reminders follow your Alert Cooldown setting (default 5 minutes).
• Acknowledged incidents: acknowledging an incident stops reminder alerts until recovery.

Links and next steps

Alerts include quick links back to Blind Spot Monitor and a short “recommended next steps” checklist so your team can respond faster. Links take you straight to the relevant incident or monitor in the embedded app.

For App Library status monitors, recommended next steps are tailored to the specific app (for example, Klaviyo vs Recharge) and include common-impact guidance plus practical “what to do now / how to prepare next time” tips.

You’ll also see the recommended next steps directly on the incident in Incidents, along with helpful context like the target URL, observed status, latency, and estimated impact (if you’ve configured revenue inputs).

If you want to adjust playbook guidance for a vendor, open Monitors, find the Status Page monitor, and click Playbook.

Delivery history

If you open an incident from an alert link, Blind Spot highlights that incident and shows:

• Recent delivery attempts (per channel), so you can quickly see what was sent and what failed
• Recent automation actions (for supported native integrations), so you can confirm what Blind Spot paused/resumed

Evidence bundle export

From the Incidents page, you can download an evidence bundle for an incident. This is useful when you need to share details with a vendor support team or request incident credits.

The evidence bundle includes:

• The incident timeline (started, acknowledged, resolved)
• Recent delivery attempts (what sent/failed)
• Recent automation actions (for supported native integrations like Meta Ads and Google Ads)
• Recent monitor checks around the incident window
• Estimated impact (if you’ve configured revenue inputs)

Quiet hours (Pro)

Quiet hours suppress non-critical alerts during the hours and days you choose. Critical alerts still get through.

Escalation (Pro)

If escalation is enabled, Blind Spot sends a one-time CRITICAL escalation alert when an incident stays unacknowledged past your selected delay (default 15 minutes). This is designed for “wake someone up” channels like SMS or a dedicated Slack channel.

Test alerts

Use Settings → Send Test Alert any time to confirm deliverability to your connected channels. Test alerts are sent to every connected channel that’s eligible for your plan.

What you’ll see in alerts

Blind Spot keeps alert messages short and merchant-friendly. For example, network issues are summarized as:

• “Timed out reaching the server.”
• “Couldn’t resolve the domain (DNS issue).”
• “Secure connection failed (TLS/SSL issue).”

Example payload

{
  "type": "incident",
  "incidentEvent": "opened",
  "severity": "HIGH",
  "shopId": "your-store.myshopify.com",
  "monitorId": "mon_123",
  "monitorType": "HTTP",
  "monitorName": "Checkout URL",
  "url": "https://your-store.myshopify.com/checkout",
  "statusCode": 500,
  "latencyMs": 120,
  "incidentId": "inc_456",
  "message": "Returned HTTP 500 (expected 200).\nURL: https://your-store.myshopify.com/checkout",
  "timestamp": "2025-12-21 16:12:00 UTC",
  "recommendedActions": [
    "Open Blind Spot Monitor and acknowledge the incident to stop reminders.",
    "Check Shopify Status and any recent theme/app changes around the time the incident started.",
    "Try reaching checkout from both desktop and mobile; if you changed payment/shipping settings recently, review those changes."
  ],
  "links": {
    "settings": "https://admin.shopify.com/store/your-store/apps/blindspot-monitor/app/settings",
    "billing": "https://admin.shopify.com/store/your-store/apps/blindspot-monitor/app/billing",
    "incidents": "https://admin.shopify.com/store/your-store/apps/blindspot-monitor/app/incidents",
    "monitors": "https://admin.shopify.com/store/your-store/apps/blindspot-monitor/app/monitors",
    "incident": "https://admin.shopify.com/store/your-store/apps/blindspot-monitor/app/incidents?incidentId=inc_456",
    "monitor": "https://admin.shopify.com/store/your-store/apps/blindspot-monitor/app/monitors?monitorId=mon_123"
  }
}

Troubleshooting

• No alerts? Confirm the channel is connected, run a test alert, and verify routing (monitor + severity).
• Too noisy? Increase Alert Cooldown, route only CRITICAL/HIGH to paging channels, and use quiet hours for non-critical alerts.
• Not waking anyone up? Enable escalation (Pro) and route CRITICAL to your fastest channels (SMS/Slack).