KlusterAlert

Notification Channels

Route alerts to Microsoft Teams, Slack, or email. Notification channels are configured per cluster. Each cluster can have its own webhook URLs and email addresses.

Notification settings are per-cluster. Go to KlusterAlert → Clusters → [your cluster] → Settings → Notifications to configure them.

Microsoft Teams

Starter and above
  1. 1In Microsoft Teams, navigate to the channel you want alerts posted in.
  2. 2Click ··· next to the channel name → Connectors → Incoming Webhook → Configure.
  3. 3Enter a name such as "KlusterAlert" and click Create.
  4. 4Copy the webhook URL that appears.
  5. 5In the KlusterAlert dashboard, go to Clusters → select your cluster → Settings → Notifications.
  6. 6Paste the webhook URL into the Teams Webhook URL field and click Save.

Slack

Starter and above
  1. 1In your Slack workspace, go to your app directory and create a new Incoming Webhook.
  2. 2Select the channel you want alerts posted in and click Allow.
  3. 3Copy the webhook URL provided by Slack.
  4. 4In the KlusterAlert dashboard, go to Clusters → select your cluster → Settings → Notifications.
  5. 5Paste the webhook URL into the Slack Webhook URL field and click Save.

Email

All plans
  1. 1In the KlusterAlert dashboard, go to Clusters → select your cluster → Settings → Notifications.
  2. 2Enter one or more email addresses in the Email Notifications field.
  3. 3Click Save. KlusterAlert will send alerts to these addresses when issues are detected.

What an alert notification looks like

Every notification includes the cluster name, namespace, affected pod, issue type, and restart count. On Pro and above, it also includes an AI-generated explanation and a suggested kubectl command.

Example Teams / Slack message
🔴 CRITICAL · payments-service · namespace: production

What's happening:
Pod 'payments-service' is in CrashLoopBackOff with 7 restarts.
The container exits immediately after starting.

Most likely causes:
- Missing required environment variable or secret
- Application bug causing a fatal error on startup
- Incompatible Docker image tag recently deployed

Investigate with:
kubectl logs payments-service -n production --previous

Alert deduplication

KlusterAlert deduplicates notifications so you don't receive repeated alerts for the same ongoing issue. A second notification for the same pod and issue type is suppressed until the deduplication window passes or the issue resolves and reoccurs.

Previous
Issue Detection
Next
AI Explanations