From 0d75837545b16ccdd4b7a293ebfd708eb585f0f6 Mon Sep 17 00:00:00 2001 From: Paula Mallol Date: Wed, 8 Oct 2025 11:21:21 +0200 Subject: [PATCH 1/5] docs: add section on mixing different monitor types in groups --- platform/groups.mdx | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/platform/groups.mdx b/platform/groups.mdx index 9160cce..b1038fc 100644 --- a/platform/groups.mdx +++ b/platform/groups.mdx @@ -145,4 +145,19 @@ Groups can serve different organizational needs: - **Strict templates:** Enforce consistency through shared configurations - **Loose containers:** Provide structure without imposing shared settings - **Team boundaries:** Enable clear ownership and delegation of monitoring responsibilities -- **Scaling mechanism:** Manage complexity through logical decomposition as your infrastructure grows \ No newline at end of file +- **Scaling mechanism:** Manage complexity through logical decomposition as your infrastructure grows + +## Mixing Different Monitor Types in a Group + +When you purchase a plan in Checkly, it comes with certain feature entitlements, which you can review on our [pricing page](https://www.checklyhq.com/pricing/). These entitlements differ by monitor type: + +* Synthetic checks (e.g. API, Multistep, Browser, Playwright Check Suites) +* Uptime monitors (e.g. URL, TCP, DNS) + +This means checks and monitors on the same plan may not all have access to the same features. For example: An API check might support `parallel` scheduling, while a TCP monitor only allows for `round-robin` scheduling. + +Groups let you organize any type of checks/monitors together and define shared settings. If those shared settings aren't supported by all monitors in the group, Checkly will throw a validation error asking you to either adjust the setting or remove the incompatible monitor. + +Example: If your plan only allows `round-robin` for uptime monitors and you configure the group with `parallel` scheduling, you'll see an error. To resolve it, switch to `round-robin`, move uptime monitors into a separate group, or upgrade your plan. + +If you're unsure how to proceed, don't hesitate to reach out to our [support team](mailto:support@checklyhq.com), we're happy to help. \ No newline at end of file From 4b99cd9e667fcbb63022dcbd5e0db244d1d892c1 Mon Sep 17 00:00:00 2001 From: Paula Mallol Date: Wed, 8 Oct 2025 11:21:27 +0200 Subject: [PATCH 2/5] docs: add section on overrides for mixed groups in CheckGroupV2 documentation --- constructs/check-group-v2.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/constructs/check-group-v2.mdx b/constructs/check-group-v2.mdx index 43caa4d..632dec8 100644 --- a/constructs/check-group-v2.mdx +++ b/constructs/check-group-v2.mdx @@ -265,6 +265,12 @@ When referencing existing groups with `fromId()`, note: If you need these features, you can either import the group using the [Checkly import feature](/cli/checkly-import) (e.g. `npx checkly import check-group:123`) or define a new group directly in your project. +## How overrides work for mixed groups + +Group validation ensures that all checks within a group can support the selected configuration settings. Since uptime monitors and synthetic checks have different feature limitations based on your plan tier, Checkly validates group settings against the lowest common denominator of supported features to prevent configuration conflicts. + +For detailed guidance, see [Mixing Different Monitor Types in a Group](/docs/platform/groups/#mixing-different-monitor-types-in-a-group). + ## Examples From 3f31a8354b2eb06d31740ccb8e2a577c3e4c0dee Mon Sep 17 00:00:00 2001 From: Paula Mallol Date: Wed, 8 Oct 2025 11:25:07 +0200 Subject: [PATCH 3/5] fix: link to Mixing Different Monitor Types in a Group section --- constructs/check-group-v2.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/constructs/check-group-v2.mdx b/constructs/check-group-v2.mdx index 632dec8..9217137 100644 --- a/constructs/check-group-v2.mdx +++ b/constructs/check-group-v2.mdx @@ -269,7 +269,7 @@ If you need these features, you can either import the group using the [Checkly i Group validation ensures that all checks within a group can support the selected configuration settings. Since uptime monitors and synthetic checks have different feature limitations based on your plan tier, Checkly validates group settings against the lowest common denominator of supported features to prevent configuration conflicts. -For detailed guidance, see [Mixing Different Monitor Types in a Group](/docs/platform/groups/#mixing-different-monitor-types-in-a-group). +For detailed guidance, see [Mixing Different Monitor Types in a Group](/platform/groups/#mixing-different-monitor-types-in-a-group). ## Examples From 5158ecb039147a231c812a34fcf251b76244056f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Susa=20T=C3=BCnker?= Date: Thu, 9 Oct 2025 14:04:27 +0200 Subject: [PATCH 4/5] proposal for new wording --- constructs/check-group-v2.mdx | 9 ++++++--- platform/groups.mdx | 12 +++++------- 2 files changed, 11 insertions(+), 10 deletions(-) diff --git a/constructs/check-group-v2.mdx b/constructs/check-group-v2.mdx index 9217137..486937e 100644 --- a/constructs/check-group-v2.mdx +++ b/constructs/check-group-v2.mdx @@ -265,11 +265,14 @@ When referencing existing groups with `fromId()`, note: If you need these features, you can either import the group using the [Checkly import feature](/cli/checkly-import) (e.g. `npx checkly import check-group:123`) or define a new group directly in your project. -## How overrides work for mixed groups +## Shared settings in groups with different monitor types -Group validation ensures that all checks within a group can support the selected configuration settings. Since uptime monitors and synthetic checks have different feature limitations based on your plan tier, Checkly validates group settings against the lowest common denominator of supported features to prevent configuration conflicts. +With `CheckGroupV2` you can group uptime monitors (e.g. URL, TCP, DNS) and synthetic checks (e.g. API, Multistep, Playwright Check Suites). Depending on your plan type, some [group settings](/constructs/check-group-v2#configuration) (such as parallel runs or advanced retry strategies) may not be supported across both monitor types. + +To prevent issues, Checkly validates group settings against the lowest common denominator of supported features across all monitors in the group. + +See [Mixing Checks and Monitors in a Group](/platform/groups/#mixing-checks-and-monitors-in-a-group) for details and examples. -For detailed guidance, see [Mixing Different Monitor Types in a Group](/platform/groups/#mixing-different-monitor-types-in-a-group). ## Examples diff --git a/platform/groups.mdx b/platform/groups.mdx index ad7c543..51c621d 100644 --- a/platform/groups.mdx +++ b/platform/groups.mdx @@ -148,17 +148,15 @@ Groups can serve different organizational needs: - **Scaling mechanism:** Manage complexity through logical decomposition as your infrastructure grows -## Mixing Different Monitor Types in a Group +## Mixing Checks and Monitors in a Group -When you purchase a plan in Checkly, it comes with certain feature entitlements, which you can review on our [pricing page](https://www.checklyhq.com/pricing/). These entitlements differ by monitor type: +When you purchase a plan in Checkly, it includes access to specific monitoring features. As shown on our [pricing page](https://www.checklyhq.com/pricing), feature availability can differ between: -* Synthetic checks (e.g. API, Multistep, Browser, Playwright Check Suites) * Uptime monitors (e.g. URL, TCP, DNS) +* Synthetic checks (e.g. API, Multistep, Browser, Playwright Check Suites) -This means checks and monitors on the same plan may not all have access to the same features. For example: An API check might support `parallel` scheduling, while a TCP monitor only allows for `round-robin` scheduling. - -Groups let you organize any type of checks/monitors together and define shared settings. If those shared settings aren't supported by all monitors in the group, Checkly will throw a validation error asking you to either adjust the setting or remove the incompatible monitor. +This means monitors and checks on the same plan may not all have access to the same features. For example: A Browser check might support `parallel` scheduling, while a TCP monitor only allows for `round-robin` scheduling. -Example: If your plan only allows `round-robin` for uptime monitors and you configure the group with `parallel` scheduling, you'll see an error. To resolve it, switch to `round-robin`, move uptime monitors into a separate group, or upgrade your plan. +Groups let you organize any type of checks/monitors together and define [shared settings](/platform/groups#configuration). If those shared settings aren't supported by all monitors in the group, Checkly will throw a validation error asking you to either adjust the configuration or remove the incompatible monitor. If you're unsure how to proceed, don't hesitate to reach out to our [support team](mailto:support@checklyhq.com), we're happy to help. \ No newline at end of file From 81f2a95df2cf7ee01499328bbd713f71214625c7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Susa=20T=C3=BCnker?= Date: Thu, 9 Oct 2025 14:12:26 +0200 Subject: [PATCH 5/5] adjusted wording --- constructs/check-group-v2.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/constructs/check-group-v2.mdx b/constructs/check-group-v2.mdx index 486937e..13ec7f3 100644 --- a/constructs/check-group-v2.mdx +++ b/constructs/check-group-v2.mdx @@ -265,13 +265,13 @@ When referencing existing groups with `fromId()`, note: If you need these features, you can either import the group using the [Checkly import feature](/cli/checkly-import) (e.g. `npx checkly import check-group:123`) or define a new group directly in your project. -## Shared settings in groups with different monitor types +## Shared Settings in Groups with Different Monitor Types With `CheckGroupV2` you can group uptime monitors (e.g. URL, TCP, DNS) and synthetic checks (e.g. API, Multistep, Playwright Check Suites). Depending on your plan type, some [group settings](/constructs/check-group-v2#configuration) (such as parallel runs or advanced retry strategies) may not be supported across both monitor types. -To prevent issues, Checkly validates group settings against the lowest common denominator of supported features across all monitors in the group. +To avoid conflicts, Checkly validates group settings against the lowest common denominator of supported features in the group. -See [Mixing Checks and Monitors in a Group](/platform/groups/#mixing-checks-and-monitors-in-a-group) for details and examples. +See [Mixing Checks and Monitors in a Group](/platform/groups/#mixing-checks-and-monitors-in-a-group) for details. ## Examples