PagerDuty Alerts - Infisical

Create PagerDuty incidents when certificate events occur using the Events API v2. Get paged when certificates are about to expire or are revoked.

<Info> Alerts are configured per Application and apply to all certificates within that Application. </Info>

Create a PagerDuty Alert

<Steps> <Step title="Create a PagerDuty Service"> 1. Go to **PagerDuty → Services → Service Directory → New Service** 2. Name the service (e.g., "Infisical PKI Alerts") 3. Select **Events API v2** as the integration 4. Click **Create Service**

<Note>
  To use an existing service, go to **Integrations → Add an Integration → Events API v2**.
</Note>

</Step> <Step title="Copy the Integration Key"> After creating the service, copy the 32-character **Integration Key** from the **Integrations** tab.

<Note>
  Keep your integration key secure. Anyone with access can send events to your PagerDuty service.
</Note>

</Step> <Step title="Navigate to your Application"> Go to **Certificate Manager → Applications** and select your Application. </Step> <Step title="Create an alert"> Go to the **Settings** tab and find the **Alerting** section. Click **Create Alert**.

| Setting | Description |
|---------|-------------|
| **Alert Type** | Certificate Expiration, Issuance, Renewal, or Revocation |
| **Alert Name** | A slug-friendly name like `tls-expiry-alert` |
| **Description** | Optional context about this alert |
| **Alert Before** | *(Expiration only)* Time before expiry to trigger, e.g., `30d` |

</Step> <Step title="Add a PagerDuty channel"> Add a **PagerDuty** notification channel and paste the integration key. </Step> </Steps>

Severity Mapping

Infisical automatically maps alert types to PagerDuty severity levels.

Expiration Alerts

Time Until Expiry	PagerDuty Severity
≤ 7 days	`critical`
≤ 14 days	`error`
≤ 30 days	`warning`
> 30 days	`info`

Other Alert Types

Alert Type	PagerDuty Severity
Certificate Issuance	`info`
Certificate Renewal	`info`
Certificate Revocation	`warning`

Incident Grouping

Alerts with the same alert ID are grouped into the same PagerDuty incident via dedup_key. Repeated triggers update the existing incident rather than creating duplicates.

What's Next?

<CardGroup cols={2}> <Card title="Webhook Alerts" icon="webhook" href="/documentation/platform/pki/applications/alerting/webhook-alerts"> Send alerts to custom HTTP endpoints. </Card> <Card title="Slack Alerts" icon="slack" href="/documentation/platform/pki/applications/alerting/slack-alerts"> Send alerts to a Slack channel. </Card> <Card title="Certificate Syncs" icon="arrows-rotate" href="/documentation/platform/pki/applications/certificate-syncs/overview"> Push certificates to cloud destinations. </Card> <Card title="Managing Certificates" icon="list" href="/documentation/platform/pki/applications/certificates"> View and manage certificates. </Card> </CardGroup>