Answering simple questions about your total cloud cost using native tools is not straight forward with:
Understanding the current cost and the estimated trend across cloud environments is very complicated because of the complex nature of cloud layers. Here’s what’s missing with native tools and cost solutions to troubleshoot effectively today:
The context of how these cloud resources work to power your business
The configuration change or behavior that originated the cost on your cloud bill
The impact radius of these changes for cost in your environment.
Why does the world need a cloud cost troubleshooting solution?
Existing solutions (native tools and legacy FinOps vendors) completely miss the context of these resources in your environment and the network traffic of your cloud. Your DevOps and platform teams need to review the configuration changes and the actual traffic of your environment to fully understand total cloud cost. Only then, can you start optimizing and implementing best practices. A solution to this problem did not exist for DevOps teams, so we created one!
We’ve created the world’s first cloud cost troubleshooting solution for DevOps/Cloud teams. Here’s the why and how:
How much did auto-scaling groups cost us last month?
Are we optimizing data egress cost for data shared with partners? Ingress between regions?
How did we accumulate these network line items on our cloud bill? Which apps consumed that?