Skip to content

Commit 50ba09e

Browse files
authored
Heartbeat monitor renaming (#1320)
1 parent 92c3a5e commit 50ba09e

File tree

12 files changed

+32
-31
lines changed

12 files changed

+32
-31
lines changed

site/config.toml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -109,8 +109,8 @@ disqusShortname = "checkly"
109109
weight = 30
110110

111111
[[menu.resources]]
112-
name = "Heartbeat checks"
113-
url = "/docs/heartbeat-checks/"
112+
name = "Heartbeat monitors"
113+
url = "/docs/heartbeat-monitors/"
114114
weight = 35
115115

116116
[[menu.resources]]

site/content/docs/_index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,10 +88,10 @@ monitoring in minutes.
8888
{{< doc-card
8989
class="two-column-card"
9090
headerTag="h3"
91-
title="Create a Heartbeat check"
91+
title="Create a Heartbeat monitor"
9292
img="/docs/images/icons/heartbeats-check-stroked.svg"
9393
description="Monitor your backup jobs, data imports, and other recurring jobs or scripts by pinging Checkly at a regular interval."
94-
link="/docs/heartbeat-checks/"
94+
link="/docs/heartbeat-monitors/"
9595
>}}
9696
{{< doc-card
9797
class="two-column-card"

site/content/docs/alerting-and-retries/retries.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Whether you need to retry a check or a test session, there are different retries
1818
1919
## Check retry strategies
2020

21-
All check types and check groups, except for Heartbeat checks, have a **Retries & Alerting** section available, where you can define the number of retries and which retry strategy your check or check group uses.
21+
All check types and check groups, except for Heartbeat monitors, have a **Retries & Alerting** section available, where you can define the number of retries and which retry strategy your check or check group uses.
2222

2323
Click **Edit check** or **Edit group** on the 3-dot menu on your [Checkly Home page](https://app.checklyhq.com/) and select the **Retries & Alerting** tab:
2424

site/content/docs/heartbeat-checks/_index.md renamed to site/content/docs/heartbeat-monitors/_index.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,21 @@
11
---
2-
title: Getting started with Heartbeat checks - Checkly Docs
3-
displayTitle: Getting started with Heartbeat checks
2+
title: Getting started with Heartbeat monitors - Checkly Docs
3+
displayTitle: Getting started with Heartbeat monitors
44
navTitle: Overview
55
weight: 14
66
slug: /
77
menu:
88
resources:
9-
parent: "Heartbeat checks"
10-
identifier: "heartbeat-checks"
9+
parent: "Heartbeat monitors"
10+
identifier: "heartbeat-monitors"
1111
aliases:
1212
- /docs/heartbeat-checks/quickstart/
1313
- /docs/heartbeat-checks/getting-started/
14+
- /docs/heartbeat-checks/
1415

1516
---
1617

17-
Monitor your scheduled jobs with Heartbeat checks. Heartbeat checks listen for regular pings from your automated tasks, to ensure that they are running as expected.
18+
Track your scheduled jobs with Heartbeat monitors. Heartbeat monitors listen for regular pings from your automated tasks, to ensure that they are running as expected.
1819

1920
> Heartbeat checks are available on our [Team and Enterprise plans](https://www.checklyhq.com/pricing).
2021
File renamed without changes.

site/content/docs/monitoring/check-results.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -132,23 +132,23 @@ These include:
132132

133133
e. Download
134134

135-
## Heartbeat check results
135+
## Heartbeat monitor results
136136

137-
Heartbeat check results show information about the ping request, like when it was recieved and its source.
137+
Heartbeat monitor results show information about the ping request, like when it was recieved and its source.
138138

139-
![Using the Heartbeat check results view](/docs/images/monitoring/check-results-heartbeat.png)
139+
![Using the Heartbeat monitor results view](/docs/images/monitoring/check-results-heartbeat.png)
140140

141-
The state indicates when your scheduled job pinged the Heartbeat check, relative to the expected time:
141+
The state indicates when your scheduled job pinged the Heartbeat monitor, relative to the expected time:
142142

143143
| State | Description |
144144
| -------- | ------- |
145145
| `EARLY` | Ping recieved before the expected time. |
146146
| `RECEIVED` | Ping recieved right at the expected time. |
147147
| `GRACE` | Ping recieved after the expected time, during the grace period. |
148-
| `LATE` | Ping recieved during the few seconds between the end of the grace period and before the check is marked as failing. This is very rare. |
149-
| `FAILING` | No ping recieved by the end of the grace period. Indicates a failing Heartbeat check. |
148+
| `LATE` | Ping recieved during the few seconds between the end of the grace period and before the monitor is marked as failing. This is very rare. |
149+
| `FAILING` | No ping recieved by the end of the grace period. Indicates a failing Heartbeat monitor. |
150150

151-
The source shows where your ping originated, determined by the `origin` and `referer` request headers. [Learn more about configuring the ping source](/docs/heartbeat-checks/#pinging-your-heartbeat-check).
151+
The source shows where your ping originated, determined by the `origin` and `referer` request headers. [Learn more about configuring the ping source](/docs/heartbeat-monitors/#pinging-your-heartbeat-monitor).
152152

153153
## Multistep check results
154154

site/content/docs/terraform-provider/checks-groups.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Checks make up the most important unit of your Checkly monitoring setup. Groups
1212

1313
## Checks
1414

15-
[Browser checks](/docs/browser-checks/), [API checks](/docs/api-checks/), [Heartbeat checks](/docs/heartbeat-checks/) and [Multistep checks](/docs/multistep-checks/) share many arguments, configuration-wise,
15+
[Browser checks](/docs/browser-checks/), [API checks](/docs/api-checks/), [Heartbeat monitors](/docs/heartbeat-monitors/) and [Multistep checks](/docs/multistep-checks/) share many arguments, configuration-wise,
1616
but also have their own unique ones. The type of your check is controlled using the `type` argument.
1717

1818
### Browser checks
@@ -122,15 +122,15 @@ resource "checkly_check" "get-books" {
122122

123123
> You can see all the configuration options for checks on the official Terraform registry [documentation page](https://registry.terraform.io/providers/checkly/checkly/latest/docs/resources/check#schema).
124124
125-
### Heartbeat checks
125+
### Heartbeat monitors
126126

127-
For example, a heartbeat check can look as follows:
127+
For example, a heartbeat monitor can look as follows:
128128

129129
```terraform
130130
resource "checkly_check" "send-weekly-digest-v-2" {
131-
name = "Send Weekly Digest" // The name of the check
132-
type = "HEARTBEAT" // The type of the check
133-
activated = true // Whether the check will start as active on creation
131+
name = "Send Weekly Digest" // The name of the monitor
132+
type = "HEARTBEAT" // The type of the monitor
133+
activated = true // Whether the monitor will start as active on creation
134134
heartbeat {
135135
period = 7 // The expected period of time between each ping. Between 30 seconds and 365 days.
136136
period_unit = "days" // The unit of time for the period, the available options are `'seconds' | 'minutes' | 'hours' | 'days'`

site/content/learn/monitoring/frontend-monitoring.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ Key metrics in detail:
103103

104104
- **Core Web Vitals**: [Largest Contentful Paint](https://web.dev/articles/lcp) (LCP), [Interaction to Next Pain](https://web.dev/articles/inp) (INP), Cumulative Layout Shift (CLS). These metrics are considered to be quite critical for search engine optimization.
105105
- **JavaScript Error Rates**: Frequency of client-side code failures. You may need to implement filtering for common errors.
106-
- **API Response Times**: Speed and reliability of API calls. This may be called ‘[heartbeat monitoring](https://www.checklyhq.com/docs/heartbeat-checks/#heartbeat-monitoring---checkly-docs)’ if you’re only measuring the reliability of straightforward `get` requests.
106+
- **API Response Times**: Speed and reliability of API calls. This may be called ‘[heartbeat monitoring](https://www.checklyhq.com/docs/heartbeat-monitors/#heartbeat-monitoring---checkly-docs)’ if you’re only measuring the reliability of straightforward `get` requests.
107107
- **Network Request Failures**: Broken or delayed network requests
108108
- **Errors and Crashes**: Stability of the application under different conditions
109109
- **User Interactions and Engagement**: Clicks, scrolls, and session durations

site/content/learn/monitoring/monitoring-as-code.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -215,7 +215,7 @@ MaC makes it easy to monitor performance across regions, simulating user experie
215215

216216
Scheduled jobs or cron jobs are crucial for automating tasks, but failures can lead to major problems if undetected. MaC enables [heartbeat monitoring](https://www.checklyhq.com/blog/heartbeat-monitoring-with-checkly/) to ensure these jobs run on schedule.
217217

218-
A heartbeat check verifies that a job reports back within the expected timeframe. If it doesn’t, an alert is triggered, giving you a chance to fix the issue before it impacts your system.
218+
A heartbeat monitor verifies that a job reports back within the expected timeframe. If it doesn’t, an alert is triggered, giving you a chance to fix the issue before it impacts your system.
219219

220220
This proactive approach ensures your critical automation workflows are reliable and resilient.
221221

site/content/learn/monitoring/synthetic-monitoring.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ A comparison of RUM vs. Synthetics
6767

6868

6969
## Types of Synthetic Monitoring
70-
There are a number of terms used around synthetic monitoring; everything from "Synthetic User Monitoring" to "Heartbeat Checks" can refer to the same test! However, in general, there are four types of monitoring that are most critical for monitoring your production services:
70+
There are a number of terms used around synthetic monitoring; everything from "Synthetic User Monitoring" to "Heartbeat Monitors" can refer to the same test! However, in general, there are four types of monitoring that are most critical for monitoring your production services:
7171

7272
### Uptime or Availability Monitoring
7373
Availability Monitoring is fundamental. Its primary objective is to verify whether a web service or application is accessible at any given time. This type of monitoring simulates user interactions to check the availability of websites, APIs, and servers. It's not just about confirming that a server is up and returning "200 OK" status messages; it's about ensuring that the application is operational and responding as expected.

0 commit comments

Comments
 (0)