Skip to content

Commit ca9a808

Browse files
Update diagnostics-log-analytics.md
Minor edits
1 parent ecb5f59 commit ca9a808

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-desktop/diagnostics-log-analytics.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ To set up Log Analytics for a new object:
8888
For example, when you're enabling diagnostics for an app group, you'll see options to configure checkpoints, errors, and management. For workspaces, these categories configure a feed to track when users subscribe to the list of apps. To learn more about diagnostic settings see [Create diagnostic setting to collect resource logs and metrics in Azure](../azure-monitor/platform/diagnostic-settings.md).
8989

9090
>[!IMPORTANT]
91-
>Remember to enable diagnostics for each ARM object that you want to monitor. Data will be available for activities after diagnostics has been enabled. It might take a few hours after first set-up.
91+
>Remember to enable diagnostics for each Azure Resource Manager object that you want to monitor. Data will be available for activities after diagnostics has been enabled. It might take a few hours after first set-up.
9292
9393
5. Enter a name for your settings configuration, then select **Send to Log Analytics**. The name you use shouldn't have spaces and should conform to [Azure naming conventions](../azure-resource-manager/management/resource-name-rules.md). As part of the logs, you can select all the options that you want added to your Log Analytics, such as Checkpoint, Error, Management, and so on.
9494

@@ -141,7 +141,7 @@ Log Analytics only reports in these intermediate states for connection activitie
141141

142142
The following example queries show how the diagnostics feature generates a report for the most frequent activities in your system.
143143

144-
To get list of connections made by your users, run this cmdlet:
144+
To get a list of connections made by your users, run this cmdlet:
145145

146146
```powershell
147147
WVDConnections

0 commit comments

Comments
 (0)