Note: You can use HTTP monitoring in conjunction with scripts to monitor other services like database servers.
- Go to Manage Jobs:
- Click on the add button in the HTTP card:
- Enter the link to the website you want to monitor.
Domain names will be resolved during the setup and a separate monitoring job for every DNS entry (A and AAAA) will be created. If, for instance, your domain points to an IPv4 address as well as an IPv6 address 2 jobs will be created, one for each protocol.
IDNs (Internationalized Domain Names) are supported and automatically translated to Punycode. The (encoded) domain name will be used for lookups and as the HTTP host header. The domain name can be replaced by an IP address which will then be used as the HTTP host header:
The scheme can be either HTTP or HTTPS. Port numbers are supported. To monitor a service on port 400 using TLS connections you would write:
You can skip the automatic name resolution and set the request properties directly using the advanced setup form.
- Optionally you can add a short description helping to identify this monitoring job.
- Adjust the check interval. In the example your website will be checked every 19 minutes.
- Notifications will be sent as soon as the alert threshold is reached. This threshold is related to the last 10 checks. If you want to receive notifications if 2 or more of the last 10 checks have failed you have to set this value to 20%:
- Adjust the timeout of the HTTP requests. A check fails if the HTTP response is not received within the selected timeout.
- Choose the HTTP response code of a correct server response. Alarm is triggered if the response code differs from this reference value.
- You are done. Click on 'Create' to start the monitoring.