Connecting Sentro to PagerDuty and OpsGenie: A Complete Guide

Why integrate with PagerDuty or OpsGenie

Slack and email are great for awareness. PagerDuty and OpsGenie are great for accountability. They handle on-call rotations, escalation chains, and acknowledged states in ways that general-purpose chat tools don't. If your team has an on-call schedule, connecting Sentro to your incident management tool means the right person gets paged — not just notified.

Both integrations are available on Sentro's Max plan ($19/mo).

Setting up PagerDuty

Step 1: Create a PagerDuty service integration

1. In PagerDuty, go to Services and click an existing service (or create a new one called "Sentro Monitoring").
2. Click the Integrations tab, then Add an Integration.
3. Search for Events API V2 and click Add.
4. Copy the Integration Key that appears — it's a 32-character string.

Step 2: Add the channel in Sentro

1. In the Sentro dashboard, go to Alerts → Add Channel.
2. Select PagerDuty as the type.
3. Give it a name (e.g. "PagerDuty Production") and paste the integration key.
4. Click Create Channel.

Step 3: Attach to an alert rule or escalation policy

You can use the PagerDuty channel in a regular alert rule, or as a step in an escalation policy. The most common pattern: create an escalation policy where Slack fires immediately (Step 0) and PagerDuty fires after 15 minutes if the incident is still open (Step 1).

How Sentro's PagerDuty integration works

• Trigger: When a DOWN or DEGRADED incident fires, Sentro sends an event to PagerDuty's Events API v2 with event_action: "trigger". The severity is critical for DOWN and warning for DEGRADED.
• Deduplication: Sentro uses dedup_key: "sentro-{monitorId}", so multiple alerts for the same monitor never create duplicate PagerDuty incidents.
• Auto-resolve: When the incident resolves in Sentro, it automatically sends event_action: "resolve" to PagerDuty. Your PagerDuty incident closes itself — no manual cleanup.

# Example: what Sentro sends to PagerDuty Events API
{
  "routing_key": "YOUR_INTEGRATION_KEY",
  "event_action": "trigger",
  "dedup_key": "sentro-01jwx4abc123",
  "payload": {
    "summary": "api.yourservice.com is DOWN",
    "severity": "critical",
    "source": "Sentro Monitor",
    "custom_details": {
      "monitor": "Production API",
      "cause": "Expected status 200, got 503"
    }
  }
}

Setting up OpsGenie

Step 1: Create an OpsGenie API key

1. In OpsGenie, go to Settings → API key management.
2. Click Add new API key, give it a name (e.g. "Sentro"), and check Write access.
3. Copy the generated API key.

Step 2: Add the channel in Sentro

1. Go to Alerts → Add Channel, select OpsGenie.
2. Paste the API key and save.

Sentro creates a P1 alert on DOWN, P3 on DEGRADED, and automatically closes the alert when the incident resolves. The alert alias is set to sentro-{monitorId} for deduplication — just like PagerDuty.

Testing the integration

Once the channel is set up, you can test it by temporarily lowering a monitor's confirmations to 1 and pointing it at a URL that returns an error. The incident fires, PagerDuty/OpsGenie gets triggered, and when you resolve the Sentro incident, both systems close automatically.

Tip: Use the alert channel test button in Sentro's dashboard to send a test payload before relying on it in production.