Skip to main content
Installation

Start here: one command to install

One command is all you need to get started. No Helm orkubectl apply steps here 🚀

Recommended

Interactive manager

/bin/bash -c "$(curl -fsSL https://kwatch.dev/kwatch.sh)"

Install, configure, upgrade, check, or uninstall kwatch from one menu. The manager asks for your cluster and alert destination, stores credentials in a Secret, and waits for kwatch to become ready.

1
Select your clusterThe manager never changes your kubectl context.
2
Choose your alert channelCredentials are stored in a Kubernetes Secret.
3
Start watchingThe manager verifies that kwatch is ready.

Need to inspect release artifacts or understand the supported lifecycle? Read the full installation guide.

🏠Runs in your clusterNo hosted backend or metrics database
One guided commandInstall, configure, upgrade, and recover
📣56 notification providersSend one clear incident to every team

🧐 What is kwatch?

kwatch is like a smart friend for your Kubernetes cluster:

💥
Something crashes → you get a message that says why (not just "pod is broken")
🔇
Smart about noise — groups related problems and avoids repeating the same alert
🧠
Explains itself — every alert says the cause, the impact, and what changed
Works from one command — a few simple answers and a ready cluster

🚫 No Prometheus🚫 No Grafana🚫 No 50-step setup
You can keep your existing monitoring tools. kwatch is the alarm that tells you what needs attention. 🎯

🚨 From confusing errors to clear next steps

🤷 Before
CrashLoopBackOff
😰 Raw YAML output — good luck figuring it out
Error
😰 Just "Error" — no context, no cause
kwatch
💡 After
🚨 OOMKilled
💡 memory limit: 512Mi — try raising limits.memory
📋 logs + events included
🚨 Liveness probe failed
💡 :8080/healthz timed out — check the endpoint and startup timing
🔧 points to the failing probe

🎯 What does it catch?

Most monitors are on by default — zero config needed:

🟥 Pod crashes (CrashLoop, OOM, ImagePull, Error)

Container state + last logs + events — tells you *why*

⏳ Pending pods (stuck Unschedulable)

Alerts after 300s stuck

🖥️ Node issues (NotReady, Disk/Memory pressure)

Per-condition severity

💾 PVC running out of space

Warn at 80%, critical at 90%

❌ Failed Jobs & stuck CronJobs

JobFailed / suspended / missed runs

🚀 Stuck rollouts & StatefulSets

ProgressDeadlineExceeded — deployment didn't finish

📡 DaemonSet pods not running

Unavailable pods detected

📈 HPA stuck at max replicas

After 20 minutes sustained

📣 Cluster autoscaler can't scale

FailedToScaleUp / NotTriggerScaleUp

🔒 TLS certs expiring

Enable if you want cert expiry warnings

💓 Heartbeat (dead man's switch)

Enable to page you if kwatch itself goes down

TLS and heartbeat are opt-in — the core monitors work out of the box.

🧠 Alerts that explain themselves

kwatch ships with a diagnosis engine that runs inside your cluster, reads the logs and events, and tells you what's wrong and what to do next.

How does the insight engine work?

1
Something breaks — a pod crashes, a node goes down, a deployment gets stuck
2
kwatch works out the root cause — it maps the pod to its node, owner, services, PVCs and config, and reads the container logs, events, and crash reasons
3
You get a plain-English fix — "OOMKilled — try raising memory limit" instead of a cryptic error code

🕳️ Knows when it was blind: kwatch stamps its own liveness, so if it was down while your cluster wasn't, the next startup message says how long nobody was watching.

diagnosis configuration
# Says *why* a crash happened — the root cause, impact, and what changed.
# Configuration is optional: the insight/dependency graph is on by default.

When a crash happens, the diagnosis engine reads the logs and tells you the most likely cause and what to do next. Like having a senior SRE on-call with you. 🎯

🧭 An alert, not a dashboard

kwatch does one job really well: it tells you when something breaks and explains what to do next. It does not collect metrics, store logs, or build dashboards.

Already use Prometheus, Grafana, or Loki? Keep them. kwatch works alongside them as the alarm that tells you something needs attention right now. ⏰

📨 Get alerts where you already work

kwatch delivers clear incident alerts to your team's messaging platform — no extra tools needed

SlackSlack
DiscordDiscord
Microsoft TeamsMicrosoft Teams
TelegramTelegram
PagerDutyPagerDuty
OpsGenieOpsGenie
MattermostMattermost
RocketChatRocketChat
MatrixMatrix
Google ChatGoogle Chat
FeishuFeishu
ZendutyZenduty
EmailEmail
DingTalkDingTalk
WebhookWebhook

… and 41 more — GitLab, Gitea, Splunk, SendGrid, AWS SNS/SES, Twilio & Jira. 56 providerssupported in total.

🚀 Who uses kwatch?

Trusted by engineering teams around the world

🏢 Want to add your company? Open an issue!