🧐 What is kwatch?
kwatch is like a smart friend for your Kubernetes cluster:
🚫 No Prometheus🚫 No Grafana🚫 No 50-step setup
Just alerts that make sense. 🎯
🆚 kwatch vs the scary stuff
| Feature | 👑 kwatch | 😰 DIY | 💸 SaaS |
|---|---|---|---|
| ⏱️ Setup time | ~5 minutes | hours of YAML | agent + backend setup |
| 📦 Size | ~20 MB single binary | whole monitoring stack | per-node agents + cloud costs |
| 💬 Alerts | Self-explaining ("OOMKilled — raise memory limit") | Rule-defined message | Depends on configuration |
| 🗄️ Storage | None (stateless) | Prometheus TSDB | Full retention (costly) |
| 📚 Learning curve | One ConfigMap | PromQL + alert rules | Platform-specific DSL |
🚨 Before vs After
limits.memory:8080/healthz (exit 137) — container ran out of memory🎯 What does it catch?
Every monitor below is on by default — zero config needed:
Container state + last logs + events — tells you *why*
Alerts after 300s stuck
Per-condition severity
Warn at 80%, critical at 90%
JobFailed / suspended / missed runs
ProgressDeadlineExceeded — deployment didn't finish
Unavailable pods detected
After 20 minutes sustained
FailedToScaleUp / NotTriggerScaleUp
Enable if you want cert expiry warnings
Enable to page you if kwatch itself goes down
✅ TLS and heartbeat are the only ones off — everything else just works 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?
🕳️ 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.
# 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. 🎯
60-second install
Pick your method — both take under a minute 🚀
📦 Helm
helm repo add kwatch https://kwatch.dev/chartshelm install [RELEASE_NAME] kwatch/kwatch --namespace kwatch --create-namespace --version 0.11.0-rc.6
More details in the chart docs 📖
kubectl
curl -L https://raw.githubusercontent.com/abahmed/kwatch/v0.11.0-rc.6/deploy/config.yaml -o config.yaml
vim config.yaml # ✏️ add your webhookkubectl apply -f config.yaml
kubectl apply -f https://raw.githubusercontent.com/abahmed/kwatch/v0.11.0-rc.6/deploy/deploy.yaml
📖 Not a monitoring platform — and proud of it! 🎉
kwatch is not a metrics collector, dashboard, or observability backend. No TSDB, no dashboards, no log storage, no query language. kwatch is the alarm — your existing tools are the archive.
Need full observability? Pair kwatch with Prometheus + Grafana for metrics, or Loki for logs. kwatch handles the one thing a dashboard cannot: telling you something broke right now. ⏰
📨 Send alerts where you already work
kwatch delivers crash alerts to your team's messaging platform — no extra tools needed
… and 41 more — GitLab, Gitea, Matrix, Splunk, SendGrid, AWS SNS/SES, Twilio, PagerDuty & Jira. 56 providers supported in total.
🚀 Who uses kwatch?
Trusted by engineering teams around the world
🏢 Want to add your company? Open an issue!

