You must understand how the built-in execution logging of Azure Functions has a cost impact

208608276-9ed6bf1e-dda4-4fbd-8646-358bc3

When you enable Application Insights when you create a Function App, the built-in logging mechanism (built-in logging) will be enabled by default, and the records will be stored in the Table of the Azure Storage account. We have an Azure Function (v1) application, which has been running stably for 4 years, but recently found that even if there is no traffic, the storage fee is very high. Since our website has not had much traffic recently, how can we still spend so much money? I analyzed it and found that Table Storage alone occupies as much as 113 GiB of storage. I was shocked. It turned out that it was the function of the Function App. They automatically stored all the monitored data in the designated Azure Storage storage account. bingo! Today I will explain how to delete these obsolete records efficiently to avoid unnecessary resource consumption.

continue reading

This article is transferred from http://blog.miniasp.com/post/2022/12/21/Azure-Functions-built-in-logging-cause-high-cost
This site is only for collection, and the copyright belongs to the original author.