Merge pull request #263664 from neilghuman/update-troubleshooter-ama

Update AMA troubleshooters

Author: ttorble

articles/azure-monitor/agents/troubleshooter-ama-linux.md

@@ -1,24 +1,62 @@
 ---
-title: Use Azure Monitor Agent Troubleshooter for Linux
+title: How to use the Linux Operating System (OS) Azure Monitor Agent Troubleshooter
 description: Detailed instructions on using the Linux agent troubleshooter tool to diagnose potential issues.
 ms.topic: conceptual
 author: RepinStyle
-ms.author: bhumphrey
+ms.author: guywild
 ms.date: 12/14/2023
 ms.custom: references_regions
 ms.reviewer: jeffwo
 
 # customer-intent: When AMA is experiencing issues, I want to investigate the issues and determine if I can resolve the issue on my own.
 ---
 
-# Use the Azure Monitor Agent Troubleshooter for Linux
+# How to use the Linux operating system (OS) Azure Monitor Agent Troubleshooter
 The Azure Monitor Agent Troubleshooter (AMA) is designed to help identify issues with the agent and perform general health assessments. It can perform various checks to ensure that the agent is properly installed and connected, and can also gather AMA-related logs from the machine being diagnosed.
 
 > [!Note]
 > The AMA Troubleshooter is an executable that is shipped with the agent for all versions newer than **1.25.1** for Linux.
 
 ## Prerequisites
-The linux Troubleshooter requires Python 2.6+ or any Python 3 installed on the machine. In addition, the following Python packages are required to run (all should be present on a default install of Python 2 or Python 3):
+
+### Python requirement
+The Linux AMA Troubleshooter requires **Python 2.6+** or any **Python 3** version installed on the machine.
+
+To check if python is installed on your machine, copy the following command and run in Bash as root:
+```Bash
+sudo python -V
+sudo python3 -V
+```
+
+:::image type="content" source="media/agent-linux/python-version-check.png" alt-text="Screenshot of commands to check Python version in Linux." lightbox="media/agent-linux/python-version-check.png":::
+
+Multiple versions of Python can be installed and aliased – if multiple versions are installed, use:
+
+```Bash
+ls -ls /usr/bing/python*
+```
+
+:::image type="content" source="media/agent-linux/python-multiple-version-check.png" alt-text="Screenshot of command to check multiple versions of Python for Linux." lightbox="media/agent-linux/python-multiple-version-check.png":::
+
+If your virtual machine is using a distro that doesn't include Python 3 by default, then you must install it. The following sample commands install Python 3 on different distros:
+
+# [Red Hat, CentOS, Oracle](#tab/redhat)
+```Bash
+sudo yum install -y python3
+```
+# [Ubuntu, Debian](#tab/ubuntu)
+```Bash
+sudo apt-get update
+sudo apt-get install -y python3
+```
+# [Suse](#tab/suse)
+```Bash
+sudo zypper install -y python3
+```
+
+---
+
+In addition, the following Python packages are required to run (all should be present on a default install of Python 2 or Python 3):
 
 |Python Package|Required for Python 2?|Required for Python 3?|
 |:---|:---|:---|
@@ -34,23 +72,27 @@ The linux Troubleshooter requires Python 2.6+ or any Python 3 installed on the m
 |url lib|yes|no|
 |xml.dom.minidom|yes|yes|
 
-On the machine to be diagnosed, does this directory exist:
+### Troubleshooter existence check
+Check for the existence of the AMA Agent Troubleshooter directory on the machine to be diagnosed to confirm the installation of the agent troubleshooter:
+
 ***/var/lib/waagent/Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-{version}***
 
-To verify the Agent Troubleshooter is present, copy the following command and run in Bash as root:
+To verify the Azure Monitor Agent Troubleshooter is presence, copy the following command and run in Bash as root:
 
 ```Bash
 ls -ltr /var/lib/waagent | grep "Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-*"
 ```
 
 :::image type="content" source="./media/use-azure-monitor-agent-troubleshooter/ama-nix-prerequisites-shell.png" alt-text="Screenshot of the Bash window, which shows the result of ls command for the AMA installation directory." lightbox="media/use-azure-monitor-agent-troubleshooter/ama-nix-prerequisites-shell.png":::
 
-If not, the directory doesn't exist and the installation failed. In this case, follow [Basic troubleshooting steps](azure-monitor-agent-troubleshoot-linux-vm.md#basic-troubleshooting-steps) instead.
+If directory doesn't exist or the installation is failed, follow [Basic troubleshooting steps](azure-monitor-agent-troubleshoot-linux-vm.md#basic-troubleshooting-steps).
 
