Skip to content

Commit 68f288c

Browse files
author
Manika Dhiman
committed
review feedback
1 parent 3bdbc98 commit 68f288c

File tree

4 files changed

+20
-18
lines changed

4 files changed

+20
-18
lines changed

azure-stack/hci/manage/collect-logs.md

Lines changed: 20 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: alkohli
66
ms.topic: how-to
77
ms.service: azure-stack
88
ms.subservice: azure-stack-hci
9-
ms.date: 06/27/2024
9+
ms.date: 09/27/2024
1010
---
1111

1212
# 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
1717

1818
## About on-demand log collection
1919

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/).
2121

2222
### When to use on-demand log collection
2323

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:
2525

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.
3131

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).
3333

3434
## Prerequisites
3535

@@ -56,18 +56,18 @@ Follow these steps to collect diagnostic logs for your Azure Stack HCI cluster v
5656

5757
:::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" :::
5858

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.
60-
61-
:::image type="content" source="./media/collect-logs/log-details-pane.png" alt-text="Screenshot shows the Log details pane." lightbox="./media/collect-logs/log-details-pane.png" :::
62-
6359
1. To collect and send logs now, select **Send logs**.
6460

6561
:::image type="content" source="./media/collect-logs/diagnostics-tab.png" alt-text="Screenshot shows the Send logs button." lightbox="./media/collect-logs/diagnostics-tab.png" :::
6662

67-
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.->
6864

6965
:::image type="content" source="./media/collect-logs/send-logs-pane.png" alt-text="Screenshot shows the Send logs pane." lightbox="./media/collect-logs/send-logs-pane.png" :::
7066

67+
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.
68+
69+
:::image type="content" source="./media/collect-logs/log-details-pane.png" alt-text="Screenshot shows the Log details pane." lightbox="./media/collect-logs/log-details-pane.png" :::
70+
7171
## [PowerShell](#tab/powershell)
7272

7373
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
595595

596596
If you encounter an issue and need help from Microsoft Support, they might ask for specific information to locate your logs.
597597

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-
600598
### [Azure portal](#tab/azureportal)
601599

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.
603605

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" :::
605607

606608
### [PowerShell](#tab/powershell)
607609

337 KB
Loading
105 KB
Loading
109 KB
Loading

0 commit comments

Comments
 (0)