# abahmed/kwatch

:eyes: monitor & detect crashes in your Kubernetes(K8s) cluster instantly

Repository: https://github.com/abahmed/kwatch
Canonical: https://ross.abutalabs.com/products/kwatch
Homepage: https://kwatch.dev
Language: Go
License: MIT
License Family: permissive
Topics: kubernetes, monitoring, k8s, crash-reporting, event-notifier, kwatch, go, golang, discord, slack
Last push: 2026-08-31T16:57:20+00:00

## Health v2 (maintenance only)
Score: 84/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 100, release rhythm 53, longevity 100
- inputs: {"age_days": 1747, "days_push": 2, "days_rel": 158, "gap_med": 145.0, "n_releases_24m": 5}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1016, forks 82 (observed 2026-09-01T02:13:58.387158+00:00)

## What it is
kwatch is a lightweight, stateless Kubernetes monitoring tool that watches pods, nodes, PVCs, jobs, HPAs, and rollouts and sends self-explaining crash alerts (with root cause, logs, and events) to team chat channels. It is deployed as a single small pod via Helm or kubectl and supports 56 notification providers including Slack, Discord, Teams, PagerDuty, and email.

## Use cases
- get notified when pods crash in my kubernetes cluster
- alert on OOMKilled and CrashLoopBackOff with logs
- send kubernetes crash alerts to slack or discord
- monitor stuck deployments and failed jobs in k8s
- lightweight kubernetes alerting without prometheus
- watch pvc disk usage and node health in kubernetes
- route kubernetes alerts by namespace and severity

## When to choose
- you want fast, simple kubernetes crash alerting without running Prometheus or Grafana
- you need alerts that include root cause, recent logs, and events in team chat
- you want a stateless single-pod deployment with minimal configuration
- you need alert routing, retries, and fallback across many notification providers

## When to avoid
- you need metrics collection, dashboards, or long-term log storage
- you already run a full Prometheus/Alertmanager stack with custom PromQL rules
- you need per-pod agents or deep application-level observability

## Facets
- artifact type: service
- maturity: active
- function: monitoring, alerting, logging
- domain: monitoring
- platform: self-hosted, go, cli
- tags: kubernetes, crash-detection, crash-reporting, event-notifier, slack, discord, helm-chart, pod-monitoring, alert-routing, devops, containers, docker

## Member repositories
- abahmed/kwatch (main) score 84

## Provenance
- Observed fields: from GitHub, fetched 2026-09-01T02:13:58.387158+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T07:11:17.250174+00:00, confidence not recorded.
  - readme: https://github.com/abahmed/kwatch (fetched 2026-09-01T02:13:58.387158+00:00, sha e1f490e877ae)
  - homepage: https://kwatch.dev (fetched 2026-08-29T13:10:19.292750+00:00, sha 88f31844cca2)
  - site_page: https://kwatch.dev/docs (fetched 2026-08-29T13:10:19.302174+00:00, sha ebe2f7ca998b)
  - site_page: https://kwatch.dev/docs/installation (fetched 2026-08-29T13:10:19.304167+00:00, sha 7a6825fc3360)
  - site_page: https://kwatch.dev/docs/channels (fetched 2026-08-29T13:10:19.306015+00:00, sha c2625469d589)
  - site_page: https://kwatch.dev/docs/general-configuration (fetched 2026-08-29T13:10:19.308196+00:00, sha a457362df02b)
  - site_page: https://kwatch.dev/docs/cli-commands (fetched 2026-08-29T13:10:19.310545+00:00, sha 89cacaf74c57)
  - site_page: https://kwatch.dev/docs/rollout-monitor-configuration (fetched 2026-08-29T13:10:19.312209+00:00, sha b00ef231285e)
  - site_page: https://kwatch.dev/docs/job-monitor-configuration (fetched 2026-08-29T13:10:19.313706+00:00, sha 6e6f4fe8b93f)
  - site_page: https://kwatch.dev/docs/hpa-monitor-configuration (fetched 2026-08-29T13:10:19.315358+00:00, sha 6e1507441ed4)
- Data as of 2026-08-30T08:39:29.467469+00:00.