BlackTide Alerts Drive Your PagerDuty Escalations
When BlackTide detects a degraded node, a failed on-chain check, or a breached SLA, it triggers a PagerDuty incident immediately — routing through your existing escalation policies, on-call schedules, and acknowledgment workflows. No duplicate tooling, no manual incident bridges.
Why monitoring without escalation policies breaks at scale
- Alerts go to a shared email or Slack channel — no one owns the incident, no one is paged, and the first user complaint is what triggers a response
- On-call schedules exist in PagerDuty but your monitoring tool has no idea who is actually on-call right now, so everyone gets notified or no one does
- Acknowledging an incident in your monitoring dashboard does not suppress the PagerDuty page — engineers get double-paged for the same event, creating alert fatigue. PagerDuty incident management guide
- Resolving an incident requires manual action in two separate tools — monitoring dashboard and PagerDuty — which slows MTTR and creates data inconsistencies
- Escalation policies are misconfigured for Web3 infrastructure because generic monitoring tools fire incidents with no blockchain context, making severity assessment impossible without investigating first
How BlackTide and PagerDuty work together
- BlackTide triggers a PagerDuty incident the moment a monitor fails, using your configured service key so the alert routes through your existing escalation policies automatically
- Incident metadata includes monitor name, affected chain, failure type, check interval, and a direct link to the BlackTide incident timeline — on-call engineers have full context at page time
- Bidirectional sync: acknowledging an incident in PagerDuty suppresses re-alerting in BlackTide; resolving in either platform propagates to the other within seconds
- Severity mapping lets you configure which BlackTide alert levels trigger which PagerDuty urgency — critical node failures page immediately, warning-level degradation creates a low-urgency incident
Capabilities
Full PagerDuty lifecycle support
BlackTide does not just fire and forget — it participates in the full PagerDuty incident lifecycle.
Configure a PagerDuty service key per monitor or alert rule. Incidents route through your existing escalation policies, on-call schedules, and notification rules exactly as configured in PagerDuty — no changes to your existing incident workflow required. Teams with multiple on-call rotations (web3 infra, DeFi protocol, validator ops) can map each BlackTide monitor group to the appropriate PagerDuty service.
BlackTide incidents respect your PagerDuty on-call schedule without any manual configuration. When a P1 node failure triggers at 3 AM, PagerDuty routes the page to whoever is on-call at that moment based on your schedule — BlackTide doesn't need to know who that is. Your existing escalation layers, overrides, and shift handoffs all apply automatically.
Acknowledge an incident in PagerDuty and BlackTide stops re-alerting. Resolve it in BlackTide and PagerDuty marks the incident resolved. The two platforms stay in sync so your incident state is never inconsistent — no manual reconciliation at the end of an on-call shift to clean up stale incidents.
Map BlackTide alert severities (P1, P2, P3) to PagerDuty urgency levels (high, low). P1 production failures trigger an immediate high-urgency page; P3 degradation warnings create low-urgency incidents for review during business hours. This lets your escalation policies apply the right notification rules for each severity level.
Every PagerDuty incident triggered by BlackTide includes: monitor name, affected chain or endpoint, failure type (timeout, block height lag, smart contract error), last known healthy state, and a direct deep-link to the BlackTide incident timeline. On-call engineers can assess and begin investigating before opening a single additional tab.
Use Cases
Who uses BlackTide with PagerDuty
Validator team with 24/7 on-call rotation
Your validators run across 10 Cosmos SDK chains. A single missed block can cascade into slashing. BlackTide detects the issue in 30 seconds and fires a PagerDuty incident through your validator on-call escalation policy — the right engineer is paged before any slashing occurs.
DeFi protocol with a defined incident severity matrix
Your protocol has a documented P1-P3 severity matrix. BlackTide maps each monitor failure type to the correct severity and fires PagerDuty incidents with the appropriate urgency — P1 smart contract failures page immediately, P3 latency degradation creates a ticket for next-business-hours review.
Enterprise Web3 team with compliance requirements
Regulators require documented incident response times. BlackTide triggers PagerDuty incidents with millisecond-accurate timestamps, and PagerDuty logs acknowledgment and resolution times — giving you a complete, auditable incident lifecycle record for every monitoring event.
Frequently asked questions
How do I connect BlackTide to PagerDuty?
Does BlackTide support PagerDuty escalation policies?
What happens when I acknowledge an incident in PagerDuty?
Can different monitors trigger different PagerDuty services?
Does BlackTide support PagerDuty Opsgenie as well?
Ready to connect BlackTide to PagerDuty?
Set up in 5 minutes. Your existing escalation policies and on-call schedules apply automatically.