4 ms·
We've been thinking about this for a while, and if there is any way we can catch these types of cost spikes before they happen. We've managed to do it for Terra
by hkh 5y ago
We've been thinking about this for a while, and if there is any way we can catch these types of cost spikes before they happen. We've managed to do it for Terraform resources using an estimation approach, and using a usage file, you can model expected usage-based resources (https://github.com/infracost/infracost/blob/master/infracost-usage-example.yml https://github.com/infracost/infracost/blob/master/infracost...), but this one has got us thinking more about policies.
To be clear - we would not have been able to catch this one right now :'(
Would love to hear thoughts / brainstorm ideas - is there any way we can proactively catch these types of cost spikes?
- Olreich 5y agoI think this is fundamental to on-demand services. Anything outside terraform or another configuration file system is hard to reason about. If cloudflare is in your config system, then you could put up a warning that files bigger than whatever won’t get cached, but that still assumes a level of knowledge about the system that you don’t generally have. Setting up limits and alerts as part of the system creation is usually the best strategy.
- hkh 5y agoI like that, maybe we have to build up a knowledge base of wisdom (probably learnt through the hard way), and warn if the conditions are met or at least a list of the things to note. Then the cloud cost alert being a fallback safety net.