cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1208
Views
0
Helpful
2
Replies

High cacheTotalRespTimeNow value but no indication of problem

ondjultomte
Level 1
Level 1

Hi!

 

We are SNMP monitoring cacheTotalRespTimeNow and from time to time this value peaks extremely high, but no users has complain

 

 

We have added the accesslogs

Date: %L Dst-IP: %k UsrAgnt: %u ADGroup: %g AuthMethod: %m TransID: %I PrfPara: %:<a %:<b %:<d %:<h %:<r %:<s %:>1 %:>a %:>b %:>c %:>d %:>h %:>r %:>s %:1< %:1> %:b< %:b> %:h< %:h> %:m< %:m> %:w< %:w> %x 

 

but cant find any deviation there.

 

What could cause these high values ? The general load on the WSA low.

 

Proxy Traffic Characteristics
Transactions per Second
Average in last minute: 4
Maximum in last hour: 30
Average in last hour: 5
Maximum since proxy restart: 163
Average since proxy restart: 4
Bandwidth
Average in last minute: 1.7Mbps
Maximum in last hour: 647.9Mbps
Average in last hour: 3.4Mbps
Maximum since proxy restart: 3.4Gbps
Average since proxy restart: 2.4Mbps
Response Time (ms)
Average in last minute: 1,050
Maximum in last hour: 300.0k
Average in last hour: 6,412
Maximum since proxy restart: 242.6M
Average since proxy restart: 311
Cache Hit Rate
Average in last minute: 0
Maximum in last hour: 1
Average in last hour: 0
Maximum since proxy restart: 54
Average since proxy restart: 0
Connections
Current idle client connections: 120
Current idle server connections: 41
Current total client connections: 433
Current total server connections: 344

 image.png

2 Replies 2

Handy Putra
Cisco Employee
Cisco Employee

Hi,

 

Response time from the graph suggested that there are traffic on that specific time that taking longer time to be processed, this could be due to a big total bytes on that particular requests.

You can check the past accesslogs from the WSA and try to find those high elapse time for that specific time.

 

You can perform a filter from the 'grep' command from CLI for that specific time (since you have added %L in the accesslogs to show the human readable time) to find out what requests that are high in response(elapse) time.

 

If you need further assistance on this, recommend to open TAC case for the engineer to assist you further.

 

Regards

Handy Putra

1531102150.668 240068 10..xx.xx.xx TCP_MISS/200 950 TCP_CONNECT 216.58.209.138:443 - DIRECT/safebrowsing.googleapis.com - PASSTHRU_CUSTOMCAT_7-NoAuthPolicy-NoAuthId-NONE-NONE-NONE-DefaultGroup <C_NoAu,1.5,-,"-",-,-,-,-,"-",-,-,-,"-",-,-,"-","-",-,-,IW_srch,-,"-","-","Unknown","Unknown","-","-",0.03,0,-,"-","-",-,"-",-,-,"-","-",-,-,"-"> - Date: "09/Jul/2018:04:09:10 +0200" Dst-IP: 216.58.209.138 UsrAgnt: - ADGroup: - AuthMethod: NONE TransID: 147715995 PrfPara: 0 0 0 0 0 0 0 0 240052 0 0 0 0 0 0 0 0 240052 3 0 0 0 0 0 3

 

 

*240052ms - %:>b - Server respones time - Wait-time for complete response body after header received.

 

*240052ms - %:b> - Wait-time for complete body written to client.

 

that is odd , really slow transfer from googles api