![]() In Azure App Service, for increased performance and throughput, you can adjust the scale at which you are running your application. These memory dumps are snapshots of the process and can often help you troubleshoot more complicated issues with your app.įor more information on features available in Kudu, seeĪzure Websites online tools you should know about. debug console in which you can run PowerShell cmdlets and basic DOS commands.Īnother useful feature of Kudu is that, in case your application is throwing first-chance exceptions, you can use Kudu and the SysInternals tool Procdump to create memory dumps.environment settings for your application.You can access this dashboard by going to the link Some of the things that Kudu provides are: This is called the Kudu Console or the SCM Dashboard for your app. Use the Kudu Debug ConsoleĪpp Service comes with a debug console that you can use for debugging, exploring, uploading files, as well as JSON endpoints for getting information about your environment. In the left navigation, click on Diagnose and solve problems. To access App Service diagnostics, navigate to your App Service app or App Service Environment in the Azure portal. When you do run into issues with your app, the diagnostics tool will point out what’s wrong to guide you to the right information to more easily and quickly troubleshoot and resolve the issue. Some of the metrics that you might want to monitor for your app areĪpp Service provides an intelligent and interactive experience to help you troubleshoot your app with no configuration required. The Metric blade will show you all the metrics you can add. In your app’s blade, click the Requests and errors tile. This option enables you to find out if your application is having any issues. For more information, see Track service health. You can track the health of the service on the Azure Portal. Microsoft Azure publicizes each time there is a service interruption or performance degradation. Observe and monitor application behavior Track Service health Observe and monitor application behaviorĪpp Service gives you various options at each step.ġ.Troubleshooting can be divided into three distinct tasks, in sequential order: Troubleshooting steps to solve "502 bad gateway" and "503 service unavailable" errors application crashing due to an exception.This problem is often caused by application level issues, such as: When you browse to the app, it returns a HTTP "502 Bad Gateway" error or a HTTP "503 Service Unavailable" error. Go to the Azure Support site and click on Get Support. Alternatively, you can also file an Azure support incident. If you need more help at any point in this article, you can contact the Azure experts on the MSDN Azure and the Stack Overflow forums. This article helps you troubleshoot these errors. ![]() ![]() "502 bad gateway" and "503 service unavailable" are common errors in your app hosted in Azure App Service. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |