🔗 Custom Webhook

Use the interactive kwatch manager to configure Custom Webhook 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.webhook.url	🔗 Webhook URL	Yes
alert.webhook.headers	📋 Custom headers	No
alert.webhook.basicAuth	🔐 Username + password	No

Configuration example

alert:
  webhook:
    url: "${file:/config/webhook-url}"
    headers:
      - name: X-Custom
        value: "${file:/config/webhook-header}"
    basicAuth:
      username: "user"
      password: "${file:/config/webhook-password}"

Routing

alert:
  webhook:
    url: "${file:/config/webhook-url}"
    headers:
      - name: X-Custom
        value: "${file:/config/webhook-header}"
    basicAuth:
      username: "user"
      password: "${file:/config/webhook-password}"
    routes:
      - namespaces: ["production"]
        severities: ["high", "critical"]
      - reasons: ["OOMKilled"]

Retry

alert:
  webhook:
    url: "${file:/config/webhook-url}"
    headers:
      - name: X-Custom
        value: "${file:/config/webhook-header}"
    basicAuth:
      username: "user"
      password: "${file:/config/webhook-password}"
    retry:
      maxAttempts: 5
      delay: 5s

Fallback

alert:
  webhook:
    url: "${file:/config/webhook-url}"
    headers:
      - name: X-Custom
        value: "${file:/config/webhook-header}"
    basicAuth:
      username: "user"
      password: "${file:/config/webhook-password}"
    fallback: <another_provider>