Sleuth integrates with your Error and Metrics trackers to automatically verify the health of your deploys
Once a deploy has shipped how does your team know if the change was good or bad? How long does it take for your team to discover this? Minutes, hours, days or weeks?
Sleuth determined your deploy is unhealthy and shows you why
Auto-verification of your deploys with Impact tracking allows you to:
- Easily include production health in your developers definition of done, no more tracking down graphs and trying to understand what normal should look like, Sleuth alerts authors directly in Slack when a deploy is unhealthy
- Avoid creeping, incremental declines in performance, memory, cpu usage and more. Know when your changes take your service out of its normal range!
- Automate deploy locking or creating rollback pull requests when Sleuth sees an unhealthy deploy