From adb614b7512675ab00fa8925d0b4ef3ba436e818 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Fri, 17 Jul 2026 13:08:37 +0000
Subject: [PATCH 1/3] docs: clarify Prometheus metric vs billing and multi-repo
git metadata
---
cli/attaching-git-metadata.mdx | 16 +++++++++++++++-
integrations/observability/prometheus-v2.mdx | 4 ++++
2 files changed, 19 insertions(+), 1 deletion(-)
diff --git a/cli/attaching-git-metadata.mdx b/cli/attaching-git-metadata.mdx
index f14def0d9..ddc7cb897 100644
--- a/cli/attaching-git-metadata.mdx
+++ b/cli/attaching-git-metadata.mdx
@@ -37,4 +37,18 @@ Or, if you want to set repo URL you invoke:
```bash Terminal
CHECKLY_REPO_URL="https://my.git.solution/project/" npx checkly test
-```
\ No newline at end of file
+```
+
+## Working with multiple repositories
+
+Each `checkly test --record` or `checkly deploy` invocation attaches metadata for a **single** `repoUrl`. If your monitors span multiple source repositories (for example, a backend repo and a frontend repo), run the CLI separately from each repository's CI pipeline and set `CHECKLY_REPO_URL` (and the other git variables) to point at the repo that owns the checks being tested or deployed in that pipeline.
+
+```bash Terminal
+# Backend CI pipeline
+CHECKLY_REPO_URL="https://github.com/acme/backend" npx checkly deploy
+
+# Frontend CI pipeline
+CHECKLY_REPO_URL="https://github.com/acme/frontend" npx checkly deploy
+```
+
+To keep checks from different repos isolated, scope each pipeline to its own set of resources — for example by placing each repo's checks in a separate [group](/platform/groups) or by using the [`--tags`](/cli/checkly-deploy) and check-file globs in `checkly.config` so that a deploy from one repo only touches its own checks.
\ No newline at end of file
diff --git a/integrations/observability/prometheus-v2.mdx b/integrations/observability/prometheus-v2.mdx
index b6c924c36..c90a53f1f 100644
--- a/integrations/observability/prometheus-v2.mdx
+++ b/integrations/observability/prometheus-v2.mdx
@@ -88,6 +88,10 @@ checkly_check_status{name="Passing Browser Check",status="degraded"} 0
`checkly_check_status` can be useful for viewing the current status of a check, whereas `checkly_check_result_total` can be useful for calculating overall statistics.
+
+`checkly_check_result_total` counts individual **check run results** over a 1-hour window and is intended for statistics and alerting, not for reconciling billing. Plan usage and billing are tracked separately in the Checkly app under [Billing](https://app.checklyhq.com/settings/account/billing) and via the CLI ([`checkly account plan`](/cli/checkly-account)), which report **active checks** and **check run volume** as measured by the billing system. A difference between this metric and your billing dashboard is expected — they measure different things.
+
+
The metrics `checkly_browser_check_web_vitals_seconds`, `checkly_browser_check_errors`, `checkly_api_check_timing_seconds`, `checkly_tcp_monitor_timing_seconds`, `checkly_icmp_monitor_timing_seconds`, and `checkly_dns_monitor_timing_seconds` contain a `type` label.
This label indicates the different Web Vitals, error types, and timing phases being measured.
From bf2a5bd1f173b575579ccd91271c64d6d4c7cd79 Mon Sep 17 00:00:00 2001
From: Hannes Lenke
Date: Tue, 3 Nov 2026 20:31:11 -0500
Subject: [PATCH 2/3] Apply suggestion from @hlenke
---
integrations/observability/prometheus-v2.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/integrations/observability/prometheus-v2.mdx b/integrations/observability/prometheus-v2.mdx
index c90a53f1f..8147df0f6 100644
--- a/integrations/observability/prometheus-v2.mdx
+++ b/integrations/observability/prometheus-v2.mdx
@@ -89,7 +89,7 @@ checkly_check_status{name="Passing Browser Check",status="degraded"} 0
`checkly_check_status` can be useful for viewing the current status of a check, whereas `checkly_check_result_total` can be useful for calculating overall statistics.
-`checkly_check_result_total` counts individual **check run results** over a 1-hour window and is intended for statistics and alerting, not for reconciling billing. Plan usage and billing are tracked separately in the Checkly app under [Billing](https://app.checklyhq.com/settings/account/billing) and via the CLI ([`checkly account plan`](/cli/checkly-account)), which report **active checks** and **check run volume** as measured by the billing system. A difference between this metric and your billing dashboard is expected — they measure different things.
+`checkly_check_result_total` counts check results for statistics and alerting. It is not a billing measure and does not match the usage shown on the [Billing page](https://app.checklyhq.com/settings/account/billing) or by [`checkly account usage summary`](/cli/checkly-account).
The metrics `checkly_browser_check_web_vitals_seconds`, `checkly_browser_check_errors`, `checkly_api_check_timing_seconds`, `checkly_tcp_monitor_timing_seconds`, `checkly_icmp_monitor_timing_seconds`, and `checkly_dns_monitor_timing_seconds` contain a `type` label.
From f8ba950636e3c83dad01c065c7d9e9a4e2922fbb Mon Sep 17 00:00:00 2001
From: Hannes Lenke
Date: Tue, 3 Nov 2026 20:31:20 -0500
Subject: [PATCH 3/3] Apply suggestion from @hlenke
---
cli/attaching-git-metadata.mdx | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/cli/attaching-git-metadata.mdx b/cli/attaching-git-metadata.mdx
index ddc7cb897..c113d63b5 100644
--- a/cli/attaching-git-metadata.mdx
+++ b/cli/attaching-git-metadata.mdx
@@ -41,14 +41,17 @@ CHECKLY_REPO_URL="https://my.git.solution/project/" npx checkly test
## Working with multiple repositories
-Each `checkly test --record` or `checkly deploy` invocation attaches metadata for a **single** `repoUrl`. If your monitors span multiple source repositories (for example, a backend repo and a frontend repo), run the CLI separately from each repository's CI pipeline and set `CHECKLY_REPO_URL` (and the other git variables) to point at the repo that owns the checks being tested or deployed in that pipeline.
+Each `checkly test --record` or `checkly deploy` run attaches one repository URL. If your checks live in more than one repository, for example a backend and a frontend repository, give each repository its own Checkly project: a `checkly.config.ts` with a unique [`logicalId`](/constructs/project#param-logical-id) and its own [`repoUrl`](/constructs/project#param-repo-url).
-```bash Terminal
-# Backend CI pipeline
-CHECKLY_REPO_URL="https://github.com/acme/backend" npx checkly deploy
+```ts checkly.config.ts
+import { defineConfig } from 'checkly'
-# Frontend CI pipeline
-CHECKLY_REPO_URL="https://github.com/acme/frontend" npx checkly deploy
+export default defineConfig({
+ projectName: 'Backend monitoring',
+ logicalId: 'backend-monitoring',
+ repoUrl: 'https://github.com/acme/backend',
+ /* More options... */
+})
```
-To keep checks from different repos isolated, scope each pipeline to its own set of resources — for example by placing each repo's checks in a separate [group](/platform/groups) or by using the [`--tags`](/cli/checkly-deploy) and check-file globs in `checkly.config` so that a deploy from one repo only touches its own checks.
\ No newline at end of file
+Do not deploy two repositories with the same `logicalId`. A deploy deletes the checks in the project that its code does not declare, so the second repository's deploy removes the first one's checks.
\ No newline at end of file