This article explains how to use the User Experience Monitoring drill-down page to analyze performance and user experience for remote and office users.
For more about reviewing analytics on the Experience Monitoring page, see Understanding the Experience Monitoring Drill-Down Pages.
When you click on a specific remote or office user in the Experience Monitoring page, a User Experience Monitoring drill-down page opens with data for that user. The page shows a set of widgets customized to help analyze application traffic for a user. The following sections describe the widgets shown on the page.
These are the widgets shown for drilling down and analyzing user experience monitoring data:
-
User summary - The widget at the top of the page shows basic information about the user such as the user name, the site the user connected from, the last PoP the user connected to, and the ISP. Additionally, the widget shows details about the user's device, including the last device the user connected from, the OS, the Cato Client version, and the internal and external IP addresses used in the connection.
-
Select Application - Shows the average experience scores and total data usage for the user's top used applications. Select an application to filter the page to show data specific to that application. By default, the page is filtered for the top application by usage.
-
Usage summary - The widget to the right of the Select Application widget shows usage and traffic information for the selected application
-
User Devices - Shows information for the devices the user connected from
-
User Application Experience Score - Shows the user's average experience score for the selected application (Good/ Fair/Poor), as well as a graph showing the application score over the configured time range compared with the overall score for all applications
The average experience score is based on these application performance metrics:
-
Time to First byte
-
TCP Connect
-
TLS Connect
-
HTTP Latency
-
HTTP/S error
Cato's AI-based algorithm creates unique thresholds for every app.
For more information about how Application Experience Score is calculated, see this article.
-
-
Connection Details - Shows data for the different logical nodes in the network path. For users, these are the nodes that are shown: Devices, Wi-Fi, LAN Gateway, Last Mile, and the selected application.
For more information about the experience monitoring scoring for each node, see Experience Monitoring Connection Details (EA-Socket and Last Mile Underlay).
The widget also provides expandable sections for each node to let you further drill down into detailed data to identify potential issues in each part of the network path. These are described in the following subsections.
The Device Hardware section shows the following data for the user devices:
-
Device Performance -
-
Avg. Experience - The average experience score for device performance based on the average device CPU usage (CPU Load) and memory usage (Memory Load) for the device over the configured time range. The score is calculated based on the least good result between the two metrics. For example, if the CPU Load is Good, but the Memory Load is Fair, the node score is Fair. These are the metrics for each score:
-
CPU Load
-
Good - CPU in use is less than 70%
-
Fair - CPU in use is between 70-90%
-
Poor - CPU in use is greater than 90%
-
-
Memory Load
-
Good - Memory used is below 60%
-
Fair - Memory used is between 60-80%
-
Poor - Memory used is greater than 80%
-
-
-
Avg. CPU Load - The average CPU usage for the user's device over the configured time range
-
Avg. Memory Load - The average memory usage for the user's device over the configured time range
-
-
Device Performance graphs - Graphs showing CPU and Memory load over time
The Wi-Fi section displays information about the Wi-Fi signal strength, including:
-
Wi-Fi Performance -
-
Avg. Experience - The average experience score for wi-fi performance based on the Signal Strength metric. This is how wi-fi experience is scored:
-
Good - signal strength -67 dBm or higher
-
Fair - signal strength between -67 dBm and -80 dBm
-
Poor - signal strength -80 dBm or lower
-
-
Avg. Signal Strength - The average wi-fi signal strength for the user over the configured time range
-
-
Wi-Fi Signal Strength - A graph showing signal strenth over time for each of the wi-fi networks used by the user
The LAN Gateway section shows information about the LAN gateway performance, including:
-
LAN Gateway Performance -
-
Avg. Experience - The average experience score for LAN gateway performance based on the average packet loss and distance over the configured time range. The score is calculated based on the least good result between the two metrics. For example, if LAN Gateway Distance is Good and LAN Gateway Packet Loss is Poor, the node score is Poor. These are the metrics for each score:
-
LAN Gateway Packet Loss
-
Good - less than 1% packet loss.
-
Fair - between 1-5% packet loss.
-
Poor - more than 5% packet loss.
-
-
LAN Gateway Distance
-
Good - below 10 ms.
-
Fair - between 10-50 ms.
-
Poor - exceeding 50 ms
-
-
-
Avg. Packet Loss - The average percentage of packets lost inside the LAN gateway over the configured time range
-
Avg. Distance - The average distance between the site and the Cato Cloud inside the tunnel over the configured time range
-
-
LAN Gateway Performance graphs - Graphs showing Packet Loss and Distance load over time
The Last Mile section shows the following data for the quality of connection for the encrypted tunnel connection to the PoP:
-
Last Mile Performance -
-
Avg. Experience - The average experience score for last mile performance.
The score for the Last Mile node is based on the following metrics for the Last Mile Overlay, as shown in the widgets:
-
Tunnel Upstream Packet Loss
-
Good - less than 1% packet loss.
-
Fair - between 1-5% packet loss.
-
Poor - more than 5% packet loss.
-
-
Tunnel Downstream Packet Loss
-
Good - less than 1% packet loss.
-
Fair - between 1-5% packet loss.
-
Poor - more than 5% packet loss.
-
-
Tunnel Distance
-
Good - below 20 ms.
-
Fair - between 20-100 ms.
-
Poor - exceeding 100 ms
-
The score displayed for the node is based on the best result between the two metrics. For example, if the Tunnel Packet Loss is Good, and Tunnel Distance is Poor, the node score is Good.
-
-
Avg. Packet Loss - Percentage of packets that were lost over the last mile inside the tunnel for upstream and downstream traffic, averaged over the configured time range
-
Avg. Distance - Distance between the site and the Cato Cloud inside the tunnel, averaged over the configured time range
-
-
Last Mile graphs - These graphs include metrics based on two different types of probes. These are the probe types and the widgets shown for each:
-
Underlay - Probes sent on the unecrypted out-of-tunnel last mile connection to measure the quality of the ISP connection to the PoP, independent of the encrypted overlay. This helps identify and diagnose out-of-tunnel issues that could impact last-mile performance for Socket sites.
Note: Underlay data is available only for Office Users connecting from a Socket site.
The probes are sent for each WAN interface in the Socket. The widgets show the interface name and the name of the connected PoP location, as well as the IP address of the connected service node in the PoP. If the PoP name is unavailable, only the service node IP address is shown.
Note: For data to be collected for the Underlay Probes feature, Socket v21.1.18975 or higher is required
Graph
Description
Packet Loss
Percentage of packets that were lost over the last mile outside the tunnel.
Distance
Distance between the site and the Cato Cloud outside the tunnel.
-
Overlay - These probes measure the quality of connection for the encrypted tunnel connection to the PoP.
Graph
Description
Packet Loss Upstream
Percentage of packets that were lost over the last mile inside the tunnel for upstream traffic.
Packet Loss Downstream
Percentage of packets that were lost over the last mile inside the tunnel for downstream traffic.
Discarded Packets Upstream
Percentage of packets that were received but not processed for upstream traffic.
Discarded Packets Downstream
Percentage of packets that were received but not processed for downstream traffic.
Distance
Distance between the site and the Cato Cloud inside the tunnel.
Tunnel Age
Total time that the current DTLS tunnel between the Socket and the PoP is connected.
Jitter Upstream
Difference in time delay in milliseconds (ms) between upstream data packets.
Jitter Downstream
Difference in time delay in milliseconds (ms) between downstream data packets.
Max Throughput Upstream
Maximum measured throughput inside the tunnel for upstream traffic
Max Throughput Downstream
Maximum measured throughput inside the tunnel for downstream traffic
Avg Throughput Upstream
Average upstream throughput inside the tunnel for each link (over the length of the bucket)
Avg Throughput Downstream
Average downstream throughput inside the tunnel for each link (over the length of the bucket)
-
The Application section shows the following metrics for application performance:
-
Avg. Experience -
The average experience score is based on these application performance metrics:
-
Time to First byte
-
TCP Connect
-
TLS Connect
-
HTTP Latency
-
HTTP/S error
Cato's AI-based algorithm creates unique thresholds for every app.
For more information about how Application Experience Score is calculated, see this article.
-
-
Application graphs - These metrics are described in the following table:
|
Graph |
Description |
|---|---|
|
Time to First Byte |
Duration of time between the HTTP request and the receipt of the first byte. |
|
TCP Connect |
Time taken to establish a TCP connection. |
|
TLS Connect |
Time taken to establish a TLS connection. |
|
HTTP/S Latency |
Duration of time between the request and the response. |
|
HTTP/S Error Rate |
Percentage of HTTP errors. |
|
Packet Loss |
Percentage of packets that were lost over the last mile inside the tunnel. |
|
Distance |
Distance between the site and the Cato Cloud inside the tunnel. |
0 comments
Article is closed for comments.