Prometheus | Chaos Edition

Create a small proxy that intercepts /metrics endpoints:

Prometheus Chaos Edition turns the old monitoring paradox on its head. Instead of trusting your monitoring blindly, you break it on purpose – gently, repeatedly, and observably. prometheus chaos edition

In short: How to Run Prometheus Chaos Edition (Step-by-Step) Create a small proxy that intercepts /metrics endpoints:

Despite its dramatic name, Prometheus Chaos Edition is not an official Prometheus release. It is a concept (and accompanying script/container) popularized by the Prometheus community and tools like kube-prometheus-stack chaos experiments. | | Alertmanager might be misconfigured for months

# Pull the chaos edition sidecar docker pull quay.io/prometheuschaos/chaos-sidecar:latest docker run -d --name prometheus-chaos --network container:prometheus quay.io/prometheuschaos/chaos-sidecar

| | With PCE | | --- | --- | | You assume Prometheus is always healthy. | You prove it can survive partial failures. | | Alertmanager might be misconfigured for months. | You test silences, inhibitions, and receivers. | | A slow scrape delays critical alerts. | You detect latency thresholds before they matter. | | Grafana dashboards freeze, but no one notices. | You build fallback visualizations. |