A gazer is what checks your website periodically. It triggers a request to the website or service you want to monitor. Gazers can monitor different services.
In addition to these, WebGazer also checks SSL certificates of your gazers without any configuration.
💡 Learn more on Setting up a gazer.
The response is evaluated according to the status code. The status codes below 400 are considered as OK. All other status codes trigger an incident. The reason for the incident is also generated according to the status code of the response.
In case of an incident, WebGazer performs three more checks. If all of the checks result in the same response, an incident is registered. An alert is sent to you on the preferred channel.
WebGazer uses 10 seconds as the timeout limit. Page load time is an important determinant in user engagement. According to the surveys by Akamai and Gomez.com, 40% of visitors abandon your website if it takes more than 3 seconds to load. This is why a short timeout limit is set. An incident is registered if a request fails to get a response in this time frame.
Incident verification applies to timeout cases as well. If a total of 4 consecutive timeouts take place, an incident is registered. Since the website speed is important for user experience, we do not plan to increase the timeout limit for the time being. 🙌
In case of an incident, WebGazer sends a notification to your preferred channel. You can set an instant alert (or delayed) for a gazer under the Alerts section.
💡 Learn more on Alerts.