Skip to content

Draft improvements from assistant conversations: URL monitor limits and group UI steps #437

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Draft improvements from assistant conversations: URL monitor limits and group UI steps #437

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions detect/uptime-monitoring/url-monitors/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,10 @@ URL monitors track the availability of your HTTP-based services by sending reque
* Checking that your SSL certificate is still valid
* Confirming that a public pricing endpoint is reachable for customers

<Note>
URL monitors always send a plain `GET` request. They do not support custom request headers, cookies, request bodies, authentication, or [dynamic variables](/detect/synthetic-monitoring/api-checks/configuration) such as `{{moment}}`. If you need any of those, use an [API check](/detect/synthetic-monitoring/api-checks/overview) instead — API checks support all HTTP methods, custom headers (including `Cookie`), request bodies, and body/header assertions.
</Note>

## 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.
Expand Down
9 changes: 9 additions & 0 deletions platform/groups.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,15 @@ You can populate a group by moving existing checks into it or by creating new ch

<Note>By default, newly created check groups behave like folders, with no group-level configuration applied. To get started:</Note>

## Creating a group in the UI

1. In the Checkly app, open the **Checks** page from the left sidebar.
2. Click the **New check** dropdown in the top right and select **Group**.
3. Give the group a name, then click **Save**.
4. Add checks to the group either by opening an existing check and setting its **Group** field, or by creating a new check from within the group.

To manage groups as code, see the [CheckGroup construct](/constructs/check-group) for the Checkly CLI or the [`checkly_check_group` resource](/integrations/iac/terraform/overview) for Terraform.

## Configuration

Groups let you apply shared configuration to standardize how checks behave. Group-level configurations override check-level settings when applied.
Expand Down
Loading