Documentation
PagerDuty and Opsgenie
Connecting REAP to PagerDuty (opens in a new tab) and Opsgenie (opens in a new tab): prerequisites, permissions, setup, what is read and written, troubleshooting.
Overview
Planned, not available today: REAP would route investigation summaries to the on-call engineer and read schedules to address the right person. Today the Investigation Window reaches on-call through ServiceNow (opens in a new tab), Slack (opens in a new tab) or Microsoft Teams (opens in a new tab).
Status Planned Not available today and without a date. The sections below describe the design, so a reviewer can see what the integration would read and write; tell us if you need it.
Prerequisites
- PagerDuty (opens in a new tab) or Opsgenie (opens in a new tab) account with API access
- A dedicated service/integration for REAP
Permissions requested
| Scope | Permission | Why |
|---|---|---|
| Read | Schedules, on-call, incidents | Routing and context |
| Write | Create/annotate incidents on the REAP service | Prioritized alerts and summaries |
Setup
- Create a service (PagerDuty (opens in a new tab)) or team integration (Opsgenie (opens in a new tab)) for REAP; note the key.
- In REAP: Integrations → On-call → provider, key; map REAP severities.
- Test: a test alert reaches the on-call engineer with the Investigation Window link.
What REAP reads
- Schedules, current on-call, incident state
What REAP writes
- Alerts with summary and evidence link; notes on resolution
Troubleshooting
| Symptom | Likely cause | Check |
|---|---|---|
| Alerts not received | Wrong service key or routing rule | Check the integration key |
| Duplicates | Both the monitoring tool and REAP paging | Decide which system pages for which alert class |
Changelog
- September 2026 · page created (draft).
Last reviewed: October 7, 2026 (draft) · Owner: solutions engineering · Corrections: security@reapnet.ai