Notifications
Alert delivery to Slack, Discord and email when insights fire. Optional — disabled when no channel is configured.
Channels
The open-source edition delivers to three channels — Slack, Discord and email — and nothing else. Each one activates when its connection details are set. You can enable one, two or all three at once.
- Slack — Block Kit messages with severity colour bar and a button that deep-links back to the resource in KubeBolt.
- Discord — Embed messages with equivalent formatting.
- Email (SMTP) — Plain/HTML email with three delivery modes:
instant(the default),hourlydigest, ordailydigest. Supports multiple recipients.
Global settings
Cross-channel knobs that apply to every notifier:
| Env var | Default | Purpose |
|---|---|---|
KUBEBOLT_NOTIFICATIONS_ENABLED | true | Master kill switch — set false for maintenance windows. |
KUBEBOLT_NOTIFICATIONS_MIN_SEVERITY | warning | Insights below this threshold don’t notify. Values: critical, warning, info. |
KUBEBOLT_NOTIFICATIONS_COOLDOWN | 1h | Dedup window — the same insight fires at most once per cooldown. |
KUBEBOLT_NOTIFICATIONS_BASE_URL | — | Public URL of your KubeBolt — embedded as a deep link in messages. |
KUBEBOLT_NOTIFICATIONS_INCLUDE_RESOLVED | false | Also notify when an insight transitions to resolved. |
KUBEBOLT_SLACK_ENABLED · KUBEBOLT_DISCORD_ENABLED · KUBEBOLT_EMAIL_ENABLED | true | Pause one channel without clearing its configuration. |
Always-on across clusters
Insight notifications fire for any registered runtime — the active cluster or one running in the background (including agent-proxy connections) — not just the cluster you currently have open. The fresh-episode filter still applies, so restored or flapping insights don’t re-notify. An incident on a cluster you aren’t watching no longer slips by unnoticed.
Slack
# Create an Incoming Webhook in Slack, then:
KUBEBOLT_SLACK_WEBHOOK_URL=https://hooks.slack.com/services/T.../B.../...Discord
# Server Settings → Integrations → Webhooks → New Webhook, then:
KUBEBOLT_DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/...KUBEBOLT_SMTP_HOST=smtp.example.com
KUBEBOLT_SMTP_PORT=587 # default 587 (STARTTLS)
KUBEBOLT_SMTP_USERNAME=alerts@example.com
KUBEBOLT_SMTP_PASSWORD=...
KUBEBOLT_SMTP_FROM=KubeBolt <alerts@example.com>
KUBEBOLT_SMTP_TO=sre@example.com,oncall@example.com
KUBEBOLT_SMTP_DIGEST_MODE=hourly # instant (default) | hourly | dailyOn KubeBolt Cloud, Kobi Autopilot’s recommendations don’t depend on these channels being on. When none would carry a ready recommendation, Autopilot emails it to the organization’s admins, plus a weekly digest of what is still waiting. See KubeBolt Cloud.
Admin UI: Administration → System → Notifications (/admin/system, Admin role) edits the channels and the global settings without a restart, and sends a test notification to each channel. Values saved there override the environment variables; Reset to env defaults returns to them. Requires authentication to be enabled.