Monitor management · Monitor types
Use a website monitor
Monitor a public web page or customer-facing route for availability and expected HTTP response behavior. The guide follows the same monitor workflow used in the dashboard, so you can create, pause, remove, and troubleshoot monitors with confidence.
When to use it
Use a website monitor for a public web page, landing page, login page, or customer-facing route. The monitor checks that the page is reachable and returns the expected HTTP status code.
Recommended settings
- Use GET for standard pages.
- Use the public URL customers actually rely on.
- Keep authentication disabled unless the page intentionally requires basic auth.
- Set the expected status code to the page's healthy response.
- Enable SSL verification for HTTPS pages.
Use with status pages
Website monitors are often the best source for customer-facing status pages because they represent the route users can recognize. Choose the monitor in status-page Structure and select the widget detail customers need.
Use customer language
When a website monitor appears on a status page, prefer a clear service name over an internal host name.