feat: URL monitors (#1315)

* feat: add HTTP checks resource and update weights for menu items

* feat: add HTTP check card to the documentation index

* feat: update analytics API documentation to include HTTP check endpoints

* feat: add HTTP Check documentation with examples and assertion details

* feat: add metric name for HTTP check timing in Prometheus V2 documentation

* feat: add example for creating an HTTP check in Pulumi documentation

* feat: add HTTP check results section with details and new image

* docs: enhance Playwright Check Suites section with HTTP checks

* feat: update incident automation documentation to include HTTP checks

* feat: add  HTTP checks documentation with examples and configuration details

* style: improve formatting and readability in API and TCP checks documentation

* docs: add HTTP checks section with links to documentation

* rework config and index

* undo index.md changes

* Update CLI reference

* Updated dev docs with latest uRL monitor requirements

* Improve wording

* Adjusted results page

* Updated analytics and prometheus wording

* Updated screenshot

* Tcp monitor renaming (#1319)

* docs: update references from TCP checks to TCP monitors

* docs: rename tc-monitors url

* docs: update reference from Check construct to Monitor construct

* docs: improve formatting in constructs reference

* docs: update terminology from check to monitor in TCP monitors documentation

* Added one missing case for rewording

* added alias

---------

Co-authored-by: Susa Tünker <[email protected]>
Co-authored-by: Susa Tünker <[email protected]>

* docs: update HTTP check title and description to reflect URL monitoring

* Changed HTTP check to URL monitor (regression)

* Update CLI construct reference

* Updated pricing references

* hide pricing page

* Update landing page

* Included Albertos changes

* Added updated icons

* Update site/content/docs/cli/constructs-reference.md

Co-authored-by: Simo Kinnunen <[email protected]>

* fix: folder naming

Co-authored-by: Simo Kinnunen <[email protected]>

* fix: check.ts extension

Co-authored-by: Simo Kinnunen <[email protected]>

* Update site/content/docs/cli/constructs-reference.md

Co-authored-by: Simo Kinnunen <[email protected]>

* Update site/content/docs/cli/constructs-reference.md

Co-authored-by: Simo Kinnunen <[email protected]>

* Update site/content/docs/cli/constructs-reference.md

Co-authored-by: Simo Kinnunen <[email protected]>

* Update site/content/docs/cli/constructs-reference.md

Co-authored-by: Simo Kinnunen <[email protected]>

* Update site/content/docs/cli/constructs-reference.md

Co-authored-by: Simo Kinnunen <[email protected]>

* Update site/content/docs/cli/constructs-reference.md

Co-authored-by: Simo Kinnunen <[email protected]>

* Update site/content/docs/cli/constructs-reference.md

Co-authored-by: Simo Kinnunen <[email protected]>

* Incorporate Simo's feedback

* Updated CLI references with shared properties

* Removed monitor class section

* Updated path to rener icons

* Clean up landing page

* Add checkly_api_check_timing_seconds

* Update SVG icons for TCP and URL with new designs and improved structure

---------

Co-authored-by: Susa Tünker <[email protected]>
Co-authored-by: Susa Tünker <[email protected]>
Co-authored-by: Simo Kinnunen <[email protected]>

Author: 3 people

site/assets/docs/images/monitoring/check-results-url.png

@@ -108,60 +108,65 @@ disqusShortname = "checkly"
 	url = "/docs/browser-checks/"
 	weight = 30
 
-[[menu.resources]]
-	name = "Heartbeat monitors"
-	url = "/docs/heartbeat-monitors/"
-	weight = 35
-
 [[menu.resources]]
 	name = "Multistep checks"
 	url = "/docs/multistep-checks/"
 	weight = 40
 
-[[menu.resources]]
-	name = "TCP checks"
-	url = "/docs/tcp-checks/"
-	weight = 45
-
 [[menu.resources]]
 	name = "Playwright Check Suites (Beta)"
 	url = "/docs/playwright-checks/"
 	weight = 50
 
+[[menu.resources]]
+	name = "URL monitors"
+	url = "/docs/url-monitors/"
+	weight = 60
+
+[[menu.resources]]
+	name = "TCP monitors"
+	url = "/docs/tcp-monitors/"
+	weight = 70
+
+[[menu.resources]]
+	name = "Heartbeat monitors"
+	url = "/docs/heartbeat-monitors/"
+	weight = 80
+
 [[menu.resources]]
 	name = "Groups"
 	url = "/docs/groups/"
-	weight = 55
+	weight = 90
 
 [[menu.resources]]
 	name = "Alerting & retries"
 	url = "/docs/alerting/"
-	weight = 60
+	weight = 100
 
 [[menu.resources]]
 	name = "Maintenance windows"
 	url = "/docs/maintenance-windows/"
-	weight = 70
+	weight = 110
 
 [[menu.resources]]
     name = "Dashboards"
     url = "/docs/dashboards/"
-    weight = 80
+    weight = 120
 
 [[menu.resources]]
     name = "Status Pages"
     url = "/docs/status-pages/"
-    weight = 85
+    weight = 130
 
 [[menu.resources]]
 	name = "Accounts & Users"
 	url = "/docs/accounts-users/"
-	weight = 90
+	weight = 140
 
 [[menu.resources]]
 	name = "Private Locations"
 	url = "/docs/private-locations/"
-	weight = 95
+	weight = 150
 
 [[menu.resources]]
 	name = "Reporting"

site/assets/docs/images/tcp-checks/create-tcp-check.png renamed to site/assets/docs/images/tcp-monitors/create-tcp-check.png

@@ -7,7 +7,7 @@ There are two ways to store configuration information in Checkly: Variables and
 - **Variables** are used to store non-sensitive information. Variables are shown in plaintext when being edited, on the check result page and in logs. Variables can be accessed via the CLI and API.
 - **Secrets** allow you to store sensitive data for use in checks. Once saved secrets are never shown in the UI or in logs. The secret value cannot be accessed via the CLI or API.
 
-> Secrets are available for [Private Locations](/docs/private-locations/) on agent version `3.3.4` and later. Secrets are available on [CLI](/docs/cli/) version `4.9.0` and later.
+> Secrets are fully supported starting with runtime version 2024.09 and later. For [Private Locations](/docs/private-locations/), secrets are available in agent version `3.3.4` and later, and for the [CLI](/docs/cli/), in version `4.9.0` and later.
 
 > [!WARNING]
 > To ensure the integrity of Playwright artifacts (traces, videos and screenshots), the following are not scrubbed, even when saved as secrets: The characters `/` and `*` and the full or partial match of `/artifact/`, `https://`, `http://`, `*********`, and `123`.

site/assets/docs/images/tcp-checks/tcp-check-overview.png renamed to site/assets/docs/images/tcp-monitors/tcp-check-overview.png

@@ -27,7 +27,7 @@ Checkly offers two integrations for Vercel users:
 To install Checkly's managed Vercel integration, navigate to the [integration's marketplace listing](https://vercel.com/integrations/checkly) and click `Install`.
 
 1. Select `Create new account` in the installation guide and click `Next` to accept the terms and conditions.
-2. Select your plan type. You can read about our pricing plans [here](https://www.checklyhq.com/pricing/), and more about how we bill checks [here](/docs/monitoring/check-pricing/).
+2. Select your plan type. You can read about our pricing plans [here](https://www.checklyhq.com/pricing/) here.
 3. Name your account and review your plan selection. You can change your account name later.
 4. Press `Create` to continue to the integration settings page. Select `Getting started` to go to the setup guide in Vercel. You can also click `Open in Checkly` to go through the Checkly + Vercel onboarding and get you started with an example project showcasing how to use Monitoring as Code together with Vercel. You can find the [example NextJS project on GitHub](https://github.com/checkly/nextjs-checkly-starter-template) which includes a guide on how to use Monitoring as Code with a NextJS project.
 

site/config.toml

@@ -46,6 +46,9 @@ Checks, Browser Checks and all other constructs.
 Not quite ready to start your monitoring as code journey? No problem. Get started using just the web UI and you'll be
 monitoring in minutes.
 
+### Synthetic Checks
+Checkly synthetic checks are automated end to end tests that simulate user interactions or API requests to monitor the performance and availability of web applications and services.
+
 <div class="cards-list">
 {{< doc-card
 	  class="two-column-card"
@@ -60,7 +63,7 @@ monitoring in minutes.
 	  headerTag="h3"
 	  title="Create an API check"
 	  img="/docs/images/icons/api.svg"
-	  description="Monitor the latency and assert the correctness of your API endpoints. Use inline scripts and code to customize everything."
+	  description="Monitor the latency and assert the correctness of your API endpoints. Use setup and teardown scripts to customize your requests."
 	  link="/docs/api-checks"
 >}}
 </div>
@@ -77,10 +80,32 @@ monitoring in minutes.
 {{< doc-card
 	  class="two-column-card"
 	  headerTag="h3"
-    title="Create a TCP check"
+	  title="Create a Playwright check suite (Beta)"
+	  img="/docs/images/icons/playwright-check.svg"
+	  description="Use your existing Playwright tests as live, scheduled checks to verify functionality, performance, and reliability from different locations"
+	  link="/docs/playwright-checks/"
+>}}
+</div>
+
+### Uptime Monitors
+Use Uptime monitors to regularly check if a website, port, or service is available and responding as expected.
+
+<div class="cards-list">
+{{< doc-card
+   class="two-column-card"
+   headerTag="h3"
+   title="Create a URL monitor"
+   img="/docs/images/icons/url.svg"
+   description="Monitor HTTP resources to verify that your website or service is online and returning the expected response."
+   link="/docs/url-monitors/"
+>}}
+{{< doc-card
+	class="two-column-card"
+	headerTag="h3"
+    title="Create a TCP monitor"
     img="/docs/images/icons/tcp.svg"
     description="Monitor the availability and performance of your TCP services by establishing TCP connections and verifying the response."
-    link="/docs/tcp-checks/"
+    link="/docs/tcp-monitors/"
 >}}
 </div>
 
@@ -93,14 +118,6 @@ monitoring in minutes.
    description="Monitor your backup jobs, data imports, and other recurring jobs or scripts by pinging Checkly at a regular interval."
    link="/docs/heartbeat-monitors/"
 >}}
-{{< doc-card
- class="two-column-card"
- headerTag="h3"
- title="Set up alert channels"
- img="/docs/images/icons/alerting.svg"
- description="Get notified about outages or slow downs in your webapps and APIs. Connect to one of our many integrations like Slack and Pagerduty."
- link="/docs/alerting"
->}}
 </div>
 
 ## Additional resources

site/content/_shared/variables-and-secrets.md

@@ -27,10 +27,11 @@ or keep reading for more examples!
 
 There are three main endpoints.
 
-1. `/v1/analytics/metrics/`: returns all the available metrics for a specific check-type (`API`, `TCP` or `BROWSER`)
-2. `/v1/analytics/browser-checks/{checkId}`: returns metrics for Browser checks. 
+1. `/v1/analytics/metrics/`: returns all the available metrics for a specific check-type (`API`, `URL`, `TCP` or `BROWSER`)
+2. `/v1/analytics/browser-checks/{checkId}`: returns metrics for Browser checks.
 3. `/v1/analytics/api-checks/{checkId}`: returns metrics for API checks.
-4. `/v1/analytics/tcp-checks/{checkId}`: returns metrics for TCP checks.
+4. `/v1/analytics/url-monitors/{checkId}`: returns metrics for URL monitors.
+5. `/v1/analytics/tcp-checks/{checkId}`: returns metrics for TCP monitors.
 
 The specific endpoints per check type return a JSON response that includes a check's attributes, period requested, 
 grouped `series` and a `metadata` section where you'll have additional information about the metrics to create rich reports.

site/content/docs/CICD/vercel.md

@@ -18,6 +18,7 @@ Ensure your API is working properly with API checks. API checks work by sending
 ![Screenshot of the API check overview page](/docs/images/api-checks/overview-check-overview.png)
 
 For example, you can use these checks to verify that:
+
 * Your endpoint returns a 200 status code.
 * Your endpoint responds with valid JSON that matches the expected schema.
 * Your endpoint is properly authenticating requests.
@@ -41,7 +42,7 @@ This is where you configure the API endpoint. The most important part of your AP
 
 Endpoints can be accessed and manipulated through [HTTP methods](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods). Not all methods are valid for all endpoints.
 
-You can import a cURL command, Swagger.json or OpenAPI specification here too. 
+You can import a cURL command, Swagger.json or OpenAPI specification here too.
 
 ### Setup and teardown scripts
 
@@ -57,6 +58,7 @@ Sometimes APIs can be slow, but not broken. We call this degraded. You can set [
 
 This is where you determine whether the response of the HTTP request is correct or not.
 You can assert on different sources. These could be:
+
 - The HTTP status code returned from the API
 - Something missing or required within the response body
 - A specific response header

site/content/docs/_index.md

@@ -20,9 +20,9 @@ You should therefore **replace any confidential data in your check scripts with
 
 You can create variables at three hierarchical levels:
 
-- **Check** level - Browser and multistep check supported.
-- **Group** level - API & network as well as browser and multistep checks supported.
-- **Global** level - API & network as well as browser and multistep checks supported.
+- **Check** level (Only supported by API, Browser, Multistep & Playwright checks)
+- **Group** level
+- **Global** level
 
 Add variables specific to a Check variables on the **Variables** tab for each browser and multistep check.