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
This article describes how to collect diagnostic logs using the Azure portal 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 via the Azure portal and send them to Microsoft to help identify and fix any issues with your Azure Stack HCI solution.
17
17
18
-
For information on on-demand log collection, its benefits and prerequisites, see []to collect diagnostic logs via PowerShell, see [Collect diagnostic logs for Azure Stack HCI](./collect-logs.md).
18
+
To learn about how to collect logs via PowerShell, see [Collect diagnostic logs for Azure Stack HCI](./collect-logs.md).
19
19
20
20
## On-demand log collection
21
21
22
-
On-demand log collection involves manually collecting and sending diagnostic logs to Microsoft. You can perform on-demand log collection using any of the following methods:
22
+
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/).
23
23
24
-
- (Recommended) Azure portal. When you collect logs and send them to Microsoft using the Azure portal, you collect logs at the cluster level. This send the default logs.
25
-
- PowerShell. But if you need like specific parameters around, OK like you need to share them, you need to either like save them to an SMB share or you need to just send the supplementary logs or you only wanna send specific rules, then you still need to use PowerShell. If you want to Use the `Send-DiagnosticData` cmdlet from any node within the Azure Stack HCI cluster to collect logs and send them to Microsoft. 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/).
24
+
You can perform on-demand log collection using any of the following methods:
25
+
26
+
- (Recommended) Azure portal. When you collect logs and send them to Microsoft using the Azure portal, you collect logs at the cluster level.
27
+
28
+
- PowerShell. But if you need like specific parameters around, OK like you need to share them, you need to either like save them to an SMB share or you need to just send the supplementary logs or you only wanna send specific rules, then you still need to use PowerShell. If you want to Use the `Send-DiagnosticData` cmdlet from any node within the Azure Stack HCI cluster to collect logs and send them to Microsoft. When you run this cmdlet, the logs are temporarily copied locally. This copy is parsed, sent to Microsoft, and then deleted from your system.
26
29
27
30
### When to use on-demand log collection
28
31
@@ -43,7 +46,7 @@ Before you collect on-demand logs via the Azure portal, you must complete the fo
43
46
- You must have access to an Azure Stack HCI cluster.
44
47
- You must have access to Azure.
45
48
- 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).
46
-
-Review the terms and conditions for log collection.
49
+
-You must review the terms and conditions for log collection.
47
50
48
51
## Collect logs via the Azure portal
49
52
@@ -52,25 +55,10 @@ Follow these steps to collect diagnostic logs for you Azure Stack HCI cluster vi
52
55
1. the Azure portal, go to the Azure Stack HCI cluster resource.
53
56
1. In the left pane, under **Settings**, select **HCI diagnostics and Support**.
54
57
1. On the **Troubleshoot issues and get support** pane, under the **Send Diagnostics Logs** tile, select **Go to diagnostics**.
55
-
1.The**Diagnostics** tab displays the log activity, the timestamp of collected logs and their statuses. To collect logs now, select **Send logs**.
56
-
1. On the **Send logs** pane on the right, select the *Log start time** and **Log end tme** by selecting a date and time from the.
58
+
1.Review the**Diagnostics** tab displays the log activity, the timestamp of collected logs and their statuses. To collect logs now, select **Send logs**.
59
+
1. On the **Send logs** pane on the right, select the **Log start time** and **Log end tisme**.
57
60
1. Select the **Collect and upload logs** button. By selecting this, you agree to the terms and conditions of collection logs.
58
61
59
-
Run the `Send-DiagnosticData` cmdlet from any node on your Azure Stack HCI cluster to perform on-demand log collection.
60
-
61
-
Here are some important points to consider:
62
-
63
-
- The completion time of the `Send-DiagnosticData` cmdlet varies depending on factors, such as the roles for which logs are being collected, time duration specified, and the number of nodes in your Azure Stack HCI environment.
64
-
- If you don't specify any parameters, the `Send-DiagnosticData` cmdlet collects data from all nodes for the previous one-hour duration.
For reference information on `Send-DiagnosticData`, see the [`Send-DiagnosticData` command reference](#send-diagnosticdata-command-reference) section later in this article.
73
-
74
62
## Perform on-demand log collection via Windows Admin Center in the Azure portal
75
63
76
64
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.
0 commit comments