StreamForge v2.1 — Custom Alert Thresholds
StreamForge v2.1 — Custom Alert Thresholds
What's New
- Per-metric Z-score threshold — default 3.0 sigma, now fully configurable per metric
- Alert cooldown — minimum time between alerts per metric (prevents alert spam)
- POST /config — set custom threshold and cooldown for any metric via API
- GET /config — view current thresholds for all configured metrics
- DELETE /config/{metric} — reset any metric back to default threshold (3.0)
How to use
Set strict threshold for payment failures (alert at 1.5 sigma, max 1 alert/min)
curl -X POST "http://localhost:9090/config?metric=payment_failures&threshold=1.5&cooldown=60"
Set relaxed threshold for CPU (alert at 4.0 sigma, max 1 alert/5min)
curl -X POST "http://localhost:9090/config?metric=cpu_usage&threshold=4.0&cooldown=300"
View all current thresholds
curl http://localhost:9090/config
Reset metric to default
curl -X DELETE http://localhost:9090/config/cpu_usage
Why this matters
Different metrics need different sensitivity.
A payment failure rate of 0.1% is an emergency.
A CPU spike to 80% might be normal during batch jobs.
v2.1 lets you tune every metric without recompiling.