Reported errors vs total time

Document ID : KB000097129
Last Modified Date : 22/05/2018
Show Technical Document Details
Question:
We have noticed that errors are reported for our Monitor which also affects the availability % but that total time is reported in the error log is less than the configured threshold for this monitor.
 
Answer:
The errors started on March 1st at 13:06 and ended on March 2nd at 12:03 PM and was seen from many different monitoring stations.

https://docops.ca.com/ca-asm/search?q=9228&max=10&key=cacm82
  9228
  Curl Operation timeout.

The specified time-out period was reached according to the conditions. You currently have the Montior timeout set to 10 seconds.

The errors started on March 1st at 13:06 and ended on March 2nd at 12:03 PM and was seen from many different monitoring stations. 

https://docops.ca.com/ca-asm/search?q=9228&max=10&key=cacm82 
9228 <https://docops.ca.com/ca-asm/error-messages/9228

This was caused by a curl operation timeout. The specified time-out period was reached according to the conditions. <https://docops.ca.com/ca-asm/error-messages/9228

The Monitor timeout is set to 10 seconds. 

So what these errors mean is that the checks ran from the monitoring stations and attempted to go to the site https://mysite.com/. It tried for 10 seconds but could not connect to the site which is indicated by the "0 bytes received" in the error message. 

This could mean a few things: 
1. The site was down 
2. The site was up but experiencing network issues or load issues. 
3. Some central hop that all the monitoring stations will go through to get to the site was down or experiencing network issues. 
4. The site may have been down for some maintenance. 

Given that most at one point and at a later point all the monitoring stations exhibited this behavior, most likely the site was experiencing some network issues. Given that the time range that this happened was not on a weekend, most likely it was not down for maintenance and probably had a network issue.