HTTP Monitor

What is HTTP Monitor?

The HTTP Monitor tracks a website or URL regularly to make sure that it is up.

Parameters

A HTTP Monitor takes the following parameters:-

  • Name: The unique name for the monitor to identify it
  • URL: The URL to monitor. Must begin with http:// or https://
  • Interval: Controls how frequently to monitor the URL. You can select a range from 1 minute to 24 hours. The free plan is restricted to a 3 minute minimum interval.

Response Time

The response time of a HTTP monitor is the time from when the request started and the first byte was received from the server. The technical term for response time is Time to First Byte (TTFB).

How to track Response Time of a website?

The HTTP Monitor automatically tracks the response times for a URL. All you need to do is Add an HTTP Monitor. To see the response times follow these steps:-

  • Goto the Monitors Area by selecting it from the left sidebar
  • Click on an appropriate Status from the left
  • Find your monitor and click on it to see it's detail
  • You can see a line chart that shows the response time for the last 24 hours (by default)
  • The average response time for the period is also listed
  • Click on any of the buttons on the top left (1H, 6H, 12H, etc) to select the date and time range for which you want to see the response times

SSL Monitoring

You can enable HTTP monitoring for URLs starting with https://. Once enabled, Pinger Man will validate the SSL certificates on the target server. Any SSL issues such as host name mismatch or certificate chain errors will cause the monitor to go down. All alerts you have associated with the monitor will be sent out.

Pinger Man will also send out email notifications 1 day, 7 days and 15 days before the SSL certificate expires.

Email alerts must be configured on the monitor for expiry alerts to work.

Custom HTTP Headers

You can send custom HTTP headers along with the request. All headers must specify a Key and a Value. You can use this feature to specify things like HTTP Authorization headers, Client IDs or anything else your server requires.

Custom HTTP Codes

You can customize the HTTP status codes by choosing the ones that should be considered for a monitor to be up. By default 20x and 30x HTTP status codes are considered to be up.

HTTP Authentication

Password protected websites can be monitored by specifying a username and password. Pinger Man will perform the HTTP request using basic authentication.

For Bearer tokens, use a custom HTTP header specifying your API token.