HTTP monitors will send a request (GET, POST, DELETE or PUT) on port 80 or 443 (depending on whether you use an HTTP or HTTPS URL) and expects a web server to respond. It replicates a user browsing to the URL so measures full page load time. It can include custom headers and HTTP basic auth, as well as a body of content to send (more on these options later). This guide will walk you through creating an HTTP monitor
Adding an HTTP Monitor
- Navigate to the Monitoring subsection of the portal
- Click on the "Create Monitor" button
- Below is the "Create Monitor" page in its entirety
Name: This is the vanity name for the monitor you will see in your Monitoring overview page. Set this to whatever you like and it doesn't necessarily need to be relevant to the monitored site, though that's recommended.
Protocol: HTTP or TCP. Since we're creating an HTTP monitor, use HTTP.
URL: This is the URL or IP that will be monitored. You can also choose between HTTP and HTTPS here with the dropdown.
Method: HTTP method that the monitor will use. Choose between GET and POST requests.
IP version: Will chose if the monitor will try to resolve the URL using IPv4 or IPv6.
Locations: Decide the locations you wish to have the URL/IP monitored from. Each location chosen will send its own request to your chosen URL/IP and will have its own monitoring data available. You can find a full list of locations here.
Frequency: This option is currently not selectable. In the future, this option will determine how often the monitor will send out requests. The default and only option is 5 minutes.
Timeout: How long the monitor will attempt to make a connection with the monitored URL/IP. If the timeout is reached, the site is considered down for the location that reached the timeout. There's a hard cap of 20 seconds for timeouts, the default timeout is 10 seconds.
Strict SSL Validation: If the connection is not secure, the resource is treated as down.
Authentication: Monitors can optionally make use of Basic or Digest authentication and you can upload public and private certificates here.
Headers: Custom headers to be sent when the monitor makes the HTTP/S request.
Request body content: Data to be sent when the monitor makes the HTTP/S request.
Now that you understand each option you can go ahead and create your monitor.
Viewing Monitor Results
Here you can see connection data for your monitor including response times, and a breakdown of what constitutes that response time. If you want more information about Monitoring metrics on this page, you can refer to our article.
Your monitor has now been created and the chosen URL/IP is being monitored. We will create one alert for you by default, but feel free to add more alerts if you have specific monitoring requirements. You can add alerts from the alerting tab (be sure to read our Alerting Best Practices):
If you have other questions related to monitoring, feel free to contact our 24x7 support through live chat and firstname.lastname@example.org.