PagerDuty

This capability is only available to BYOC deployments. Check out our pricing page for more information about subscription plans and the available deployment modes.

Generate PagerDuty Routing (Integration) Key

1. In PagerDuty, Go to the your desired service, then click on integrations tab

2. Click on "Add an integration" or "+ Add another integration"

3. Select "Events API V2" Integration, and click on Add.

   

   Events API V2
4. Copy the Integration Key.

   

Create an PagerDuty Connected App in groundcover

1. In groundcover, go to Settings → Connected-Apps.

2. Click on PagerDuty.

1. Select a name and paste your routing key.

1. Test the connection (Optional) - sends a test alert to verify the integration.

2. Save

PagerDuty Event Payload

groundcover sends events to PagerDuty using the Events API V2 format:

{
  "routing_key": "<your-routing-key>",
  "event_action": "trigger|resolve",
  "dedup_key": "{{ fingerprint }}",
  "payload": {
    "summary": "{{ summary }}",
    "severity": "critical|error|warning|info",
    "source": "groundcover",
    "custom_details": {
      "monitor_name": "{{ monitor_name }}",
      "value": "{{ value }}",
      "threshold": "{{ threshold }}",
      "renotification_count": 0,
      "labels": { ... }
    }
  },
  "links": [
    { "href": "{{ urls.issue }}", "text": "View Issue" },
    { "href": "{{ urls.monitor }}", "text": "View Monitor" }
  ]
}

Key Fields for Automation

renotification_count: Starts at 0 for the first notification and increments with each re-notification while the alert is firing. This field is included in every event payload and can be used in PagerDuty Event Orchestration for automation:

• renotification_count == 0 - First notification

• renotification_count > 0 - Re-notification (alert still firing)

The counter resets to 0 when the alert resolves and fires again.

dedup_key: Uses the alert fingerprint to group related events. PagerDuty will deduplicate events with the same dedup_key.

Severity Mapping

groundcover severities are mapped to PagerDuty severities:

groundcover	PagerDuty
S1	critical
S2	error
S3	warning
S4	info