Show HN: Why it's hard to know which deployment caused a production incident (github.com)
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 ;)
2 comments
[ 234 ms ] story [ 679 ms ] thread