1. Support
  2. Knowledge base
  3. HTTP and HTTPS
  4. HTTP monitor overview

HTTP monitor overview

We’re changing our user interface. Some info may not yet be up to date. Please check From classic to new UI.

An HTTP monitor checks for your web pages' availability from the designated checkpoints located around the world. At the monitor’s most basic, the monitor checks for an error-free response from the web server. Beyond checking for basic website monitoring availability (or uptime monitoring), you can also monitor and trigger alerts for your page load times, minimum page size, content, and status codes. An HTTP monitor is a “basic” check. Learn the difference between basic checks and real browser checks.

Note: Need help creating an HTTP monitor? Jump over to the Academy for a quick how-to.

Error conditions

You have several conditions you can check and trigger alerts for on your web page. From the Error conditions tab, you can set the page’s load time expectations, expected minimum page size, and set up content matching.

Page load times

Slow pages increase bounce rates. You can set up to two different maximum load times and trigger alerts when the page takes longer to load. The default setting is 2.5 and 5 seconds, but you should configure your pages to keep the load times under 2 seconds. Please note that an HTTP monitor only downloads the HTML content of a page. If you want to monitor all elements of a page (including stylesheets, scripts and images) we recommend using a Real Browser Check or Full Page Check. Learn more about setting load time limits and alerting based on load time.

Minimum page size

Your page may load quickly. However, if the full page doesn’t load, what is the point of having a fast page? By setting a minimum page size (in bytes), you will know if part of your page fails to load.

Page content match

If you have a crucial element on the page, you can include a particular word or phrase in the content match field. If the monitor doesn’t find it in the returned page, you can trigger an alert.

Note: You can also check to make sure a word is NOT on the page by prefixing it with an exclamation mark. For example, if you wanted to make sure the word “error” doesn’t appear on the page, type “!error” in the content field.

HTTP Status code

Sometimes you expect an error code or another code other than a success. For example, if you have a redirect on an old web page to a new page, you may want to know if the redirect is failing. For a complete list of status codes visit the Internet Assigned Numbers Authority’s (IANA) HTTP Status Code Registry.

Advanced HTTP settings

With the basic HTTP monitor, you can expand the check by declaring a user agent, use basic authentication, and define HTTP Requests on the Advanced tab.

User agent:

Do you want to test your web page with specific browsers? Using the User Agent settings you can choose between 15 different commonly used browsers or you can create a custom agent. Please note that this only sends the chosen User Agent along with the request. As such, we do not actually monitor the site in a browser. If you want to monitor a single page in a real browser, please use a Real Browser Check or Full Page Check.

Authenticate Users:

If your page requires user authentication, you can provide a username and password to verify that your authentication processes work correctly. Learn how Uptrends uses encryption to keep your authentication information safe.

Custom HTTP requests:

The basic HTTP monitor uses a “get” header, but you can test the post headers as well. You can also create and test your own custom HTTP request headers.

Note: The HTTP monitor type will only download the HTML content of a page. It does not include any images, scripts, or interactive elements that the page may contain. If you need to check the complete content of a web page, we suggest you consider the Full Page Check monitor type.
By using the Uptrends website, you consent to the use of cookies in accordance with our Cookie Policy.