HTTP Monitoring Sensor
It supports GET and POST requests, SSL certificate validation, cookies, a custom user agent, timeouts, wanted and unwanted string matches with regular expression support, and all HTTP response codes, allowing all aspects of your web server to be monitored for both performance and availability.
The URL to be monitored. Use the complete url, including http:// or https:// for a secure connection.
A username & password can be supplied for use with HTTP Basic Authentication - it should be specified as part of the URL: http://username:firstname.lastname@example.org/
By including expected text, for the test to pass the supplied text must be found somewhere in the body of the HTTP response. Prefix this with regex: to do a perl-compatible regular expression match.
Text that, if found in the HTTP response body, will cause the test to fail. Prefix this with regex: to do a perl-compatible regular expression match.
Number of seconds before the request times out, and the test fails. Default is 30 seconds.
HTTP POST Data
If specified, an HTTP POST request will be made, using the contents as the POST submission. For example, in HTTP URL encoded format:
Expected HTTP Response
This will normally be 200 OK, however you can also monitor correct functioning of other HTTP responses such as 403 Forbidden, 302 Found.
Verify SSL Certificate
Enable this option to verify that the web servers' SSL certificate is valid and issued by a recognized certificate authority.
Minimum SSL certificate validity
This parameter allows you to trigger an alert when your SSL Certificate(s) are due to expire within the specified period of time. e.g. a value of "30" will result in alerts once your certificate(s) are due to expire within 30 days.
Cookies to send
Sends the contents of this parameter as an HTTP Cookie. Use the standard HTTP cookie format:
Identifies the HTTP client as the supplied user agent. By default a blank agent string is sent.
Match content in headers
If yes, Expected text & Unwanted text will match content present in the HTTP response headers as well as the response body
Custom Request Headers
You can override HTTP request headers, or supply custom ones. e.g.:
You might use this method to monitoring a web server which sits behind a Content Distribution Network (CDN). You could address the web server by it's IP address (thus avoid connecting to the CDN endpoint), and supply the relevant Host: header to request the resource being monitored.
Learn more about monitoring web servers behind a load balancer.