@@ -38,6 +38,10 @@ The current list of supported commands are
38
38
Command Name: ` mde-agent-information ` \
39
39
Arguments: None
40
40
41
+ - Collect MDE diagnostic support logs\
42
+ Command Name: ` mde-support-diagnostics ` \
43
+ Arguments: None
44
+
41
45
- Collect Dell Hardware Rollup Status\
42
46
Command Name: ` hardware-rollup-status ` \
43
47
Arguments: None
@@ -76,6 +80,16 @@ az networkcloud baremetalmachine run-data-extract --name "bareMetalMachineName"
76
80
--limit-time-seconds 600
77
81
```
78
82
83
+ This example executes the ` mde-support-diagnostics ` command without arguments.
84
+
85
+ ``` azurecli
86
+ az networkcloud baremetalmachine run-data-extract --name "bareMetalMachineName" \
87
+ --resource-group "resourceGroupName" \
88
+ --subscription "subscription" \
89
+ --commands '[{"command":"mde-support-diagnostics"}]' \
90
+ --limit-time-seconds 600
91
+ ```
92
+
79
93
This example executes the ` hardware-rollup-status ` command without arguments.
80
94
81
95
``` azurecli
@@ -135,6 +149,47 @@ Script execution result can be found in storage account:
135
149
https://cmzhnh6bdsfsdwpbst.blob.core.windows.net/bmm-run-command-output/f5962f18-2228-450b-8cf7-cb8344fdss63b0-action-bmmdataextcmd.tar.gz?se=2023-07-26T19%3A07%3A22Z&sig=X9K3VoNWRFP78OKqFjvYoxubp65BbNTq%2BGnlHclI9Og%3D&sp=r&spr=https&sr=b&st=2023-07-26T15%3A07%3A22Z&sv=2019-12-12
136
150
```
137
151
152
+ Data collected from the ` mde-support-diagnostics ` command uses the MDE Client Analyzer tool to bundle information from ` mdatp ` commands and relevant log files. The storage account ` tgz ` file will contain a ` zip ` file named ` mde-support-diagnostics-<hostname>.zip ` . The ` zip ` should be sent along with any support requests to ensure the supporting teams can use the logs for troubleshooting and root cause analysis, if needed.
153
+
154
+ ``` azurecli
155
+ ====Action Command Output====
156
+ Executing mde-support-diagnostics command
157
+ [2024-01-23 16:07:37.588][INFO] XMDEClientAnalyzer Version: 1.3.2
158
+ [2024-01-23 16:07:38.367][INFO] Top Command output: [/tmp/top_output_2024_01_23_16_07_37mel0nue0.txt]
159
+ [2024-01-23 16:07:38.367][INFO] Top Command Summary: [/tmp/top_summary_2024_01_23_16_07_370zh7dkqn.txt]
160
+ [2024-01-23 16:07:38.367][INFO] Top Command Outliers: [/tmp/top_outlier_2024_01_23_16_07_37aypcfidh.txt]
161
+ [2024-01-23 16:07:38.368][INFO] [MDE Diagnostic]
162
+ [2024-01-23 16:07:38.368][INFO] Collecting MDE Diagnostic
163
+ [2024-01-23 16:07:38.613][WARNING] mde is not running
164
+ [2024-01-23 16:07:41.343][INFO] [SLEEP] [3sec] waiting for agent to create diagnostic package
165
+ [2024-01-23 16:07:44.347][INFO] diagnostic package path: /var/opt/microsoft/mdatp/wdavdiag/5b1edef9-3b2a-45c1-a45d-9e7e4b6b869e.zip
166
+ [2024-01-23 16:07:44.347][INFO] Successfully created MDE diagnostic zip
167
+ [2024-01-23 16:07:44.348][INFO] Adding mde_diagnostic.zip to report directory
168
+ [2024-01-23 16:07:44.348][INFO] Collecting MDE Health
169
+ [...snip...]
170
+ ================================
171
+ Script execution result can be found in storage account:
172
+ https://cmmj627vvrzkst.blob.core.windows.net/bmm-run-command-output/7c5557b9-b6b6-a4a4-97ea-752c38918ded-action-bmmdataextcmd.tar.gz?se=2024-01-23T20%3A11%3A32Z&sig=9h20XlZO87J7fCr0S1234xcyu%2Fl%2BVuaDh1BE0J6Yfl8%3D&sp=r&spr=https&sr=b&st=2024-01-23T16%3A11%3A32Z&sv=2019-12-12
173
+ ```
174
+
175
+ After downloading the execution result file, the support files can be unzipped for analysis.
176
+
177
+ ``` azurecli
178
+ Archive: mde-support-diagnostics-rack1compute02.zip
179
+ inflating: mde_diagnostic.zip
180
+ inflating: process_information.txt
181
+ inflating: auditd_info.txt
182
+ inflating: auditd_log_analysis.txt
183
+ inflating: auditd_logs.zip
184
+ inflating: ebpf_kernel_config.txt
185
+ inflating: ebpf_enabled_func.txt
186
+ inflating: ebpf_syscalls.zip
187
+ inflating: ebpf_raw_syscalls.zip
188
+ inflating: messagess.zip
189
+ inflating: conflicting_processes_information.txt
190
+ [...snip...]
191
+ ```
192
+
138
193
Data is collected with the ` hardware-rollup-status ` command and formatted as JSON to ` /hostfs/tmp/runcommand/rollupStatus.json ` . The JSON file is found
139
194
in the data extract zip file located in the storage account.
140
195
0 commit comments