When a query gets slow, our postmortems always start the same way: someone opens Grafana, someone else scrolls through Argo CD history, and we try to match timestamps by eye. I got tired of that and wrote something to do it automatically. It reads pg_stat_statements, picks up deploy events from Argo CD, Argo Rollouts, Flux or a webhook, and checks whether a latency shift in any query lines up with a rollout. If it does, you get the query, the deploy, before/after latency and how confident it is, in Slack/Teams/PagerDuty. If you use Argo Rollouts it can also abort a canary (off by default). You can run it as a single binary or as a controller with CRDs, in which case every regression shows up as a resource you can `kubectl get`. Repo: https://github.com/joao00001/pg-regression-radar Browser demo, no cluster needed: https://joao00001.github.io/pg-regression-radar/playground/ It's a side project and I'm looking for people willing to try it on a staging cluster. Any feedback is welcome, including "this is noisy" or "I'd never use this because X".   submitted by   /u/joao_detomini [link]   [comments]