Skip to content

Commit ef4d524

Browse files
author
Manika Dhiman
committed
Updates
1 parent 71d6177 commit ef4d524

File tree

6 files changed

+36
-98
lines changed

6 files changed

+36
-98
lines changed

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

Lines changed: 0 additions & 78 deletions
This file was deleted.

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

Lines changed: 36 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,29 @@
11
---
22
title: Collect diagnostic logs for Azure Stack HCI
3-
description: How to collect diagnostic logs and share them with Microsoft.
3+
description: Learn how to collect diagnostic logs and share them with Microsoft.
44
author: alkohli
55
ms.author: alkohli
66
ms.topic: how-to
77
ms.service: azure-stack
88
ms.subservice: azure-stack-hci
9-
ms.date: 03/19/2024
9+
ms.date: 06/18/2024
1010
---
1111

1212
# Collect diagnostic logs for Azure Stack HCI
1313

1414
[!INCLUDE [applies-to](../../includes/hci-applies-to-23h2.md)]
1515

16-
This article describes how to collect diagnostic logs and send them to Microsoft to help identify and fix any issues with your Azure Stack HCI solution.
16+
This article describes how to collect diagnostic logs for Azure Stack HCI and send them to Microsoft via the Azure portal or PowerShell. These diagnostic logs help identify and fix any issues with your Azure Stack HCI solution.
1717

1818
## On-demand log collection
1919

20-
On-demand log collection involves manually collecting and sending diagnostic logs to Microsoft using the `Send-DiagnosticData` cmdlet from any node within the Azure Stack HCI cluster. When you run this cmdlet, the logs are temporarily copied locally. This copy is parsed, sent to Microsoft, and then deleted from your system. 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 involves manually collecting and sending diagnostic logs to Microsoft. After you collect logs, they're sent to the Kusto database. Microsoft Support can then use the information provided to locate your logs in Kusto and help you in resolving the 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/).
21+
22+
You can perform on-demand log collection using any of the following methods:
23+
24+
- **(Recommended) Azure portal**. Use this method when you want to collect logs at the cluster level and send them to Microsoft. See [Collect logs via the Azure portal](#collect-logs-via-the-azure-portal)
25+
26+
- **PowerShell**. Use this method if you want to collect logs based on specific parameters. You can save them to an SMB share, send supplementary logs, or send logs for specific rules only. To collect logs and send them to Microsoft, run the `Send-DiagnosticData` cmdlet from any node within the Azure Stack HCI cluster. When you run this cmdlet, the logs are temporarily copied locally. This copy is parsed, sent to Microsoft, and then deleted from your system. See [Collect logs via PowerShell](#collect-logs-via-powershell)
2127

2228
### When to use on-demand log collection
2329

@@ -33,15 +39,38 @@ To explore additional log collection methods in Azure Stack HCI and understand w
3339

3440
## Prerequisites
3541

36-
Before you collect on-demand logs, you must complete the following prerequisites:
42+
Before you collect on-demand logs via the Azure portal, you must complete the following prerequisites:
3743

3844
- You must have access to an Azure Stack HCI cluster.
3945
- You must have access to Azure.
4046
- You must have installed the `AzureEdgeTelemetryAndDiagnostics` extension to collect telemetry and diagnostics information from your Azure Stack HCI system. For information about the extension, see [Azure Stack HCI telemetry and diagnostics extension overview](../concepts/telemetry-and-diagnostics-overview.md).
47+
- You must review the terms and conditions for log collection.
48+
49+
## Collect logs via the Azure portal
50+
51+
Follow these steps to collect diagnostic logs for you Azure Stack HCI cluster via the Azure portal:
52+
53+
1. the Azure portal, go to the Azure Stack HCI cluster resource.
54+
1. In the left pane, under **Settings**, select **Diagnostics and Remote Support**.
55+
1. On the **Get started** tab, under the **Send Diagnostics Logs** tile, select **Go to diagnostics**.
56+
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+
59+
1. On the **Diagnostics** page, under **Log activity**, review log collection history. You can also select a link under **Time collected** to view details about a specific log collection in the **Log details** pane.
60+
61+
:::image type="content" source="./media/collect-logs/log-details-pane.png" alt-text="Screenshot shows the Diagnostics tab." lightbox="./media/collect-logs/log-details-pane.png" :::
4162

42-
## Perform on-demand log collection via PowerShell
63+
1. To collect and send logs now, select **Send logs** .
4364

44-
You can perform on-demand log collection using PowerShell, the recommended method, or Windows Admin Center in the Azure portal, as described later in this article.
65+
:::image type="content" source="./media/collect-logs/diagnostics-tab.png" alt-text="Screenshot shows the Diagnostics tab." lightbox="./media/collect-logs/diagnostics-tab.png" :::
66+
67+
1. On the **Send logs** pane on the right, select the **Log start time** and **Log end time**.
68+
69+
1. Select the **Collect and upload logs** button. By selecting this, you agree to the terms and conditions of collection logs.
70+
71+
:::image type="content" source="./media/collect-logs/send-logs-pane.png" alt-text="Screenshot shows the Diagnostics tab." lightbox="./media/collect-logs/send-logs-pane.png" :::
72+
73+
## Collect logs via PowerShell
4574

4675
Run the `Send-DiagnosticData` cmdlet from any node on your Azure Stack HCI cluster to perform on-demand log collection.
4776

@@ -586,19 +615,6 @@ The following roles are available for filtering by the **FilterByRole** paramete
586615
| TestObservability | Collects logs from the `Test-Observability` cmdlet, which is used to test that the `TelemetryAndDiagnostics` extension is working properly. |
587616
| URP | Consists of logs related to the `UpdateService` and `OsUpdate` ECE role events. The `Update Service` manages updates for Azure Stack HCI systems. The `OsUpdate` ECE role is used to acquire and install operating system updates on machines (physical hosts and InfraVMs) which aren't part of the cluster during the deployment, add node, repair node, and Infra VMs update scenarios. Traces from these two components are part of the `URP` role. |
588617

589-
## Perform on-demand log collection via Windows Admin Center in the Azure portal
590-
591-
The `Diagnostics` extension in Windows Admin Center in the Azure portal enables you to perform on-demand log collection and share the logs with Microsoft.
592-
593-
Follow these steps to perform on-demand log collection via Windows Admin Center in the Azure portal:
594-
595-
1. Connect to Windows Admin Center in the Azure portal. For information, see [Manage Azure Stack HCI clusters using Windows Admin Center in Azure](/windows-server/manage/windows-admin-center/azure/manage-hci-clusters).
596-
1. In the left pane, under **Extensions**, select **Diagnostics**.
597-
1. On the **Diagnostics** page, under **Log activity** review log collection history or select a row to show the details about a specific log collection.
598-
1. Select **Send manually**. In the context pane on the right, enter the log start and end time and then select **Collect & upload logs**.
599-
600-
:::image type="content" source="./media/collect-logs/send-logs-manually.png" alt-text="Screenshot of the Diagnostics page showing the Send manually button for on-demand log collection." lightbox="./media/collect-logs/send-logs-manually.png" :::
601-
602618
## Next steps
603619

604620
- [Contact Microsoft Support](get-support.md)
224 KB
Loading
237 KB
Loading
259 KB
Loading
277 KB
Loading

0 commit comments

Comments
 (0)