3 ms·
Show HN: Why it's hard to know which deployment caused a production incident
We’re a team of two building Valiant after too many incidents where “something changed” but nobody could tell what actually caused production issues.
Valiant correlates intent (Git commits, CI/CD signals) with actual execution (Kubernetes rollouts) and links them to Prometheus metrics, so you can see the real impact of each change - not just what was deployed.
It’s open-source, still under active development, and very much a work in progress. Feedback, ideas, or contributors are welcome.
No website yet — just the GitHub repo ;)
- direwolf20 9mo agoAI slop
- veinar_gh 9mo agoNah, just made some assumptions for this project with AI. But thanks for feedback.
- af_arc 9mo agoNice. The "5 deploys in one hour, which one broke it?" scenario is painfully common. We deal with this weekly. One thing I'd love to see: integration with PagerDuty/OpsGenie so that when an alert fires, it could automatically surface the ranked list of suspect changes.
- veinar_gh 9mo agoThanks for feedback! Good idea for future improvements.