docs/documentation/platform/pki/alerting/pagerduty-alerts.mdx
Infisical can send PKI certificate alert notifications to PagerDuty using the Events API v2. This guide walks through creating a PagerDuty service and configuring a PagerDuty alert.
4. Click **Create Service**
If you want to use an existing service, go to the service's **Integrations** tab → **Add an Integration** → select **Events API v2**.
Here's some guidance for each field in the alert configuration sequence:
- **Alert Type**: The type of certificate event to alert on. Options are **Certificate Expiration**, **Certificate Issuance**, **Certificate Renewal**, and **Certificate Revocation**.
- **Alert Name**: A slug friendly name for the alert such as `tls-expiry-alert`.
- **Description**: An optional description for the alert.
- **Alert Before** *(Expiration alerts only)*: The time before certificate expiration to trigger the alert such as 30 days denoted by `30d`.
- **Filters**: A list of filters that determine which certificates the alert applies to. Each row includes a **Field**, **Operator**, and **Value** to match against. For example, you can filter for certificates with a common name containing `example.com` by setting the field to **Common Name**, the operator to **Contains**, and the value to `example.com`.
For expiration alerts, Infisical automatically maps the time remaining until certificate expiry to a PagerDuty event severity:
| Time Until Expiry | PagerDuty Severity |
|---|---|
| ≤ 7 days | critical |
| ≤ 14 days | error |
| ≤ 30 days | warning |
| > 30 days | info |
| Alert Type | PagerDuty Severity |
|---|---|
| Certificate Issuance | info |
| Certificate Renewal | info |
| Certificate Revocation | warning |
Alerts with the same alert ID are grouped into the same PagerDuty incident via dedup_key. This means repeated triggers update the existing incident rather than creating duplicates.