This guide walks you through creating your first URL monitor to check the availability and performance of your websites, APIs, or any HTTP-based service. Each URL monitor is defined by its request configuration, which includes the target URL and how its availability and performance should be validated.
Monitoring as Code: To get started with your first URL Monitor using code, learn more about the URL Monitor Construct.

​
Basic Setup

Configure your URL monitor by specifying the endpoint and request method:
URL monitor setup interface showing HTTP method selection, URL input field, and options for Skip SSL and Follow redirects
  • Request method: Always GET
  • URL: The HTTP(S) URL to monitor (e.g. https://api.example.com)
  • IP family: Defaults to IPv4

​
Response Validation

​
Assertions

Validate the returned response status code:
URL monitor assertions interface showing status code configuration

​
Response Performance

Define performance thresholds for degraded or failed states:
URL monitor response time limits interface showing degraded and failed thresholds

​
Frequency

Set how often the monitor runs (every 10 seconds to 24 hours).
URL monitor frequency interface showing 10 seconds to 24 hours options

​
Scheduling & Locations

URL monitor scheduling strategy interface showing round robin vs fixed schedule options
  • Scheduling: Choose between round-robin or parallel execution. Learn more about scheduling strategies
  • Locations: Select one or more public or private locations to run the monitor from

​
Additional Settings