Sometimes, web applications run smoothly during development and testing, but mysterious issues only surface in the production environment. Debugging these production problems can be challenging, especially when you don’t have direct access to the server. For example, when deploying on a traditional VM, it’s straightforward for developers to capture memory dumps for in-depth analysis. But what happens when your application is hosted on a PaaS solution like Azure App Service, where you can’t access the underlying VM? Let's check out.
In certain scenarios, you may need to restart your Azure Container Apps on schedule. Like I always joke about, a restart fixes 95% problems. However, if you do it manually, it will make you work 996. We need an automated way to complete this task. Azure Functions are perfect for this kind of "do something on a schedule" task. In this post, I will introduce how to use Azure Function timed trigger to automate this process.
