Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response and for extension installation. However, in several sections, PowerShell/Windows examples are presented before or with more detail than Linux equivalents. The PowerShell tab for installing the extension uses 'ApplicationHealthWindows' as the default type, while the CLI example uses 'ApplicationHealthLinux'. The PowerShell HTTP server example is more elaborate than the Bash/Python one. The documentation sometimes refers to Windows-specific extension types first and provides more PowerShell-centric guidance, which may create friction for Linux users.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, and alternate which is shown first in tabbed sections.
- When referencing extension types, clarify when to use 'ApplicationHealthLinux' vs. 'ApplicationHealthWindows' and provide explicit Linux-focused examples in PowerShell sections if relevant.
- Balance the detail and complexity of Linux and Windows sample scripts (e.g., the Bash/Python HTTP server could include more robust error handling or logging, similar to the PowerShell example).
- Where possible, provide cross-platform (e.g., Python-only) examples that work on both Linux and Windows.
- In troubleshooting and verification sections, ensure Linux commands (e.g., Bash/curl) are as detailed as PowerShell equivalents.
Create Pull Request