Monitoring highly available websites / minimum polling frequency

Monitoring a website every 5 seconds is extremely aggressive. Especially for user experience monitoring. However if you need to monitor this application more frequently you can always create multiple application templates for this web server, each with a 1 minute polling interval. The more you create, the more frequently it will be polled.

Interesting idea - would creating 12 of the same template guarantee that we would poll in even 5 second increments? Does the number of components on each template have an affect on the frequency?

Just to give an idea of the amount of traffic I'm talking about - For a website that gets 1 million hits per hour, polling every 60 seconds means that 16,667 potential hits have already failed without us knowing. It's extremely important for us to know about a problem before the customer does.

Components within a given application template are polled serially, so you would need multiple application templates to ensure the job scheduler is spacing out the polling appropriately. There's no guarantee that each monitor will be polled in 5 second increments, but the more of them you have your odds improve.

Ahh.. I submitted a feature request to allow for lowering the polling frequency to 5 seconds. Unfortunately, we'll have to keep ipMonitor around in the meantime.