You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-stack/hci/manage/collect-logs.md
+20-18Lines changed: 20 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: alkohli
6
6
ms.topic: how-to
7
7
ms.service: azure-stack
8
8
ms.subservice: azure-stack-hci
9
-
ms.date: 06/27/2024
9
+
ms.date: 09/27/2024
10
10
---
11
11
12
12
# Collect diagnostic logs for Azure Stack HCI
@@ -17,19 +17,19 @@ This article describes how to collect diagnostic logs for Azure Stack HCI and se
17
17
18
18
## About on-demand log collection
19
19
20
-
On-demand log collection involves manually collecting and sending diagnostic logs to Microsoft. The logs you collect are sent to the Kusto database. Microsoft Support can then use the information you provide to locate your logs in Kusto and assist you in resolving your reported issue. Microsoft retains this diagnostic data for up to 30 days and handles it as per the[standard privacy practices](https://privacy.microsoft.com/).
20
+
On-demand log collection refers to the process of manually gathering and sending diagnostic logs to Microsoft. These logs are stored in the Kusto database, where Microsoft Support can access them to help resolve your reported issues. The collected diagnostic data is retained for up to 30 days and is managed according to Microsoft’s[standard privacy practices](https://privacy.microsoft.com/).
21
21
22
22
### When to use on-demand log collection
23
23
24
-
Here are the scenarios in which you can perform on-demand log collection:
24
+
You can perform on-demand log collection in the following scenarios:
25
25
26
-
- Microsoft Support requests for logs based on an open case.
27
-
-Logs are collected when a cluster is connected and registered.
28
-
-Logs are collected when the observability components are operational and installed.
29
-
-Logs are collected when a cluster is only partly registered.
30
-
-Logs are collected for issues not related to registration failures.
26
+
-When Microsoft Support requests logs for an open case.
27
+
-When a cluster is connected and registered.
28
+
-When observability components are operational and installed.
29
+
-When a cluster is only partially registered.
30
+
-For issues unrelated to registration failures.
31
31
32
-
To explore other log collection methods in Azure Stack HCI and understand when to use them, see [Diagnostics](../concepts/observability.md#diagnostics).
32
+
For more information on other log collection methods in Azure Stack HCI and their appropriate use cases, see [Diagnostics](../concepts/observability.md#diagnostics).
33
33
34
34
## Prerequisites
35
35
@@ -56,18 +56,18 @@ Follow these steps to collect diagnostic logs for your Azure Stack HCI cluster v
56
56
57
57
:::image type="content" source="./media/collect-logs/get-started-tab.png" alt-text="Screenshot shows the Get started tab." lightbox="./media/collect-logs/get-started-tab.png" :::
58
58
59
-
1. On the **Diagnostics** tab, under **Log activity**, review log collection history for your cluster. To get more details about a specific log collection entry, select the link under **Time collected** and view the **Log details** pane.
1. On the **Send logs** pane on the right, select the **Log start time** and **Log end time**, and then select the **Collect and upload logs** button. By doing this, you agree to the terms and conditions of collecting logs.
63
+
1. On the **Send diagnostic logs to Microsoft** pane on the right, select the **Log start time** and **Log end time**, and then select the **Collect and upload logs** button. <!--check with Shireen about this-By doing this, you agree to the terms and conditions of collecting logs.->
1. (Optional) On the **Diagnostics** tab, under **Log activity**, you can review the log collection history for your cluster. To get more details about a specific log collection entry, select the link under **Time collected** and view the **Log detail** pane.
To use PowerShell for log collection, run the `Send-DiagnosticData` cmdlet from any node within the Azure Stack HCI cluster. This cmdlet temporarily copies the logs locally. The copied logs are parsed, sent to Microsoft, and then deleted from your system.
@@ -595,13 +595,15 @@ The following roles are available for filtering by the **FilterByRole** paramete
595
595
596
596
If you encounter an issue and need help from Microsoft Support, they might ask for specific information to locate your logs.
597
597
598
-
You can obtain this information directly from the problematic page in the Azure portal or from the output of the `Send-DiagnosticData` cmdlet.
599
-
600
598
### [Azure portal](#tab/azureportal)
601
599
602
-
On the problematic page in the Azure portal, press CTRL+ALT+A to download a diagnostic file with the following information: session ID and the URL. In most cases, this information is sufficient to get Microsoft Support started on troubleshooting.
600
+
Follow these steps to provide the required information in the Azure portal:
601
+
602
+
1. On the **Diagnostics** tab, under **Log activity**, select the link under **Time collected** for the relevant log.
603
+
604
+
1. On the **Log detail** pane, share the **UTC time zone** and **Correlation ID** values with Microsoft Support.
603
605
604
-
If you're on any of the Azure Stack HCI blades where you're experiencing issues, the current URI has the resource ID needed to debug the service.
606
+
:::image type="content" source="./media/collect-logs/log-details-pane-required-values.png" alt-text="Screenshot of the Log details pane highlighting the required information to share with Microsoft Support." lightbox="./media/collect-logs/log-details-pane-required-values.png" :::
0 commit comments