OpsgenieExecution

Send a notification with the execution information via Opsgenie

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, and (if failed) the task that led to a failure.

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 OpsgenieAlert task.

yaml
type: "io.kestra.plugin.notifications.opsgenie.OpsgenieExecution"

Send notification on a failed flow execution via Opsgenie

yaml
id: failure_alert
namespace: company.team

tasks:
  - id: send_alert
    type: io.kestra.plugin.notifications.opsgenie.OpsgenieExecution
    url: "{{ secret('OPSGENIE_REQUEST') }}" # format: 'https://api.opsgenie.com/v2/alerts/requests/xxxxxxyx-yyyx-xyxx-yyxx-yyxyyyyyxxxx'
    message: "Kestra Opsgenie alert"
    alias: ExecutionError
    responders:
      4513b7ea-3b91-438f-b7e4-e3e54af9147c: team
      bb4d9938-c3c2-455d-aaab-727aa701c0d8: user
      aee8a0de-c80f-4515-a232-501c0bc9d715: escalation
      80564037-1984-4f38-b98e-8a1f662df552: schedule
    visibleTo:
      4513b7ea-3b91-438f-b7e4-e3e54af9147c: team
      bb4d9938-c3c2-455d-aaab-727aa701c0d8: user
    priority: P1
    tags:
      - ExecutionError
      - Error
      - Fail
      - Execution
    authorizationToken: sampleAuthorizationToken
    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

Alert creation URL

Dynamic YES

Map of variables to use for the message template

Dynamic YES

GenieKey. Authorization token from Opsgenie

Dynamic YES

Custom fields to be added on notification

Dynamic YES

Custom message to be added on notification

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

Map of variables to use for the message template

Dynamic YES

Options

The options to set to customize the HTTP client

Dynamic YES

Opsgenie alert payload

Dynamic YES

Map of variables to use for the message template

SubType string

Dynamic YES

Map of variables to use for the message template

SubType string

Dynamic YES

Map of variables to use for the message template

Dynamic YES

Map of variables to use for the message template

SubType string

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 YES

Default UTF-8

Dynamic YES

Default 10485760

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.

​Opsgenie​Execution

OpsgenieExecution