Redis
69
Total Pages
42
Linux-Friendly Pages
27
Pages with Bias
39.1%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
144 issues found
Showing 126-144 of 144 flagged pages
Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/troubleshoot-client.md
...e-docs/blob/main/articles/redis/troubleshoot-client.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references the 'Page Faults/Sec' performance counter, which is a Windows-specific monitoring metric, without mentioning equivalent Linux tools or metrics. There are no Linux-specific examples or guidance for monitoring memory pressure or other client-side issues.
Recommendations
- Include Linux equivalents for monitoring memory pressure, such as using 'vmstat', 'top', 'free', or checking '/proc/meminfo'.
- Mention Linux-specific metrics or commands (e.g., 'vmstat -s', 'sar -B', or 'ps') alongside Windows performance counters.
- Provide example commands or scripts for both Windows (Performance Monitor, PowerShell) and Linux (shell commands) to ensure parity.
- Use platform-neutral language where possible, or explicitly address both Windows and Linux environments in troubleshooting steps.
Create Pull Request
Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/aspnet-core-output-cache-provider.md
...in/articles/redis/aspnet-core-output-cache-provider.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently refers to 'command prompt' and uses Windows-centric terminology and patterns (e.g., 'cmd' code blocks, references to 'command prompt', and instructions like 'code .'), without mentioning or providing equivalent instructions for Linux or macOS users. There are no bash/zsh examples, and no mention of terminal or shell alternatives. This may confuse or exclude non-Windows users.
Recommendations
- Use neutral terms like 'terminal' or 'shell' instead of 'command prompt', and clarify that instructions apply to Windows, Linux, and macOS.
- Provide both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) command examples, using appropriate code block annotations (e.g., 'cmd', 'bash').
- Mention that .NET CLI commands work cross-platform, and specify any OS-specific differences if relevant.
- Include notes or callouts for any steps that differ on Linux/macOS (e.g., launching VS Code, environment variable management).
- Review and update screenshots, output, and instructions to ensure they are not Windows-specific unless necessary.
Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/dotnet-core-quickstart.md
...ocs/blob/main/articles/redis/dotnet-core-quickstart.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias by using Windows-centric command prompts (e.g., 'dos' code blocks), and omits explicit Linux or cross-platform shell examples. There is no mention of Linux-specific instructions or terminal usage, and the build/run commands are shown in a Windows context. No Linux tools or shell commands are referenced, and the instructions for editing configuration files do not acknowledge platform differences.
Recommendations
- Provide both Windows (cmd/PowerShell) and Linux/macOS (bash) command examples for building and running the app.
- Use 'bash' or 'shell' code blocks for cross-platform commands instead of 'dos', or show both.
- Explicitly state that the .NET Core SDK and StackExchange.Redis are cross-platform, and mention any platform-specific considerations.
- Include screenshots or terminal output from both Windows and Linux environments where applicable.
- Clarify file path conventions (e.g., backslashes vs. forward slashes) if relevant.
- Mention that editing configuration files (like appsettings.json) is the same across platforms, but note where file locations or editors may differ.
Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/nodejs-get-started.md
...re-docs/blob/main/articles/redis/nodejs-get-started.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias in its instructions for setting environment variables and installing Node.js. Specifically, it only provides Windows-specific commands (using 'set' in cmd.exe) for setting environment variables and links exclusively to Windows installation instructions for Node.js. There are no Linux or macOS equivalents provided for these common setup steps, which may hinder non-Windows users.
Recommendations
- Provide equivalent Linux/macOS commands for setting environment variables (e.g., 'export VAR=value' for bash/zsh).
- Include a link to Node.js installation instructions for Linux and macOS, or reference the official Node.js installation page that covers all platforms.
- Consider using cross-platform instructions or clearly labeling platform-specific steps, ensuring parity and clarity for all users.
- Wherever possible, use code blocks with platform tabs or side-by-side examples for Windows, Linux, and macOS.
Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/troubleshoot-client.md
...e-docs/blob/main/articles/redis/troubleshoot-client.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references the 'Page Faults/Sec' performance counter, which is a Windows-specific monitoring tool, without mentioning Linux equivalents or providing cross-platform guidance. There are no Linux-specific commands, tools, or examples for monitoring memory pressure or other client-side issues.
Recommendations
- Include Linux equivalents for monitoring memory usage and page faults, such as referencing 'vmstat', 'top', or 'free' commands.
- When mentioning Windows-specific tools (like 'Page Faults/Sec'), add parallel instructions for Linux environments.
- Provide example commands or scripts for both Windows (e.g., using Performance Monitor) and Linux (e.g., using 'ps', 'vmstat', or 'htop') to ensure parity.
- Review other troubleshooting steps to ensure that any platform-specific advice is balanced with alternatives for major operating systems.
Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/python-get-started.md
...re-docs/blob/main/articles/redis/python-get-started.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias, particularly in the installation instructions for Python and the redis-py library. Windows-specific instructions and links are provided before or instead of Linux equivalents, and screenshots show Windows terminals. There are no explicit Linux/macOS command-line examples or screenshots, and the command-line usage section references the Windows-specific 'py' launcher and Windows Python FAQ, without mentioning Linux/macOS alternatives.
Recommendations
- Provide parallel installation instructions and links for Linux and macOS users alongside Windows instructions, not after or as an afterthought.
- Include screenshots of terminal sessions from Linux/macOS environments, or use generic terminal screenshots where possible.
- When referencing command-line usage, mention both 'python3' (Linux/macOS) and 'py' (Windows), and avoid linking only to Windows-specific documentation.
- Explicitly state any OS-specific differences in commands, paths, or environment setup.
- Ensure all code and command-line examples are cross-platform or provide OS-specific variants as appropriate.
Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/redis-cache-bicep-provision.md
...lob/main/articles/redis/redis-cache-bicep-provision.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying and managing Azure Cache for Redis resources. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI in all code example tabs, and is always presented immediately after CLI, rather than being de-emphasized or separated. There are no Linux-specific shell examples (e.g., Bash), and no mention of Linux tooling or patterns. The documentation assumes parity between CLI and PowerShell, but does not clarify that PowerShell is primarily a Windows tool, nor does it highlight Linux workflows or considerations.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and available on Linux, macOS, and Windows, while PowerShell examples are primarily for Windows users.
- Add Bash shell examples or clarify that Azure CLI commands can be run in Bash on Linux/macOS.
- Consider presenting CLI (Bash) examples first, and PowerShell examples second, to avoid implicit Windows-first bias.
- Add a note or section about installing and using Azure CLI on Linux, and link to relevant documentation.
- Where appropriate, provide Linux-specific troubleshooting or environment setup tips.
Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/web-app-aspnet-core-howto.md
.../blob/main/articles/redis/web-app-aspnet-core-howto.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page provides instructions and code samples that are platform-neutral in most places, but the 'Run the app locally' section uses 'dos' code blocks and refers to a 'command window' without clarifying cross-platform usage. There are no explicit Linux or macOS terminal instructions or examples, and no mention of Linux-specific tools or patterns. This may cause confusion for Linux users or suggest a Windows-first approach.
Recommendations
- Provide explicit Linux/macOS terminal instructions alongside Windows instructions, using 'bash' or 'sh' code blocks where appropriate.
- Replace or supplement 'command window' with 'terminal' or 'shell', and clarify that the dotnet CLI commands work on all platforms.
- Add a note or section confirming cross-platform compatibility, and if there are any platform-specific steps (such as environment variable configuration or file path differences), document them.
- Include screenshots or terminal output examples from Linux/macOS environments, not just Windows.
- Avoid using 'dos' code blocks unless the commands are truly Windows-specific; use 'console', 'bash', or 'shell' for cross-platform commands.
Redis
Best practices for development for Azure Managed Redis
...blob/main/articles/redis/best-practices-development.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page for Azure Managed Redis exhibits mild Windows bias, particularly in the 'Consider enabling Data Persistence or Data Backup' section, where export operations are described as being triggered from the portal, CLI, PowerShell, or SDK tools. PowerShell is mentioned explicitly, while Linux/macOS equivalents (such as Bash, Azure CLI on Linux, or shell scripting) are not referenced. Additionally, the ordering of tools places PowerShell before SDK tools, which may suggest a Windows-first approach. No explicit Linux/macOS examples or tools are provided, and there are no code samples demonstrating cross-platform usage.
Recommendations
- Explicitly mention Linux/macOS-compatible tools, such as Bash and Azure CLI, alongside PowerShell.
- Provide example commands for both PowerShell and Bash/Azure CLI to illustrate cross-platform usage.
- Avoid listing Windows tools (PowerShell) before cross-platform tools unless there is a technical reason.
- Add a note clarifying that all operations can be performed from Linux/macOS environments using Azure CLI and SDKs.
Redis
Import and Export data in Azure Managed Redis
.../blob/main/articles/redis/how-to-import-export-data.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing Windows and PowerShell examples and terminology before Linux equivalents. In the FAQ, automation instructions mention PowerShell first, then Azure CLI, without explicit Linux/macOS parity notes. The documentation does not provide Linux/macOS-specific examples or highlight cross-platform CLI usage, and references to Windows environments precede Linux in some sections.
Recommendations
- Present Azure CLI instructions before or alongside PowerShell, emphasizing CLI as cross-platform.
- Explicitly mention that Azure CLI works on Linux/macOS and provide example commands for those platforms.
- Include screenshots or instructions for Linux/macOS environments where applicable.
- Avoid listing Windows environments before Linux unless contextually relevant.
- Add notes or links for Linux/macOS users regarding prerequisites or differences in workflow.
Redis
Scale an Azure Managed Redis instance
...cs/azure-docs/blob/main/articles/redis/how-to-scale.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing PowerShell as the first scripting/tool example for scaling Azure Managed Redis, followed by Azure CLI. PowerShell is a Windows-centric tool, while Azure CLI is cross-platform. No Linux/macOS-specific instructions or examples are provided, but the CLI examples are applicable to all platforms. There are no exclusive references to Windows-only tools or patterns, and the CLI is given equal coverage.
Recommendations
- List Azure CLI examples before PowerShell, as CLI is cross-platform and more widely used outside Windows.
- Explicitly mention that Azure CLI commands work on Linux/macOS/Windows, and that PowerShell is primarily for Windows users.
- Add a brief note or section for Linux/macOS users, confirming that all CLI instructions are fully supported on those platforms.
- Consider including Bash or shell script examples for common automation tasks, if relevant.
Redis
Quickstart: Connect to Azure Managed Redis with TypeScript in a Node.js app
...re-docs/blob/main/articles/redis/nodejs-get-started.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates minor Windows bias by using 'dos' code blocks for build/run commands (tsc, node index.js), which suggests a Windows command prompt. There are no explicit Linux/macOS examples or terminal instructions, and the order of presentation favors Windows conventions. However, the actual commands are cross-platform, and no Windows-specific tools or patterns are required.
Recommendations
- Use 'bash' or 'sh' code blocks for generic commands that work across platforms.
- Add explicit notes or examples for Linux/macOS users, such as running commands in a terminal.
- Clarify that the commands provided work on all major platforms, not just Windows.
- If there are platform-specific steps (e.g., environment variables, file paths), document them for both Windows and Linux/macOS.
Redis
Deploy Azure Cache for Redis using Bicep
...lob/main/articles/redis/redis-cache-bicep-provision.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup tasks. However, PowerShell examples are given equal prominence to CLI, and the use of PowerShell (a Windows-centric tool) is highlighted throughout. There is no explicit mention of Linux/macOS-specific considerations, nor are there any examples using Bash scripting or other Linux-native tools. The CLI examples are cross-platform, but the documentation does not clarify this, and PowerShell is not available natively on most Linux distributions.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and are recommended for cross-platform usage.
- Note that PowerShell is primarily a Windows tool, and provide installation guidance for PowerShell Core on Linux/macOS if PowerShell usage is necessary.
- Consider listing CLI examples first, as they are more universally applicable.
- Add explicit statements or sections for Linux/macOS users, confirming that all steps can be completed on those platforms using Azure CLI.
- Remove or de-emphasize PowerShell if not strictly required, or provide Bash equivalents for scripting tasks.
Redis
Configure active geo-replication for Azure Managed Redis instances
...b/main/articles/redis/how-to-active-geo-replication.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring geo-replication, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and no explicit Linux/macOS shell examples (e.g., Bash, zsh) are provided. There are no instructions or notes for Linux/macOS users regarding environment setup, nor are there references to platform-specific differences. The CLI examples are generic and cross-platform, but PowerShell's inclusion and parity may suggest a slight Windows bias, especially since PowerShell is not natively available on most Linux/macOS systems.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS and Windows equally, and provide explicit Bash/zsh shell examples where appropriate.
- Add a note about installing Azure CLI on Linux/macOS, with a link to installation instructions.
- Mention that PowerShell is available cross-platform, but is less commonly used on Linux/macOS; consider prioritizing CLI examples or providing Bash script equivalents.
- If there are platform-specific behaviors (e.g., file paths, authentication), call these out in the documentation.
- Consider listing CLI examples before PowerShell, as CLI is more universal.
Redis
Quickstart: Connect to Azure Managed Redis with TypeScript in a Node.js app
...re-docs/blob/main/articles/redis/nodejs-get-started.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows minor Windows bias by using the 'dos' code block for build/run commands (tsc, node index.js), which implies Windows command prompt usage and may confuse Linux/macOS users. No explicit Linux/macOS examples or terminal instructions are provided, and Windows is implicitly prioritized in the run instructions.
Recommendations
- Use 'bash' or 'sh' code blocks for cross-platform commands like 'tsc' and 'node index.js', or provide both Windows and Linux/macOS examples.
- Add a note clarifying that these commands work in any terminal (Windows CMD, PowerShell, Bash, Zsh, etc.).
- Explicitly mention Linux/macOS compatibility in the prerequisites and run sections.
- If any platform-specific steps exist (e.g., environment variables, file paths), document them for both Windows and Linux/macOS.
Redis
Deploy Azure Cache for Redis using Bicep
...lob/main/articles/redis/redis-cache-bicep-provision.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment and resource management tasks. However, PowerShell examples are given equal prominence to CLI, and the PowerShell examples use Windows-specific cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResourceGroup) without noting that PowerShell on Linux/macOS may require additional setup. The CLI examples are cross-platform, but PowerShell is a Windows-centric tool and is presented as a primary option throughout, which may create friction for Linux/macOS users.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note clarifying that Azure PowerShell is available on Linux/macOS, but may require installation and configuration.
- Consider listing CLI examples first to emphasize cross-platform compatibility.
- Provide links or instructions for installing Azure PowerShell on Linux/macOS if PowerShell usage is recommended.
- Explicitly state that all tasks can be completed using Azure CLI, which is natively supported on Linux/macOS.
Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/quickstart-create-managed-redis.md
...main/articles/redis/quickstart-create-managed-redis.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any platform-specific examples or instructions, but it also omits any mention of command-line tools or steps for either Windows or Linux. However, the absence of Linux-specific instructions or parity checks (such as CLI commands, shell scripts, or Linux tooling) can be considered a subtle bias, as many Azure quickstarts often default to Windows-centric tools or examples elsewhere. In this case, the page is neutral but lacks explicit Linux guidance.
Recommendations
- Add explicit instructions or examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash, Azure CLI on Linux) when showing how to create or manage a Redis instance.
- Include sample commands for common Linux shells (bash, zsh) alongside any Windows examples.
- If using downloadable scripts or templates, provide both .ps1 (PowerShell) and .sh (Bash) versions.
- Reference Linux-specific tools or workflows (such as using Azure CLI on Linux) in the prerequisites or creation steps.
Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/quickstart-create-managed-redis.md
...main/articles/redis/quickstart-create-managed-redis.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any platform-specific examples or instructions. However, it also does not include any Linux-specific guidance, CLI commands, or cross-platform considerations. The absence of examples or instructions means Linux users are not directly excluded, but there is a missed opportunity to ensure parity by explicitly including Linux-relevant content.
Recommendations
- Add explicit examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash, Azure CLI on Linux) when demonstrating how to create or manage a Redis instance.
- Mention cross-platform tools such as the Azure CLI and provide installation or usage instructions for both Windows and Linux environments.
- If using code snippets or command-line instructions, ensure both Windows and Linux variants are shown side by side or clearly labeled.
- Include troubleshooting notes or prerequisites that are relevant to Linux users, such as package dependencies or environment setup.
Redis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/redis/includes/cache-delete-resource-group.md
...articles/redis/includes/cache-delete-resource-group.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation only describes how to delete a resource group using the Azure Portal (web UI) and does not provide any command-line examples. There are no instructions for deleting resource groups using cross-platform tools such as Azure CLI or Azure PowerShell. This omission can disadvantage Linux users who are more likely to use CLI tools, as no Linux-friendly (or even cross-platform) command-line instructions are provided.
Recommendations
- Add examples for deleting a resource group using the Azure CLI (az group delete), which works on Windows, Linux, and macOS.
- If relevant, provide Azure PowerShell examples, but ensure Azure CLI is presented first or alongside it for cross-platform parity.
- Explicitly mention that the Azure Portal method is platform-agnostic, but highlight that CLI methods are available for automation and scripting, especially for Linux users.
- Include links to official documentation for both Azure CLI and Azure PowerShell resource group deletion commands.