PagerDuty Integration

Field	Value
Document ID	ASCEND-ENT-003
Version	1.0.0
Last Updated	December 19, 2025
Author	Ascend Engineering Team
Publisher	OW-KAI Technologies Inc.
Classification	Enterprise Client Documentation
Compliance	SOC 2 CC6.1/CC6.2, PCI-DSS 7.1/8.3, HIPAA 164.312, NIST 800-53 AC-2/SI-4

Reading Time: 6 minutes | Skill Level: Advanced

Overview

ASCEND integrates with PagerDuty for on-call alerting and incident management. Route critical AI governance events to your incident response team with intelligent escalation policies.

Configuration

Connect PagerDuty

curl -X POST "https://pilot.owkai.app/api/pagerduty/configure" \
  -H "Authorization: Bearer <admin_jwt>" \
  -H "Content-Type: application/json" \
  -d '{
    "api_key": "your-pagerduty-api-key",
    "service_id": "P1234567",
    "escalation_policy_id": "PABCDEF",
    "default_severity": "warning",
    "auto_resolve": true
  }'

Event Routing

{
  "routing_rules": [
    {
      "event_type": "security.kill_switch",
      "severity": "critical",
      "service_id": "P_SECURITY",
      "escalation_policy_id": "P_CRITICAL"
    },
    {
      "event_type": "security.alert",
      "severity": "high",
      "service_id": "P_SECURITY"
    },
    {
      "event_type": "action.denied_critical",
      "severity": "warning",
      "service_id": "P_AIOPS"
    }
  ]
}

Event Types

ASCEND Event	PagerDuty Severity	Use Case
security.kill_switch	Critical	Immediate response
security.alert	High	Security incident
action.denied_critical	Warning	Review needed
agent.killed	High	Agent emergency
system.degraded	Warning	Performance issue

Incident Payload

{
  "routing_key": "your-integration-key",
  "event_action": "trigger",
  "dedup_key": "ascend-act_abc123",
  "payload": {
    "summary": "High-risk AI action denied: trading-bot-001 trade_execution",
    "severity": "warning",
    "source": "ascend-governance",
    "component": "trading-bot-001",
    "group": "ai-agents",
    "class": "action.denied",
    "custom_details": {
      "action_id": "act_abc123",
      "agent_id": "trading-bot-001",
      "risk_score": 85,
      "risk_level": "critical",
      "denial_reason": "Exceeds trading limit"
    }
  },
  "links": [
    {
      "href": "https://dashboard.owkai.app/actions/act_abc123",
      "text": "View in ASCEND"
    }
  ]
}

Escalation Policies

Configure Escalation

curl -X PUT "https://pilot.owkai.app/api/pagerduty/escalation" \
  -H "Authorization: Bearer <admin_jwt>" \
  -d '{
    "critical_events": {
      "escalation_policy_id": "P_CRITICAL",
      "escalation_delay_minutes": 5
    },
    "high_events": {
      "escalation_policy_id": "P_HIGH",
      "escalation_delay_minutes": 15
    },
    "warning_events": {
      "escalation_policy_id": "P_DEFAULT",
      "escalation_delay_minutes": 30
    }
  }'

Auto-Resolution

When ASCEND events are resolved, incidents are automatically closed:

{
  "event_action": "resolve",
  "dedup_key": "ascend-act_abc123",
  "payload": {
    "summary": "Action approved and executed successfully",
    "custom_details": {
      "resolved_by": "admin@company.com",
      "resolution": "Approved after review"
    }
  }
}

Best Practices

1. Set appropriate severities - Reserve critical for true emergencies
2. Use dedup keys - Prevent duplicate incidents for same event
3. Configure auto-resolve - Reduce alert fatigue
4. Test routing - Verify incidents reach correct teams

---

Document Version: 1.0.0 | Last Updated: December 2025