User and devices in Monitor Cloud PCs

The User and devices page provides detailed connection, health, and performance data for Cloud PCs. Use this page to compare devices, investigate connection problems, and identify resource constraints that might affect the user experience. The data retention for this page is 28 days.

Understand the charts

Connection data

Connection duration

Chart Description
Connection history Shows the total Cloud PC connection duration, in hours, over time.
Total hours per device Shows the total connection duration, in hours, for each Cloud PC during the selected time range.
Average connection duration (hours) Shows the average connection duration over time.
Average connection duration (hours) per device Shows the average connection duration for each Cloud PC during the selected time range.

How to use these charts:

  • Use the total duration chart to understand overall usage.

  • Use the average duration chart to understand the typical length of an individual connection.

A device can have a high total duration chart because it has many connections, long connections, or both.

Connection errors

Chart Description
Connection error count Shows the number of Cloud PC connection errors over time, grouped by error type.
Percentage of errors by error type Shows the percentage distribution of Cloud PC connection errors by error type during the selected time range.

How to use these charts:

  • Use the error count chart to determine when errors occurred and whether their frequency is changing.

  • Use the percentage chart to identify which error types account for the largest share of recorded errors.

A large percentage doesn't always represent a large number of errors. Review the percentage chart together with the error count chart.

Remote sign-in time

Chart Description
Average remote sign-in time (seconds) Shows the average remote sign-in time, in seconds, over time.
Average remote sign-in time per device (seconds) Shows the average remote sign-in time, in seconds, for each Cloud PC during the selected time range.

How to use these metrics:

  • Use the average remote sign-in time trend chart to identify when sign-in performance changed.

  • Use the average remote sign-in time per-device chart to identify Cloud PCs with comparatively slower sign-ins.

Lower values generally indicate a faster connection experience.

Round trip time

Chart Description
Round trip time history Shows the P50 network round trip time, in milliseconds, for Cloud PC connections over time.
P50 round trip time per device (milliseconds) Shows the P50 network round trip time, in milliseconds, for each Cloud PC during the selected time range.

P50 is the middle observed value, half of the measured round trips were faster and half were slower. Compared with an average, the median is less affected by a small number of unusually high values. Lower round trip times generally indicate a more responsive network connection. Higher values indicate increased latency but don't independently identify its cause.

Cloud PC health

Chart Description
Cloud PC health trends Shows the percentage of selected Cloud PCs that are in a healthy state over time.

How to use this metric:

  • Identify changes in overall device health.

  • Determine whether connection or performance changes coincide with a decrease in healthy devices.

  • Narrow the selected population to investigate affected Cloud PCs.

Investigate a user or device issue

  1. Select the relevant user (by UPN or username), Cloud PC (by device name or device ID), and time range.

  2. Review connection history to confirm when and how long the Cloud PC was used.

  3. Check connection errors and identify the most common error types.

  4. Review remote sign-in time and round trip time for connection delays.

  5. Check Cloud PC health for changes during the same period.

  6. Compare the affected device with other Cloud PCs to determine whether the pattern is isolated or widespread.

Note

These charts show patterns and correlations. A high or low value doesn't independently establish the root cause of a connection or performance issue.

Next steps