PagerDuty Integration | Cloudmon

PagerDuty

Third Party Integration

PagerDuty

Automatically trigger incidents in PagerDuty when Cloudmon alarms fire, and optionally resolve them when the alarm clears.

Overview

The PagerDuty integration allows Cloudmon to trigger incidents in a PagerDuty service when an alarm fires. If automatic resolution is enabled, Cloudmon also resolves the incident when the alarm clears, so on-call responders are paged for active alarms and the incident closes when the alarm does.

Before You Begin: Collect Details from PagerDuty

Collect the following details in PagerDuty before you configure the integration in Cloudmon.

FieldDescription
Integration KeyCreated by adding an Events API v2 integration to a PagerDuty service. See Services and Integrations.
Escalation PolicySet on the service. It controls who is paged when this integration triggers an incident. See Escalation Policies and Schedules.

The Integration Key is stored encrypted and is never shown again after saving. Test Connection sends a test event to PagerDuty and immediately resolves it, so verifying the key may briefly show a "Cloudmon test connection" entry in the service's activity timeline. This is safe to ignore.

Step 1: Configure in Cloudmon

  1. Navigate to Settings → General Settings → Integrations.
  2. Locate the PagerDuty widget and click the + Service button.
  3. In the PagerDuty Service section, fill in the fields as described in the first table.
  4. Click Test Connection to verify the integration key.
  5. In the Incident Settings section, configure how alarms become incidents, as described in the second table.
  6. Click Save.

PagerDuty Service

FieldDescription
Integration NameA display name to identify this integration in Cloudmon, such as "On Call Escalation".
PagerDuty URLOptional. Your PagerDuty URL, for example acme.pagerduty.com.
Integration KeyThe Events API v2 Integration Key copied from the PagerDuty service.
Sender NameThe sender name used for incidents from Cloudmon. The default is Cloudmon.

Incident Settings

FieldDescription
Incident SummaryThe text used as the incident summary. The default is $device_name is $severity - $title. Type $ to pick a replaceable tag from the list, and use the reset icon beside the field to restore the default.
Trigger Incidents For SeveritiesSelect the alarm severities that trigger an incident: Down, Critical, Trouble and Attention. At least one must be selected.
Resolve Incident Automatically When Alarm ClearsEnabled by default. When enabled, Cloudmon resolves the incident when the alarm clears. When disabled, the incident must be resolved manually.
Incident TagsOptional. Type a tag and press Enter to add it. Add as many as you need.

The Reset button restores the form to its default values, and Close exits without saving.

Step 2: Enable in Alarm Rules

  1. Navigate to Settings → Configurations → Alarm Rules.
  2. Click the Add button to create a new alarm rule, or open an existing one.
  3. Add a trigger and configure the alarm conditions.
  4. In the THEN section, enable Third Party Services and select the configured PagerDuty integration from the dropdown.
  5. Click Save.

When this alarm fires, Cloudmon creates an incident in PagerDuty automatically, for the severities selected in the integration.