Learn more about Check Groups in the Groups overview.
CheckGroup
is deprecated. Please use CheckGroupV2
instead. See CheckGroupV2 documentation for details.CheckGroup
to organize your checks into logical groups. This provides better organization, shared configuration, and group-level controls for your monitoring setup.
Configuration
Parameter | Type | Required | Default | Description |
---|---|---|---|---|
name | string | ✅ | - | Friendly name for your check group |
activated | boolean | ❌ | true | Whether checks in the group are running |
apiCheckDefaults | object | ❌ | - | Default settings for API checks in the group |
alertEscalationPolicy | AlertEscalationPolicy | ❌ | - | Advanced alert escalation settings |
alertChannels | AlertChannel[] | ❌ | [] | Alert channels for all checks in the group |
environmentVariables | object[] | ❌ | [] | Group-level environment variables |
concurrency | number | ❌ | 10 | Number of concurrent Checks to run when a group is triggered |
frequency | Frequency | ❌ | - | How often to run checks within the group |
localSetupScript (deprecated) | string | ❌ | - | Code to run before each check/monitor in this group |
localTearDownScript (deprecated) | string | ❌ | - | Code to run after each check/monitor in this group |
locations | string[] | ❌ | - | Public locations for all checks in the group |
muted | boolean | ❌ | false | Whether alert notifications are muted |
privateLocations | string[] | ❌ | - | Private Location slugs |
retryStrategy | RetryStrategy | ❌ | - | Strategy for configured retries |
runtimeId | string | ❌ | - | Runtime ID for all checks in the group |
runParallel | boolean | ❌ | - | Whether to run checks in parallel across locations |
tags | string[] | ❌ | [] | Tags to organize all checks in the group |
browserChecks | object | ❌ | - | Settings for Browser Checks in the group |
multistepChecks | object | ❌ | - | Settings for Multistep Checks in the group |
Group Options
Friendly name for your check group that will be displayed in the Checkly dashboard and used for organization.Usage:Use cases: Group organization, dashboard display, team coordination.
Whether checks in the group are running. When false, all checks in the group are paused.Usage:Use cases: Environment-specific checks, maintenance windows, temporary disabling.
Whether to mute alerts for all checks in the group. Checks will still run but won’t send notifications.Usage:Use cases: Non-production environments, testing phases, scheduled maintenance.
How often to run checks within the group. This frequency applies to all checks in the group unless overridden at the check level.Usage:Available frequencies:
EVERY_10S
, EVERY_20S
, EVERY_30S
, EVERY_1M
, EVERY_2M
, EVERY_5M
, EVERY_10M
, EVERY_15M
, EVERY_30M
, EVERY_1H
, EVERY_2H
, EVERY_6H
, EVERY_12H
, EVERY_24H
Generally, Check Groups support all available frequencies, but if a group includes a check type that doesn’t support high frequencies,
npx checkly deploy
will fail. We recommend separating high-frequency ones into their own groups.Public locations for all checks in the group. Checks inherit these locations unless they specify their own.Usage:Use cases: Global monitoring, regional service coverage, user experience testing.
Setting to automatically create and apply Browser Checks to a group.Usage:Use cases: Automated test discovery, E2E test organization, user flow monitoring.
Setting to automatically create and apply MultiStep Checks to a group.Usage:Use cases: Automated test discovery, E2E test organization, user flow monitoring.