I switched from legacy Cloudscript to Azure Functions in order to be able to interact with Inventory v2.
The thing is that I spent years with legacy and everything was transparent and fine: I would pay only for excess function executions or excess time to execute functions.
now with Azure I had to create a storage account that is already showing some kind of "this will cost" stats started reaching their limit even 2 days after creating them, and it's only me logging in to the game.
What is LRS Write Operations? What is Protocol Operations? What is Read Operations? In which way do functions trigger those things? is it logging? is it calling Server API? is it about the info received from a client in a request? I have spent a whole week searching information about how to know what causes costs in Azure functions and I cannot find anything. This is too obscure, as I have absolutely no idea about what to configure, what to avoid, what to do in order to avoid extra costs, or even what these read, write or protocol operations are about. The worst is that most of the predicted cost (very small but still) is all from storage, not from the function itself.
WIth Legacy cloudscript there was not anything of this cryptic stuff, and I just had to care about optimizing for less execution time, and amount of executions, and that was it. I knew exactly how my function would influnece it's cost. Now with the whole storage stuff I don't even know what is contributing to costs.