Skip to main content

​
PagerDuty Integration

Integrate with PagerDuty to automatically create incidents from Roboticks alerts, leveraging your existing on-call schedules and escalation policies.

​
Features

  • Automatic incident creation from alerts
  • Severity mapping to PagerDuty urgency
  • Deduplication to prevent alert storms
  • Incident resolution when alerts clear
  • Custom routing to different services

​
Setup

​
Step 1: Create a Service in PagerDuty

  1. Log in to your PagerDuty account
  2. Go to Services > Service Directory
  3. Click New Service or use an existing service
  4. Note the service name for later
We recommend creating a dedicated service for Roboticks alerts to keep your incident routing organized.

​
Step 2: Add Events API v2 Integration

  1. In your PagerDuty service, go to the Integrations tab
  2. Click Add Integration
  3. Select Events API v2
  4. Copy the Integration Key (32-character alphanumeric string)

​
Step 3: Configure in Roboticks

  1. Go to Settings > Integrations in Roboticks
  2. Find PagerDuty and click Add
  3. Enter a name for this integration (e.g., “PagerDuty Production”)
  4. Paste the Integration Key
  5. Click Create

​
Configuration Options

OptionDescriptionRequired
Integration KeyEvents API v2 integration keyYes
NameDisplay name for this integrationYes
DescriptionOptional descriptionNo
EnabledToggle the integration on/off-
Enabled for AlertsCreate incidents from alerts-

​
Severity Mapping

Roboticks alert severities map to PagerDuty urgency:
Roboticks SeverityPagerDuty Urgency
CriticalHigh
WarningLow
InfoLow (suppressed by default)

​
How It Works

​
Deduplication

Roboticks uses a consistent deduplication key based on:
  • Alert rule ID
  • Device ID
  • Project ID
This prevents multiple incidents from the same ongoing issue.

​
Auto-Resolution

When an alert clears in Roboticks, a resolve event is sent to PagerDuty, automatically closing the incident.

​
Example Incident

When an alert triggers, PagerDuty receives: 
{
  "routing_key": "your-integration-key",
  "event_action": "trigger",
  "dedup_key": "roboticks-alert-123-device-456",
  "payload": {
    "summary": "Device Offline: warehouse-robot-01",
    "severity": "critical",
    "source": "roboticks",
    "custom_details": {
      "device_id": 456,
      "device_name": "warehouse-robot-01",
      "alert_rule": "Device Offline",
      "project": "warehouse"
    }
  },
  "links": [{
    "href": "https://app.roboticks.io/devices/456",
    "text": "View in Roboticks"
  }]
}

​
Troubleshooting

  • Verify the Integration Key is correct
  • Check that the PagerDuty service is not disabled
  • Review integration logs in Roboticks for errors
  • Ensure deduplication is working by checking the dedup_key
  • Verify your PagerDuty service doesn’t have conflicting alert grouping rules
  • Check that the integration is still enabled
  • Verify the alert actually cleared in Roboticks
  • Review PagerDuty’s incident timeline for resolve events
Check your alert severity in Roboticks. Critical alerts map to High urgency, all others to Low.

​
Best Practices

  1. Create dedicated services - Separate services for different environments (production, staging)
  2. Configure escalation policies - Ensure someone is always on-call for critical alerts
  3. Use PagerDuty’s alert grouping - Group related incidents to reduce noise
  4. Set up maintenance windows - Suppress alerts during planned maintenance