Skip to content

Alerts

Alerts covers both reactive event watching and a proactive rules engine, plus outbound integrations.

What it does

  • Watches Kubernetes Warning events across tenant namespaces (CrashLoopBackOff, OOMKilled, BackOff, and similar), classified by severity and deduplicated for 5 minutes
  • Rules engine — 10 condition types (pod restart threshold, pod phase match, pod not ready, deployment degraded, node condition, PVC unbound, event pattern, job failed, metric threshold, scan severity threshold), evaluated every 30 seconds with per-rule cooldown
  • Integrations — Slack, Email/SMTP, PagerDuty, CloudWatch, OpsGenie, Datadog, and generic Webhook; all enabled integrations fire in parallel
  • Alertmanager ingest — KubeManta can also act as an alert consumer: point an Alertmanager receiver at its webhook and inbound firings land in the feed (see Observability)

How to get there

Click Alerts in the sidebar (OBSERVE group). Three sub-tabs: Alerts (live feed), Rules (CRUD + firing history), Integrations (destination config).

Key actions

  • Create a rule: Rules tab → New Rule → pick a condition type, set thresholds and cooldown, Test to dry-run before enabling
  • Configure a destination: Integrations tab → pick a provider card → enter credentials → Save → Test
  • Clear alert history or firing history from the Alerts tab if you need a clean slate

Screenshots coming

A walkthrough of the Rules builder and Integrations cards will be added here in a follow-up pass.