Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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: 3 additions & 1 deletion communicate/alerts/retries.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -28,13 +28,15 @@ Click **Edit check** or **Edit group** on the 3-dot menu on your [Checkly Home p

### Scheduled check retries

There are three distinct retry strategies based on the time between retry attempts, and each one comes with different retry/backoff characteristics.
There are four retry strategies based on the time between retry attempts, and each one comes with different retry/backoff characteristics.

- **Single** — retry once after a fixed interval, e.g. 5s.
- **Fixed** — a fixed time between retries, e.g. 5s, 5s, 5s etc.
- **Linear** — a linearly increasing time between retries, e.g. 5s, 10s, 15s etc.
- **Exponential** — an exponentially increasing time between retries, e.g. 5s, 25s, 125s (2m and 5s) etc.

For uptime monitors, the strategies you can use depend on your [plan](https://www.checklyhq.com/pricing/): **Fixed**, **Linear** and **Exponential** aren't available on every plan.

On top of the time between attempts, you can also set:

- **maximum number of retries** - the maximum number of retries for this check or check group.
Expand Down
2 changes: 2 additions & 0 deletions concepts/scheduling.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,8 @@ With **Parallel Scheduling**, each time the check is scheduled it will run once

Use **Parallel Scheduling** to reduce detection times for regional outages and reduce time to detect service degradations that impact the customer experience.

For uptime monitors, parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/).

## How scheduling works

Checkly runs each check on a fixed interval, its frequency, not at specific clock times. Frequencies range from every 10 seconds to every 24 hours, depending on the check type. Cron expressions and time-of-day schedules such as "every day at 1:00 AM" are not supported.
Expand Down
4 changes: 2 additions & 2 deletions detect/uptime-monitoring/dns-monitors/configuration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -352,15 +352,15 @@ Set how often the monitor runs (every 10 seconds to 24 hours):
<img className="hidden dark:block" src="/images/dns-monitors/scheduling-dark.png" alt="DNS monitor scheduling strategy and location selection interface" />
</Frame>

* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling)
* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/).
* **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from

### Additional Settings

* **Name:** Give your monitor a clear name to identify it in dashboards and alerts
* **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/ai/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview)
* **Tags:** Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview)
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries)
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/).
* **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations

## Common Use Cases
Expand Down
4 changes: 2 additions & 2 deletions detect/uptime-monitoring/grpc-monitors/configuration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -76,13 +76,13 @@ Set how often the monitor runs (every 10 seconds to 24 hours).

### Scheduling & Locations

* **Strategy**: Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling)
* **Strategy**: Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/).
* **Locations**: Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from

### Additional Settings

* **Name**: Give your monitor a clear name to identify it in dashboards and alerts
* **Description**: Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/ai/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview)
* **Tags**: Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview)
* **Retries**: Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries)
* **Retries**: Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/).
* **Alerting**: Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations
4 changes: 2 additions & 2 deletions detect/uptime-monitoring/icmp-monitors/configuration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -96,15 +96,15 @@ Set how often the monitor runs (every 10 seconds to 24 hours):
<img className="hidden dark:block" src="/images/dns-monitors/scheduling-dark.png" alt="ICMP monitor scheduling strategy and location selection interface" />
</Frame>

* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling)
* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/).
* **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from

### Additional Settings

* **Name:** Give your monitor a clear name to identify it in dashboards and alerts
* **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/ai/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview)
* **Tags:** Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview)
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries)
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/).
* **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations


4 changes: 2 additions & 2 deletions detect/uptime-monitoring/ssl-monitors/configuration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -139,13 +139,13 @@ Set how often the monitor runs. SSL monitors run at most **once per minute** (ev

### Scheduling & Locations

* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling).
* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/).
* **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from.

### Additional Settings

