🔔 DingTalk

Use the interactive kwatch manager to configure DingTalk 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.dingtalk.accessToken	🔑 Access token	Yes
alert.dingtalk.secret	🔐 Signing secret	No
alert.dingtalk.title	✏️ Custom title	No

Configuration example

alert:
  dingtalk:
    accessToken: "${file:/config/dingtalk-access-token}"
    secret: "${file:/config/dingtalk-secret}"
    title: "optional customized title"

Routing

alert:
  dingtalk:
    accessToken: "${file:/config/dingtalk-access-token}"
    secret: "${file:/config/dingtalk-secret}"
    routes:
      - namespaces: ["production"]
        severities: ["high", "critical"]
      - reasons: ["OOMKilled"]

Retry

alert:
  dingtalk:
    accessToken: "${file:/config/dingtalk-access-token}"
    secret: "${file:/config/dingtalk-secret}"
    retry:
      maxAttempts: 5
      delay: 5s

Fallback

alert:
  dingtalk:
    accessToken: "${file:/config/dingtalk-access-token}"
    secret: "${file:/config/dingtalk-secret}"
    fallback: <another_provider>

Compact mode

alert:
  dingtalk:
    accessToken: "${file:/config/dingtalk-access-token}"
    secret: "${file:/config/dingtalk-secret}"
    compact: true