Say you've set a check frequency of 5 minutes for your web transaction monitors and the first poll takes place at 10.00 AM. The last poll time in the monitor summary page will be updated when the entire data collection for that poll is completed. This might have a delay of a couple of seconds.
The poll logic in Site24x7 is as follows:
1. Data collection in the primary location will take place as per the set check frequency.
2. We also perform a poll from the secondary locations (knows as the hourly poll), every half an hour. The hourly poll will be performed from a set of 8 secondary locations at a time. If you have configured 10 secondary locations, the first poll will happen from 8 secondary locations after which a poll from the other 2 locations will be initiated.
Let's say that your monitor was polled at 10.25 AM. The next poll is supposed to take place at 10.30 AM. But please note that 10.30 AM is also supposed to do an hourly poll (from secondary locations). Due to this, data collection might be delayed by a couple of minutes and hence there will be a slight variation in the last polled time in comparison to the actual set frequency.
Monitors associated with an On-Premise Poller will have data collected as per the scheduled check frequency without any delays. However, the data will be pushed to the web client with a slight delay. This is because, the Poller is scheduled to push the data to the web client at a specified time interval only. However, a downtime will be updated immediately.