How to create a PagerDuty integration with RMON

Send incidents to PagerDuty

Choose the PagerDuty service responsible for the monitored application. You need permission to manage that service's integrations and to create a PagerDuty destination in RMON. Use a test service or agree a test window with the on-call team: a channel test can trigger an incident.

1. Prepare the service integration

  1. Open PagerDuty's Service Directory and select the service that should receive the incidents.
  2. Review the service's escalation policy and confirm the intended responders.
  3. Add an Events API V2 integration under the service's integrations.
  4. Copy its Integration Key for RMON. Use the key belonging to this integration rather than an account API key.

PagerDuty's service and integration guide covers the required service permissions and integration setup.

2. Save and test the RMON destination

  1. Select the RMON group owning the checks and open Channels.
  2. In the PagerDuty section, click + Add.
  3. Paste the integration key into Token and give Channel name a clear label such as Customer API on-call.
  4. Save, then click Test during the agreed test window.
  5. Open the selected PagerDuty service and confirm the test reaches it. Review and close the test incident according to your team's process.

The RMON channel name is a label for selecting the destination. The integration key determines the PagerDuty service receiving the event.

3. Assign checks and verify recovery

Edit a check, open Notifications, select Customer API on-call under PagerDuty and choose an appropriate priority. Add the responders' runbook URL and save.

Use a disposable check to generate a failure and subsequent recovery. Confirm the incident appears in the intended service and that the corresponding recovery resolves it. See the complete alert test.

Troubleshoot the destination

Scroll horizontally to view the full table.

SymptomWhat to check
Channel test is rejectedThe integration key is current, the Events API V2 integration belongs to the intended service, and RMON can reach PagerDuty.
Event reaches the wrong serviceReplace Token with the integration key from the correct service; changing only Channel name does not reroute events.
Incident exists but nobody is notifiedReview the service's escalation policy, schedules and notification rules in PagerDuty.
Incident remains open after recoveryConfirm a fresh healthy result in RMON and inspect recovery-delivery errors before changing the incident manually.