Interval and Timeout set to two seconds on HTTP/HTTPS health monitor

When you increase the frequency of a monitor you're adding more load to the end point servers. So in your scenario you are creating more 'hits' to the web servers from the F5.

Here are a few things to keep in mind:

1. Your monitor is checking the root index of your web site. Try deploying a basic status page that only your F5 can connect to or knows about. You can then filter your logs on the web server to ignore that status check.

    

2. How many pool members do you have? Increasing the monitor to 2 second intervals seems extreme. Does your testing reflect actual use cases? What error are you trying to avoid for the end user?

    

3. Have you considered adding more web servers to the pool? This would diminish the percentage of your user base impacted by a failed web server.

    

Hope that helps!