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. 🙂