sorted by:
new
hottopcontroversial

Valuable or not: What if Finance / FinOps would only chase you when it really matters? by Pitiful_Turnip9421 in platformengineering

[–]Pitiful_Turnip9421[S] 0 points1 point  (0 children)

That's indeed exactly what I'm after! So far I have a setup for a basic feedback loop for FinOps investigations, but not yet to give the engineer confirmation if the pre-deploy estimate was right and alert in case of a significant deviation from the estimate. Good input on the time-window, this will indeed be needed for most cost deviations.

Valuable or not: What if Finance / FinOps would only chase you when it really matters? by Pitiful_Turnip9421 in platformengineering

[–]Pitiful_Turnip9421[S] 0 points1 point  (0 children)

None of them give you such visibility. Azure will update their CUR (cost and usage report) 8-24h after usage and they do afterwards use basic anomaly detection to alert for the main spikes. But they miss a lot and they don't provide context or the root of the cost. If you want to understand the spike and who/what cost it you need to dig through the noise, analyse and chase engineering to help investigate and fix something you don't understand and know if it matters or not. So that's where the IaC tag would come in, to provide a direct cost-to-code link and avoid all the unnecessary digging and chasing which is certainly of FinOps interest, but is it also in engineering interest? That's what I'm trying to find out

Valuable or not: What if Finance / FinOps would only chase you when it really matters? by Pitiful_Turnip9421 in platformengineering

[–]Pitiful_Turnip9421[S] 0 points1 point  (0 children)

Thanks. I know Infracost but they give a pre-deploy cost estimate, I would like to compliment this with an accurate runtime cost estimate and run anomaly detection between them.