๐ก๏ธ 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 Proโ
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โ

Relatedโ
- Zenduty provider settings for every field
- All alert providers and troubleshoot missing alerts