Urgency and Priority Mapping between SD-WAN and PagerDuty Incidents
Explanation of the urgency and priority mapping between SD-WAN Incident and PagerDuty
Incident.
| Where Can I Use This? | What Do I Need? |
|---|
|
|
- Prisma SD-WAN license
- PagerDuty Notifier CloudBlade
|
This mapping defines the urgency of an incident in PagerDuty based on
its priority in Prisma SD-WAN.
| Prisma SDWAN Incident Priority | PagerDuty Incident Urgency |
|---|
This mapping links a specific Prisma SD-WAN priority to a corresponding
priority level in PagerDuty.
| Prisma SDWAN Incident Priority | PagerDuty Incident Urgency |
|---|
| P1 | First Priority reported by PagerDuty Priority API (Index
0). |
| P2 | Second Priority reported by PagerDuty Priority API (Index
1). |
| P3 | Third Priority reported by PagerDuty Priority Api (Index
2). |
| P4 | Fourth Priority reported by PagerDuty Priority Api (Index
3) |
If PagerDuty does not provide a priority, the CloudBlade
creates an incident without an assigned priority. Additionally, the CloudBlade does not
set the PagerDuty severity field for the incidents it creates.
