K-C10 · size M · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
ServiceMonitor with auth from a Secret, PrometheusRules (heartbeat stale, queue depth/age, delivery failures, cert expiry, readiness flapping, store latency), OTLP values, a Grafana dashboard.
Done when
Rules fire in the lab chaos run and are quiet otherwise
**K-C10** · size M · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
ServiceMonitor with auth from a Secret, PrometheusRules (heartbeat stale, queue depth/age, delivery failures, cert expiry, readiness flapping, store latency), OTLP values, a Grafana dashboard.
**Done when**
- Rules fire in the lab chaos run and are quiet otherwise
jcoffey-dev
added this to the 27.1 milestone 2026-11-18 05:14:45 +00:00
Started: inbuxa/inbuxa-server#488, #27, inbuxa/inbuxa-k8s-lab#28. Every rule fires in the lab from real breakage and is quiet otherwise, except the two kube-state-metrics ones (no kube-state-metrics in the lab).
Started: inbuxa/inbuxa-server#488, #27, inbuxa/inbuxa-k8s-lab#28. Every rule fires in the lab from real breakage and is quiet otherwise, except the two kube-state-metrics ones (no kube-state-metrics in the lab).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
K-C10 · size M · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
ServiceMonitor with auth from a Secret, PrometheusRules (heartbeat stale, queue depth/age, delivery failures, cert expiry, readiness flapping, store latency), OTLP values, a Grafana dashboard.
Done when
Folded into the checklist on inbuxa/inbuxa-charts#14 to keep the issue list short. The details stay here; reopen this when work on it starts.
Started: inbuxa/inbuxa-server#488, #27, inbuxa/inbuxa-k8s-lab#28. Every rule fires in the lab from real breakage and is quiet otherwise, except the two kube-state-metrics ones (no kube-state-metrics in the lab).