Tuesday, October 4, 2016

Enabling application and site diagnostics Logs

Diagnostic logging is not enabled by default. It is up to you to enable and conigure logging in a way that provides the information you need to troubleshoot issues. There are two categories of Azure Website log files:

  •  Application diagnostic logs
  •  Site diagnostic logs
Application diagnostic logs contain information produced by the application code. This can be tracing that the developers instrumented when writing the code, or exceptions that were raised by the application. When you enable application logs, you must specify the logging level, which can be one of the following:

  •  Error
  •  Warning
  •  Information
  •  Verbose

Site diagnostic logs contain information produced by the web server that the web application is running on. Three types of site diagnostic logs can be enabled:

 Web Server Logging Contains all HTTP events on a website and is formatted using the W3C extended log file format
 Detailed Error Messages Contains information on requests that resulted in a HTTP status code of 400 or higher.
 Failed Request Tracing Contains detailed traces for any failed requests. This log also contains traces for all of the IIS components that were involved in processing the request. This can be useful when trying to isolate where in the system a failure is occurring.

Note :: Application diagnostic logs can be saved to the website's file system, Azure Table Storage,or Azure Blob Storage. The web server logging in site diagnostics can be saved to the website's file system or Azure Blob Storage.



Featured Posts

Adding Accesspolicy to KeyVault for Service Principal Using Portal and Powershell

  Scripts path : https://drive.google.com/drive/folders/1sbBpnVFgXhUIXLdf2E9heyWDeU2f9427?usp=sharing  Adding Accesspolicy to KeyVault for S...