🛡️ Zenduty

Use the interactive kwatch manager to configure Zenduty alerts. It stores credentials in Kubernetes Secrets and verifies the installation. The configuration fragments below explain provider settings; they are not separate installation steps.

Parameter	Description	Required
alert.zenduty.integrationKey	🔑 Integration Key	Yes
alert.zenduty.alertType	🏷️ Alert type (default: critical)	No

Configuration example

alert:
  zenduty:
    integrationKey: "${file:/config/zenduty-integration-key}"
    alertType: critical

Routing

alert:
  zenduty:
    integrationKey: "${file:/config/zenduty-integration-key}"
    alertType: critical
    routes:
      - namespaces: ["production"]
        severities: ["high", "critical"]
      - reasons: ["OOMKilled"]

Retry

alert:
  zenduty:
    integrationKey: "${file:/config/zenduty-integration-key}"
    alertType: critical
    retry:
      maxAttempts: 5
      delay: 5s

Fallback

alert:
  zenduty:
    integrationKey: "${file:/config/zenduty-integration-key}"
    alertType: critical
    fallback: <another_provider>

Compact mode

alert:
  zenduty:
    integrationKey: "${file:/config/zenduty-integration-key}"
    alertType: critical
    compact: true

Screenshot