Web App http logging does not work

Kris 0 Reputation points
2025-08-27T21:28:37.6833333+00:00

I am using a Web App in Azure and I want to log all incoming http get requests.

In the App Service Logs configuration page, I set Application logging (filesystem) on, set the log level to verbose + set Web Server logging to filesystem, and click save

Then I use a browser to request a few static web pages to make sure that some http get requests is processed.

But there is no \Home\LogFiles\http directory created after 30 minutes for the Web App so no raw http W3C files are visible.

What can be wrong here?

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Suwarna S Kale 3,956 Reputation points
    2025-08-28T03:02:11.5966667+00:00

    Hello Kris,

    Thank you for posting your question in the Microsoft Q&A forum. 

    The absence of the \LogFiles\http directory likely stems from a fundamental misunderstanding of the logging features you have enabled. Application Logging (Filesystem) captures output from your application's code, such as traces written via ILogger or Console.WriteLine, not raw HTTP requests.

    Similarly, Web Server Logging (Filesystem) records low-level IIS events but not in the customizable W3C format you expect. For comprehensive HTTP request logging, you must explicitly enable and configure HTTP Logging within your application's code, typically via middleware in Program.cs that records details like method, path, and status code.

    Additionally, ensure your application is actively handling requests and not encountering errors that bypass logging logic. If the application is functionally offline or misconfigured, no logs will generate. For a platform-based solution, consider enabling Diagnostic Settings to stream HTTP platform logs directly to Azure Monitor, Storage, or Event Hubs, which provides a more reliable and centralized approach without relying on local filesystem storage. Always verify that your application publishes content correctly and that logging configurations deploy successfully, as misapplied settings are a common culprit. 

    Please, let me know the response helps answer your question? If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. 🙂 


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.