I was running a web app service and all of a sudden I see a degraded performance in the response time. I did not do code changes but I get the followin warning:
We analyzed 15 slow request(s) and identified module(s) consuming most of the time are - HandlerChanged to (httpPlatformHandlerMain)(95.83%)
I did not explicitly change any configuration on Azure so thats why I am suprised to see such degraded service.
I redeployed the same code and restarted the webapp
There might be several reasons for degraded performance in your Azure Web App Service, such as increased traffic, changes in modifying infrastructure.
Follow the below steps to troubleshoot Azure Web App Performance issue.
Check the resource utilization: Kindly check the Azure Web App utilization such as CPU, Memory, and Disk Space.
If your Web App utilization is high, you may need to scale up your App Service plan, Like below.
Check the Web Application logs: Kindly check if any error messages in the logs that could indicate the cause of the issue. You can check the logs in the Azure portal by navigating to below options.
Azure Portal > Select your App Service > Log stream
Monitor your app performance: Monitor the performance of your Azure Web App by sending Apps Logs to Log Analytics workspace to get a better understanding of the App performance degradation issues,
Azure Portal > Select your App Service > Diagnostic settings > Add diagnostic setting
You can check for recent changes in your application., such as changes to the code & configuration, to see if they are causing any performance issues in your application.
Restart the App Service: Sometimes you can resolve the Azure App performance issues by restarting the application.
Azure Portal > App Service > Select your application > Overview > Restart
For more information refer : Troubleshoot slow app performance issues in Azure App Service
Related
I want to monitor my azure app service. Two use cases:
Application availability hosted inside azure app service (Application availability part)
To do this - I have enabled Azure app insights (workspace-backed) and configured 'availability tests' -> Run a Kusto Query to query the availability test -> Create Monitors/Alerts etc -> Able to show this via Azure dashboard
Azure App service availability (Infra part)
I currently do not know how to 'monitor' if there is a problem with the app service. For example, if the app service (infra / instances) has problem and the application does not have problem.
Example: If the App service gets 'stopped' for a random reason, I should be able to tell by the logs that the issue was with the azure app service and not the application.
I have configured the Diagnostic Settings to forward logs to Analytics workspace. No luck.
I have checked the metrics 'memory work set' and 'CPU time' as well -> If I 'STOP' the app service, these two metrics do not hit ZERO value.
Does anyone know how to 'monitor' the infra part of the Azure app service? We want to do this, because we have infra team who looks after the infrastructure. And the DevOps team who looks after the application. I need two different types of alerts depending on the 'origin' of the issue.
I am trying to use the "FREE" layer of Azure App Services using the GitLab Container Registry.
To do the DEPLOY I am using WebHook, but I am not having success. I call WebHook to start Deploy (via Postman) and when analyzing the deployment LOGs, nothing happens.
The strangest thing is that at times it works, but it seems to be only once a day.
I call WebHook as follows:
https://$<my-app>:<token>#<my-app>.scm.azurewebsites.net/docker/hook
Are there any limitations for being a free tier?
#Junior, please note that with Web Apps free tier there are a few quotas.
The two that you might be hitting are:
You can only use the CPU 3 out of every 5 minutes
You can only use the CPU 60 minutes every 24 hours
Source:https://learn.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits#app-service-limits
Windows Web Apps have a quota blade that allow you to see if you are actively hitting a quota. I would suggest checking there. Also check the diagnose and solve blade for your app to verify one of the above quotas are being hit.
I am intending to enable logging in my Azure app. I am following the instructions by Microsoft on here, where they state to go to my app and select App service logs, but I see no such option for my app. This resource has the same instruction but I don't have that option. I am running on the Basic configuration for the app (the cheapest option), could that be the issue?
This is all I have under Monitoring (see image below)
What am I missing?
Which region are you running your app service on?
I just tried with Basic(B1) app service and I was able to configure app service logs
Seems like I had to upgrade to a minimum of Standard tier configuration to get the option to set up App Service Logs. It is Unfortunately about triple the cost of the Basic tier.
We have an App Service Plan in Azure (PremiumV2: 1 Medium) with 14 App Services setup, but they are all stopped.
So without any load (that I know of), our CPU sometimes spikes to 100%. Is this normal? How can I find out what is causing the spikes? I'm guessing it isn't one of the App Services, since they are all stopped.
Generally, we click stop botton in the panel of Azure portal to stop an app service, but it only stop the main site you deployed under wwwroot, not the SCM site where Kudu & WebJob runs.
There is an offical document of Kudu wiki Full stopping a Web App which may explain your current case. When you deployed some WebJobs running in your App Services, they will not be stoped by clicking the stop operation in Azure portal. And it seems to be some continous WebJob running which cause the CPU & Memory consuming.
If you want to stop all of them thoroughly, please follow the wiki above to know how to do. Hope it helps.
In our current setup there are 2 slots for an Azure App service, the question that I have is, when the slot is stopped would it also shut down the webjob that is deployed on that slot or would the web job continue to run?
It is possible to run an Azure WebJob even when the Azure App Service Web App is not running.
Though you can force the WebJob not to run or stop when the Web App is running using WEBJOBS_STOPPED setting in your Web App's "Application Settings"
Take a look at this article about this subject for more details:
https://blogs.msdn.microsoft.com/benjaminperkins/2017/03/01/failed-to-run-webjob/
The following picture shows a running WebJob when the web app is not running:
https://github.com/projectkudu/kudu/wiki/Full-stopping-a-Web-App
I have actually deleted some running jobs, but even though my jobs were shown as deleted in the UI, they are silently running and consuming the memory. I observed this from availability and Performance > Memory Analysis dashboard under Memory Drill Down > Memory Usage (App) > Physical Memory Usage section. Shocked to see the jobs still running after they are deleted. Luckily this solution helped me kill all the processes.