Merge branch 'main' into michelle/red-89-update-docs-with-new-troubleshooting-cases

Author: miliberlin

detect/testing/playwright-reporter-changelog.mdx

@@ -13,6 +13,14 @@ Learn more about:
 
 ## Full release history
 
+<Update label="v1.4.1" tags={["February 2026"]}>
+  **Critical Bug Fix**
+
+  **1.4.0 is deprecated. Use this version.**
+
+  - Fixed npm install failing with 404 error due to missing dependency.
+</Update>
+
 <Update label="v1.4.0" tags={["February 2026"]}>
   **Added**
 

integrations/alerts/gitlab_alerts.mdx

@@ -1,42 +1,29 @@
 ---
-title: 'Integrating GitLab Alerts'
-description: 'Configure GitLab Alerts integration to receive failure, degradation, and recovery messages from Checkly'
-sidebarTitle: 'GitLab Alerts'
+title: "Integrating GitLab Alerts"
+description: "Configure GitLab Alerts integration to receive failure, degradation, and recovery messages from Checkly"
+sidebarTitle: "GitLab Alerts"
 ---
 
-Checkly integrates with [GitLab Alerts](https://docs.gitlab.com/ee/operations/incident_management/alerts.html) and can
-deliver failure, degradation, and recovery messages to any project in your GitLab installation. More specifically, Checkly will:
+Checkly integrates with [GitLab Alerts](https://docs.gitlab.com/ee/operations/incident_management/alerts.html) and can deliver failure, degradation, and recovery messages to any project in your GitLab installation. More specifically, Checkly will:
 
 - Open new alerts when a check fails.
 - Close alerts automatically when a failing check recovers.
 - Alert when SSL certificates are about to expire.
 
-1. First, create an **Incoming Webhook**. Log in to GitLab and go to "Settings" > "Operations" and expand the "Alerts" tab
-and select the **HTTP Endpoint** integration type 
-
-   ![setup checkly gitlab_integration step 1](/images/docs/images/integrations/gitlab/gitlab_step1.png)
-
+1. First, create an **HTTP Endpoint**. Log in to GitLab, select a project workspace and go to "Settings" \> "Monitor" and expand the "Alerts" tab and click the "add new integration" button. Then select "HTTP Endpoint" as the integration type.
 2. **Choose a name** for your integration like "Checkly".
 
    ![setup checkly gitlab integration step 2](/images/docs/images/integrations/gitlab/gitlab_step2.png)
-
 3. Save the integration **copy the displayed Webhook URL and Authorization Key**. It should start with something like `https://gitlab.com/...`
 
    ![setup checkly gitlab integration step 3](/images/docs/images/integrations/gitlab/gitlab_step3.png)
-
-
-4. Log in to Checkly and navigate to [Alert Settings](https://app.checklyhq.com/alert-settings/).
-   Click the "Add more channels" button, find GitLab Alerts on the list, and click "Add channel".
+4. Log in to Checkly and navigate to [Alert Settings](https://app.checklyhq.com/alert-settings/). Click the "Add more channels" button, find GitLab Alerts on the list, and click "Add channel".
 
    ![setup checkly gitlab_integration step 5](/images/docs/images/integrations/gitlab/gitlab_step4.png)
-
-
-6. Give the alert channel a name and **paste the Webhook URL and Authorization Key** in their respective input fields. You can now also tweak
-   which alerts you want to be notified of and which checks or check groups should be subscribed to this channel.
+6. Give the alert channel a name and **paste the Webhook URL and Authorization Key** in their respective input fields. You can now also tweak which alerts you want to be notified of and which checks or check groups should be subscribed to this channel.
 
    ![setup checkly gitlab integration step 5](/images/docs/images/integrations/gitlab/gitlab_step5.png)
 
-   > Note that we provide a preconfigured message payload but you are free to edit the payload and add more or different
-   > variables. Just click the "Edit payload" button and reference the "Help & variables tab".
+   > Note that we provide a preconfigured message payload but you are free to edit the payload and add more or different variables. Just click the "Edit payload" button and reference the "Help & variables tab".
 
 Congratulations! You have successfully integrated Checkly with GitLab Alerts!

integrations/incident-management/rootly.mdx

@@ -10,19 +10,18 @@ Checkly integrates with [Rootly](https://rootly.com/) and can deliver failure, d
 - Close incidents automatically when a failing check recovers.
 - Alert when SSL certificates are about to expire.
 
-1. First, create a **Webhook integration**. Log in to your Rootly account, go to "Integrations" and search for the *Webhook* integration.
 
-2. Add the **Webhook** integration and click "Enable Integration" on the next screen. Now **copy the URL**.
+1. Log in to Rootly and navigate to **Alerts > Alert Sources**, click **Add Alert Source** and select "Checkly"."
 
-3. Log in to Checkly and navigate to [Alert Settings](https://app.checklyhq.com/alert-settings/).
-   Click the "Add more channels" button, find Rootly on the list, and click "Add channel".
+2. Take note of the following:
+   - The **Secret** that Rootly.io provides you with.
+   - The **type** you want to target: either **Service**, **Group** or **Escalation Policy**.
+   - The **ID** of the target.
+  Now head over to [Checkly > Alerts](https://app.checklyhq.com/alerts/settings), click **Add more channels** and select **Rootly**.
 
-4. Give the alert channel a name and **paste the URL** in the dedicated URL input field. You can now also tweak
-   which alerts you want to be notified of and which checks or check groups should be subscribed to this channel.
+3. Copy and paste in the API key, select the type and paste in the ID.
+4. Hit **Test Rootly alert** to verify the connection. On the Incident.io side, you should now see a test alert pop up!
+5. Now you are all set up! When an alert is triggered, an incident will be created in Rootly.
 
-   <Callout type="note">
-   Note that we provide a preconfigured message payload but you are free to edit the payload and add more or different
-   variables. Just click the "Edit payload" button and reference the "Help & variables tab".
-   </Callout>
 
-Congratulations! You have successfully integrated Checkly with Rootly!
+You now have successfully integrated Checkly with Rootly.

integrations/observability/prometheus-v2.mdx

@@ -27,8 +27,8 @@ Here is an example
 # prometheus.yml
 - job_name: 'checkly'
   scrape_interval: 60s
-  metrics_path: '/accounts/993adb-8ac6-3432-9e80-cb43437bf263/v2/prometheus/metrics'
-  bearer_token: 'lSAYpOoLtdAa7ajasoNNS234'
+  metrics_path: '/accounts/<your account ID>/v2/prometheus/metrics'
+  bearer_token: '<your bearer token>'
   scheme: https
   static_configs:
   - targets: ['api.checklyhq.com']
@@ -96,6 +96,27 @@ In addition, the check metrics all contain the following labels:
 
 > The counter and histogram metrics are reset every hour. These resets can be handled in Prometheus by using the [rate](https://prometheus.io/docs/prometheus/latest/querying/functions/#rate) or [increase](https://prometheus.io/docs/prometheus/latest/querying/functions/#increase) functions.
 
+### Check Run Location Label
+
+To avoid creating a high volume of metrics, by default the metrics don't include a label for the check run location. It is possible to enable this by adding the query param `locationLabelEnabled=true` to your API request. This will add a `location` label giving the location where the checks ran.
+
+Since check status and SSL days remaining is only tracked on a per-check basis rather than by location, `checkly_check_status` and `checkly_time_to_ssl_expiry_seconds` do not have the `location` label included. All other [check metrics](#check-metrics) will have the `location` label added.
+
+Here is an example for how to set this in your `prometheus.yml` config:
+
+```yaml
+# prometheus.yml
+- job_name: 'checkly'
+  scrape_interval: 60s
+  metrics_path: '/accounts/<your account ID>/v2/prometheus/metrics'
+  bearer_token: '<your bearer token>'
+  scheme: https
+  static_configs:
+  - targets: ['api.checklyhq.com']
+  params:
+    locationLabelEnabled: ['true']
+```
+
 ### PromQL Examples
 
 This section contains a few PromQL queries that you can use to start working with the Prometheus data.
@@ -143,4 +164,4 @@ The Private Location metrics all contain the following labels:
 | ------|-------------|
 | `private_location_name` | the name of the Private Location. |
 | `private_location_slug_name` | the Private Location's human readable unique identifier. |
-| `private_location_id` | the Private Location's UUID. |
+| `private_location_id` | the Private Location's UUID. |