About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
missing_linux_example
⚠️
windows_tools
Summary:
The documentation page demonstrates a Windows-first bias by providing more detailed instructions, features, and examples for Windows App Service apps compared to Linux. Several logging types (web server logging, detailed error messages, failed request tracing) are documented only for Windows, with no Linux equivalents or alternatives described. Windows-specific tools and file paths are mentioned (e.g., Log Parser, D:\home\LogFiles), while Linux paths and tools are less emphasized or omitted. There are also sections where only .NET (Windows) logging to blob storage is supported, with other languages/platforms (often used on Linux) excluded or requiring code changes.
Recommendations:
- Provide equivalent, step-by-step instructions for enabling web server logging, detailed error messages, and failed request tracing on Linux App Service (or clearly state if these features are unavailable).
- Include Linux-specific file paths and examples (e.g., /home/LogFiles) alongside Windows paths in all relevant sections.
- Mention Linux-compatible tools for viewing and parsing logs (e.g., less, tail, grep, jq) in addition to or instead of Windows tools like Log Parser.
- Clarify feature parity and limitations for Linux and container-based App Service plans, and offer workarounds or alternatives where features are missing.
- Expand code examples to include common Linux-targeted languages and frameworks (Node.js, Python, Java) with logging best practices for App Service.
- Where a feature is Windows-only, provide a clear note and suggest alternative approaches for Linux users.
Create pull request