Application HTTP Latency Anomaly for SDP users

This playbook describes the steps to investigate and resolve HTTP latency issues affecting remote users connecting with the Client (SDP users).

Overview

HTTP latency can be caused by a variety of factors, including network conditions, endpoint performance, and application responsiveness. This playbook helps identify the root cause and determine the appropriate mitigation.

Verify HTTP Latency

The following methods can be used by a Cato Management Application administrator to verify that an HTTP Latency Anomaly occurred for remote users.

Using the Story Drill-Down

1. From the navigation menu, click Home > Stories Workbench.
2. In the filter bar, add a filter set to Producer Name in Experience Anomaly.
3. Add the filter Indication in Application HTTP Latency Anomaly for SDP users.

1. Verify that a story was generated. 
   
2. Click in the row of the story to open the drill-down page to review the incident details, including the timeline and affected users. 
   
3. Review the incident timeline and the number of affected users to determine when the incident started and whether it is isolated or widespread.

Filter for Related Events

In the Home > Events page, apply the following filters:

• Sub-Type is Anomaly
• Event Message Contains HTTP Latency 
   

Troubleshooting Steps

Review Application Performance

1. Open the Home > Experience Monitoring page.
2. Filter the data for the affected users and applications.
3. Review the application performance metrics and determine whether increased HTTP latency correlates with the incident timeline.

Review Related Network Metrics

In the Experience Monitoring page, review the user metrics for any degradation during the incident timeframe, such as:

• High CPU or memory utilization
• Poor Wi-Fi signal quality (if applicable)
• Increased packet loss or latency towards the host gateway
• Increased packet loss or latency towards the Cato PoP

Review the Connection Details widget and examine the traceroute results for packet loss, increased latency, and other network abnormalities during the incident.

Note: Traceroute metrics are available only when using Windows client 6.10 or Mac client v5.14 or later.

Review Endpoint Performance

If no issues are identified in the previous steps, proceed to Cato SDP Client Performance Troubleshooting and investigate potential endpoint-related causes.

Raising Cases to Cato Support

If following this playbook has not resolved an issue, submit a Support ticket. To get the most helpful response to a request, an admin should provide the results of the troubleshooting steps taken.