> ## Documentation Index
> Fetch the complete documentation index at: https://checkly-422f444a-mda-troubleshooting-section.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# URL Monitors Overview

> Monitor websites and apps to verify their availability and performance.

<Tip>
  **Monitoring as Code**: Learn more about the [URL Monitor Construct](/constructs/url-monitor).
</Tip>

## What are URL Monitors?

URL monitors track the availability of your HTTP-based services by sending requests to specified URLs and validating avaliability and performance.

<Frame>
  <img className="block dark:hidden" src="https://mintcdn.com/checkly-422f444a-mda-troubleshooting-section/CyrWpE-3guep-OG4/images/next/url-monitor-overview-light.png?fit=max&auto=format&n=CyrWpE-3guep-OG4&q=85&s=61d20c721ecdc074dd079c01383f28d7" alt="URL monitor overview" width="1888" height="1220" data-path="images/next/url-monitor-overview-light.png" />

  <img className="hidden dark:block" src="https://mintcdn.com/checkly-422f444a-mda-troubleshooting-section/CyrWpE-3guep-OG4/images/next/url-monitor-overview-dark.png?fit=max&auto=format&n=CyrWpE-3guep-OG4&q=85&s=d7fcaf43e9cffd86450fb2114bb3eff1" alt="URL monitor overview" width="1886" height="694" data-path="images/next/url-monitor-overview-dark.png" />
</Frame>

**Typical Use Cases Include:**

* Ensuring your marketing site returns a 200 OK
* Verifying your documentation site loads quickly
* Checking that your SSL certificate is still valid
* Confirming that a public pricing endpoint is reachable for customers

## How URL Monitors Work

URL monitors send HTTP requests to specified URLs and validate availability and performance. They can be configured to check for specific status codes and response times while running from multiple global locations.

<Steps>
  <Step title="Enter your URL">
    Enter the URL you want to monitor.
  </Step>

  <Step title="Configure Response Times and Status Codes">
    Configure the response times and status codes you want to check for.
  </Step>

  <Step title="Select your locations">
    Select the locations you want to run the monitor from.
  </Step>

  <Step title="Configure your alerting">
    Configure your alerting to send you an alert when the monitor fails.
  </Step>

  <Step title="Schedule your monitor">
    Schedule your monitor to run at the frequency you want.
  </Step>
</Steps>

## Best Practices

<Accordion title="Choosing Frequencies">
  * **Critical services**: Every 1-2 minutes
  * **Important services**: Every 5 minutes
  * **Standard services**: Every 10-15 minutes
  * **Background services**: Every 30 minutes to 1 hour
</Accordion>

<Accordion title="Location Selection">
  * Choose 2-3 locations covering your user base
  * Include at least one location near your infrastructure
  * Consider regulatory requirements for data residency
</Accordion>

<Accordion title="Assertion Strategy">
  * Always check status codes
  * Set appropriate response time thresholds
  * Test assertions thoroughly before deployment
</Accordion>

<Accordion title="Implement as a Construct">
  For monitoring as code workflows, use the URL Monitor construct to version control your monitoring configuration and deploy alongside your application code. [Learn about URL Monitor Construct →](/constructs/url-monitor)
</Accordion>