ZendutyExecution
ZendutyExecution
type: "io.kestra.plugin.notifications.zenduty.ZendutyExecution"
Send a Zenduty 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, 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 ZendutyAlert task.
Examples
Send a Zenduty notification on a failed flow execution
id: zenduty_failure_alert
namespace: company.team
tasks:
- id: send_alert
type: io.kestra.plugin.notifications.zenduty.ZendutyExecution
url: "https://www.zenduty.com/api/events/{{ secret('ZENDUTY_INTEGRATION_KEY') }}/"
executionId: "{{ trigger.executionId }}"
message: Kestra workflow execution {{ trigger.executionId }} of a flow {{ trigger.flowId }} in the namespace {{ trigger.namespace }} changed status to {{ trigger.state }}
triggers:
- id: failed_prod_workflows
type: io.kestra.plugin.core.trigger.Flow
conditions:
- type: io.kestra.plugin.core.condition.ExecutionStatusCondition
in:
- FAILED
- WARNING
- type: io.kestra.plugin.core.condition.ExecutionNamespaceCondition
namespace: prod
prefix: true
Properties
url
- Type: string
- Dynamic: ✔️
- Required: ✔️
- Min length:
1
Zenduty API endpoint
alertType
- Type: string
- Dynamic: ✔️
- Required: ❌
- Possible Values:
CRITICAL
ACKNOWLEDGED
RESOLVED
ERROR
WARNING
INFO
Event alert type
customFields
- Type: object
- Dynamic: ✔️
- Required: ❌
Custom fields to be added on notification
customMessage
- Type: string
- Dynamic: ✔️
- Required: ❌
Custom message to be added on notification
entityId
- Type: string
- Dynamic: ✔️
- Required: ❌
A unique id for the alert. If not provided, the Zenduty API will create one
executionId
- Type: string
- Dynamic: ✔️
- Required: ❌
- Default:
{{ execution.id }}
The execution id to use
Default is the current execution, change it to {{ trigger.executionId }} if you use this task with a Flow trigger to use the original execution.
message
- Type: string
- Dynamic: ✔️
- Required: ❌
Event title
options
- Type: AbstractHttpOptionsTask-RequestOptions
- Dynamic: ✔️
- Required: ❌
Options
The options to set to customize the HTTP client
payload
- Type: string
- Dynamic: ✔️
- Required: ❌
Zenduty alert request payload
summary
- Type: string
- Dynamic: ✔️
- Required: ❌
Event message. Summary description
templateRenderMap
- Type: object
- Dynamic: ✔️
- Required: ❌
Map of variables to use for the message template
urls
- Type: array
- SubType: string
- Dynamic: ✔️
- Required: ❌
List of URLs related to the alert
Outputs
Definitions
java.nio.charset.Charset
Properties
io.kestra.plugin.notifications.AbstractHttpOptionsTask-RequestOptions
Properties
connectTimeout
- Type:
- string
- string
- Dynamic: ✔️
- Required: ❌
connectionPoolIdleTimeout
- Type:
- string
- string
- Dynamic: ✔️
- Required: ❌
defaultCharset
- Type:
- Charset
- string
- Dynamic: ✔️
- Required: ❌
maxContentLength
- Type:
- integer
- string
- Dynamic: ✔️
- Required: ❌
readIdleTimeout
- Type:
- string
- string
- Dynamic: ✔️
- Required: ❌
readTimeout
- Type:
- string
- string
- Dynamic: ✔️
- Required: ❌
Was this page helpful?