Chaos Edition — Prometheus

In short: How to Run Prometheus Chaos Edition (Step-by-Step)

Create a small proxy that intercepts /metrics endpoints: prometheus chaos edition

Enter – a little-known, experimental tool designed to do the unthinkable: intentionally break your Prometheus deployment so you can fix it before a real disaster. In short: How to Run Prometheus Chaos Edition

| Risk | Mitigation | | --- | --- | | PCE accidentally runs on production | Use namespace isolation, explicit --chaos.enabled=false flag in prod. | | Permanent data loss | Run against a replica Prometheus with --storage.tsdb.retention.time=6h . | | Alert fatigue | Notify a separate “chaos channel” during experiments. | | Controller plane overload | Limit chaos duration (e.g., 5 minutes max). | | | Alert fatigue | Notify a separate

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.

# malicious_exporter.py from flask import Flask, Response import random app = Flask()

# Inject 5s latency into 50% of scrape requests for 2 minutes curl -X POST http://localhost:9091/inject/latency \ -d '"duration":"2m","percent":50,"delay":"5s"' If you run Prometheus Operator, pair it with Chaos Mesh (CNCF project) and a NetworkChaos experiment: