Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for querying logs via Azure CLI, but PowerShell examples are consistently shown after Bash. However, there is a subtle Windows bias in the variable assignment example: the Bash example uses 'SET', which is a Windows CMD command, not standard Bash ('export' or variable assignment with '=' is typical in Bash). Additionally, PowerShell examples are present throughout, and the use of 'Invoke-AzOperationalInsightsQuery' is a Windows PowerShell-specific tool, with no mention of Linux/macOS alternatives for querying logs outside of Azure CLI. The Azure Portal instructions are platform-neutral.
Recommendations
- Correct the Bash variable assignment to use standard Bash syntax (e.g., WORKSPACE_ID=<WORKSPACE_ID> or export WORKSPACE_ID=<WORKSPACE_ID>) instead of 'SET', which is a Windows CMD command.
- Clarify that PowerShell examples are for Windows users, and Bash examples are for Linux/macOS users.
- If possible, provide examples using cross-platform tools (e.g., curl, jq) for querying logs, especially for Linux/macOS users.
- Explicitly state platform applicability for each example to reduce ambiguity.
- Consider providing a table or note summarizing command differences between platforms.
Create Pull Request