Can I monitor web servers behind a load balancer?
If you have multiple HTTP servers sitting behind a load balancer, you can still monitor them individually if they are reachable via a public IP address - even if they host multiple domains.
To achieve this, your monitoring configuration needs to make an HTTP request directly to the web servers' IP address instead of the load balancers' IP address.
Because many web servers inspect the Host: request header (for name based virtual-hosting), you will most likely want to override this request header so it contains your domain name rather than the IP address of the server.
You can achieve this configuration with the Wormly HTTP monitoring sensor. Simply put your web servers' public IP address in the URL field, e.g:
And specify your Host: header in the Custom Request Headers field, e.g:
By overriding the Host: header, the web server will treat the above request in the same way as if the client had requested the URL http://www.example.com/my_app directly.
Not what you were looking for? Try a search:
Also in this topic:
- Can I monitor the entire page, including images, CSS, Flash, etc?
- Can I perform an HTTP POST and monitor the results?
- Can I monitor a multiple page transaction (e.g. login)?
- Can I specify an username and password for a web page (HTTP Auth)?
- Can I verify that a specific phrase or text appears on my website?
- Unknown SSL protocol error in connection to [example.com]
- Can I monitor SSL certificate expiration?
- What does "Operation timed out after x with y bytes received" mean?
- What does "couldn't connect to host" mean?
- What does "name lookup timed out" mean?
- What does "empty reply from server" mean?