HTTP monitors


Table of contents
  1. Name
  2. URL
  3. Interval
  4. HTTP request
    1. Request method
    2. Request headers
    3. Request body
  5. SSL
    1. Verify SSL certificate
  6. Performance monitoring
  7. Alerts

Let's go over configuration parameters for the HTTP monitors.


Name is the displayed name/title of the monitor. It is used both on the application and the status page. When multiple monitors are listed, they are sorted alphabetically by the name.


URL is the server URL that will be used for periodical checks by the monitor. It can use protocols HTTP or HTTPS.


Interval is the time gap between two consecutive checks for the monitor. It can be set between 30 seconds and 24 hours.

The minimum interval you can set depends on the plan you are on. For the plan Hobbyist it is 5 minutes, Basic and Pro it is 1 minute, and Business it is 30 seconds. Please see pricing for details.

HTTP request

Request method

Method is the HTTP request method that will be used with outgoing requests. The available options are DELETE, GET, HEAD, OPTIONS, PATCH, POST, PUT.

Request headers

Headers are the HTTP message headers used with outgoing requests. One of the most common use cases for headers is authentication. If your server authenticates by a particular header in the request (for example, authorization), you can utilize headers to authenticate.

Request body

Body is the HTTP message body that will be included in outgoing requests. You can use JSON or XML according to your server-side application's requirements.


Verify SSL certificate

With this option enabled, the monitor requires the response to have a valid SSL certificate. To check for invalid or expired SSL certificates, you can enable this option.

Performance monitoring

You can configure the monitor to be marked as Slow (and trigger an alert possibly) when its performance degrades. You can set a

  • time window,
  • slow response time limit,
  • slow response count.

For example:

"Mark this monitor as slow if there are 3 or more responses in the last 10 minutes with response time greater than 3 seconds."

If you are not sure about the average response time of your server, you can start with the default configuration and fine-tune it in time, according to reports.

If you want to learn more about performance monitoring or how it works in detail, you can read more about it here.

Performance monitoring feature is available for Pro and Business plans. See pricing.


In case of downtime or underperformance, WebGazer can alert the relevant person or team via various channels. For more, please see alerts documentation.