Gazer has these configuration parameters:
Let's go and see what each of these are and how they work.
Name is the displayed name/title of the gazer. It is used both on the application and the status page. When multiple gazers are listed, they are sorted alphabetically by the name.
URL is the server URL that will be used for periodical checks by the gazer. It can use protocols HTTP or HTTPS.
Interval is the time gap between two consecutive checks for the gazer. You can set it between 1 minute and 24 hours.
Method is the HTTP request method that will be used with outgoing requests. The available options are DELETE, GET, HEAD, OPTIONS, PATCH, POST, PUT.
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.
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.
Performance monitoring options
You can configure the gazer to be marked as Underperforming (and trigger an alert possibly). You can set a
- time window,
- slow response time limit,
- slow response count.
"Mark this gazer as underperforming 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.
In case of downtime or underperformance, WebGazer can alert the relevant person or team via various channels. For more, please see alerts documentation.