[vegannet]

I love the idea but one of the challenges I’ve found at quite a few companies is a difficulty across the organisation in understanding the true cost of infrastructure: I’ve experienced situations in which putting the $ upfront causes people to focus on the $ amount.

Do you have a guide for how this information should be used most effectively? I’m thinking of co-workers who would request a change that reduces the monthly cost by $10 but the time it takes to go through the code review and make the change and test it... by that point any $ cost saving has been spent on the time it spent in code review.

My instinct is that perhaps rather than reporting the $ or % change, instead projects could have alarms / limits on cost increases, but I’m not so sure if that is really tackling the problem.

[aliscott]

You're right. It has to be a balance between the cost of the infrastructure and the developer's time. One feature we have for this is to only show comments in PRs if the cost increase is above a certain threshold.

Another idea we have is to allow developers to set alerts based on their actual project/IaC concepts instead of configuring alerts based on tags and services. Do you think this would help?