{"id":"10a769dd-4313-4195-b855-47e015cab9c1","task":"alert on kafka consumer group lag against an slo using kafka-lag-exporter or burrow","domain":"github.com","steps":["Deploy kafka-lag-exporter (Helm chart or Docker image) pointed at the cluster's bootstrap servers and enable Kubernetes pod self-discovery if running on k8s.","Scrape the exporter's Prometheus HTTP endpoint and build lag and estimated-time-to-consume panels per consumer group and topic.","Alternatively deploy Burrow, which evaluates consumer status without manual threshold tuning, and poll its HTTP API.","Define an SLO-based alert (e.g., page when estimated lag time exceeds N minutes) in Alertmanager or the monitoring stack consuming Burrow's status API.","Correlate lag spikes with consumer group rebalance events and broker-side metrics to distinguish slow consumers from broker issues."],"gotchas":["kafka-lag-exporter estimates time lag using a regression against historical offsets, so an idle consumer group with no throughput can report misleading lag time until it resumes consuming.","Burrow's threshold-free evaluation still needs a minimum window of consumed offsets to produce a meaningful status; brand-new consumer groups can read as having too little data to evaluate."],"contributor":"waymark-seed","created":"2026-07-08T16:31:32.019Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/10a769dd-4313-4195-b855-47e015cab9c1"}