Skip to content

Commit 356c6f3

Browse files
committed
Updating based on feedback.
1 parent 0f9c3b4 commit 356c6f3

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/virtual-desktop/connection-latency.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure Virtual Desktop user connection quality - Azure
33
description: Connection quality for Azure Virtual Desktop users.
44
author: Heidilohr
55
ms.topic: conceptual
6-
ms.date: 09/21/2022
6+
ms.date: 09/26/2022
77
ms.author: helohr
88
manager: femila
99
---
@@ -45,9 +45,9 @@ To check and modify your diagnostics settings in the Azure portal:
4545

4646
7. Repeat this process for all other host pools you want to measure.
4747

48-
8. Make sure the network data is going to your selected destination by returning to the host pool's resource page, selecting **Logs**, then running one of the queries in [Sample queries for Azure Log Analytics](#sample-queries-for-azure-log-analytics). In order for your query to get results, your host pool must have active users who have been connecting to sessions. Keep in mind that it can take up to 15 minutes for network data to appear in the Azure portal.
48+
8. Make sure the network data is going to your selected destination by returning to the host pool's resource page, selecting **Logs**, then running one of the queries in [Sample queries for Azure Log Analytics](#sample-queries-for-azure-log-analytics:-network-data). In order for your query to get results, your host pool must have active users who have been connecting to sessions. Keep in mind that it can take up to 15 minutes for network data to appear in the Azure portal.
4949

50-
To check network data, return to the host pool's resource page, select **Logs**, then run one of the queries in [Sample queries for Azure Log Analytics](connection-latency.md#sample-queries-for-azure-log-analytics). In order for your query to get results, your host pool must have active users who've connected to sessions before. Keep in mind that it can take up to 15 minutes for network data to appear in the Azure portal.
50+
To check network data, return to the host pool's resource page, select **Logs**, then run one of the queries in [Sample queries for Azure Log Analytics](connection-latency.md#sample-queries-for-azure-log-analytics:-network-data). In order for your query to get results, your host pool must have active users who've connected to sessions before. Keep in mind that it can take up to 15 minutes for network data to appear in the Azure portal.
5151

5252
### Connection network data
5353

@@ -57,7 +57,7 @@ The network data you collect for your data tables includes the following informa
5757

5858
- The **estimated round trip time (milliseconds)** is the average estimated round trip time during each connection time interval. Round trip time is how long a network request takes to go from the end-user's device to the session host through the network, then return from the session host to the end-user device.
5959

60-
- The **Correlation ID** is the activity ID of a specific Azure Virtual Desktop connection that's assigned to every diagnostic within that connection.
60+
- The **Correlation ID** is the ActivityId of a specific Azure Virtual Desktop connection that's assigned to every diagnostic within that connection.
6161

6262
- The **time generated** is a timestamp in Coordinated Universal Time (UTC) time that marks when an event the data counter is tracking happened on the virtual machine (VM). All averages are measured by the time window that ends at the marked timestamp.
6363

@@ -101,7 +101,7 @@ The graphics data you collect for your data tables includes the following inform
101101

102102
- The **estimated round trip time (milliseconds)**, which is the average estimated round trip time during the second with the highest end-to-end delay in the time interval. Round trip time is how long a network request takes to go from the end-user's device to the session host through the network, then return from the session host to the end-user device.
103103

104-
- The **Correlation ID**, which is the activity ID of a specific Azure Virtual Desktop connection that's assigned to every diagnostic within that connection.
104+
- The **Correlation ID**, which is the ActivityId of a specific Azure Virtual Desktop connection that's assigned to every diagnostic within that connection.
105105

106106
- The **time generated**, which is a timestamp in UTC time that marks when an event the data counter is tracking happened on the virtual machine (VM). All averages are measured by the time window that ends that the marked timestamp.
107107

articles/virtual-desktop/troubleshoot-connection-quality.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Troubleshoot Azure Virtual Desktop connection quality
33
description: How to troubleshoot connection quality issues in Azure Virtual Desktop.
44
author: Heidilohr
55
ms.topic: troubleshooting
6-
ms.date: 09/21/2022
6+
ms.date: 09/26/2022
77
ms.author: helohr
88
manager: femila
99
---

0 commit comments

Comments
 (0)