You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: site/content/_shared/variables-and-secrets.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ There are two ways to store configuration information in Checkly: Variables and
7
7
-**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.
8
8
-**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.
9
9
10
-
> 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.
10
+
> 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.
11
11
12
12
> [!WARNING]
13
13
> 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`.
Copy file name to clipboardExpand all lines: site/content/docs/CICD/vercel.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Checkly offers two integrations for Vercel users:
27
27
To install Checkly's managed Vercel integration, navigate to the [integration's marketplace listing](https://vercel.com/integrations/checkly) and click `Install`.
28
28
29
29
1. Select `Create new account` in the installation guide and click `Next` to accept the terms and conditions.
30
-
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/).
30
+
2. Select your plan type. You can read about our pricing plans [here](https://www.checklyhq.com/pricing/)here.
31
31
3. Name your account and review your plan selection. You can change your account name later.
32
32
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.
Copy file name to clipboardExpand all lines: site/content/docs/_index.md
+28-11Lines changed: 28 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,9 @@ Checks, Browser Checks and all other constructs.
46
46
Not quite ready to start your monitoring as code journey? No problem. Get started using just the web UI and you'll be
47
47
monitoring in minutes.
48
48
49
+
### Synthetic Checks
50
+
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.
51
+
49
52
<divclass="cards-list">
50
53
{{< doc-card
51
54
class="two-column-card"
@@ -60,7 +63,7 @@ monitoring in minutes.
60
63
headerTag="h3"
61
64
title="Create an API check"
62
65
img="/docs/images/icons/api.svg"
63
-
description="Monitor the latency and assert the correctness of your API endpoints. Use inline scripts and code to customize everything."
66
+
description="Monitor the latency and assert the correctness of your API endpoints. Use setup and teardown scripts to customize your requests."
64
67
link="/docs/api-checks"
65
68
>}}
66
69
</div>
@@ -77,10 +80,32 @@ monitoring in minutes.
77
80
{{< doc-card
78
81
class="two-column-card"
79
82
headerTag="h3"
80
-
title="Create a TCP check"
83
+
title="Create a Playwright check suite (Beta)"
84
+
img="/docs/images/icons/playwright-check.svg"
85
+
description="Use your existing Playwright tests as live, scheduled checks to verify functionality, performance, and reliability from different locations"
86
+
link="/docs/playwright-checks/"
87
+
>}}
88
+
</div>
89
+
90
+
### Uptime Monitors
91
+
Use Uptime monitors to regularly check if a website, port, or service is available and responding as expected.
92
+
93
+
<divclass="cards-list">
94
+
{{< doc-card
95
+
class="two-column-card"
96
+
headerTag="h3"
97
+
title="Create a URL monitor"
98
+
img="/docs/images/icons/url.svg"
99
+
description="Monitor HTTP resources to verify that your website or service is online and returning the expected response."
100
+
link="/docs/url-monitors/"
101
+
>}}
102
+
{{< doc-card
103
+
class="two-column-card"
104
+
headerTag="h3"
105
+
title="Create a TCP monitor"
81
106
img="/docs/images/icons/tcp.svg"
82
107
description="Monitor the availability and performance of your TCP services by establishing TCP connections and verifying the response."
83
-
link="/docs/tcp-checks/"
108
+
link="/docs/tcp-monitors/"
84
109
>}}
85
110
</div>
86
111
@@ -93,14 +118,6 @@ monitoring in minutes.
93
118
description="Monitor your backup jobs, data imports, and other recurring jobs or scripts by pinging Checkly at a regular interval."
94
119
link="/docs/heartbeat-monitors/"
95
120
>}}
96
-
{{< doc-card
97
-
class="two-column-card"
98
-
headerTag="h3"
99
-
title="Set up alert channels"
100
-
img="/docs/images/icons/alerting.svg"
101
-
description="Get notified about outages or slow downs in your webapps and APIs. Connect to one of our many integrations like Slack and Pagerduty."
Copy file name to clipboardExpand all lines: site/content/docs/api-checks/_index.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,7 @@ Ensure your API is working properly with API checks. API checks work by sending
18
18
19
19
20
20
For example, you can use these checks to verify that:
21
+
21
22
* Your endpoint returns a 200 status code.
22
23
* Your endpoint responds with valid JSON that matches the expected schema.
23
24
* 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
41
42
42
43
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.
43
44
44
-
You can import a cURL command, Swagger.json or OpenAPI specification here too.
45
+
You can import a cURL command, Swagger.json or OpenAPI specification here too.
45
46
46
47
### Setup and teardown scripts
47
48
@@ -57,6 +58,7 @@ Sometimes APIs can be slow, but not broken. We call this degraded. You can set [
57
58
58
59
This is where you determine whether the response of the HTTP request is correct or not.
59
60
You can assert on different sources. These could be:
61
+
60
62
- The HTTP status code returned from the API
61
63
- Something missing or required within the response body
0 commit comments