Inputs

The notify function in the PagerdutyProvider class takes the following parameters:

kwargs (dict):
    title (str): Title of the alert or incident. *Required*
    alert_body (str): UTF-8 string of custom message for alert. Shown in incident body for events, and in the body for incidents. *Required for events, optional for incidents*
    dedup (str | None): Any string, max 255 characters, used to deduplicate alerts for events. *Required for events, optional for incidents*
    service_id (str): ID of the service for incidents. *Required for incidents, optional for events*
    body (dict): Body of the incident. *Required for incidents, optional for events*
    requester (str): Requester of the incident. *Required for incidents, optional for events*
    incident_key (str | None): Key to identify the incident. If not given, a UUID will be generated. *Required for incidents, optional for events*

Authentication Parameters

The PagerdutyProviderAuthConfig class takes the following parameters: python routingkey (str | None): Routing key, which is an integration or ruleset key. Optional, default is None. _Required for events, optional for incidents**No apikey (str | None): API key, which is a user or team API key. Optional, default is None. _Required for incidents, optional for events**

Connecting with the Provider

To use the PagerdutyProvider, you’ll need to provide either a routing_key or an api_key.

You can find your integration key or routing key in the PagerDuty web app under Configuration > Integrations, and select the integration you want to use. You can find your API key in the PagerDuty web app under Configuration > API Access.

The routing_key is used to post events to Pagerduty using the events API. The api_key is used to create incidents using the incidents API.

Notes

The provider uses either the events API or the incidents API to create an alert or an incident. The choice of API to use is determined by the presence of either a routing_key or an api_key.