Find out if a spike was caused because of a bad deployment, increase in business/traffic, or a bug in your code.
When shit hits the fan, dollars keep burning while you find a fix. Why should you have to wrangle information from disparate teams, services and tools to get a timely answer? That's why we made it super easy to tie your events from any deployment or CI/CD tool (e.g.: Jenkins, CloudFormation, Terraform, GitHub Actions) as well as business data to AWS cost anomalies.