Diagnose and Mitigate issues with Azure Web Apps Support portal

Kudu is the engine behind git deployments in Azure Web Sites. It can also run outside of Azure. Every Azure web app has a Kudu web site that can be accessed by the this URL format : https://azuresitename.scm.azurewbesites.net . The Kudu site has many tools to manage the environment and gather data to diagnose issues. One such tool is the support portal which allows you to observe, analyze and mitigate issues with you web application. To access this support portal , use the SCM site URL in this format https://azuresitename.scm.azurewebsites.net/Support

  • Observe : This allows you to see live traffic to your website. The requests and server errors occurring in real time

  • Analyze : This allows you to access your event viewer logs ,IIS FREB logs, ClearDB (if your application has a database connection string to a ClearDB database) , metrics on each instance running your web app.
  • Diagnose Now : Clicking on Diagnose now, will generate a report with PHP process report , PHP logs , Http Logs, memory dump and event viewer. When using Diagnose now tool, it can generate a lot of data under D:\home\data\DaaS . This can cause your to hit the storage limit for your web app. Hence make sure you regularly clean up or move it to a Azure storage account


    Note the logs report is generated for all the instances your web app is running on (in case your app is scaled at more than one instance ). This is useful when investigating an ongoing issue with your web app.


    • Metrics : RD000D3A31CFE5 is the instance that my web app is running on . I can see CPU/memory, network and HTTP statistics as shown below. If there are other sites running on the same instance or instances you will see the metrics for those sites as well on this page.




    • Event Viewer : You can access the event viewer log. You can filter then by date , source and event ID. You can see the detailed on the error as well for event logged.  
  • FREB Logs : Freb logs needs to be turned on for your web app before you use FREB logs tab . To learn more about how to enable FREB logs here.
  • ClearDB : If your web app has a connection string under Settings->Application settings in the portal , you will see ClearDB tab show the MySQL database information such as slow queries and maximum connection etc


  • Mitigate: It allows you to set up auto healing for your web app. You need to turn on Autoheal and set up rules based on the scenarios mentioned below:
    • Max requests
    • Status code
    • Slow requests
    • Memory Private set

    Some of the common actions you can perform to autoheal are Recycle the instance, Log an event but Auto heal here gives you flexibility to run a custom action as well. For more details , learn about these rules here



Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s