* **Name:** Give your monitor a clear name to identify it in dashboards and alerts.
* **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/ai/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview).
* **Tags:** Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview).
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries).
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/).
* **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations.
4 changes: 2 additions & 2 deletions detect/uptime-monitoring/tcp-monitors/configuration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -62,15 +62,15 @@ Set how often the monitor runs (every 10 seconds to 24 hours). Sub-minute freque
<img src="/images/tcp-scheduling-strategy.png" alt="TCP monitor scheduling strategy and location selection interface" />
</Frame>

* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling)
* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/).
* **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from

### Additional Settings

* **Name:** Give your monitor a clear name to identify it in dashboards and alerts
* **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/ai/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview)
* **Tags:** Use tags to organize monitors across dashboards and [maintenance windows](/communicate/maintenance-windows/overview)
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries)
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/).
* **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations

<Note>
Expand Down
4 changes: 2 additions & 2 deletions detect/uptime-monitoring/tcp-monitors/quickstart.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -60,15 +60,15 @@ Set how often the monitor runs (every 10 seconds to 24 hours):
<img src="/images/tcp-scheduling-strategy.png" alt="TCP monitor scheduling strategy and location selection interface" />
</Frame>

* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling#scheduling-strategies)
* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling#scheduling-strategies). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/).
* **Locations:** Select [public](/concepts/locations) or [private](/platform/private-locations/overview) locations to run the monitor from

## Additional Settings

* **Name:** Give your monitor a clear name to identify it in dashboards and alerts
* **Tags:** Use tags to organize monitors across dashboards and [maintenance windows](/communicate/maintenance-windows/overview)
* **Description:** A description of the check. Supports Markdown. Maximum length: 500 characters
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries)
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/).
* **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations


Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -100,13 +100,13 @@ Set how often the monitor runs. Traceroute monitors run at most **once every 30

### Scheduling & Locations

* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling)
* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/).
* **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from

### Additional Settings

* **Name:** Give your monitor a clear name to identify it in dashboards and alerts
* **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/ai/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview)
* **Tags:** Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview)
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries)
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/).
* **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations
6 changes: 5 additions & 1 deletion detect/uptime-monitoring/url-monitors/configuration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ Choose when and how your checks run across multiple locations:

* **Round Robin** (Default): Checks run on one of the selected locations each time it is scheduled

* **Parallel**: Checks run from all selected locations simultaneously. Higher consumption but provides immediate global visibility for critical services
* **Parallel**: Checks run from all selected locations simultaneously. Higher consumption but provides immediate global visibility for critical services. Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/).

Learn more in our documentation on [Scheduling strategies](/concepts/scheduling/#scheduling-strategies).

Expand Down Expand Up @@ -92,6 +92,10 @@ Select the retry strategy to determine how failed checks are retried:
| **Linear** | Increase retry delay linearly with each attempt to avoid overwhelming failed services |
| **Exponential** | Grow the retry delay exponentially (base delay to the power of the attempt, e.g. 5s, 25s, 125s) for maximum protection against service overload |

<Note>
Most plans offer **None** and **Single** only. **Fixed**, **Linear** and **Exponential** need a [plan](https://www.checklyhq.com/pricing/) that includes multiple retries for uptime monitors.
</Note>

### Alert Settings

Configure notifications for your team:
Expand Down
4 changes: 2 additions & 2 deletions detect/uptime-monitoring/url-monitors/quickstart.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -56,15 +56,15 @@ Set how often the monitor runs (every 10 seconds to 24 hours).
<img src="/images/url-monitor-scheduling-strategy.png" alt="URL monitor scheduling strategy interface showing round robin vs fixed schedule options" />
</Frame>

* **Scheduling:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling)
* **Scheduling:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/).
* **Locations:** Select [public](/concepts/locations) or [private](/platform/private-locations/overview) locations to run the monitor from

## Additional Settings

* **Name:** Give your monitor a clear name to identify it in dashboards and alerts
* **Tags:** Use tags to organize monitors across dashboards and [maintenance windows](/communicate/maintenance-windows/overview)
* **Description:** A short description of the check. Supports Markdown. Maximum length: 500 characters
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries)
* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/).
* **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations


Expand Down
Loading