-Yes, the directory exists. Proceed to [Run the Troubleshooter](#run-the-troubleshooter).
+If the directory exists, proceed to [Run the Troubleshooter](#run-the-troubleshooter).
 
 ## Run the Troubleshooter
-On the machine to be diagnosed, run the Agent Troubleshooter.
+On the machine to be diagnosed, run the Agent Troubleshooter. 
+
+**Log Mode** enables the collection of logs, which can then be compressed into .tgz format for export or review. **Interactive Mode** allows users to actively engage in troubleshooting scenarios and view the output directly within the shell.
 
 # [Log Mode](#tab/GenerateLogs)
 
@@ -87,7 +129,7 @@ It runs a series of scenarios and displays the results.
 > [!Note]
 > The interactive mode will **not** generate log files, but will **only** output results to the screen. Switch to log mode, if you need to generate log files.
 
-:::image type="content" source="media/use-azure-monitor-agent-troubleshooter/ama-nix-run-the-troubleshooter-option-l-shell.png" alt-text="Screenshot of the Bash window, which shows the result of the AgentTroubleshooter running with the -A option to output Troubleshooter results to the screen." lightbox="media/use-azure-monitor-agent-troubleshooter/ama-nix-run-the-troubleshooter-option-l-shell.png":::
+:::image type="content" source="media/agent-linux/ama-troubleshooter-interactive-mode.png" alt-text="Screenshot of the Bash window, which shows the result of the AgentTroubleshooter running with the -A option to output Troubleshooter results to the screen." lightbox="media/agent-linux/ama-troubleshooter-interactive-mode.png":::
 
 ---
 
@@ -98,4 +140,4 @@ It isn't possible to use the Troubleshooter to diagnose an older version of the
 
 ## Next Steps
 - [Troubleshooting guidance for the Azure Monitor agent](../agents/azure-monitor-agent-troubleshoot-linux-vm.md) on Linux virtual machines and scale sets
-- [Syslog troubleshooting guide for Azure Monitor Agent](../agents/azure-monitor-agent-troubleshoot-linux-vm-rsyslog.md) for Linux
+- [Syslog troubleshooting guide for Azure Monitor Agent](../agents/azure-monitor-agent-troubleshoot-linux-vm-rsyslog.md) for Linux

articles/azure-monitor/agents/troubleshooter-ama-windows.md

@@ -1,5 +1,5 @@
 ---
-title: Use Azure Monitor Agent Troubleshooter for Windows
+title: How to use the Windows operating system (OS) Azure Monitor Agent Troubleshooter
 description: Detailed instructions on using the Windows agent troubleshooter tool to diagnose potential issues.
 ms.topic: conceptual
 author: RepinStyle
@@ -11,14 +11,16 @@ ms.reviewer: jeffwo
 # customer-intent: When AMA is experiencing issues, I want to investigate the issues and determine if I can resolve the issue on my own.
 ---
 
-# Use the Azure Monitor Agent Troubleshooter for Windows
+# How to use the Windows operating system (OS) Azure Monitor Agent Troubleshooter
 The Azure Monitor Agent (AMA) Troubleshooter is designed to help identify issues with the agent and perform general health assessments. It can perform various checks to ensure that the agent is properly installed and connected, and can also gather AMA-related logs from the machine being diagnosed.
 
 > [!Note]
-> The AMA Troubleshooter is a command line executable that is shipped with the agent for all versions newer than **1.12.0.0** for Windows. 
+> The Windows AMA Troubleshooter is a command line executable that is shipped with the agent for all versions newer than **1.12.0.0**. 
 
 ## Prerequisites
-On the machine to be diagnosed, does this directory exist:
+### Troubleshooter existence check
+Check for the existence of the AMA Agent Troubleshooter directory on the machine to be diagnosed to confirm the installation of the agent troubleshooter:
+
 ***C:/Packages/Plugins/Microsoft.Azure.Monitor.AzureMonitorWindowsAgent***
 
 # [PowerShell](#tab/WindowsPowerShell)
@@ -43,7 +45,7 @@ If the directory exists, the cd command changes directories successfully.
 
 ---
 
-If not, the directory doesn't exist and the installation failed. In this case, follow [Basic troubleshooting steps](../agents/azure-monitor-agent-troubleshoot-windows-vm.md#basic-troubleshooting-steps-installation-agent-not-running-configuration-issues) instead.
+If directory doesn't exist or the installation is failed, follow [Basic troubleshooting steps](../agents/azure-monitor-agent-troubleshoot-windows-vm.md#basic-troubleshooting-steps-installation-agent-not-running-configuration-issues).
 
 Yes, the directory exists. Proceed to [Run the Troubleshooter](#run-the-troubleshooter).
 
@@ -96,4 +98,4 @@ It isn't possible to use the Troubleshooter to diagnose an older version of the
 
 ## Next Steps
 - [Troubleshooting guidance for the Azure Monitor agent](../agents/azure-monitor-agent-troubleshoot-windows-vm.md) on Windows virtual machines and scale sets
-- [Troubleshooting guidance for the Azure Monitor agent](../agents/azure-monitor-agent-troubleshoot-windows-arc.md) on Windows Arc-enabled server
+- [Troubleshooting guidance for the Azure Monitor agent](../agents/azure-monitor-agent-troubleshoot-windows-arc.md) on Windows Arc-enabled server