Send a PagerDuty message with the execution information.

The message will include a link to the execution page in the UI along with the execution ID, namespace, flow name, the start date, duration, and the final status of the execution. If failed, then the task that led to the failure is specified.

Use this notification task only in a flow that has a Flow trigger. Don't use this notification task in errors tasks. Instead, for errors tasks, use the PagerDutyAlert task.

yaml
type: "io.kestra.plugin.notifications.pagerduty.pagerdutyexecution"

Send a PagerDuty notification on a failed flow execution.

yaml
id: failure_alert
namespace: company.team

tasks:
  - id: send_alert
    type: io.kestra.plugin.notifications.pagerduty.PagerDutyExecution
    url: "{{ secret('PAGERDUTY_EVENT') }}" # format: https://events.pagerduty.com/v2/enqueue
    payloadSummary: "PagerDuty Alert"
    deduplicationKey: "dedupkey"
    routingKey: "routingkey"
    eventAction: "acknowledge"
    executionId: "{{trigger.executionId}}"

triggers:
  - id: failed_prod_workflows
    type: io.kestra.plugin.core.trigger.Flow
    conditions:
      - type: io.kestra.plugin.core.condition.ExecutionStatus
        in:
          - FAILED
          - WARNING
      - type: io.kestra.plugin.core.condition.ExecutionNamespace
        namespace: prod
        prefix: true

Dynamic YES

Min length 1

PagerDuty event URL

Dynamic YES

Custom fields to be added on notification

Dynamic YES

Custom message to be added on notification

Dynamic YES

Deduplication key for correlating triggers and resolves

Dynamic YES

The type of event. Can be trigger, acknowledge or resolve.

Dynamic YES

Default {{ execution.id }}

The execution id to use

Default is the current execution, change it to if you use this task with a Flow trigger to use the original execution.

Dynamic YES

Options

The options to set to customize the HTTP client

Dynamic YES

PagerDuty message payload

Dynamic YES

Max length 1024

Brief text summary of the event, used to generate the summaries/titles of any associated alerts.

Dynamic YES

Integration Key for an integration on a PagerDuty service

Dynamic YES

Map of variables to use for the message template

Dynamic YES

Format duration

The time allowed to establish a connection to the server before failing.

Dynamic YES

Default PT0S

Format duration

The time an idle connection can remain in the client's connection pool before being closed.

Dynamic NO

Default UTF-8

The default charset for the request.

SubType string

Dynamic YES

HTTP headers

HTTP headers to include in the request

Dynamic NO

Default 10485760

The maximum content length of the response.

Dynamic YES

Default PT5M

Format duration

The time allowed for a read connection to remain idle before closing it.

Dynamic YES

Default PT10S

Format duration

The maximum time allowed for reading data from the server before failing.