Note
Note: Please contact feature-releases@catonetworks.com for more information about enabling and using this feature.
Physical and virtual App Connectors connect your private applications to the Cato Cloud. Use the Network Analytics page to monitor App Connector availability, throughput, transport quality, and hardware load. This page helps you determine whether the connector is connected, carrying traffic, experiencing packet loss or discards, or under CPU pressure during the selected time range.
Use the Site & Tunnels tab to monitor traffic behavior and the Hardware tab to monitor CPU utilization over time.
This section explains how to use the Sites & Tunnels tab to review connector availability, traffic levels, and transport quality for the selected time range.
-
Connector Status: Shows whether the connector is currently connected and available to carry traffic
-
Troubleshooting example: If users report that apps are unreachable, first check whether the connector has connectivity
-
-
Avg Throughput: Shows the average upstream and downstream traffic, which helps you verify that the connector handled traffic and understand the overall traffic pattern.
-
Troubleshooting example: If users reported activity, but the throughput is unexpectedly low, traffic might not have used this connector at that time
-
-
Avg. Packet Loss: Shows the average upstream and downstream packet loss, which helps you identify transport quality issues that can affect application performance and session stability
-
Troubleshooting example: If users report slow performance or unstable sessions, check whether packet loss is elevated during the relevant time range
-
-
Avg. Discards: Shows the average upstream and downstream discarded traffic, which helps you identify whether traffic was dropped instead of forwarded successfully
-
Troubleshooting example: If application sessions fail or degrade during busy periods, review discards together with throughput to see whether traffic quality was impacted
-
Use this procedure to review the App Connector CPU utilization and determine whether physical or virtual hardware resources were under pressure during the selected time range.
-
Avg. CPU: Shows the average CPU utilization for the connector, which helps you determine whether the connector was under sustained hardware load
-
Troubleshooting example: If throughput increases at the same time that CPU remains elevated, the connector might be approaching capacity limits
-
-
CPU Load: Shows CPU utilization over time for each core, which helps you see whether CPU activity was steady, briefly elevated, or sustained
-
Troubleshooting example: If users reported intermittent slowness, review the graph for sustained periods of higher CPU utilization during the relevant time window
-
0 comments
Article is closed for comments.