Freshness review

Author: PatAltimore

articles/iot-edge/troubleshoot-in-portal.md

@@ -4,7 +4,7 @@ description: Use the troubleshooting page in the Azure portal to monitor IoT Edg
 author: PatAltimore
 
 ms.author: patricka
-ms.date: 04/08/2024
+ms.date: 05/09/2025
 ms.topic: conceptual
 ms.service: azure-iot-edge
 services: iot-edge
@@ -14,63 +14,63 @@ services: iot-edge
 
 [!INCLUDE [iot-edge-version-all-supported](includes/iot-edge-version-all-supported.md)]
 
-IoT Edge provides a streamlined way of monitoring and troubleshooting modules in the Azure portal. The troubleshooting page is a wrapper for the IoT Edge agent's direct methods so that you can easily retrieve logs from deployed modules and remotely restart them. This article shows you how to access and filter device and module logs in the Azure portal.
+IoT Edge lets you monitor and troubleshoot modules in the Azure portal. The troubleshooting page wraps the IoT Edge agent's direct methods, letting you retrieve logs from deployed modules and restart them remotely. This article explains how to access and filter device and module logs in the Azure portal.
 
 ## Access the troubleshooting page
 
 You can access the troubleshooting page in the portal through either the IoT Edge device details page or the IoT Edge module details page.
 
-1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your IoT hub.
+1. Sign in to the [Azure portal](https://portal.azure.com), and go to your IoT hub.
 
-1. In the left pane, select **Devices** under the **Device management** menu.
+1. In the left pane, select **Devices** under **Device management**.
 
 1. Select the IoT Edge device that you want to monitor from the list of devices.
 
-1. On this device details page, you can either select **Troubleshoot** from the menu.
+1. On the device details page, select **Troubleshoot** from the menu.
 
-   :::image type="content" source="./media/troubleshoot-in-portal/troubleshoot-tab.png" alt-text="Screenshot of the location of the Troubleshoot tab on the Azure portal, device details page.":::
+   :::image type="content" source="./media/troubleshoot-in-portal/troubleshoot-tab.png" alt-text="Screenshot of the Troubleshoot tab on the Azure portal device details page.":::
 
-   Or, select the runtime status of a particular module that you want to inspect.
+   Or, select the runtime status of the module you want to inspect.
 
-   :::image type="content" source="./media/troubleshoot-in-portal/runtime-status.png" alt-text="Screenshot of the location of the Runtime status column on the Azure portal, device details page." lightbox="./media/troubleshoot-in-portal/runtime-status.png":::
+   :::image type="content" source="./media/troubleshoot-in-portal/runtime-status.png" alt-text="Screenshot of the Runtime status column on the Azure portal device details page." lightbox="./media/troubleshoot-in-portal/runtime-status.png":::
 
-1. From the device details page, you can also select the name of a module to open the module details page. From there, you can select **Troubleshoot** from the menu.
+1. From the device details page, select the name of a module to open the module details page. Then, select **Troubleshoot** from the menu.
 
-   :::image type="content" source="./media/troubleshoot-in-portal/troubleshoot-module.png" alt-text="Screenshot of the location of the Troubleshoot tab on the Azure portal, module details page.":::
+   :::image type="content" source="./media/troubleshoot-in-portal/troubleshoot-module.png" alt-text="Screenshot of the Troubleshoot tab on the Azure portal module details page.":::
 
 ## View module logs in the portal
 
 On the **Troubleshoot** page of your device, you can view and download logs from any of the running modules on your IoT Edge device.
 
-This page has a maximum limit of 1,500 log lines, and any logs longer are truncated. If the logs are too large, the attempt to get module logs fails. In that case, try to change the time range filter to retrieve less data or consider using direct methods to [Retrieve logs from IoT Edge deployments](how-to-retrieve-iot-edge-logs.md) to gather larger log files.
+This page has a maximum limit of 1,500 log lines, and logs longer than this are truncated. If the logs are too large, the attempt to get module logs fails. In that case, change the time range filter to retrieve less data or use direct methods to [retrieve logs from IoT Edge deployments](how-to-retrieve-iot-edge-logs.md) to gather larger log files.
 
 Use the dropdown menu to choose which module to inspect.
 
 :::image type="content" source="./media/troubleshoot-in-portal/select-module.png" alt-text="Screenshot showing how to choose a module from the dropdown menu that you want to inspect.":::
 
-By default, this page displays the last 15 minutes of logs. Select the **Time range** filter to see different logs. Use the slider to select a time window within the last 60 minutes, or check **Enter time instead** to choose a specific datetime window.
+By default, this page shows the last 15 minutes of logs. Select the **Time range** filter to view different logs. Use the slider to select a time window within the last 60 minutes, or select **Enter time instead** to choose a specific datetime window.
 
 :::image type="content" source="./media/troubleshoot-in-portal/select-time-range.png" alt-text="Screenshot showing how to choose a time or time range from the time range popup filter.":::
 
-Once you have the logs and set your time filter from the module you want to troubleshoot, you can use the **Find** filter to retrieve specific lines from the logs. You can filter for either warnings or errors, or provide a specific term or phrase to search for. 
+After you get the logs and set your time filter for the module you want to troubleshoot, use the **Find** filter to retrieve specific lines from the logs. Filter for warnings, errors, or a specific term or phrase. 
 
 :::image type="content" source="./media/troubleshoot-in-portal/find-filter.png" alt-text="Screenshot showing how to use a dotnet regex pattern to search the logs, using the Find filter.":::
 
-The **Find** feature supports plaintext searches or [.NET regular expressions](/dotnet/standard/base-types/regular-expression-language-quick-reference) for more complex searches.
+The **Find** feature supports plaintext searches and [.NET regular expressions](/dotnet/standard/base-types/regular-expression-language-quick-reference) for complex searches.
 
 You can download the module logs as a text file. The downloaded log file reflects any active filters you applied to the logs.
 
 >[!TIP]
->The CPU utilization on a device spikes temporarily as it gathers logs in response to a request from the portal. This behavior is expected, and the utilization should stabilize after the task is complete.
+>The CPU utilization on a device temporarily spikes as it gathers logs in response to a portal request. This behavior is expected, and the utilization stabilizes after the task is complete.
 
 ## Restart modules
 
-The **Troubleshoot** page includes a feature to restart a module. Selecting this option sends a command to the IoT Edge agent to restart the selected module. Restarting a module won't affect your ability to retrieve logs from before the restart.
+The **Troubleshoot** page lets you restart a module. Selecting this option sends a command to the IoT Edge agent to restart the selected module. Restarting a module doesn't affect your ability to retrieve logs from before the restart.
 
-:::image type="content" source="./media/troubleshoot-in-portal/restart-module.png" alt-text="Screenshot that shows how to restart a module from the Troubleshoot page.":::
+:::image type="content" source="./media/troubleshoot-in-portal/restart-module.png" alt-text="Screenshot of how to restart a module from the Troubleshoot page.":::
 
 ## Next steps
 
-Find more tips for [Troubleshooting your IoT Edge device](troubleshoot.md) or learn about [Common issues and resolutions](troubleshoot-common-errors.md). 
+Find more tips for [troubleshooting your IoT Edge device](troubleshoot.md) or learn about [common issues and resolutions](troubleshoot-common-errors.md).
 
-If you have more questions, create a [Support request](https://portal.azure.com/#create/Microsoft.Support) for help.
+If you have more questions, create a [support request](https://portal.azure.com/#create/Microsoft.Support) for help.