From 9b33cfe6bae0c38b33387a5df51ba5c8d8d9c99f Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Tue, 27 Oct 2026 21:39:25 -0400 Subject: [PATCH 1/3] docs: make casing of check types, features and brand names consistent Applies the pattern from Laura's capitalization commits (c0043be7, 2f3d950d) across the docs: capitalized check and monitor types with a lowercase noun (Browser checks, Multistep checks, API checks, URL monitors), lowercase feature nouns in prose (status page, private location, alert channel), and vendor casing for third-party names (GitHub, TypeScript, PagerDuty, OpenTelemetry, Opsgenie). Code, commands, identifiers, URLs and quoted UI labels are unchanged. DOC-238 Co-Authored-By: Claude Opus 5.5 --- admin/team-management/overview.mdx | 2 +- ai/ai-assistant.mdx | 14 ++++---- ai/mcp-server.mdx | 2 +- ai/mcp-server/tools.mdx | 2 +- ai/mcp-server/troubleshooting.mdx | 2 +- ai/rocky-ai.mdx | 2 +- ai/skills.mdx | 4 +-- .../heartbeats/create-a-heartbeat-check.mdx | 2 +- .../get-a-list-of-events-for-a-heartbeat.mdx | 2 +- .../get-a-specific-heartbeat-event.mdx | 2 +- .../heartbeats/get-heartbeat-availability.mdx | 2 +- .../heartbeats/update-a-heartbeat-check.mdx | 2 +- .../monitors/update-an-icmp-monitor.mdx | 2 +- api-reference/usage/overview.mdx | 2 +- cli/checkly-deploy.mdx | 6 ++-- cli/checkly-destroy.mdx | 8 ++--- cli/checkly-runtimes.mdx | 2 +- cli/checkly-sync-playwright.mdx | 2 +- cli/checkly-test.mdx | 2 +- cli/dependencies.mdx | 10 +++--- cli/environment-variables.mdx | 14 ++++---- cli/importing.mdx | 2 +- cli/installation.mdx | 2 +- cli/overview.mdx | 4 +-- communicate/alerts/channels.mdx | 8 ++--- communicate/alerts/notification-log.mdx | 4 +-- communicate/alerts/overview.mdx | 2 +- communicate/alerts/ssl-expiration.mdx | 8 ++--- communicate/dashboards/configuration.mdx | 10 +++--- communicate/dashboards/custom-css.mdx | 2 +- communicate/dashboards/overview.mdx | 2 +- communicate/maintenance-windows/overview.mdx | 4 +-- communicate/overview.mdx | 20 +++++------ .../status-pages/creating-a-status-page.mdx | 6 ++-- communicate/status-pages/custom-domain.mdx | 6 ++-- communicate/status-pages/customization.mdx | 2 +- communicate/status-pages/incidents.mdx | 14 ++++---- .../status-pages/maintenance-windows.mdx | 4 +-- communicate/status-pages/overview.mdx | 2 +- .../status-pages/password-protection.mdx | 2 +- .../status-pages/subscriber-notifications.mdx | 4 +-- communicate/status-pages/v2-deprecated.mdx | 2 +- .../moving-from-puppeteer-to-playwright.mdx | 6 ++-- .../frameworks/playwright-vs-cypress.mdx | 2 +- comparisons/status-pages/overview.mdx | 6 ++-- concepts/checks.mdx | 26 +++++++------- concepts/locations.mdx | 6 ++-- concepts/metrics.mdx | 4 +-- constructs/alert-channel.mdx | 2 +- constructs/api-check.mdx | 28 +++++++-------- constructs/browser-check.mdx | 36 +++++++++---------- constructs/check-group-v2.mdx | 18 +++++----- constructs/check-group.mdx | 16 ++++----- constructs/dashboard.mdx | 10 +++--- constructs/dns-monitor.mdx | 24 ++++++------- constructs/email-alert-channel.mdx | 6 ++-- constructs/grpc-monitor.mdx | 18 +++++----- constructs/heartbeat-monitor.mdx | 20 +++++------ constructs/icmp-monitor.mdx | 16 ++++----- constructs/incident-trigger.mdx | 2 +- constructs/incidentio-alert-channel.mdx | 4 +-- constructs/including-checks.mdx | 4 +-- constructs/maintenance-window.mdx | 6 ++-- constructs/msteams-alert-channel.mdx | 4 +-- constructs/multistep-check.mdx | 30 ++++++++-------- constructs/opsgenie-alert-channel.mdx | 4 +-- constructs/pagerduty-alert-channel.mdx | 18 +++++----- constructs/phone-call-alert-channel.mdx | 4 +-- constructs/playwright-check.mdx | 6 ++-- constructs/private-location.mdx | 8 ++--- constructs/project.mdx | 24 ++++++------- constructs/slack-alert-channel.mdx | 4 +-- constructs/slack-app-alert-channel.mdx | 4 +-- constructs/sms-alert-channel.mdx | 6 ++-- constructs/ssl-monitor.mdx | 16 ++++----- constructs/status-page-service.mdx | 10 +++--- constructs/status-page-v3-automation-rule.mdx | 2 +- constructs/status-page-v3-component.mdx | 2 +- constructs/status-page-v3.mdx | 2 +- constructs/status-page.mdx | 8 ++--- constructs/tcp-monitor.mdx | 10 +++--- constructs/telegram-alert-channel.mdx | 4 +-- constructs/traceroute-monitor.mdx | 16 ++++----- constructs/url-monitor.mdx | 10 +++--- constructs/webhook-alert-channel.mdx | 4 +-- detect/overview.mdx | 2 +- .../agentic-checks/migrate.mdx | 6 ++-- .../agentic-checks/overview.mdx | 4 +-- .../api-checks/api-structure.mdx | 8 ++--- .../api-checks/overview.mdx | 14 ++++---- .../api-checks/quickstart.mdx | 4 +-- .../api-checks/troubleshooting.mdx | 2 +- .../browser-checks/examples.mdx | 8 ++--- .../browser-checks/file-system.mdx | 10 +++--- .../browser-checks/mac-structure.mdx | 12 +++---- .../browser-checks/overview.mdx | 14 ++++---- .../browser-checks/performance-metrics.mdx | 4 +-- .../browser-checks/playwright-support.mdx | 16 ++++----- .../browser-checks/quickstart.mdx | 20 +++++------ .../browser-checks/timeouts.mdx | 6 ++-- .../browser-checks/troubleshooting.mdx | 2 +- .../browser-checks/visual-regressions.mdx | 10 +++--- .../multistep-checks/degraded-states.mdx | 2 +- .../multistep-checks/examples.mdx | 2 +- .../multistep-checks/file-system.mdx | 8 ++--- .../multistep-checks/multistep-structure.mdx | 8 ++--- .../multistep-checks/overview.mdx | 12 +++---- .../multistep-checks/quickstart.mdx | 8 ++--- .../multistep-checks/troubleshooting.mdx | 4 +-- .../multistep-checks/websockets.mdx | 2 +- detect/synthetic-monitoring/overview.mdx | 12 +++---- .../playwright-checks/custom-dependencies.mdx | 10 +++--- .../environment-variables.mdx | 6 ++-- .../playwright-checks/overview.mdx | 2 +- .../playwright-checks/performance-metrics.mdx | 2 +- .../playwright-monitoring-comparison.mdx | 12 +++---- detect/testing/creating-your-first-test.mdx | 4 +-- detect/testing/overview.mdx | 4 +-- .../testing/playwright-reporter-changelog.mdx | 4 +-- detect/testing/playwright-reporter.mdx | 4 +-- detect/testing/using-env-variables.mdx | 4 +-- .../dns-monitors/configuration.mdx | 4 +-- .../dns-monitors/overview.mdx | 6 ++-- .../grpc-monitors/configuration.mdx | 4 +-- .../grpc-monitors/overview.mdx | 10 +++--- .../heartbeat-monitors/examples.mdx | 2 +- .../heartbeat-monitors/overview.mdx | 16 ++++----- .../heartbeat-monitors/quickstart.mdx | 22 ++++++------ .../icmp-monitors/configuration.mdx | 2 +- .../icmp-monitors/overview.mdx | 8 ++--- detect/uptime-monitoring/overview.mdx | 12 +++---- .../ssl-monitors/configuration.mdx | 4 +-- .../ssl-monitors/overview.mdx | 10 +++--- .../tcp-monitors/configuration.mdx | 4 +-- .../tcp-monitors/overview.mdx | 12 +++---- .../tcp-monitors/quickstart.mdx | 4 +-- .../traceroute-monitors/configuration.mdx | 4 +-- .../traceroute-monitors/overview.mdx | 12 +++---- .../url-monitors/configuration.mdx | 4 +-- .../url-monitors/overview.mdx | 12 +++---- .../url-monitors/quickstart.mdx | 4 +-- guides/agentic-workflows.mdx | 2 +- guides/claude-code-monitoring.mdx | 12 +++---- guides/communicate-availability.mdx | 4 +-- guides/global-monitoring.mdx | 2 +- guides/keyword-monitoring.mdx | 4 +-- guides/monitoring-an-openapi-spec.mdx | 2 +- ...toring-ecommerce-apps-using-playwright.mdx | 6 ++-- ...itoring-ecommerce-apps-using-terraform.mdx | 10 +++--- guides/monitoring-the-stripe-api.mdx | 8 ++--- guides/overview.mdx | 4 +-- guides/playwright-testing-to-monitoring.mdx | 4 +-- guides/reading-traces.mdx | 2 +- guides/sdlc-monitoring.mdx | 8 ++--- guides/setup-scripts-for-apis.mdx | 2 +- integrations/alerts/slack.mdx | 4 +-- integrations/alerts/webhooks.mdx | 10 +++--- integrations/ci-cd/github/deployments.mdx | 4 +-- .../ci-cd/vercel/deployment-protection.mdx | 8 ++--- integrations/ci-cd/vercel/overview.mdx | 8 ++--- integrations/iac/pulumi/best-practices.mdx | 4 +-- integrations/iac/pulumi/ci-cd.mdx | 2 +- integrations/iac/pulumi/examples.mdx | 12 +++---- integrations/iac/pulumi/setup.mdx | 2 +- integrations/iac/terraform/alerting.mdx | 4 +-- integrations/iac/terraform/checks-groups.mdx | 10 +++--- integrations/iac/terraform/dashboards.mdx | 2 +- .../iac/terraform/environment-variables.mdx | 4 +-- .../iac/terraform/maintenance-windows.mdx | 2 +- integrations/iac/terraform/overview.mdx | 6 ++-- .../iac/terraform/parameterized-resources.mdx | 4 +-- .../iac/terraform/testing-scripts-locally.mdx | 6 ++-- integrations/incident-management/opsgenie.mdx | 2 +- .../incident-management/pagerduty.mdx | 16 ++++----- integrations/observability/coralogix.mdx | 14 ++++---- integrations/observability/prometheus-v2.mdx | 36 +++++++++---------- learn/incidents/anatomy-of-a-status-page.mdx | 10 +++--- learn/incidents/mttr-challenges.mdx | 2 +- learn/incidents/overview.mdx | 2 +- learn/incidents/reduce-mttd.mdx | 2 +- learn/incidents/root-cause-with-traces.mdx | 4 +-- learn/incidents/slo-sla-sli.mdx | 20 +++++------ learn/monitoring/api-monitoring.mdx | 8 ++--- learn/monitoring/end-to-end-monitoring.mdx | 8 ++--- learn/monitoring/frontend-monitoring.mdx | 6 ++-- learn/monitoring/monitoring-as-code.mdx | 8 ++--- learn/monitoring/synthetic-monitoring.mdx | 2 +- learn/monitoring/transaction-monitoring.mdx | 8 ++--- learn/opentelemetry/context-propagation.mdx | 2 +- learn/opentelemetry/how-to-instrument.mdx | 2 +- .../what-is-the-otel-collector.mdx | 2 +- learn/playwright/assertions.mdx | 4 +-- learn/playwright/bypass-totp.mdx | 4 +-- learn/playwright/codegen.mdx | 4 +-- learn/playwright/steps-decorators.mdx | 2 +- learn/playwright/testing-apis.mdx | 4 +-- learn/playwright/testing-pyramid.mdx | 2 +- platform/allowlisting-traffic.mdx | 12 +++---- platform/dynamic-secret-scrubbing.mdx | 4 +-- platform/groups.mdx | 6 ++-- platform/ip-information.mdx | 4 +-- platform/manage-secrets-at-scale.mdx | 6 ++-- .../private-locations/agent-configuration.mdx | 20 +++++------ platform/private-locations/agent-images.mdx | 2 +- platform/private-locations/autoscaling.mdx | 14 ++++---- platform/private-locations/change-log.mdx | 10 +++--- .../kubernetes-deployment.mdx | 2 +- platform/private-locations/overview.mdx | 32 ++++++++--------- platform/private-locations/proxy-setup.mdx | 14 ++++---- .../private-locations/scaling-redundancy.mdx | 20 +++++------ platform/reporting/analytics-api.mdx | 4 +-- platform/reporting/overview.mdx | 2 +- platform/runtimes/overview.mdx | 2 +- platform/runtimes/runtime-specification.mdx | 6 ++-- platform/secrets.mdx | 2 +- platform/variables.mdx | 8 ++--- quickstart.mdx | 6 ++-- resolve/ai-root-cause-analysis/overview.mdx | 4 +-- resolve/automatic-check-repair.mdx | 14 ++++---- resolve/traces/import/missing-spans.mdx | 6 ++-- resolve/traces/import/open-telemetry.mdx | 4 +-- resolve/traces/overview.mdx | 4 +-- snippets/check-intent.mdx | 4 +-- snippets/general-monitor-options-table.mdx | 2 +- what-is-checkly.mdx | 2 +- 225 files changed, 806 insertions(+), 806 deletions(-) diff --git a/admin/team-management/overview.mdx b/admin/team-management/overview.mdx index a9ed12b73..bdd1d98c8 100644 --- a/admin/team-management/overview.mdx +++ b/admin/team-management/overview.mdx @@ -24,7 +24,7 @@ Each account has one Owner. The account creator is the Owner until they [transfe | Access locked variables | ✓ | ✓ | ✓ | ✗ | ✗ | | Manage team members (only below their current role. i.e. Owners can remove Admins, but Admins cannot remove Owners or other Admins.) | ✓ | ✓ | ✗ | ✗ | ✗ | | Manage account settings | ✓ | ✓ | ✗ | ✗ | ✗ | -| Manage Private Locations | ✓ | ✓ | ✗ | ✗ | ✗ | +| Manage private locations | ✓ | ✓ | ✗ | ✗ | ✗ | | Create service API keys | ✓ | ✓ | ✗ | ✗ | ✗ | | Transfer ownership | ✓ | ✗ | ✗ | ✗ | ✗ | diff --git a/ai/ai-assistant.mdx b/ai/ai-assistant.mdx index ce6dec55c..698ea03d6 100644 --- a/ai/ai-assistant.mdx +++ b/ai/ai-assistant.mdx @@ -5,9 +5,9 @@ description: 'Plan monitoring and create checks and monitors with the Checkly AI canonical: 'https://www.checklyhq.com/docs/ai/ai-assistant/' --- -The AI Assistant helps you turn a monitoring goal into a plan and create the checks you approve. It can create Browser, Multistep, and API Checks, as well as uptime and Heartbeat Monitors. It does not create Playwright Check Suites. +The AI Assistant helps you turn a monitoring goal into a plan and create the checks you approve. It can create Browser, Multistep, and API checks, as well as uptime and Heartbeat monitors. It does not create Playwright Check Suites. -Every check it creates includes an intent: the goal and required outcomes the check should prove. For Browser and Multistep Checks created in Checkly, [automatic repair](../resolve/automatic-check-repair) can use that intent when repairing the check's script. +Every check it creates includes an intent: the goal and required outcomes the check should prove. For Browser and Multistep checks created in Checkly, [automatic repair](../resolve/automatic-check-repair) can use that intent when repairing the check's script. @@ -21,15 +21,15 @@ Every check it creates includes an intent: the goal and required outcomes the ch 1. Open **AI Assistant** in the Checkly app and select **New**. 2. Describe the site, app, or API you want to monitor. Include the starting point, the journey, and the observable outcome that should pass. -3. Review the proposed monitoring plan and linked Test Session results. Ask the assistant to adjust the flow, assertions, frequency, locations, or alerting before you approve it. +3. Review the proposed monitoring plan and linked test session results. Ask the assistant to adjust the flow, assertions, frequency, locations, or alerting before you approve it. 4. Select the checks you want and choose **Create checks**. -5. Open each new check, run it, and review its behavior and settings. For Browser and Multistep Checks, also review the **Check intent** section in the check settings. +5. Open each new check, run it, and review its behavior and settings. For Browser and Multistep checks, also review the **Check intent** section in the check settings. -While preparing your plan, the Assistant tests Browser, Multistep, and API Checks in recorded Test Sessions. URL and Heartbeat Monitors are outside this testing step. +While preparing your plan, the Assistant tests Browser, Multistep, and API checks in recorded test sessions. URL and Heartbeat monitors are outside this testing step. -For a browser journey, ask for a Browser Check. For an API endpoint, ask for an API Check; for several related requests, ask for a Multistep Check. Use a URL Monitor for site availability or a Heartbeat Monitor for a scheduled job. If a journey has important negative cases or guardrails, describe them in your request and confirm they appear in the generated intent. +For a browser journey, ask for a Browser check. For an API endpoint, ask for an API check; for several related requests, ask for a Multistep check. Use a URL monitor for site availability or a Heartbeat monitor for a scheduled job. If a journey has important negative cases or guardrails, describe them in your request and confirm they appear in the generated intent. -The AI Assistant does not change a check's automatic repair setting when it creates the check. A Browser or Multistep Check inherits the account default until you [set automatic repair for that check](../resolve/automatic-check-repair#enable-automatic-repair). Review its intent and choose **On** if you want to enable repair explicitly. +The AI Assistant does not change a check's automatic repair setting when it creates the check. A Browser or Multistep check inherits the account default until you [set automatic repair for that check](../resolve/automatic-check-repair#enable-automatic-repair). Review its intent and choose **On** if you want to enable repair explicitly. ## Checks that need project files diff --git a/ai/mcp-server.mdx b/ai/mcp-server.mdx index 1b5638963..9eb1ef72d 100644 --- a/ai/mcp-server.mdx +++ b/ai/mcp-server.mdx @@ -16,7 +16,7 @@ https://api.checklyhq.com/mcp Use it when your agent needs live Checkly account context, check status, check results, test sessions, root cause analyses, result assets, status pages, incidents, account environment variables, or when it needs to trigger existing checks. -You can create and update standalone Browser and Multistep Checks through MCP using inline scripts. Use [Checkly Skills](/ai/skills) and the [Checkly CLI](/cli/overview) when your agent needs to work with local project files, bundle code, or deploy a project. The MCP server runs remotely and cannot access your local filesystem. +You can create and update standalone Browser and Multistep checks through MCP using inline scripts. Use [Checkly Skills](/ai/skills) and the [Checkly CLI](/cli/overview) when your agent needs to work with local project files, bundle code, or deploy a project. The MCP server runs remotely and cannot access your local filesystem. OAuth is the recommended way to connect. The OAuth flow only supports Checkly-approved clients listed in setup. User and service API keys are available for clients that can send custom headers when OAuth is unavailable or a workflow needs a stable service identity. diff --git a/ai/mcp-server/tools.mdx b/ai/mcp-server/tools.mdx index 31c9d33ca..2de47f957 100644 --- a/ai/mcp-server/tools.mdx +++ b/ai/mcp-server/tools.mdx @@ -71,7 +71,7 @@ The check write tools manage checks from a JSON configuration, without a local p A typical create flow: -1. Call `get-check-type-schema` with the `checkType` to learn the `check` payload. Every check type takes different configuration, for example `request` for API checks and uptime monitors, `script` for browser checks, and `heartbeat` for heartbeat monitors. +1. Call `get-check-type-schema` with the `checkType` to learn the `check` payload. Every check type takes different configuration, for example `request` for API checks and uptime monitors, `script` for Browser checks, and `heartbeat` for Heartbeat monitors. 2. Optionally call `list-alert-channels` to pick specific alert channels, and `list-check-groups` to find a `groupId`. 3. Call `create-check` with `checkType` and the `check` payload. By default the new check is subscribed to all of the account's alert channels. Set `autoAssignAlerts` to `false` or pass `check.alertChannelSubscriptions` to change this. diff --git a/ai/mcp-server/troubleshooting.mdx b/ai/mcp-server/troubleshooting.mdx index 064163449..5af711ad2 100644 --- a/ai/mcp-server/troubleshooting.mdx +++ b/ai/mcp-server/troubleshooting.mdx @@ -119,7 +119,7 @@ Views do not refresh automatically. Use **Refresh** to request current data. If ### The MCP server cannot access or deploy my local project -You can create and update standalone Browser and Multistep Checks through MCP using inline scripts. The MCP server runs remotely and cannot access your local project files, bundle code, or deploy a project. +You can create and update standalone Browser and Multistep checks through MCP using inline scripts. The MCP server runs remotely and cannot access your local project files, bundle code, or deploy a project. For local project authoring, use the [Checkly CLI](/cli/overview) in your project. To let your AI agent do this, install [Checkly Skills](/ai/skills). diff --git a/ai/rocky-ai.mdx b/ai/rocky-ai.mdx index 2192519f7..b844d2087 100644 --- a/ai/rocky-ai.mdx +++ b/ai/rocky-ai.mdx @@ -15,7 +15,7 @@ Use the [AI Assistant](./ai-assistant) to plan monitoring and create checks and ### Automatic Check Repair -Set an intent and enable [automatic repair](../resolve/automatic-check-repair) for a Browser or Multistep Check. +Set an intent and enable [automatic repair](../resolve/automatic-check-repair) for a Browser or Multistep check. ### Root Cause and User Impact Analysis diff --git a/ai/skills.mdx b/ai/skills.mdx index 9bc744848..34f319d09 100644 --- a/ai/skills.mdx +++ b/ai/skills.mdx @@ -73,7 +73,7 @@ Using Checkly, you can now control your monitoring setup with AI agents without **Example prompts:** - "Create a URL monitor for api.example.com that checks every 5 minutes" - - "Set up a browser check that logs into my app and verifies the dashboard loads" + - "Set up a Browser check that logs into my app and verifies the dashboard loads" - "Add a Slack alert channel for my production check group" **CLI usage:** @@ -106,7 +106,7 @@ Using Checkly, you can now control your monitoring setup with AI agents without **Example prompts:** - "Show me which checks are currently failing" - - "Investigate why the login browser check started failing yesterday" + - "Investigate why the login Browser check started failing yesterday" - "Trigger an on-demand run of my API health check" **CLI usage:** diff --git a/api-reference/heartbeats/create-a-heartbeat-check.mdx b/api-reference/heartbeats/create-a-heartbeat-check.mdx index 049fd5ec2..d363229e2 100644 --- a/api-reference/heartbeats/create-a-heartbeat-check.mdx +++ b/api-reference/heartbeats/create-a-heartbeat-check.mdx @@ -1,5 +1,5 @@ --- openapi: post /v1/checks/heartbeat -title: Create a heartbeat monitor +title: Create a Heartbeat monitor canonical: 'https://www.checklyhq.com/docs/api-reference/heartbeats/create-a-heartbeat-check/' --- \ No newline at end of file diff --git a/api-reference/heartbeats/get-a-list-of-events-for-a-heartbeat.mdx b/api-reference/heartbeats/get-a-list-of-events-for-a-heartbeat.mdx index 6f1a7ed2e..2ab1aa2f3 100644 --- a/api-reference/heartbeats/get-a-list-of-events-for-a-heartbeat.mdx +++ b/api-reference/heartbeats/get-a-list-of-events-for-a-heartbeat.mdx @@ -1,5 +1,5 @@ --- openapi: get /v1/checks/heartbeats/{checkId}/events -title: List all events for a heartbeat monitor +title: List all events for a Heartbeat monitor canonical: 'https://www.checklyhq.com/docs/api-reference/heartbeats/get-a-list-of-events-for-a-heartbeat/' --- \ No newline at end of file diff --git a/api-reference/heartbeats/get-a-specific-heartbeat-event.mdx b/api-reference/heartbeats/get-a-specific-heartbeat-event.mdx index a6433fe5b..1ef901f73 100644 --- a/api-reference/heartbeats/get-a-specific-heartbeat-event.mdx +++ b/api-reference/heartbeats/get-a-specific-heartbeat-event.mdx @@ -1,5 +1,5 @@ --- openapi: get /v1/checks/heartbeats/{checkId}/events/{id} -title: List a specific event for a heartbeat monitor +title: List a specific event for a Heartbeat monitor canonical: 'https://www.checklyhq.com/docs/api-reference/heartbeats/get-a-specific-heartbeat-event/' --- \ No newline at end of file diff --git a/api-reference/heartbeats/get-heartbeat-availability.mdx b/api-reference/heartbeats/get-heartbeat-availability.mdx index 2f8fdc3a3..9ce3f4464 100644 --- a/api-reference/heartbeats/get-heartbeat-availability.mdx +++ b/api-reference/heartbeats/get-heartbeat-availability.mdx @@ -1,5 +1,5 @@ --- openapi: get /v1/checks/heartbeats/{checkId}/availability -title: Get heartbeat monitor availability +title: Get Heartbeat monitor availability canonical: 'https://www.checklyhq.com/docs/api-reference/heartbeats/get-heartbeat-availability/' --- \ No newline at end of file diff --git a/api-reference/heartbeats/update-a-heartbeat-check.mdx b/api-reference/heartbeats/update-a-heartbeat-check.mdx index fa6ab84ed..a984c17d8 100644 --- a/api-reference/heartbeats/update-a-heartbeat-check.mdx +++ b/api-reference/heartbeats/update-a-heartbeat-check.mdx @@ -1,5 +1,5 @@ --- openapi: put /v1/checks/heartbeat/{id} -title: Update a heartbeat monitor +title: Update a Heartbeat monitor canonical: 'https://www.checklyhq.com/docs/api-reference/heartbeats/update-a-heartbeat-check/' --- \ No newline at end of file diff --git a/api-reference/monitors/update-an-icmp-monitor.mdx b/api-reference/monitors/update-an-icmp-monitor.mdx index c1dc02905..9f07192b7 100644 --- a/api-reference/monitors/update-an-icmp-monitor.mdx +++ b/api-reference/monitors/update-an-icmp-monitor.mdx @@ -1,5 +1,5 @@ --- openapi: put /v1/checks/icmp/{id} -title: Update an ICMP Monitor +title: Update an ICMP monitor canonical: 'https://www.checklyhq.com/docs/api-reference/monitors/update-an-icmp-monitor/' --- diff --git a/api-reference/usage/overview.mdx b/api-reference/usage/overview.mdx index 9a186607d..e4b4d00a8 100644 --- a/api-reference/usage/overview.mdx +++ b/api-reference/usage/overview.mdx @@ -59,7 +59,7 @@ Summary returns `totals.creditsUsed`, `breakdown`, and `coverage`. Each series r Zero credits means calculated zero consumption. Null credits means the API cannot calculate the charge, for example because of uncovered dates or unavailable or incompatible pricing. A rule absent from an otherwise configured term contributes zero credits while retaining measured quantities. -Pricing quantities depend on the rule. API and browser checks use runs, Multistep checks use requests, and Playwright suites use metered 30-second intervals. V2 also prices recorded trace conditions, uptime, AI invocations, status pages, SMS, and phone alerts. Included allowances and conditional rates can change billable quantities and prices. +Pricing quantities depend on the rule. API and Browser checks use runs, Multistep checks use requests, and Playwright suites use metered 30-second intervals. V2 also prices recorded trace conditions, uptime, AI invocations, status pages, SMS, and phone alerts. Included allowances and conditional rates can change billable quantities and prices. `include=runs` adds physical check-run counts: `totalRuns`, `finalRuns`, `retryRuns`, `cancelledRuns`, `degradedRuns`, `failedRuns`, `errorRuns`, `abortedRuns`, and `overMaxResponseTimeRuns`. Outcome flags can overlap. These counts are independent of billed quantities. diff --git a/cli/checkly-deploy.mdx b/cli/checkly-deploy.mdx index 1710e580d..5c891e60d 100644 --- a/cli/checkly-deploy.mdx +++ b/cli/checkly-deploy.mdx @@ -66,7 +66,7 @@ With `--no-plan` the overview has the same markers, but no source file column, n Under the overview, every updated resource gets a header line with its type, logical ID and source file, followed by a diff of the construct as it is in your account against the construct in your code. A legend under the header says what the two sides are: `-` lines are what is live in Checkly, replaced or removed by this deploy; `+` lines are what is in your code, added or changed by this deploy. Everything else is context, and `⋯` marks skipped lines. A `-` line with no `+` line after it is a value your code no longer sets, which the deploy removes. Once the deploy is done, the legend reads `was live in Checkly` and `now live in Checkly` instead. Both sides are rendered the way `checkly import` writes a construct, which leaves out a property whose value is its default. The properties your code spells out are the exception: they are shown on both sides whatever their values, so a move to or from a default reads as a change of that one line. Other constructs are referred to by the names your code gives them. Both need the CLI to find the construct's `new …('id', { … })` call in your code; options passed in a variable or spread into the call keep the import rendering. Facts a diff cannot show are printed as `~` notes: -- The property's path, such as `/script:`, followed by a diff of two texts rather than of the construct, for a change that lives outside it: a browser or multi-step check's script, an API check's setup or teardown script. +- The property's path, such as `/script:`, followed by a diff of two texts rather than of the construct, for a change that lives outside it: a Browser or Multistep check's script, an API check's setup or teardown script. - A property Checkly stores encrypted, such as a locked environment variable, is shown inline with its value masked as `'********'`. The side that changed reads `'******** (changed)'`, or `'******** (changed in Checkly)'` on the deployed side. When the change cannot be shown inline, for example a secret that was renamed, the note `secret changed: ` names the property holding it instead. - `changed: `, such as `changed: code bundle` or `changed: dependency cache, playwright version`, naming every cause in one note, for a change the plan reports by its cause rather than as a property: what the resource bundles or depends on, a setup or teardown snippet, its snapshots, its private locations. - `payload format changed (CLI upgrade)` when the only differences come from a newer CLI describing the same construct differently, such as a private location list or retry strategy being sent in a new form. The deploy rewrites the stored form and nothing about the resource changes. @@ -142,7 +142,7 @@ When the plan shows a resource that was edited in the Checkly web app or through Choosing it writes your account's current values into the construct files and ends the run without deploying, so you can review the result with `git diff` and run `checkly deploy` again. Only what can be written without guessing is written, so a reason found once the file is read (listed below) can still leave nothing to write: -- On every check: `name`, `description`, `activated`, `muted`, `shouldFail`, `tags`, `locations`, `frequency` and `alertEscalationPolicy`; `retryStrategy` on every check except agentic and Playwright checks, which do not take one. Also `degradedResponseTime` and `maxResponseTime` on API checks and URL, TCP, DNS, gRPC, SSL and traceroute monitors; the packet-loss thresholds on ICMP monitors; `period` and `grace` on heartbeat monitors, each written together with its unit; `environmentVariables` and `runtimeId` on API, browser, multistep and Playwright checks (a check that relied on the project-wide runtime gets the value pinned, like any other defaulted property); `intent` on API, browser, multistep and Playwright checks and on URL, TCP, DNS, ICMP and gRPC monitors; `sslCheckDomain` and `aiAutoRepairEnabled` on browser checks and `aiAutoRepairEnabled` on multistep checks; `prompt` on agentic checks (a multi-line prompt written as a template literal stays one); the `request` of an API check (`url`, `method`, `headers`, `queryParameters`, `body`, `bodyType`, `basicAuth`, `followRedirects`, `skipSSL`, `ipFamily`), URL monitor (`url`, `followRedirects`, `skipSSL`, `ipFamily`), TCP monitor (`hostname`, `port`, `data`, `ipFamily`), DNS monitor (`query`, `recordType`, `protocol`, and `nameServer` and `port`, written together), ICMP monitor (`hostname`, `pingCount`, `ipFamily`), gRPC monitor (`url`, `port`, `skipSSL`, `timeout`, `ipFamily` and the `grpcConfig` keys, except `metadata`, whose values Checkly never returns), SSL monitor (`hostname`, `port`, `ipFamily` and the `sslConfig` keys) or traceroute monitor (every key); and the `request.assertions` of an API check and of every URL, TCP, DNS, gRPC, SSL, ICMP and traceroute monitor. Agentic checks take no `shouldFail`. +- On every check: `name`, `description`, `activated`, `muted`, `shouldFail`, `tags`, `locations`, `frequency` and `alertEscalationPolicy`; `retryStrategy` on every check except agentic and Playwright checks, which do not take one. Also `degradedResponseTime` and `maxResponseTime` on API checks and URL, TCP, DNS, gRPC, SSL and Traceroute monitors; the packet-loss thresholds on ICMP monitors; `period` and `grace` on Heartbeat monitors, each written together with its unit; `environmentVariables` and `runtimeId` on API, Browser, Multistep and Playwright checks (a check that relied on the project-wide runtime gets the value pinned, like any other defaulted property); `intent` on API, Browser, Multistep and Playwright checks and on URL, TCP, DNS, ICMP and gRPC monitors; `sslCheckDomain` and `aiAutoRepairEnabled` on Browser checks and `aiAutoRepairEnabled` on Multistep checks; `prompt` on agentic checks (a multi-line prompt written as a template literal stays one); the `request` of an API check (`url`, `method`, `headers`, `queryParameters`, `body`, `bodyType`, `basicAuth`, `followRedirects`, `skipSSL`, `ipFamily`), URL monitor (`url`, `followRedirects`, `skipSSL`, `ipFamily`), TCP monitor (`hostname`, `port`, `data`, `ipFamily`), DNS monitor (`query`, `recordType`, `protocol`, and `nameServer` and `port`, written together), ICMP monitor (`hostname`, `pingCount`, `ipFamily`), gRPC monitor (`url`, `port`, `skipSSL`, `timeout`, `ipFamily` and the `grpcConfig` keys, except `metadata`, whose values Checkly never returns), SSL monitor (`hostname`, `port`, `ipFamily` and the `sslConfig` keys) or Traceroute monitor (every key); and the `request.assertions` of an API check and of every URL, TCP, DNS, gRPC, SSL, ICMP and Traceroute monitor. Agentic checks take no `shouldFail`. - On a check group: `name`, `activated`, `muted`, `tags`, `locations`, `concurrency`, `environmentVariables`, `runtimeId`, `retryStrategy`, `alertEscalationPolicy`, and `apiCheckDefaults` (`url`, `headers`, `queryParameters`, `basicAuth`, `assertions`). - On every alert channel: `sendRecovery`, `sendFailure`, `sendDegraded`, `sslExpiry` and `sslExpiryThreshold`, plus the channel's own properties: `address` on an email channel; `channel` on a Slack channel; `slackChannels` on a Slack app channel; `name`, `webhookType`, `template` and `method` on a webhook channel; `name`, `region` and `priority` on an Opsgenie channel; `account` and `serviceName` on a PagerDuty channel; `phoneNumber` and `name` on an SMS or phone call channel; `name` and `payload` on an MS Teams or incident.io channel; `name` on a Telegram channel. A credential (a webhook or Slack URL, an API key, a service key, a webhook secret, the values of `headers` and `queryParameters`) is never written, since Checkly does not return it; a channel's type, and the webhook type and method the MS Teams, Telegram and incident.io constructs fix, cannot change in the code; Telegram's `chatId`, `messageThreadId`, `payload` and `apiKey` are packed into the message template and URL, which the CLI does not unpack. - On a private location: `name`, `slugName` and `icon` (`proxyUrl` is never written). @@ -481,7 +481,7 @@ When Checkly does not schedule the checks of a deploy that asked for it, the CLI After the deploy, schedule only the checks that run every N minutes or less often. More frequent checks are left out and run at their next scheduled time; they gain little from an extra run right after a deploy. -The frequency is the one Checkly resolves for each check, including its defaults: an SSL or traceroute monitor without an explicit frequency runs every minute, so the default minimum leaves it out. Sub-minute checks count as running more often than every minute. Heartbeat monitors are never scheduled. +The frequency is the one Checkly resolves for each check, including its defaults: an SSL or Traceroute monitor without an explicit frequency runs every minute, so the default minimum leaves it out. Sub-minute checks count as running more often than every minute. Heartbeat monitors are never scheduled. With `auto`, Checkly applies its default minimum of 10 minutes. You can set any whole number up to 1440; a higher value fails the deploy. `0` schedules every check. diff --git a/cli/checkly-destroy.mdx b/cli/checkly-destroy.mdx index ac17941df..3b788b4f6 100644 --- a/cli/checkly-destroy.mdx +++ b/cli/checkly-destroy.mdx @@ -92,10 +92,10 @@ The `destroy` command removes the all the resources managed by the specified pro - **Checks** (API, Browser, Heartbeat, etc.) - **Monitors** (URL, TCP, DNC, etc.) -- **Check Groups** and their configurations -- **Alert Channels** defined in your project -- **Maintenance Windows** created via CLI -- **Private Locations** (if managed by the project) +- **Check groups** and their configurations +- **Alert channels** defined in your project +- **Maintenance windows** created via CLI +- **Private locations** (if managed by the project) When run with `--preserve-resources`, only the project itself is deleted. All of the above resources remain in your Checkly account as regular account-level resources and are no longer tracked by the CLI. diff --git a/cli/checkly-runtimes.mdx b/cli/checkly-runtimes.mdx index b1c8dadef..e97d5d3d4 100644 --- a/cli/checkly-runtimes.mdx +++ b/cli/checkly-runtimes.mdx @@ -102,7 +102,7 @@ When selecting a runtime, consider: - **Package versions** your code depends on - **Node.js features** you're using -- **Playwright compatibility** for browser checks +- **Playwright compatibility** for Browser checks - **Long-term support** for production environments Use the latest runtime for new projects to benefit from the newest features and security updates. diff --git a/cli/checkly-sync-playwright.mdx b/cli/checkly-sync-playwright.mdx index da264bd05..540d743b2 100644 --- a/cli/checkly-sync-playwright.mdx +++ b/cli/checkly-sync-playwright.mdx @@ -11,7 +11,7 @@ The `checkly sync-playwright` command synchronizes your Playwright configuration Keeping your configuration in sync ensures consistency between local testing and cloud monitoring environments. -The applied [`playwrightConfig` configuration](/constructs/project#param-checks-playwright-config) is applied to all Browser and MultiStep Checks defined in your Checkly project. +The applied [`playwrightConfig` configuration](/constructs/project#param-checks-playwright-config) is applied to all Browser and Multistep checks defined in your Checkly project. Before using `checkly sync-playwright`, ensure you have: diff --git a/cli/checkly-test.mdx b/cli/checkly-test.mdx index 4adb6506d..a27ac393b 100644 --- a/cli/checkly-test.mdx +++ b/cli/checkly-test.mdx @@ -396,7 +396,7 @@ npx checkly test --update-snapshots npx checkly test -u ``` -Snapshots are essential for [visual regression testing in Browser Checks](/detect/synthetic-monitoring/browser-checks/visual-regressions). +Snapshots are essential for [visual regression testing in Browser checks](/detect/synthetic-monitoring/browser-checks/visual-regressions). diff --git a/cli/dependencies.mdx b/cli/dependencies.mdx index eddd4b0cd..d314a8d86 100644 --- a/cli/dependencies.mdx +++ b/cli/dependencies.mdx @@ -11,14 +11,14 @@ How dependencies work depends on the check type: | Check type | Dependency model | Environment field | |------------|------------------|-------------------| -| Browser Checks and Multistep Checks | Run in a Checkly runtime with fixed Checkly-provided dependencies | `runtimeId` | +| Browser checks and Multistep checks | Run in a Checkly runtime with fixed Checkly-provided dependencies | `runtimeId` | | Playwright Check Suites | Install dependencies from your project files, including `package.json` and your lock file | `engine` | -Use `runtimeId` to choose a custom Checkly runtime for Browser Checks and Multistep Checks. Use `engine` only for Playwright Check Suites, where it overrides the JavaScript engine version that runs your own Playwright project. +Use `runtimeId` to choose a custom Checkly runtime for Browser checks and Multistep checks. Use `engine` only for Playwright Check Suites, where it overrides the JavaScript engine version that runs your own Playwright project. ## npm packages -### Browser, Multistep, and API Checks +### Browser, Multistep, and API checks Not all npm packages are available in a Checkly runtime. @@ -53,7 +53,7 @@ This is useful for defining helper functions to be reused across multiple checks The Checkly CLI automatically detects these dependencies and bundles them with the check. No additional configuration is needed. -Here is a [Browser Check](/detect/synthetic-monitoring/browser-checks/overview) example of how this works in practice. +Here is a [Browser check](/detect/synthetic-monitoring/browser-checks/overview) example of how this works in practice. The directory tree looks like the following: @@ -64,7 +64,7 @@ __checks__ └── login-helper.ts ``` -`login-helper.ts` defines a function `gitHubLogin` that can be used by multiple Browser Checks. +`login-helper.ts` defines a function `gitHubLogin` that can be used by multiple Browser checks. ```ts login-helper.ts export async function gitHubLogin (page, username, password) { diff --git a/cli/environment-variables.mdx b/cli/environment-variables.mdx index 7640cb319..4d503d579 100644 --- a/cli/environment-variables.mdx +++ b/cli/environment-variables.mdx @@ -1,7 +1,7 @@ --- -title: 'Environment Variables' +title: 'Environment variables' description: 'Learn how to use environment variables in your Checkly project' -sidebarTitle: 'Environment Variables' +sidebarTitle: 'Environment variables' canonical: 'https://www.checklyhq.com/docs/cli/environment-variables/' --- @@ -16,7 +16,7 @@ To get a quick overview of when to use which, checkout this video 👇 -## Local Environment Variables +## Local environment variables Local environment variables exist on your local machine, your CI environment, or anywhere you run the Checkly CLI. They normally are part of your shell session or stored in a `.env` file in your app's Git repo. Here is what you need to @@ -29,7 +29,7 @@ Use local environment variables to inject or replace values in your `Check`, `Al **build time** when the CLI compiles your constructs for testing and deploying. Here is an example of setting up an `SmsAlertChannel` where we pass in the actual phone number from a local environment -variable. Note the exclamation mark `!` at the end. This is to tell the Typescript compiler the value will be set. +variable. Note the exclamation mark `!` at the end. This is to tell the TypeScript compiler the value will be set. Alternatively you can use a string template. ```ts Alert-Channel.check.ts @@ -51,7 +51,7 @@ PHONE_NUMBER=0987654321 npx checkly deploy The above command will replace `process.env.PHONE_NUMBER` with the actual `PHONE_NUMBER` you prepended and then create that SMS channel in your Checkly account. -## Remote Environment Variables +## Remote environment variables Checkly also stores environment variables in your Checkly account. These can exist at [the Global, Group or Check level](/platform/variables). Here is what you need to remember: @@ -139,7 +139,7 @@ npx checkly test --env-file="./.env" You can also pull in the variables from your account and store them in a file using [the `npx checkly env pull` command](/cli/checkly-env#pull). See the examples below. -### Managing Remote Environment Variables +### Managing remote environment variables Manage your remote environment variables with the CLI using the [`checkly env` command](/cli/checkly-env). You can list, add, update, remove and export your global variables. @@ -166,7 +166,7 @@ Reference that file in your `test` command. [See the full reference documentation for the `checkly env` command](/cli/checkly-env). -## Securing Environment Variables +## Securing environment variables For storing and securing environment variables, we advise the following: diff --git a/cli/importing.mdx b/cli/importing.mdx index b005c3c21..c62325d89 100644 --- a/cli/importing.mdx +++ b/cli/importing.mdx @@ -17,7 +17,7 @@ To ensure that you can go through this process safely, and test your setup along - `npx checkly import commit`: Commits the plan, removing the **pending** state from all imported resources. Imported resources can now be deleted through the CLI by removing their constructs. At this point the `import` is completed and cannot be canceled. -Playwright check suites are never part of an import plan, whether you import everything or [name a single check by id](#importing-individual-resources): a suite is defined by the code bundle the CLI uploaded on deploy, and an import cannot turn that bundle back into source files. Naming one reports that no importable resources were found. To manage a suite from a new project, deploy it again from the Playwright project that holds its source. +Playwright Check Suites are never part of an import plan, whether you import everything or [name a single check by id](#importing-individual-resources): a suite is defined by the code bundle the CLI uploaded on deploy, and an import cannot turn that bundle back into source files. Naming one reports that no importable resources were found. To manage a suite from a new project, deploy it again from the Playwright project that holds its source. ## Importing step-by-step diff --git a/cli/installation.mdx b/cli/installation.mdx index 477e81db2..442e5bbbc 100644 --- a/cli/installation.mdx +++ b/cli/installation.mdx @@ -116,7 +116,7 @@ If you cannot access the npm registry directly, you can also download the Checkl The download is a zipped folder containing a full installation of [the boilerplate example project](https://github.com/checkly/checkly-cli/tree/main/examples/boilerplate-project). You will find the following files and folders: - a `checkly.config.ts` file. -- a `package.json` file including the necessary Typescript dependencies. +- a `package.json` file including the necessary TypeScript dependencies. - a `node_modules` directory with all dependencies pre-installed. - a `__checks__` folder with some example checks. diff --git a/cli/overview.mdx b/cli/overview.mdx index f92bbb19a..a413a84ab 100644 --- a/cli/overview.mdx +++ b/cli/overview.mdx @@ -54,7 +54,7 @@ Lastly, you deploy your Checks and related alert channels to Checkly, so we run npx checkly deploy ``` -You just created your entire synthetic monitoring setup with API and Playwright-based Browser Checks from your code base! +You just created your entire synthetic monitoring setup with API and Playwright-based Browser checks from your code base! Open up [your Checkly dashboard](https://app.checklyhq.com) and you should see your check, ready to start monitoring around the clock. For a custom installation check out [our installation docs](/cli/installation/). @@ -62,7 +62,7 @@ For a custom installation check out [our installation docs](/cli/installation/). ## Using Agents, AI IDEs and Copilots Checkly is designed to work with Agents, AI IDEs, and Copilots. You can use your preferred provider to generate code for API -Checks, Browser Checks and all other constructs. +checks, Browser checks and all other constructs. diff --git a/communicate/alerts/channels.mdx b/communicate/alerts/channels.mdx index 2a53e247e..415a33cbe 100644 --- a/communicate/alerts/channels.mdx +++ b/communicate/alerts/channels.mdx @@ -1,5 +1,5 @@ --- -title: 'Alert Channels' +title: 'Alert channels' description: 'Configure notification channels to receive alerts when checks fail, degrade, or recover. Choose from email, Slack, webhooks, PagerDuty, SMS, and custom integrations.' sidebarTitle: 'Channels' canonical: 'https://www.checklyhq.com/docs/communicate/alerts/channels/' @@ -9,7 +9,7 @@ import AlertChannelSecrets from '/snippets/alert-channel-secrets-callout.mdx'; Alert channels determine **how** alert notifications reach your team when checks fail, degrade, or recover. Checkly supports a wide range of notification methods to fit your team's communication preferences and operational workflows. -## Available Alert Channels +## Available alert channels ### Communication Platforms - [Email](/integrations/alerts/email) @@ -35,7 +35,7 @@ Alert channels determine **how** alert notifications reach your team when checks ### Custom Integrations - [Webhooks](/integrations/alerts/webhooks) -## Managing Alert Channels +## Managing alert channels ### Channel Configuration Overview @@ -44,7 +44,7 @@ Configure channels with flexible subscription and filtering options: ![Alert channels management interface](/images/docs/images/alerting/alert-channels.png) - + Choose your notification method and provide connection details diff --git a/communicate/alerts/notification-log.mdx b/communicate/alerts/notification-log.mdx index 4651fe976..2c6909043 100644 --- a/communicate/alerts/notification-log.mdx +++ b/communicate/alerts/notification-log.mdx @@ -19,9 +19,9 @@ Here's an example: In the above example, we see: 1. SMS and Email were correctly delivered. -2. The OpsGenie notification failed though. The notification result shows we got a `422` status code back and the error +2. The Opsgenie notification failed though. The notification result shows we got a `422` status code back and the error message states our API key was invalid. -3. We also see the configuration used to instrument our call to the OpsGenie API. +3. We also see the configuration used to instrument our call to the Opsgenie API. 4. We see some extra meta data about the notification: What channel was used, what check triggered the alert, when it was sent etc. diff --git a/communicate/alerts/overview.mdx b/communicate/alerts/overview.mdx index 8df725c7e..9737c03a9 100644 --- a/communicate/alerts/overview.mdx +++ b/communicate/alerts/overview.mdx @@ -42,7 +42,7 @@ You can select whether group settings will override individual check settings fo ![alert settings check / threshold alerting](/images/docs/images/alerting/alert-settings-check.png) -## Alert Channels +## Alert channels When adding an alert channel, you can select which checks to subscribe to the channel. This way you can create specific routings for specific checks. diff --git a/communicate/alerts/ssl-expiration.mdx b/communicate/alerts/ssl-expiration.mdx index 9e7b7fcf4..d726a4332 100644 --- a/communicate/alerts/ssl-expiration.mdx +++ b/communicate/alerts/ssl-expiration.mdx @@ -6,10 +6,10 @@ canonical: 'https://www.checklyhq.com/docs/communicate/alerts/ssl-expiration/' --- An expired SSL certificate can cause havoc to sites and APIs. Checkly performs an hourly check on your certificate and can -alert you up to 30 days before your certificate expires. All alert channels (e-mail, SMS, OpsGenie, Webhook etc.) can be used for this alert. +alert you up to 30 days before your certificate expires. All alert channels (e-mail, SMS, Opsgenie, Webhook etc.) can be used for this alert. Simply create or pick an existing alert channel that your check subscribes to and enable *SSL certificate expiration* and -set the day threshold to your preference. If you don't have your alert channels set up yet, see [Alert Channels](/communicate/alerts/channels). +set the day threshold to your preference. If you don't have your alert channels set up yet, see [alert channels](/communicate/alerts/channels). ![Example alert channel form](/images/docs/images/alerting/ssl_check_example.png) @@ -31,12 +31,12 @@ SSL monitoring cannot parse the domain from a URL like `{{BASE_URL}}/test-endpoi ### Getting `Error: unable to verify the first certificate` If prompted with this error, the usual cause is the certificate chain of the given website being incomplete. This will -not happen with a browser check, because the browser will complete the certificate chain on its own. When running an API check, +not happen with a Browser check, because the browser will complete the certificate chain on its own. When running an API check, though, no browser is involved - therefore the error takes place. You can use an online SSL checker (e.g.: [SSL Shopper](https://www.sslshopper.com/ssl-checker.html)) to help you diagnose issues with your certificate. ## Browser checks -Since browser checks can connect to multiple domains, you need to set the SSL certificate domain to receive certificate alerts for them. +Since Browser checks can connect to multiple domains, you need to set the SSL certificate domain to receive certificate alerts for them. When you change this setting or update your SSL cert, allow up to an hour for the SSL expiration date to update on Checkly’s end. diff --git a/communicate/dashboards/configuration.mdx b/communicate/dashboards/configuration.mdx index e86796938..1fd008f04 100644 --- a/communicate/dashboards/configuration.mdx +++ b/communicate/dashboards/configuration.mdx @@ -1,5 +1,5 @@ --- -title: 'Dashboard Configuration' +title: 'Dashboard configuration' description: "Add checks to your dashboard, control who has access, and customize your dashboard's look and feel." sidebarTitle: 'Configuration' canonical: 'https://www.checklyhq.com/docs/communicate/dashboards/configuration/' @@ -18,7 +18,7 @@ canonical: 'https://www.checklyhq.com/docs/communicate/dashboards/configuration/ -## Setting Up Your Dashboard +## Setting up your dashboard @@ -26,7 +26,7 @@ Add relevant tags to all the checks and monitors that you'd like to display on y - + Create a new dashboard and configure basic settings. @@ -146,7 +146,7 @@ To enable authentication on a dashboard: Be careful, **this is the only time you will see this password in plaintext**. We do not store the password in plaintext, so if it is ever lost, you will need to regenerate a new one and inform any users of the new credentials. -### Accessing Private Dashboards +### Accessing private dashboards After enabling password protection for your dashboard, you can continue to visit it via any custom domain you may have enabled, as well as the default `https://[dashboardId].checkly-dashboards.com` domain. The password authentication will work via both channels. @@ -154,7 +154,7 @@ After enabling password protection for your dashboard, you can continue to visit Checkly account login is only available to Enterprise customers. -If visiting via the `https://[dashboardId].checkly-dashboards.com` domain, you can also select "Login with Checkly" and sign in with your existing Checkly account via any of the supported methods (i.e. Google, Github, Username and Password). This is an Enterprise-only feature. +If visiting via the `https://[dashboardId].checkly-dashboards.com` domain, you can also select "Login with Checkly" and sign in with your existing Checkly account via any of the supported methods (i.e. Google, GitHub, Username and Password). This is an Enterprise-only feature. ## Look and Feel diff --git a/communicate/dashboards/custom-css.mdx b/communicate/dashboards/custom-css.mdx index 609429bad..bbab25b41 100644 --- a/communicate/dashboards/custom-css.mdx +++ b/communicate/dashboards/custom-css.mdx @@ -1,5 +1,5 @@ --- -title: 'Customizing Your Dashboard with CSS' +title: 'Customizing your dashboard with CSS' description: "Match a Checkly dashboard to your company branding with custom CSS rules, edited directly in the Look & Feel section of the dashboard settings." sidebarTitle: 'Custom CSS' canonical: 'https://www.checklyhq.com/docs/communicate/dashboards/custom-css/' diff --git a/communicate/dashboards/overview.mdx b/communicate/dashboards/overview.mdx index 6fbd6fd05..3de998dbb 100644 --- a/communicate/dashboards/overview.mdx +++ b/communicate/dashboards/overview.mdx @@ -1,5 +1,5 @@ --- -title: 'Dashboards Overview' +title: 'Dashboards overview' description: 'Use dashboards to instantly communicate the health and performance of your checks.' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/communicate/dashboards/overview/' diff --git a/communicate/maintenance-windows/overview.mdx b/communicate/maintenance-windows/overview.mdx index 4bc26814a..c79d71d29 100644 --- a/communicate/maintenance-windows/overview.mdx +++ b/communicate/maintenance-windows/overview.mdx @@ -1,7 +1,7 @@ --- -title: 'Maintenance Windows' +title: 'Maintenance windows' description: 'Schedule planned maintenance periods to prevent false alerts and control check behavior during downtime.' -sidebarTitle: 'Maintenance Windows' +sidebarTitle: 'Maintenance windows' canonical: 'https://www.checklyhq.com/docs/communicate/maintenance-windows/overview/' --- diff --git a/communicate/overview.mdx b/communicate/overview.mdx index 408a0c03b..3cbcbd266 100644 --- a/communicate/overview.mdx +++ b/communicate/overview.mdx @@ -12,7 +12,7 @@ canonical: 'https://www.checklyhq.com/docs/communicate/overview/' Receive instant notifications when issues are detected across multiple channels - + Keep users informed with public status pages and incident communication @@ -20,7 +20,7 @@ Keep users informed with public status pages and incident communication Create custom views of your monitoring data for teams and stakeholders - + Schedule and communicate planned maintenance to reduce alert noise @@ -28,34 +28,34 @@ Schedule and communicate planned maintenance to reduce alert noise - **Multi-Channel Alerting** — Send notifications through email, SMS, Slack, webhooks, and more to ensure critical issues reach the right people. - **Transparent Status Communication** — Build trust with users through branded status pages that provide real-time system status and incident updates. -- **Customizable Dashboards** — Create tailored views of monitoring data that match your team's workflow and stakeholder needs. +- **Customizable dashboards** — Create tailored views of monitoring data that match your team's workflow and stakeholder needs. - **Intelligent Alert Management** — Reduce alert fatigue with escalation policies, maintenance windows, and smart notification routing. ## How It Works - + Set up notification channels for your team: - Add email, SMS, and phone call recipients - Connect Slack, Microsoft Teams, and other integrations - Configure webhooks for custom notification systems - + Build public-facing status communication: - Design branded status pages for your services - Configure automatic status updates from monitoring - Set up subscriber notifications for incidents - + Create visibility for stakeholders: - Design dashboards for different audiences - Configure custom domains and branding - Share monitoring insights with teams and customers - + Plan and communicate scheduled maintenance: - Schedule maintenance windows to suppress alerts - Automatically update status pages during maintenance @@ -72,15 +72,15 @@ Ready to start communicating monitoring insights? Choose the approach that best Begin with instant notifications for critical issues - + Build transparency with public status communication - + Create custom views for monitoring data - + Plan and communicate scheduled maintenance diff --git a/communicate/status-pages/creating-a-status-page.mdx b/communicate/status-pages/creating-a-status-page.mdx index 45aecfa0f..4c427a527 100644 --- a/communicate/status-pages/creating-a-status-page.mdx +++ b/communicate/status-pages/creating-a-status-page.mdx @@ -1,7 +1,7 @@ --- -title: 'Creating a Status Page' -description: 'Create a Status Page.' -sidebarTitle: 'Creating a Status Page' +title: 'Creating a status page' +description: 'Create a status page.' +sidebarTitle: 'Creating a status page' canonical: 'https://www.checklyhq.com/docs/communicate/status-pages/creating-a-status-page/' --- diff --git a/communicate/status-pages/custom-domain.mdx b/communicate/status-pages/custom-domain.mdx index 7456b7797..d8a15f21b 100644 --- a/communicate/status-pages/custom-domain.mdx +++ b/communicate/status-pages/custom-domain.mdx @@ -13,7 +13,7 @@ You can host your status page on your own domain. To set it up, add the domain i - + ![Custom domain configuration](/images/docs/images/status-pages/status-pages-custom-domain-1.png) @@ -30,10 +30,10 @@ You can host your status page on your own domain. To set it up, add the domain i After you've added your custom domain and saved the page, one or more TXT records will be displayed depending on the domain you're using. ![Example custom domain TXT configuration](/images/docs/images/status-pages/status-pages-custom-domain-3.png) -Update your DNS settings to match the TXT record(s) displayed on your Status Page to prove the ownership of the domain. +Update your DNS settings to match the TXT record(s) displayed on your status page to prove the ownership of the domain. -Search engines require this verification to index and list your Status Page. +Search engines require this verification to index and list your status page. diff --git a/communicate/status-pages/customization.mdx b/communicate/status-pages/customization.mdx index 4066169c0..8965c5bee 100644 --- a/communicate/status-pages/customization.mdx +++ b/communicate/status-pages/customization.mdx @@ -1,5 +1,5 @@ --- -title: "Status Page Customization" +title: "Status page customization" description: "Change the logo, favicon, theme, and colors of your status page to match your brand." sidebarTitle: "Customization" canonical: 'https://www.checklyhq.com/docs/communicate/status-pages/customization/' diff --git a/communicate/status-pages/incidents.mdx b/communicate/status-pages/incidents.mdx index 023c0b23f..aa82e1603 100644 --- a/communicate/status-pages/incidents.mdx +++ b/communicate/status-pages/incidents.mdx @@ -7,19 +7,19 @@ canonical: 'https://www.checklyhq.com/docs/communicate/status-pages/incidents/' Incidents communicate downtime on one or more components. You can open incidents manually as part of your incident management process, or automatically with [automation rules](#incident-automation). -When an incident is posted, a notification will be sent to all users subscribed to the Status Page, unless you opt out of notifications when creating the incident update. +When an incident is posted, a notification will be sent to all users subscribed to the status page, unless you opt out of notifications when creating the incident update. ## Creating an incident -Create an incident when you want to communicate downtime or known issues to users via your Status Page. +Create an incident when you want to communicate downtime or known issues to users via your status page. -1. Click ‘Status pages’ in the sidebar and open your Status Page. +1. Click ‘Status pages’ in the sidebar and open your status page. 2. Click ‘Add incident’ at the top right. 3. Enter the name of the incident. 4. Select which components are impacted, and the [impact](/communicate/status-pages/overview#component-status-and-impacts) each one gets: under maintenance, degraded performance, partial outage, or major outage. 5. Write the initial incident update message, and set the status of the incident. 6. If you want to backfill the incident, select `Use custom date`. See [Backfilling incidents for more information](/communicate/status-pages/incidents#backfilling-an-incident). -7. Select if you want to notify subscribers of your Status Page about the incident. +7. Select if you want to notify subscribers of your status page about the incident. 8. Click ‘Create incident’ The incident now appears on your status page, and the impacted components show their new status. If you selected the option to notify subscribers, they receive the update message by email. @@ -52,7 +52,7 @@ You can correct the record after the fact by editing a component's impact timeli ## Incident notifications -Whenever you post an incident update, Checkly can automatically send email notifications to users subscribed to your Status Page. +Whenever you post an incident update, Checkly can automatically send email notifications to users subscribed to your status page. Emails are sent out only when an update is first posted. Notifications are not sent again if the incident update is edited. @@ -65,7 +65,7 @@ Incident notifications contain the incident name and status, and the impacted co ## Subscribing to incident notifications -Subscribing to incident notifications is done on your Status Page. To subscribe, a user needs to enter a valid email address. A verification email will be sent to the registered email, and the user will be ready to receive incident notifications after confirming the subscription. +Subscribing to incident notifications is done on your status page. To subscribe, a user needs to enter a valid email address. A verification email will be sent to the registered email, and the user will be ready to receive incident notifications after confirming the subscription. ## Incident automation @@ -77,7 +77,7 @@ Automation rules open incidents automatically when checks fail. A rule matches c To create an automation rule: -1. Open your Status Page and go to the ‘Automation’ tab. +1. Open your status page and go to the ‘Automation’ tab. 2. Click ‘Add rule’ and name the rule. 3. Add one or more tags. Any check or group carrying one of these tags can trigger the rule. 4. Select the components the incident should impact, and the impact each one gets. diff --git a/communicate/status-pages/maintenance-windows.mdx b/communicate/status-pages/maintenance-windows.mdx index 5f478622c..34a1855a4 100644 --- a/communicate/status-pages/maintenance-windows.mdx +++ b/communicate/status-pages/maintenance-windows.mdx @@ -1,5 +1,5 @@ --- -title: 'Status Page Maintenance' +title: 'Status page maintenance' description: 'Show planned maintenance windows on your status page so visitors and subscribers know what to expect, with automatic updates and subscriber notifications.' sidebarTitle: 'Maintenance' canonical: 'https://www.checklyhq.com/docs/communicate/status-pages/maintenance-windows/' @@ -26,7 +26,7 @@ You configure status page visibility from the maintenance window itself. Go to the **Maintenance Windows** page (the wrench icon in the sidebar) and create a window, or open an existing one. Set its schedule and [check behavior](/communicate/maintenance-windows/overview#check-behavior) as usual. - + In the **Status page visibility** section, turn on the toggle. This is the master switch for everything below it. diff --git a/communicate/status-pages/overview.mdx b/communicate/status-pages/overview.mdx index 9a9a524f6..124ffe076 100644 --- a/communicate/status-pages/overview.mdx +++ b/communicate/status-pages/overview.mdx @@ -1,5 +1,5 @@ --- -title: 'Status Pages Overview' +title: 'Status pages overview' description: 'Create status pages to communicate service health, incidents, and maintenance to your customers, with automated incidents and custom branding.' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/communicate/status-pages/overview/' diff --git a/communicate/status-pages/password-protection.mdx b/communicate/status-pages/password-protection.mdx index 87c20ae4c..f15e311e1 100644 --- a/communicate/status-pages/password-protection.mdx +++ b/communicate/status-pages/password-protection.mdx @@ -13,7 +13,7 @@ Password protection makes your status page private. Visitors must authenticate b ## Enabling password protection -1. Open your status page from the [Status Pages overview](https://app.checklyhq.com/status-pages). +1. Open your status page from the [Status pages overview](https://app.checklyhq.com/status-pages). 2. In the status page settings, enable the **Private** toggle. 3. A password is automatically generated. Copy it and store it somewhere safe — it is only displayed once. 4. Save your status page. diff --git a/communicate/status-pages/subscriber-notifications.mdx b/communicate/status-pages/subscriber-notifications.mdx index c9b809c75..ffaa7e9d5 100644 --- a/communicate/status-pages/subscriber-notifications.mdx +++ b/communicate/status-pages/subscriber-notifications.mdx @@ -6,11 +6,11 @@ canonical: 'https://www.checklyhq.com/docs/communicate/status-pages/subscriber-n --- ## Subscribing to incident updates -Users can choose to be notified about any incident impacting your components by subscribing through your Status Page. +Users can choose to be notified about any incident impacting your components by subscribing through your status page. -To subscribe to notifications, users click the "Get updates" button at the top of the Status Page, and then fill out a form to enter their email address. +To subscribe to notifications, users click the "Get updates" button at the top of the status page, and then fill out a form to enter their email address. diff --git a/communicate/status-pages/v2-deprecated.mdx b/communicate/status-pages/v2-deprecated.mdx index 6c5c1febd..ecfea4009 100644 --- a/communicate/status-pages/v2-deprecated.mdx +++ b/communicate/status-pages/v2-deprecated.mdx @@ -1,5 +1,5 @@ --- -title: 'Status Pages v2 (deprecated)' +title: 'Status pages v2 (deprecated)' description: 'Documentation for the deprecated cards-and-services status pages.' sidebarTitle: 'v2 (deprecated)' canonical: 'https://www.checklyhq.com/docs/communicate/status-pages/v2-deprecated/' diff --git a/comparisons/frameworks/moving-from-puppeteer-to-playwright.mdx b/comparisons/frameworks/moving-from-puppeteer-to-playwright.mdx index 7141b9275..199b345dd 100644 --- a/comparisons/frameworks/moving-from-puppeteer-to-playwright.mdx +++ b/comparisons/frameworks/moving-from-puppeteer-to-playwright.mdx @@ -290,9 +290,9 @@ You can use the [Playwright Test Generator](https://playwright.dev/docs/codegen) ![page being inspected with playwright codegen](/images/guides/images/guides-migration-playwright-codegen.png "Script recording with Playwright Inspector") -## Switching to Playwright for richer browser check results +## Switching to Playwright for richer Browser check results -Checkly browser checks run on Playwright, and their results come with [tracing and Web Vitals](/detect/synthetic-monitoring/browser-checks/performance-metrics) and make it easier to isolate the root cause of a failed check and remediate faster. +Checkly Browser checks run on Playwright, and their results come with [tracing and Web Vitals](/detect/synthetic-monitoring/browser-checks/performance-metrics) and make it easier to isolate the root cause of a failed check and remediate faster. ![performance and error tracing check results on checkly](/images/docs/images/browser-checks/tracing_web_vitals.png "A browser check result with performance and error tracing") @@ -312,7 +312,7 @@ This reveals additional information about the check execution, including: - Learn end-to-end monitoring with puppeteer and playwright to test key website flows. + Learn end-to-end monitoring with puppeteer and Playwright to test key website flows. diff --git a/comparisons/frameworks/playwright-vs-cypress.mdx b/comparisons/frameworks/playwright-vs-cypress.mdx index af18ba620..6328a67d4 100644 --- a/comparisons/frameworks/playwright-vs-cypress.mdx +++ b/comparisons/frameworks/playwright-vs-cypress.mdx @@ -41,7 +41,7 @@ Playwright is a tool focused on developer productivity with more robust built-in With Cypress, E2E went from the painful world of hard-coded waits and heavy-handed POM approaches to built in actionability and visibility checks with a focus on community building and developer experience. What we’ve seen over the course of the last five years or so is a cultural shift in the testing world from a heavy reliance on Manual QA and non-developer owned testing responsibilities to testing as a more fully incorporated practice. We’ve shifted left. -We’ve also seen testing become the battleground of where your developer velocity goes to die. Since the inception of playwright more and more teams contain dedicated roles for platform engineering, with a focus on making development, testing, and the [deployment process](/concepts/monitoring-as-code) easier for everyone. +We’ve also seen testing become the battleground of where your developer velocity goes to die. Since the inception of Playwright more and more teams contain dedicated roles for platform engineering, with a focus on making development, testing, and the [deployment process](/concepts/monitoring-as-code) easier for everyone. Titles have changed, entire departments have been lost to restructures, responsibilities have adjusted and solutions that were groundbreaking less than a decade ago are now no longer cutting edge. diff --git a/comparisons/status-pages/overview.mdx b/comparisons/status-pages/overview.mdx index 63f27dc7a..7ce61e0ea 100644 --- a/comparisons/status-pages/overview.mdx +++ b/comparisons/status-pages/overview.mdx @@ -1,10 +1,10 @@ --- -title: "Status Pages Overview" +title: "Status pages overview" description: "Compare Checkly status pages with other status page solutions" canonical: 'https://www.checklyhq.com/docs/comparisons/status-pages/overview/' --- -# Status Pages Overview +# Status pages overview This section provides detailed comparisons between Checkly's status page functionality and dedicated status page providers. Learn how to choose the right status page solution for your needs. @@ -23,7 +23,7 @@ Coming soon - detailed comparisons with popular status page services including: - Incident.io - Instatus -## Why Compare Status Pages? +## Why compare status pages? Understanding different status page solutions helps you: diff --git a/concepts/checks.mdx b/concepts/checks.mdx index 055315623..b1b772eb2 100644 --- a/concepts/checks.mdx +++ b/concepts/checks.mdx @@ -15,8 +15,8 @@ This lets you catch issues early, maintain confidence in your deployments, and e Checkly's flexible offering includes several types of Checks, each designed for different levels of complexity and testing scenarios: - -Monitor HTTP/HTTPS endpoints for availability and performance. URL Monitors check if your websites and APIs are responding correctly by making HTTP requests and validating the response. + +Monitor HTTP/HTTPS endpoints for availability and performance. URL monitors check if your websites and APIs are responding correctly by making HTTP requests and validating the response. **Perfect for:** - Website uptime monitoring @@ -24,8 +24,8 @@ Monitor HTTP/HTTPS endpoints for availability and performance. URL Monitors chec - Basic performance tracking - SSL certificate monitoring - -Verify connectivity to any TCP service by establishing connections to specific hosts and ports. TCP Monitors test the availability of non-HTTP services and infrastructure components. + +Verify connectivity to any TCP service by establishing connections to specific hosts and ports. TCP monitors test the availability of non-HTTP services and infrastructure components. **Perfect for:** - Database connectivity @@ -33,8 +33,8 @@ Verify connectivity to any TCP service by establishing connections to specific h - Network service availability - Port accessibility testing - -Monitor scheduled processes, cron jobs, and batch operations that should "check in" at regular intervals. Instead of actively testing your service, Heartbeat Monitors wait to receive a signal from your system. + +Monitor scheduled processes, cron jobs, and batch operations that should "check in" at regular intervals. Instead of actively testing your service, Heartbeat monitors wait to receive a signal from your system. **Perfect for:** - Backup job verification @@ -42,8 +42,8 @@ Monitor scheduled processes, cron jobs, and batch operations that should "check - Batch process oversight - Data pipeline health - -Verify DNS resolution by querying domain records and validating responses. DNS Monitors help ensure your domains resolve correctly and detect issues such as misconfigurations, propagation delays, or resolver failures. + +Verify DNS resolution by querying domain records and validating responses. DNS monitors help ensure your domains resolve correctly and detect issues such as misconfigurations, propagation delays, or resolver failures. **Perfect for:** - Domain resolution monitoring @@ -51,7 +51,7 @@ Verify DNS resolution by querying domain records and validating responses. DNS M - Detecting propagation issues - Troubleshooting resolver performance - + Ping hosts to measure network reachability and latency. ICMP monitors help you verify that a server or device is online and understand network-level performance. **Perfect for:** @@ -61,7 +61,7 @@ Ping hosts to measure network reachability and latency. ICMP monitors help you v - + Advanced API testing that goes beyond uptime monitoring. Use setup and teardown scripts, complex assertions, and custom request handling. Validate that your backend services respond correctly, perform within acceptable timeframes, and return the right data structures. **Perfect for:** @@ -73,7 +73,7 @@ Advanced API testing that goes beyond uptime monitoring. Use setup and teardown - Integration testing between services - + Write Node.js scripts that run multiple API requests in sequence with arbitrary code between requests. Perfect for testing complex workflows involving authentication, data manipulation, and multi-step processes that span multiple endpoints. **Perfect for:** @@ -84,8 +84,8 @@ Write Node.js scripts that run multiple API requests in sequence with arbitrary - Workflow orchestration testing - Cross-service data validation - -Simulate real user interactions in a headless browser using TypeScript/JavaScript with @playwright/test. Navigate, screenshot, and assert your key webapp flows. Browser Checks can handle complex scenarios that simple uptime monitoring cannot. + +Simulate real user interactions in a headless browser using TypeScript/JavaScript with @playwright/test. Navigate, screenshot, and assert your key webapp flows. Browser checks can handle complex scenarios that simple uptime monitoring cannot. **Perfect for:** - Complete user journey testing diff --git a/concepts/locations.mdx b/concepts/locations.mdx index bc41b2897..1c8eaba15 100644 --- a/concepts/locations.mdx +++ b/concepts/locations.mdx @@ -1,6 +1,6 @@ --- title: 'Locations' -description: 'Learn about Public and Private locations using Checkly' +description: 'Learn about public and private locations using Checkly' sidebarTitle: 'Locations' canonical: 'https://www.checklyhq.com/docs/concepts/locations/' --- @@ -34,9 +34,9 @@ Current Locations in Checkly are: *Checkly hosted location. All other locations run on AWS. Please note that the hosting provider for a location may change over time as we scale and optimize our infrastructure. -## Private Locations +## Private locations -**Private Locations** extend this concept to your own infrastructure. A **Private Location** is a monitoring location that you manage by simply deploying a lightweight Checkly Agent. Running a check from a **Private Location** allows you to monitor internal systems and test the performance and reliability of applications and APIs that are only accessible from within your network. +**Private locations** extend this concept to your own infrastructure. A **private location** is a monitoring location that you manage by simply deploying a lightweight Checkly Agent. Running a check from a **private location** allows you to monitor internal systems and test the performance and reliability of applications and APIs that are only accessible from within your network. > Learn more about [private locations](/platform/private-locations/overview) to monitor your private and segregated applications and APIs. ## Locations as User Experience Proxies diff --git a/concepts/metrics.mdx b/concepts/metrics.mdx index 02a951d75..fdf5b74dc 100644 --- a/concepts/metrics.mdx +++ b/concepts/metrics.mdx @@ -256,7 +256,7 @@ Core Web Vitals are a set of metrics defined by Google that measure real-world u ## Browser-Specific Performance Metrics -Additional performance metrics specific to browser and multistep checks that provide insights into page loading and user experience. +Additional performance metrics specific to Browser and Multistep checks that provide insights into page loading and user experience. ### Average Page Load Time @@ -275,7 +275,7 @@ Additional performance metrics specific to browser and multistep checks that pro ### Average Script Duration -**What it measures:** The total time taken to execute all JavaScript code during a browser check, including user-defined scripts and page interactions. +**What it measures:** The total time taken to execute all JavaScript code during a Browser check, including user-defined scripts and page interactions. **Unit:** Seconds **Precision:** 2 decimal places diff --git a/constructs/alert-channel.mdx b/constructs/alert-channel.mdx index 1a1ae890e..cfafcbae0 100644 --- a/constructs/alert-channel.mdx +++ b/constructs/alert-channel.mdx @@ -1,5 +1,5 @@ --- -title: 'Alert Channel Overview' +title: 'Alert channel overview' description: 'Learn how to configure alert channels with the Checkly CLI.' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/constructs/alert-channel/' diff --git a/constructs/api-check.mdx b/constructs/api-check.mdx index 18ac4fa21..beb95dd76 100644 --- a/constructs/api-check.mdx +++ b/constructs/api-check.mdx @@ -1,20 +1,20 @@ --- -title: 'API Check Construct' -description: 'Learn how to configure API Checks with the Checkly CLI.' -sidebarTitle: 'API Check' +title: 'API check construct' +description: 'Learn how to configure API checks with the Checkly CLI.' +sidebarTitle: 'API check' canonical: 'https://www.checklyhq.com/docs/constructs/api-check/' --- import CheckIntent from '/snippets/check-intent.mdx'; -Learn more about API Checks in [the API Checks overview](/detect/synthetic-monitoring/api-checks/overview). +Learn more about API checks in [the API checks overview](/detect/synthetic-monitoring/api-checks/overview). -Use API Checks to monitor HTTP endpoints, REST APIs, GraphQL APIs, and other HTTP-based services. The examples below show how to configure monitoring for different types of API endpoints. +Use API checks to monitor HTTP endpoints, REST APIs, GraphQL APIs, and other HTTP-based services. The examples below show how to configure monitoring for different types of API endpoints. -Before creating API Checks, ensure you have: +Before creating API checks, ensure you have: - An initialized Checkly CLI project - URLs or HTTP endpoints you want to monitor @@ -75,10 +75,10 @@ new ApiCheck("advanced-api-check", { ## Configuration -The API Check configuration consists of specific API Check options and inherited general check options. +The API check configuration consists of specific API check options and inherited general check options. - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| @@ -86,8 +86,8 @@ The API Check configuration consists of specific API Check options and inherited | `degradedResponseTime` | `number` | ❌ | `10000` | Response time threshold in milliseconds for degraded status | | `maxResponseTime` | `number` | ❌ | `20000` | Maximum response time in milliseconds before marking as failed | | `shouldFail` | `boolean` | ❌ | `false` | Whether a failure should count as a pass (status 400+ reported as passed) | -| `setupScript` | `object` | ❌ | - | Script to run before the API Check execution | -| `tearDownScript` | `object` | ❌ | - | Script to run after the API Check execution | +| `setupScript` | `object` | ❌ | - | Script to run before the API check execution | +| `tearDownScript` | `object` | ❌ | - | Script to run after the API check execution | @@ -105,7 +105,7 @@ The API Check configuration consists of specific API Check options and inherited | `group` | `CheckGroup` | ❌ | - | The CheckGroup this check belongs to | | `locations` | `string[]` | ❌ | `[]` | Array of public location codes | | `muted` | `boolean` | ❌ | `false` | Whether alert notifications are muted | -| `privateLocations` | `string[]` | ❌ | `[]` | Array of Private Location slugs | +| `privateLocations` | `string[]` | ❌ | `[]` | Array of private location slugs | | `retryStrategy` | `RetryStrategy` | ❌ | [`singleRetry()`](/constructs/retry-strategy#default-retry-strategy) | Strategy for configuring retries | | `runtimeId` | `string` | ❌ | - | The ID of the runtime to use | | `runParallel` | `boolean` | ❌ | `false` | Run checks in parallel or round-robin | @@ -119,7 +119,7 @@ The API Check configuration consists of specific API Check options and inherited ### `ApiCheck` Options -The HTTP request configuration that defines the API endpoint to monitor. This is the core component of any API Check. +The HTTP request configuration that defines the API endpoint to monitor. This is the core component of any API check. **Usage:** @@ -318,7 +318,7 @@ new ApiCheck("rate-limit-test", { -Script to run before the API Check execution. Useful for setting up test data or authentication tokens. +Script to run before the API check execution. Useful for setting up test data or authentication tokens. **Usage:** @@ -371,7 +371,7 @@ You must provide either `entrypoint` or `content`, but not both. -Script to run after the API Check execution. Useful for cleaning up test data or resources. +Script to run after the API check execution. Useful for cleaning up test data or resources. **Usage:** diff --git a/constructs/browser-check.mdx b/constructs/browser-check.mdx index 4af95d93e..8aa7af1aa 100644 --- a/constructs/browser-check.mdx +++ b/constructs/browser-check.mdx @@ -1,20 +1,20 @@ --- -title: 'Browser Check Construct' -description: 'Learn how to configure browser checks with the Checkly CLI.' -sidebarTitle: 'Browser Check' +title: 'Browser check construct' +description: 'Learn how to configure Browser checks with the Checkly CLI.' +sidebarTitle: 'Browser check' canonical: 'https://www.checklyhq.com/docs/constructs/browser-check/' --- import CheckIntent from '/snippets/check-intent.mdx'; -Learn more about Browser Checks in [the Browser Checks overview](/detect/synthetic-monitoring/browser-checks/overview). +Learn more about Browser checks in [the Browser checks overview](/detect/synthetic-monitoring/browser-checks/overview). -Use Browser Checks to run end-to-end tests with Playwright. The examples below show how to configure browser checks for different testing scenarios. +Use Browser checks to run end-to-end tests with Playwright. The examples below show how to configure Browser checks for different testing scenarios. -Before creating Browser Checks, ensure you have: +Before creating Browser checks, ensure you have: - An initialized Checkly CLI project - A public website you want to monitor @@ -67,10 +67,10 @@ new BrowserCheck("advanced-browser-check", { ## Configuration -The Browser Check configuration consists of specific Browser Check options and inherited general check options. +The Browser check configuration consists of specific Browser check options and inherited general check options. - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| @@ -93,7 +93,7 @@ The Browser Check configuration consists of specific Browser Check options and i | `group` | `CheckGroup` | ❌ | - | The CheckGroup this check belongs to | | `locations` | `string[]` | ❌ | `[]` | Public locations for this monitor/check | | `muted` | `boolean` | ❌ | `false` | Whether alert notifications are muted | -| `privateLocations` | `string[]` | ❌ | `[]` | Private Location slugs | +| `privateLocations` | `string[]` | ❌ | `[]` | Private location slugs | | `retryStrategy` | `RetryStrategy` | ❌ | [`singleRetry()`](/constructs/retry-strategy#default-retry-strategy) | Strategy for configured retries | | `runtimeId` | `string` | ❌ | - | The ID of the runtime to use | | `runParallel` | `boolean` | ❌ | `false` | Whether to run checks in parallel across locations | @@ -104,10 +104,10 @@ The Browser Check configuration consists of specific Browser Check options and i -### Browser Check Options +### Browser check options -The Playwright test code that defines how to execute your end-to-end browser monitor. This is the core component of any browser check. +The Playwright test code that defines how to execute your end-to-end browser monitor. This is the core component of any Browser check. **Usage:** @@ -194,7 +194,7 @@ new BrowserCheck("e2e-purchase", { ### General Check Options -Friendly name for your Browser Check that will be displayed in the Checkly dashboard and used in notifications. +Friendly name for your Browser check that will be displayed in the Checkly dashboard and used in notifications. **Usage:** @@ -208,7 +208,7 @@ new BrowserCheck("my-check", { -How often the Browser Check should run. Use the `Frequency` enum to set the check interval. +How often the Browser check should run. Use the `Frequency` enum to set the check interval. **Usage:** @@ -253,9 +253,9 @@ new BrowserCheck("standard-check", { -The Checkly runtime version used to execute the Browser Check. Runtimes are managed execution environments for Browser and Multistep Checks. They include fixed Checkly-provided dependencies, such as Playwright, browser binaries, and runtime libraries. +The Checkly runtime version used to execute the Browser check. Runtimes are managed execution environments for Browser and Multistep checks. They include fixed Checkly-provided dependencies, such as Playwright, browser binaries, and runtime libraries. -Use `runtimeId` for Browser Checks and Multistep Checks. For Playwright Check Suites, use [`engine`](/constructs/playwright-check#engine) instead to select the JavaScript engine version that runs your own Playwright project. +Use `runtimeId` for Browser checks and Multistep checks. For Playwright Check Suites, use [`engine`](/constructs/playwright-check#engine) instead to select the JavaScript engine version that runs your own Playwright project. **Usage:** @@ -272,7 +272,7 @@ new BrowserCheck("my-check", { -Array of public location codes where the Browser Check should run. Multiple locations provide geographic coverage and redundancy. +Array of public location codes where the Browser check should run. Multiple locations provide geographic coverage and redundancy. **Usage:** @@ -318,7 +318,7 @@ new BrowserCheck("europe-check", { -Whether the browser check is enabled and will run according to its schedule. +Whether the Browser check is enabled and will run according to its schedule. **Usage:** @@ -334,7 +334,7 @@ new BrowserCheck("my-check", { -Array of tags to organize and categorize your Browser Checks in the Checkly infrastructure. +Array of tags to organize and categorize your Browser checks in the Checkly infrastructure. **Usage:** diff --git a/constructs/check-group-v2.mdx b/constructs/check-group-v2.mdx index 9eb56e5f6..59c7fc57a 100644 --- a/constructs/check-group-v2.mdx +++ b/constructs/check-group-v2.mdx @@ -1,12 +1,12 @@ --- title: 'CheckGroupV2 Construct' description: 'Learn how to configure check groups with the Checkly CLI.' -sidebarTitle: 'Check Group V2' +sidebarTitle: 'Check group V2' canonical: 'https://www.checklyhq.com/docs/constructs/check-group-v2/' --- -Learn more about Check Groups in [the Groups overview](/platform/groups). +Learn more about check groups in [the Groups overview](/platform/groups). Use `CheckGroupV2` to organize your checks into logical groups. This provides better organization, shared configuration, and group-level controls for your monitoring setup. @@ -92,13 +92,13 @@ new ApiCheck("api-check-1", { | `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 | +| `privateLocations` | `string[]` | ❌ | - | Private location slugs | | `retryStrategy` | `RetryStrategy` | ❌ | - | Strategy for configured retries. Without one, each check uses its own. | | `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 | +| `browserChecks` | `object` | ❌ | - | Settings for Browser checks in the group | +| `multiStepChecks` | `object` | ❌ | - | Settings for Multistep checks in the group | If you want the group's alert settings to override check-level alert settings, you must set the [`alertEscalationPolicy`](/constructs/check-group-v2#param-alert-escalation-policy). Otherwise, the alert settings of individual checks will be used, even if `alertChannels` is defined in your group. @@ -153,7 +153,7 @@ const group = new CheckGroupV2("api-monitoring-group", { -How often to run checks within the group. Checks in your project that don't set their own frequency use this value. For Browser and Multistep Checks, the group's `browserChecks.frequency` or `multiStepChecks.frequency`, and then the same settings under `checks` in your project config, take precedence. It isn't stored on the group, so checks added to the group outside your project don't use it. +How often to run checks within the group. Checks in your project that don't set their own frequency use this value. For Browser and Multistep checks, the group's `browserChecks.frequency` or `multiStepChecks.frequency`, and then the same settings under `checks` in your project config, take precedence. It isn't stored on the group, so checks added to the group outside your project don't use it. **Usage:** @@ -168,7 +168,7 @@ const group = new CheckGroupV2('api-monitoring-group', { **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_3H`, `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. +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. @@ -188,7 +188,7 @@ const group = new CheckGroupV2("api-monitoring-group", { -Setting to automatically create and apply Browser Checks to a group. +Setting to automatically create and apply Browser checks to a group. **Usage:** @@ -206,7 +206,7 @@ const group = new CheckGroupV2("api-monitoring-group", { -Setting to automatically create and apply MultiStep Checks to a group. +Setting to automatically create and apply Multistep checks to a group. **Usage:** diff --git a/constructs/check-group.mdx b/constructs/check-group.mdx index 8dc2a81d4..fb7463c89 100644 --- a/constructs/check-group.mdx +++ b/constructs/check-group.mdx @@ -1,12 +1,12 @@ --- title: 'CheckGroup Construct' description: 'Learn how to configure check groups with the Checkly CLI.' -sidebarTitle: 'Check Group (deprecated)' +sidebarTitle: 'Check group (deprecated)' canonical: 'https://www.checklyhq.com/docs/constructs/check-group/' --- -Learn more about Check Groups in [the Groups overview](/platform/groups). +Learn more about check groups in [the Groups overview](/platform/groups). `CheckGroup` is deprecated. Please use `CheckGroupV2` instead. See [CheckGroupV2 documentation](/constructs/check-group-v2) for details. @@ -97,13 +97,13 @@ new ApiCheck("api-check-1", { | `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 | +| `privateLocations` | `string[]` | ❌ | - | Private location slugs | | `retryStrategy` | `RetryStrategy` | ❌ | [`singleRetry()`](/constructs/retry-strategy#default-retry-strategy) | 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 | +| `browserChecks` | `object` | ❌ | - | Settings for Browser checks in the group | +| `multistepChecks` | `object` | ❌ | - | Settings for Multistep checks in the group | ### Group Options @@ -169,7 +169,7 @@ const group = new CheckGroup("api-monitoring-group", { **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. +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. @@ -189,7 +189,7 @@ const group = new CheckGroup("api-monitoring-group", { -Setting to automatically create and apply Browser Checks to a group. +Setting to automatically create and apply Browser checks to a group. **Usage:** @@ -207,7 +207,7 @@ const group = new CheckGroup("api-monitoring-group", { -Setting to automatically create and apply MultiStep Checks to a group. +Setting to automatically create and apply Multistep checks to a group. **Usage:** diff --git a/constructs/dashboard.mdx b/constructs/dashboard.mdx index 2642f1bb6..e5e6e0ca5 100644 --- a/constructs/dashboard.mdx +++ b/constructs/dashboard.mdx @@ -6,7 +6,7 @@ canonical: 'https://www.checklyhq.com/docs/constructs/dashboard/' --- -Learn more about Dashboards in [the Dashboards overview](/communicate/dashboards/overview). +Learn more about dashboards in [the dashboards overview](/communicate/dashboards/overview). Use Dashboard to create public or private dashboards that display checks and their related metrics on a single page. Dashboards provide a centralized view of your monitoring data. @@ -253,7 +253,7 @@ You must provide either `entrypoint` or `content`, but not both. ``` - + ```ts new Dashboard("api-dashboard", { header: "API Endpoints Status", @@ -269,7 +269,7 @@ You must provide either `entrypoint` or `content`, but not both. ``` - + ```ts new Dashboard("us-east-dashboard", { header: "US East Region Status", @@ -285,7 +285,7 @@ You must provide either `entrypoint` or `content`, but not both. ``` - + ```ts new Dashboard("platform-team-dashboard", { header: "Platform Team Services", @@ -302,7 +302,7 @@ You must provide either `entrypoint` or `content`, but not both. ``` - + ```ts new Dashboard("branded-dashboard", { header: "ACME Corporation Status", diff --git a/constructs/dns-monitor.mdx b/constructs/dns-monitor.mdx index 375c7d56b..bb789cb85 100644 --- a/constructs/dns-monitor.mdx +++ b/constructs/dns-monitor.mdx @@ -1,7 +1,7 @@ --- title: 'DnsMonitor Construct' description: 'Learn how to configure DNS monitors with the Checkly CLI.' -sidebarTitle: 'DNS Monitor' +sidebarTitle: 'DNS monitor' canonical: 'https://www.checklyhq.com/docs/constructs/dns-monitor/' --- @@ -10,13 +10,13 @@ import CheckIntent from '/snippets/check-intent.mdx'; import GeneralMonitorOptionsTable from '/snippets/general-monitor-options-table.mdx'; -Learn more about DNS Monitors in [the DNS monitor overview](/detect/uptime-monitoring/dns-monitors/overview). +Learn more about DNS monitors in [the DNS monitor overview](/detect/uptime-monitoring/dns-monitors/overview). -Use DNS Monitors to verify that DNS records resolve correctly and to track lookup performance over time. +Use DNS monitors to verify that DNS records resolve correctly and to track lookup performance over time. -Before creating DNS Monitors, ensure you have: +Before creating DNS monitors, ensure you have: - An initialized Checkly CLI project - A domain or hostname you want to monitor @@ -79,10 +79,10 @@ new DnsMonitor("advanced-dns-monitor", { ## Configuration -A DNS Monitor has its own DNS-specific settings, plus the standard monitor options shared across all check types. +A DNS monitor has its own DNS-specific settings, plus the standard monitor options shared across all check types. - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| @@ -134,7 +134,7 @@ new DnsMonitor("dns-monitor", { -Response time threshold in milliseconds for marking the DNS Monitor as degraded (warning state). +Response time threshold in milliseconds for marking the DNS monitor as degraded (warning state). **Usage:** @@ -154,7 +154,7 @@ new DnsMonitor("dns-performance-tiers", { -Maximum response time in milliseconds before the DNS Monitor is marked as failed. +Maximum response time in milliseconds before the DNS monitor is marked as failed. **Usage:** @@ -210,7 +210,7 @@ Learn more in our docs on [Assertions](/detect/assertions). ### General Monitor Options -Friendly name for your DNS Monitor that will be displayed in the Checkly dashboard and used in notifications. +Friendly name for your DNS monitor that will be displayed in the Checkly dashboard and used in notifications. **Usage:** @@ -224,7 +224,7 @@ new DnsMonitor("my-monitor", { -How often the DNS Monitor should run. Use the `Frequency` enum to set the check interval. +How often the DNS monitor should run. Use the `Frequency` enum to set the check interval. **Usage:** @@ -239,7 +239,7 @@ new DnsMonitor("my-monitor", { -Array of [public location codes](/concepts/locations/#public-locations) where the DNS Monitor should run from. Multiple locations provide geographic coverage and help detect regional DNS issues. +Array of [public location codes](/concepts/locations/#public-locations) where the DNS monitor should run from. Multiple locations provide geographic coverage and help detect regional DNS issues. **Usage:** @@ -251,7 +251,7 @@ new DnsMonitor("global-dns-monitor", { -Whether the DNS Monitor is enabled and will run according to its schedule. +Whether the DNS monitor is enabled and will run according to its schedule. **Usage:** diff --git a/constructs/email-alert-channel.mdx b/constructs/email-alert-channel.mdx index 64c5a0d15..3a1d1ba02 100644 --- a/constructs/email-alert-channel.mdx +++ b/constructs/email-alert-channel.mdx @@ -11,7 +11,7 @@ import AlertChannelOptionsText from '/snippets/alert-channel-options-text.mdx'; For general information about alerting, see our docs on [email alerts](/integrations/alerts/email) and [alerting with Checkly](/communicate/alerts/overview/). -Use Email Alert Channels to send email notifications when checks fail or recover. +Use Email alert channels to send email notifications when checks fail or recover. @@ -44,12 +44,12 @@ const emailChannel = new EmailAlertChannel("ops-email-channel", { ## Configuration -### Email Alert Channel Options +### Email alert channel options Email address to send notifications to. To notify multiple recipients from one `EmailAlertChannel`, pass a comma-separated list of email addresses. -### General Alert Channel Options +### General alert channel options diff --git a/constructs/grpc-monitor.mdx b/constructs/grpc-monitor.mdx index c1c18b287..4a160f277 100644 --- a/constructs/grpc-monitor.mdx +++ b/constructs/grpc-monitor.mdx @@ -1,7 +1,7 @@ --- title: 'GrpcMonitor Construct' description: 'Learn how to configure gRPC monitors with the Checkly CLI.' -sidebarTitle: 'gRPC Monitor' +sidebarTitle: 'gRPC monitor' canonical: 'https://www.checklyhq.com/docs/constructs/grpc-monitor/' --- @@ -10,16 +10,16 @@ import CheckIntent from '/snippets/check-intent.mdx'; import GeneralMonitorOptionsTable from '/snippets/general-monitor-options-table.mdx'; -Learn more about gRPC Monitors in [the gRPC monitor overview](/detect/uptime-monitoring/grpc-monitors/overview). +Learn more about gRPC monitors in [the gRPC monitor overview](/detect/uptime-monitoring/grpc-monitors/overview). -Use gRPC Monitors to verify that your gRPC services are reachable, responding correctly, and meeting performance expectations. Monitors run in two modes: +Use gRPC monitors to verify that your gRPC services are reachable, responding correctly, and meeting performance expectations. Monitors run in two modes: - **BEHAVIOR** — Invokes a unary gRPC method and asserts on the response - **HEALTH** — Queries the standard `grpc.health.v1.Health/Check` endpoint -Before creating gRPC Monitors, ensure you have: +Before creating gRPC monitors, ensure you have: - An initialized Checkly CLI project - The hostname and port of the gRPC service you want to monitor @@ -91,7 +91,7 @@ new GrpcMonitor('grpc-behavior-1', { gRPC monitors have their own gRPC-specific settings, plus the standard monitor options shared across all check types. - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| @@ -263,7 +263,7 @@ Learn more in our docs on [Assertions](/detect/assertions). ### General Monitor Options -Friendly name for your gRPC Monitor displayed in the Checkly dashboard and used in notifications. +Friendly name for your gRPC monitor displayed in the Checkly dashboard and used in notifications. **Usage:** @@ -277,7 +277,7 @@ new GrpcMonitor('my-grpc-monitor', { -How often the gRPC Monitor should run. Use the `Frequency` enum to set the check interval. +How often the gRPC monitor should run. Use the `Frequency` enum to set the check interval. **Usage:** @@ -293,7 +293,7 @@ new GrpcMonitor('my-grpc-monitor', { -Array of [public location codes](/concepts/locations/#public-locations) where the gRPC Monitor runs from. Multiple locations provide geographic coverage. +Array of [public location codes](/concepts/locations/#public-locations) where the gRPC monitor runs from. Multiple locations provide geographic coverage. **Usage:** @@ -308,7 +308,7 @@ new GrpcMonitor('global-grpc-monitor', { -Whether the gRPC Monitor is enabled and will run according to its schedule. +Whether the gRPC monitor is enabled and will run according to its schedule. **Usage:** diff --git a/constructs/heartbeat-monitor.mdx b/constructs/heartbeat-monitor.mdx index 8d380d0a3..9f689d619 100644 --- a/constructs/heartbeat-monitor.mdx +++ b/constructs/heartbeat-monitor.mdx @@ -1,7 +1,7 @@ --- -title: 'Heartbeat Monitor Construct' -description: 'Learn how to configure heartbeat monitors with the Checkly CLI.' -sidebarTitle: 'Heartbeat Monitor' +title: 'Heartbeat monitor construct' +description: 'Learn how to configure Heartbeat monitors with the Checkly CLI.' +sidebarTitle: 'Heartbeat monitor' canonical: 'https://www.checklyhq.com/docs/constructs/heartbeat-monitor/' --- @@ -9,10 +9,10 @@ canonical: 'https://www.checklyhq.com/docs/constructs/heartbeat-monitor/' Learn more about Heartbeat monitors in [the Heartbeat monitor overview](/detect/uptime-monitoring/heartbeat-monitors/overview). -Use Heartbeat Monitors to track passive monitoring scenarios where external services ping Checkly at regular intervals. The examples below show how to configure monitoring for different types of scheduled jobs and services. +Use Heartbeat monitors to track passive monitoring scenarios where external services ping Checkly at regular intervals. The examples below show how to configure monitoring for different types of scheduled jobs and services. -Before creating heartbeat monitors, ensure you have: +Before creating Heartbeat monitors, ensure you have: - An initialized Checkly CLI project - External services, cron jobs, or scripts that can send HTTP POST requests @@ -69,7 +69,7 @@ new HeartbeatMonitor("newsletter-heartbeat", { The Heartbeat Monitoring configuration consists of specific heartbeat monitoring options and inherited general monitoring options. - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| @@ -260,7 +260,7 @@ new HeartbeatMonitor('my-heartbeat', { ### General Monitor Options -Friendly name for your heartbeat monitor that will be displayed in the Checkly dashboard and used in notifications. +Friendly name for your Heartbeat monitor that will be displayed in the Checkly dashboard and used in notifications. **Usage:** @@ -391,7 +391,7 @@ new HeartbeatMonitor('my-heartbeat', { ## Getting the heartbeat Ping URL -After deploying your heartbeat monitor, you can obtain the ping URL in several ways: +After deploying your Heartbeat monitor, you can obtain the ping URL in several ways: @@ -404,12 +404,12 @@ After deploying your heartbeat monitor, you can obtain the ping URL in several w - Navigate to your heartbeat monitor in the [Checkly web UI](https://app.checklyhq.com/heartbeats) to copy the ping URL. + Navigate to your Heartbeat monitor in the [Checkly web UI](https://app.checklyhq.com/heartbeats) to copy the ping URL. -The ping URL is unique for each heartbeat monitor and should be kept secure. Anyone with access to this URL can send pings to your monitor. +The ping URL is unique for each Heartbeat monitor and should be kept secure. Anyone with access to this URL can send pings to your monitor. diff --git a/constructs/icmp-monitor.mdx b/constructs/icmp-monitor.mdx index 1936b2dee..c168d4957 100644 --- a/constructs/icmp-monitor.mdx +++ b/constructs/icmp-monitor.mdx @@ -1,7 +1,7 @@ --- title: 'IcmpMonitor Construct' description: 'Learn how to configure ICMP monitors with the Checkly CLI.' -sidebarTitle: 'ICMP Monitor' +sidebarTitle: 'ICMP monitor' canonical: 'https://www.checklyhq.com/docs/constructs/icmp-monitor/' --- @@ -10,13 +10,13 @@ import CheckIntent from '/snippets/check-intent.mdx'; import GeneralMonitorOptionsTable from '/snippets/general-monitor-options-table.mdx'; -Learn more about ICMP Monitors in [the ICMP monitor overview](/detect/uptime-monitoring/icmp-monitors/overview). +Learn more about ICMP monitors in [the ICMP monitor overview](/detect/uptime-monitoring/icmp-monitors/overview). ICMP monitors check if a host is reachable by sending ICMP Echo Requests (pings). Use them to monitor network connectivity and latency. -Before creating ICMP Monitors, ensure you have: +Before creating ICMP monitors, ensure you have: - An initialized Checkly CLI project - A hostname or IP address you want to ping @@ -70,7 +70,7 @@ new IcmpMonitor('cloudflare-dns-icmp', { ICMP monitors have their own ICMP-specific settings, plus the standard monitor options shared across all check types. - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| @@ -184,7 +184,7 @@ Learn more in our docs on [Assertions](/detect/assertions). ### General Monitor Options -Friendly name for your ICMP Monitor that will be displayed in the Checkly dashboard and used in notifications. +Friendly name for your ICMP monitor that will be displayed in the Checkly dashboard and used in notifications. **Usage:** @@ -198,7 +198,7 @@ new IcmpMonitor("my-monitor", { -How often the ICMP Monitor should run. Use the `Frequency` enum to set the check interval. +How often the ICMP monitor should run. Use the `Frequency` enum to set the check interval. **Usage:** @@ -214,7 +214,7 @@ new IcmpMonitor("my-monitor", { -Array of [public location codes](/concepts/locations/#public-locations) where the ICMP Monitor should run from. Multiple locations provide geographic coverage and help detect regional network issues. +Array of [public location codes](/concepts/locations/#public-locations) where the ICMP monitor should run from. Multiple locations provide geographic coverage and help detect regional network issues. **Usage:** @@ -227,7 +227,7 @@ new IcmpMonitor("global-icmp-monitor", { -Whether the ICMP Monitor is enabled and will run according to its schedule. +Whether the ICMP monitor is enabled and will run according to its schedule. **Usage:** diff --git a/constructs/incident-trigger.mdx b/constructs/incident-trigger.mdx index f84d9df69..32ff6cac1 100644 --- a/constructs/incident-trigger.mdx +++ b/constructs/incident-trigger.mdx @@ -9,7 +9,7 @@ canonical: 'https://www.checklyhq.com/docs/constructs/incident-trigger/' **Deprecated.** Incident triggers automate incidents on v2 (services-based) status pages. On v3 pages, use [`StatusPageV3AutomationRule`](/constructs/status-page-v3-automation-rule) instead. -Learn more about Status Pages in [the Status Pages overview](/communicate/status-pages/overview). +Learn more about status pages in [the status pages overview](/communicate/status-pages/overview). Use incident triggers to automatically create and resolve an incident and notify subscribers based on the alert configuration of a monitor or check. This allows you to link synthetic monitoring failures directly to incidents on your status pages. diff --git a/constructs/incidentio-alert-channel.mdx b/constructs/incidentio-alert-channel.mdx index fe66ac5e2..912288d5a 100644 --- a/constructs/incidentio-alert-channel.mdx +++ b/constructs/incidentio-alert-channel.mdx @@ -49,7 +49,7 @@ const incidentioChannel = new IncidentioAlertChannel('incidentio-channel-1', { ## Configuration -### Incident.io Alert Channel Options +### Incident.io alert channel options Friendly name to recognise the integration. @@ -101,7 +101,7 @@ new IncidentioAlertChannel('incidentio-channel-1', { ``` -### General Alert Channel Options +### General alert channel options diff --git a/constructs/including-checks.mdx b/constructs/including-checks.mdx index c082dafaa..e80c88ee7 100644 --- a/constructs/including-checks.mdx +++ b/constructs/including-checks.mdx @@ -38,14 +38,14 @@ const config = defineConfig({ The `testMatch` property is very similar to `checkMatch`. This property allows you to write standard `*.spec.ts` Playwright files with no proprietary Checkly -config or code added — this is why it's nested under `browserChecks` as it only applies to Browser Checks. In turn, this allows you to just use `npx playwright test` on the command line to write and debug these Checks. +config or code added — this is why it's nested under `browserChecks` as it only applies to Browser checks. In turn, this allows you to just use `npx playwright test` on the command line to write and debug these Checks. Some caveats: 1. As a `.spec.ts` file does not contain any Checkly specific properties like `frequency` or `tags`, the CLI will add these properties based on the defaults set inside the `browserChecks` config object. 2. A `logicalId` and `name` will be generated based on the file name. -3. If you want to explicitly set the properties for a Browser Check and not use the defaults, you need to add [a `BrowserCheck` +3. If you want to explicitly set the properties for a Browser check and not use the defaults, you need to add [a `BrowserCheck` construct](/constructs/browser-check) in a separate `.check.ts` file and set file path to the `.spec.ts` file in the `code.entrypoint` property. 4. When you rename a file that was previously deployed, the `logicalId` will change. The effect is that once you deploy again the new `logicalId` will trigger a deletion of the "old" Check and a creation of this "new" Check and you will lose diff --git a/constructs/maintenance-window.mdx b/constructs/maintenance-window.mdx index 510cfe60a..942712fdd 100644 --- a/constructs/maintenance-window.mdx +++ b/constructs/maintenance-window.mdx @@ -1,15 +1,15 @@ --- title: 'MaintenanceWindow Construct' description: 'Learn how to configure maintenance windows with the Checkly CLI.' -sidebarTitle: 'Maintenance Window' +sidebarTitle: 'Maintenance window' canonical: 'https://www.checklyhq.com/docs/constructs/maintenance-window/' --- -Learn more about Maintenance Windows in [the Maintenance Windows documentation](/communicate/maintenance-windows/overview). +Learn more about maintenance windows in [the maintenance windows documentation](/communicate/maintenance-windows/overview). -Use Maintenance Windows to schedule planned maintenance periods that prevent your checks from running and triggering alerts during expected downtime. +Use maintenance windows to schedule planned maintenance periods that prevent your checks from running and triggering alerts during expected downtime. diff --git a/constructs/msteams-alert-channel.mdx b/constructs/msteams-alert-channel.mdx index 484b96d3a..fd56547df 100644 --- a/constructs/msteams-alert-channel.mdx +++ b/constructs/msteams-alert-channel.mdx @@ -161,7 +161,7 @@ const msTeamsAlertChannel = new MSTeamsAlertChannel('msteams-channel-01', { ## Configuration -### Microsoft Teams Alert Channel Options +### Microsoft Teams alert channel options The target URL created by [creating a Workflow in Microsoft Teams](/integrations/alerts/msteams). @@ -303,6 +303,6 @@ new MSTeamsAlertChannel('msteams-channel-01', { ``` -### General Alert Channel Options +### General alert channel options diff --git a/constructs/multistep-check.mdx b/constructs/multistep-check.mdx index 42f3896c3..1b78def2f 100644 --- a/constructs/multistep-check.mdx +++ b/constructs/multistep-check.mdx @@ -1,24 +1,24 @@ --- -title: 'Multistep Check Construct' -description: 'Learn how to configure multistep checks with the Checkly CLI.' -sidebarTitle: 'Multistep Check' +title: 'Multistep check construct' +description: 'Learn how to configure Multistep checks with the Checkly CLI.' +sidebarTitle: 'Multistep check' canonical: 'https://www.checklyhq.com/docs/constructs/multistep-check/' --- import CheckIntent from '/snippets/check-intent.mdx'; -Learn more about Multistep Checks in [the Multistep Checks overview](/detect/synthetic-monitoring/multistep-checks/overview). +Learn more about Multistep checks in [the Multistep checks overview](/detect/synthetic-monitoring/multistep-checks/overview). -Use Multistep Checks to run complex end-to-end workflows with Playwright that span multiple endpoints. The examples below show how to configure Multistep Checks for different testing scenarios. +Use Multistep checks to run complex end-to-end workflows with Playwright that span multiple endpoints. The examples below show how to configure Multistep checks for different testing scenarios. -Before creating Multistep Checks, ensure you have: +Before creating Multistep checks, ensure you have: - An initialized Checkly CLI project - Public endpoints you want to monitor -- Runtime `2023.09` or later (Multistep Checks require [newer runtimes](/platform/runtimes/runtime-specification)) +- Runtime `2023.09` or later (Multistep checks require [newer runtimes](/platform/runtimes/runtime-specification)) For additional setup information, see [CLI overview](/cli/overview). @@ -68,7 +68,7 @@ new MultiStepCheck("complex-multistep-check", { ## Configuration - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| @@ -92,7 +92,7 @@ new MultiStepCheck("complex-multistep-check", { | `locations` | `string[]` | ❌ | `[]` | Array of public location codes | | `muted` | `boolean` | ❌ | `false` | Whether alert notifications are muted | | `runtimeId` | `string` | ❌ | - | The ID of the runtime to use (2023.09 or later required) | -| `privateLocations` | `string[]` | ❌ | `[]` | Array of Private Location slugs | +| `privateLocations` | `string[]` | ❌ | `[]` | Array of private location slugs | | `retryStrategy` | `RetryStrategy` | ❌ | [`singleRetry()`](/constructs/retry-strategy#default-retry-strategy) | Strategy for configuring retries | | `runParallel` | `boolean` | ❌ | `false` | Run checks in parallel or round-robin | | `tags` | `string[]` | ❌ | `[]` | Array of tags to organize checks | @@ -102,10 +102,10 @@ new MultiStepCheck("complex-multistep-check", { -### Multistep Check Options +### Multistep check options -The Playwright test code that defines your Multistep Check monitor. +The Playwright test code that defines your Multistep check monitor. **Usage:** @@ -265,7 +265,7 @@ test("SpaceX-API Dragon Capsules & Next Launch", async ({ request }) => { ### General Check Options -Friendly name for your multistep check that will be displayed in the Checkly dashboard and used in notifications. +Friendly name for your Multistep check that will be displayed in the Checkly dashboard and used in notifications. **Usage:** @@ -278,7 +278,7 @@ new MultiStepCheck("my-multistep", { -The Checkly runtime version used to execute the Multistep Check. Runtimes are managed execution environments for Browser and Multistep Checks. They include fixed Checkly-provided dependencies, such as Playwright, browser binaries, and runtime libraries. +The Checkly runtime version used to execute the Multistep check. Runtimes are managed execution environments for Browser and Multistep checks. They include fixed Checkly-provided dependencies, such as Playwright, browser binaries, and runtime libraries. Multistep checks require runtime `2023.09` or later. @@ -297,7 +297,7 @@ Multistep checks require runtime `2023.09` or later. Earlier runtimes do not sup -How often the multistep check should run. Use the `Frequency` enum to set the check interval. +How often the Multistep check should run. Use the `Frequency` enum to set the check interval. Usage: ```ts highlight={5} @@ -314,7 +314,7 @@ new MultiStepCheck("my-multistep", { -Array of public location codes where the multistep check should run. Multiple locations provide geographic coverage and user experience insights. +Array of public location codes where the Multistep check should run. Multiple locations provide geographic coverage and user experience insights. Usage: ```ts highlight={3} diff --git a/constructs/opsgenie-alert-channel.mdx b/constructs/opsgenie-alert-channel.mdx index 3ab0fa8ce..dd13f2b15 100644 --- a/constructs/opsgenie-alert-channel.mdx +++ b/constructs/opsgenie-alert-channel.mdx @@ -51,7 +51,7 @@ const opsGenieChannel = new OpsgenieAlertChannel('opsgenie-channel-1', { ## Configuration -### Opsgenie Alert Channel Options +### Opsgenie alert channel options Friendly name to recognise the integration. @@ -69,6 +69,6 @@ A string representing the severity level, `P1` to `P5`. An API key for your Opsgenie account. -### General Alert Channel Options +### General alert channel options diff --git a/constructs/pagerduty-alert-channel.mdx b/constructs/pagerduty-alert-channel.mdx index 8c3328fb0..47150f422 100644 --- a/constructs/pagerduty-alert-channel.mdx +++ b/constructs/pagerduty-alert-channel.mdx @@ -1,7 +1,7 @@ --- title: 'PagerdutyAlertChannel Construct' -description: 'Learn how to configure Pagerduty alert channels with the Checkly CLI.' -sidebarTitle: 'Pagerduty' +description: 'Learn how to configure PagerDuty alert channels with the Checkly CLI.' +sidebarTitle: 'PagerDuty' canonical: 'https://www.checklyhq.com/docs/constructs/pagerduty-alert-channel/' --- @@ -9,10 +9,10 @@ import AlertChannelOptionsText from '/snippets/alert-channel-options-text.mdx'; -For general information about alerting, see our docs on [the Pagerduty integration](/integrations/incident-management/pagerduty) and [alerting with Checkly](/communicate/alerts/overview/). +For general information about alerting, see our docs on [the PagerDuty integration](/integrations/incident-management/pagerduty) and [alerting with Checkly](/communicate/alerts/overview/). -Sends an alert notification to a specific service in your Pagerduty account. +Sends an alert notification to a specific service in your PagerDuty account. @@ -49,20 +49,20 @@ const pagerdutyChannel = new PagerdutyAlertChannel('pagerduty-channel-1', { ## Configuration -### Pagerduty Alert Channel Options +### PagerDuty alert channel options -The name of your Pagerduty account. +The name of your PagerDuty account. -The name of your service defined in Pagerduty under which the alerts should be nested. +The name of your service defined in PagerDuty under which the alerts should be nested. -The API key created by installing the Checkly integration in Pagerduty. We advise you to [install the Pagerduty alert channel first from the UI](https://app.checklyhq.com/alerts/settings/channels/new/pagerduty/) to grab the `serviceKey`. +The API key created by installing the Checkly integration in PagerDuty. We advise you to [install the PagerDuty alert channel first from the UI](https://app.checklyhq.com/alerts/settings/channels/new/pagerduty/) to grab the `serviceKey`. -### General Alert Channel Options +### General alert channel options diff --git a/constructs/phone-call-alert-channel.mdx b/constructs/phone-call-alert-channel.mdx index ea39cdc35..0bc747ba0 100644 --- a/constructs/phone-call-alert-channel.mdx +++ b/constructs/phone-call-alert-channel.mdx @@ -45,7 +45,7 @@ const callChannel = new PhoneCallAlertChannel('call-channel-1', { ## Configuration -### Phone Call Alert Channel Options +### Phone call alert channel options Phone number to call. @@ -65,6 +65,6 @@ new PhoneCallAlertChannel('call-channel-1', { Friendly name for the phone call alert channel. -### General Alert Channel Options +### General alert channel options diff --git a/constructs/playwright-check.mdx b/constructs/playwright-check.mdx index 332ccc78d..98ce9d7d6 100644 --- a/constructs/playwright-check.mdx +++ b/constructs/playwright-check.mdx @@ -1,6 +1,6 @@ --- title: 'Playwright Check Suite' -description: 'Learn how to configure Playwright check suites with the Checkly CLI.' +description: 'Learn how to configure Playwright Check Suites with the Checkly CLI.' sidebarTitle: 'Playwright Check Suites' canonical: 'https://www.checklyhq.com/docs/constructs/playwright-check/' --- @@ -89,7 +89,7 @@ The Playwright Check Suite configuration consists of specific Playwright Check S | `group` | `CheckGroup` | ❌ | - | The CheckGroup this check belongs to | | `locations` | `string[]` | ❌ | `[]` | Array of public location codes | | `muted` | `boolean` | ❌ | `false` | Whether alert notifications are muted | -| `privateLocations` | `string[]` | ❌ | `[]` | Array of Private Location slugs | +| `privateLocations` | `string[]` | ❌ | `[]` | Array of private location slugs | | `runParallel` | `boolean` | ❌ | `false` | Run checks in parallel or round-robin | | `tags` | `string[]` | ❌ | `[]` | Array of tags to organize checks | | `testOnly` | `boolean` | ❌ | `false` | Only run with test, not during deploy | @@ -219,7 +219,7 @@ new PlaywrightCheck("critical-e2e-monitor", { -Defines the glob patterns for files and directories that should be included when bundling the Playwright Check Suite. Use this option to manually include additional test files, helper utilities, or other resources that might be outside of the tests directory that your playwright config file points to. +Defines the glob patterns for files and directories that should be included when bundling the Playwright Check Suite. Use this option to manually include additional test files, helper utilities, or other resources that might be outside of the tests directory that your Playwright config file points to. **Usage:** diff --git a/constructs/private-location.mdx b/constructs/private-location.mdx index 253a2039e..c3284a198 100644 --- a/constructs/private-location.mdx +++ b/constructs/private-location.mdx @@ -1,15 +1,15 @@ --- title: 'PrivateLocation Construct' description: 'Learn how to configure private locations with the Checkly CLI.' -sidebarTitle: 'Private Locations' +sidebarTitle: 'Private locations' canonical: 'https://www.checklyhq.com/docs/constructs/private-location/' --- -Learn more about Private Locations in [the Private Locations overview](/platform/private-locations/overview). +Learn more about private locations in [the private locations overview](/platform/private-locations/overview). -Use Private Locations to run checks from your own infrastructure, VPCs, or isolated networks. With a Private Location, you can monitor internal services and applications not accessible from the public internet. +Use private locations to run checks from your own infrastructure, VPCs, or isolated networks. With a private location, you can monitor internal services and applications not accessible from the public internet. Before creating private locations, ensure you have: @@ -67,7 +67,7 @@ new ApiCheck("internal-api-check", { | `icon` | `string` | ❌ | `location` | [Octicon name](https://primer.style/octicons/) to distinguish the location in the UI | | `proxyUrl` | `string` | ❌ | - | Proxy URL for outgoing HTTP calls from this location | -## Private Location Options +## Private location options Friendly name for your private location that will be displayed in the Checkly dashboard and used for identification. diff --git a/constructs/project.mdx b/constructs/project.mdx index c57ca4620..1f7ca6aa0 100644 --- a/constructs/project.mdx +++ b/constructs/project.mdx @@ -201,8 +201,8 @@ export default defineConfig({ | `runtimeId` | `string` | ❌ | - | Default runtime ID for all checks | | `shouldFail` | `boolean` | ❌ | `false` | Whether the behavior of when a check/alert is considered to fail is inverted. Only applies to API checks, URL monitors and TCP monitors. | | `tags` | `string[]` | ❌ | `[]` | Default tags applied to all checks | -| `browserChecks` | `object` | ❌ | - | Default settings for browser checks | -| `multiStepChecks` | `object` | ❌ | - | Default settings for multi-step checks | +| `browserChecks` | `object` | ❌ | - | Default settings for Browser checks | +| `multiStepChecks` | `object` | ❌ | - | Default settings for Multistep checks | | `playwrightChecks` | `object` | ❌ | - | Default settings for Playwright Check Suites | @@ -374,7 +374,7 @@ export default defineConfig({ -Global configuration options for the Playwright Test Runner use in [Browser Checks](/detect/synthetic-monitoring/browser-checks/overview) and [MultiStep Checks](/detect/synthetic-monitoring/multistep-checks/overview). This allows you to configure your Playwright-powered checks in a single place, instead of having to repeat the same configuration for each test file. +Global configuration options for the Playwright Test Runner use in [Browser checks](/detect/synthetic-monitoring/browser-checks/overview) and [Multistep checks](/detect/synthetic-monitoring/multistep-checks/overview). This allows you to configure your Playwright-powered checks in a single place, instead of having to repeat the same configuration for each test file. **Usage:** @@ -399,9 +399,9 @@ export default defineConfig({ }) ``` -Learn more about the supported Playwright configuration options in [the Browser Check Playwright documentation](/detect/synthetic-monitoring/browser-checks/playwright-support). +Learn more about the supported Playwright configuration options in [the Browser check Playwright documentation](/detect/synthetic-monitoring/browser-checks/playwright-support). -Browser Checks don't support the `projects`, `globalSetup`, `globalTeardown` and `storageState` options. Check [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) for full Playwright support. +Browser checks don't support the `projects`, `globalSetup`, `globalTeardown` and `storageState` options. Check [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) for full Playwright support. @@ -425,7 +425,7 @@ export default defineConfig({ -Private Locations to run your monitors and checks from. +Private locations to run your monitors and checks from. **Usage:** @@ -446,7 +446,7 @@ export default defineConfig({ }) ``` -Learn more about [Private Locations in the general documentation](/platform/private-locations/overview). +Learn more about [private locations in the general documentation](/platform/private-locations/overview). @@ -516,13 +516,13 @@ export default defineConfig({ -If your project doesn't require specific configuration and you want to quickly transform your Playwright end-to-end tests into Browser Checks, use the `browserChecks.testMatch` property. +If your project doesn't require specific configuration and you want to quickly transform your Playwright end-to-end tests into Browser checks, use the `browserChecks.testMatch` property. **Properties:** | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| -| `testMatch` | `string` | `string[]` | ❌ | - | Glob pattern for Playwright tests uses as Browser Checks | +| `testMatch` | `string` | `string[]` | ❌ | - | Glob pattern for Playwright tests uses as Browser checks | **Example:** @@ -544,13 +544,13 @@ export default defineConfig({ -If your project doesn't require specific configuration and you want to quickly transform your Playwright API tests into Multistep Checks, use the `multiStepChecks.testMatch` property. +If your project doesn't require specific configuration and you want to quickly transform your Playwright API tests into Multistep checks, use the `multiStepChecks.testMatch` property. **Properties:** | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| -| `testMatch` | `string` | `string[]` | ❌ | - | Glob pattern for Playwright tests uses as Browser Checks | +| `testMatch` | `string` | `string[]` | ❌ | - | Glob pattern for Playwright tests uses as Browser checks | **Example:** @@ -624,7 +624,7 @@ export default defineConfig({ | `frequency` | `Frequency` | ❌ | - | How often to run your check suite | | `locations` | `string[]` | ❌ | `[]` | Array of public location codes | | `muted` | `boolean` | ❌ | `false` | Whether alert notifications are muted | -| `privateLocations` | `string[]` | ❌ | `[]` | Array of Private Location slugs | +| `privateLocations` | `string[]` | ❌ | `[]` | Array of private location slugs | | `retryStrategy` | `RetryStrategy` | ❌ | - | Strategy for configuring retries | | `runParallel` | `boolean` | ❌ | `false` | Run check suites in parallel or round-robin | | `tags` | `string[]` | ❌ | `[]` | Array of tags to organize check suites | diff --git a/constructs/slack-alert-channel.mdx b/constructs/slack-alert-channel.mdx index 5158ecfd1..c87cf0616 100644 --- a/constructs/slack-alert-channel.mdx +++ b/constructs/slack-alert-channel.mdx @@ -47,7 +47,7 @@ const slackChannel = new SlackAlertChannel('slack-channel-1', { ## Configuration -### Slack Alert Channel Options +### Slack alert channel options The Slack incoming webhook URL where Checkly will send alert notifications. @@ -64,6 +64,6 @@ new SlackAlertChannel('slack-channel-1', { Target Slack channel or user for notifications. You can specify the target channel to override the default channel configured in the webhook. -### General Alert Channel Options +### General alert channel options diff --git a/constructs/slack-app-alert-channel.mdx b/constructs/slack-app-alert-channel.mdx index b18b7135f..b5b58300b 100644 --- a/constructs/slack-app-alert-channel.mdx +++ b/constructs/slack-app-alert-channel.mdx @@ -45,7 +45,7 @@ const slackAppChannel = new SlackAppAlertChannel('slack-channel-1', { ## Configuration -### Slack Alert Channel Options +### Slack alert channel options The Slack channels to alert. Can also include DM handles, e.g. "@John Doe" @@ -57,6 +57,6 @@ new SlackAppAlertChannel('slack-channel-1', { ``` -### General Alert Channel Options +### General alert channel options diff --git a/constructs/sms-alert-channel.mdx b/constructs/sms-alert-channel.mdx index 692fd770f..3d3ba8ad2 100644 --- a/constructs/sms-alert-channel.mdx +++ b/constructs/sms-alert-channel.mdx @@ -11,7 +11,7 @@ import AlertChannelOptionsText from '/snippets/alert-channel-options-text.mdx'; For general information about alerting, see our docs on [SMS alerts](/integrations/alerts/sms) and [alerting with Checkly](/communicate/alerts/overview/). -Use SMS Alert Channels to send SMS notifications to phone numbers when checks fail or recover. +Use SMS alert channels to send SMS notifications to phone numbers when checks fail or recover. @@ -46,7 +46,7 @@ const smsChannel = new SmsAlertChannel('sms-channel-1', { ## Configuration -### SMS Alert Channel Options +### SMS alert channel options Phone number to send SMS notifications to. @@ -67,6 +67,6 @@ new SmsAlertChannel('sms-channel-1', { Friendly name for the SMS alert channel. -### General Alert Channel Options +### General alert channel options diff --git a/constructs/ssl-monitor.mdx b/constructs/ssl-monitor.mdx index 324aa2964..84b621679 100644 --- a/constructs/ssl-monitor.mdx +++ b/constructs/ssl-monitor.mdx @@ -1,20 +1,20 @@ --- title: 'SslMonitor Construct' description: 'Learn how to configure SSL monitors with the Checkly CLI.' -sidebarTitle: 'SSL Monitor' +sidebarTitle: 'SSL monitor' canonical: 'https://www.checklyhq.com/docs/constructs/ssl-monitor/' --- import GeneralMonitorOptionsTable from '/snippets/general-monitor-options-table.mdx'; -Learn more about SSL Monitors in [the SSL monitor overview](/detect/uptime-monitoring/ssl-monitors/overview). +Learn more about SSL monitors in [the SSL monitor overview](/detect/uptime-monitoring/ssl-monitors/overview). -Use SSL Monitors to verify the health and security posture of your TLS certificates. The examples below show how to configure monitoring for common scenarios. +Use SSL monitors to verify the health and security posture of your TLS certificates. The examples below show how to configure monitoring for common scenarios. -Before creating SSL Monitors, ensure you have: +Before creating SSL monitors, ensure you have: - An initialized Checkly CLI project - Network access to the HTTPS endpoint you want to monitor @@ -88,7 +88,7 @@ new SslMonitor("api-ssl-advanced", { SSL monitors have SSL-specific settings and inherit the standard monitor options shared across all check types. - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| @@ -343,7 +343,7 @@ Learn more in our docs on [Assertions](/detect/assertions). ### General Monitor Options -Friendly name for your SSL Monitor, displayed in the Checkly dashboard and used in notifications. +Friendly name for your SSL monitor, displayed in the Checkly dashboard and used in notifications. ```ts highlight={2} new SslMonitor("my-ssl-monitor", { @@ -354,7 +354,7 @@ new SslMonitor("my-ssl-monitor", { -How often the SSL Monitor should run. Use the `Frequency` enum to set the check interval. +How often the SSL monitor should run. Use the `Frequency` enum to set the check interval. ```ts highlight={3} new SslMonitor("my-ssl-monitor", { @@ -380,7 +380,7 @@ new SslMonitor("global-ssl", { -Whether the SSL Monitor is enabled and will run according to its schedule. +Whether the SSL monitor is enabled and will run according to its schedule. ```ts highlight={3} new SslMonitor("my-ssl-monitor", { diff --git a/constructs/status-page-service.mdx b/constructs/status-page-service.mdx index cfc6aafd1..cfd3a1b48 100644 --- a/constructs/status-page-service.mdx +++ b/constructs/status-page-service.mdx @@ -1,7 +1,7 @@ --- title: 'StatusPageService Construct' description: 'Learn how to configure status page services with the Checkly CLI.' -sidebarTitle: 'Status Page Service (deprecated)' +sidebarTitle: 'Status page service (deprecated)' canonical: 'https://www.checklyhq.com/docs/constructs/status-page-service/' --- @@ -9,10 +9,10 @@ canonical: 'https://www.checklyhq.com/docs/constructs/status-page-service/' **Deprecated.** Services belong to v2 status pages. On v3 pages, use [`StatusPageV3Component`](/constructs/status-page-v3-component) instead. -Learn more about Status Pages in [the Status Pages overview](/communicate/status-pages/overview). +Learn more about status pages in [the status pages overview](/communicate/status-pages/overview). -Use Status Page Services to allow monitors and checks to trigger incidents and to be displayed on status pages. Services represent individual components or systems that you want to show uptime information for. +Use status page services to allow monitors and checks to trigger incidents and to be displayed on status pages. Services represent individual components or systems that you want to show uptime information for. @@ -80,7 +80,7 @@ new StatusPage("acme-status", { ## Configuration - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| @@ -266,7 +266,7 @@ new StatusPage("internal-status", { ## Integration with Checks and Monitors -Status Page Services represent logical groupings of functionality. You'll typically have multiple checks monitoring different aspects of each service, but the service itself provides a high-level view for your status page visitors. Enable checks and monitors to trigger incidents by using the `triggerIncident` property. +Status page services represent logical groupings of functionality. You'll typically have multiple checks monitoring different aspects of each service, but the service itself provides a high-level view for your status page visitors. Enable checks and monitors to trigger incidents by using the `triggerIncident` property. ```ts highlight=12,27 import { ApiCheck, StatusPageService, UrlMonitor } from "checkly/constructs" diff --git a/constructs/status-page-v3-automation-rule.mdx b/constructs/status-page-v3-automation-rule.mdx index 8965d73e5..6ffe78cdf 100644 --- a/constructs/status-page-v3-automation-rule.mdx +++ b/constructs/status-page-v3-automation-rule.mdx @@ -1,7 +1,7 @@ --- title: 'StatusPageV3AutomationRule Construct' description: 'Learn how to automate status page incidents with the Checkly CLI.' -sidebarTitle: 'Status Page Automation Rule' +sidebarTitle: 'Status page automation rule' canonical: 'https://www.checklyhq.com/docs/constructs/status-page-v3-automation-rule/' --- diff --git a/constructs/status-page-v3-component.mdx b/constructs/status-page-v3-component.mdx index 0652a9f1c..e441c605b 100644 --- a/constructs/status-page-v3-component.mdx +++ b/constructs/status-page-v3-component.mdx @@ -1,7 +1,7 @@ --- title: 'StatusPageV3Component Construct' description: 'Learn how to configure status page components with the Checkly CLI.' -sidebarTitle: 'Status Page Component' +sidebarTitle: 'Status page component' canonical: 'https://www.checklyhq.com/docs/constructs/status-page-v3-component/' --- diff --git a/constructs/status-page-v3.mdx b/constructs/status-page-v3.mdx index 0a01b7124..318001445 100644 --- a/constructs/status-page-v3.mdx +++ b/constructs/status-page-v3.mdx @@ -1,7 +1,7 @@ --- title: 'StatusPageV3 Construct' description: 'Learn how to configure status pages with the Checkly CLI.' -sidebarTitle: 'Status Page' +sidebarTitle: 'Status page' canonical: 'https://www.checklyhq.com/docs/constructs/status-page-v3/' --- diff --git a/constructs/status-page.mdx b/constructs/status-page.mdx index 917decd1a..26d42560b 100644 --- a/constructs/status-page.mdx +++ b/constructs/status-page.mdx @@ -1,7 +1,7 @@ --- title: 'StatusPage Construct' description: 'Learn how to configure status pages with the Checkly CLI.' -sidebarTitle: 'Status Page (deprecated)' +sidebarTitle: 'Status page (deprecated)' canonical: 'https://www.checklyhq.com/docs/constructs/status-page/' --- @@ -9,10 +9,10 @@ canonical: 'https://www.checklyhq.com/docs/constructs/status-page/' **Deprecated.** This construct creates a v2 (cards and services) status page. New status pages should use [`StatusPageV3`](/constructs/status-page-v3). Existing v2 pages keep working and can be migrated to v3 with the migration wizard in the Checkly app. -Learn more about Status Pages in [the Status Pages overview](/communicate/status-pages/overview). +Learn more about status pages in [the status pages overview](/communicate/status-pages/overview). -Use public Status Pages to show the uptime of your services through organized cards. Status pages help communicate service availability to your users and stakeholders. +Use public status pages to show the uptime of your services through organized cards. Status pages help communicate service availability to your users and stakeholders. @@ -80,7 +80,7 @@ new StatusPage("acme-status", { ## Configuration - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| diff --git a/constructs/tcp-monitor.mdx b/constructs/tcp-monitor.mdx index 03572834c..a6ffc6668 100644 --- a/constructs/tcp-monitor.mdx +++ b/constructs/tcp-monitor.mdx @@ -1,7 +1,7 @@ --- title: 'TcpMonitor Construct' description: 'Learn how to configure TCP monitors with the Checkly CLI.' -sidebarTitle: 'TCP Monitor' +sidebarTitle: 'TCP monitor' canonical: 'https://www.checklyhq.com/docs/constructs/tcp-monitor/' --- @@ -10,13 +10,13 @@ import CheckIntent from '/snippets/check-intent.mdx'; import GeneralMonitorOptionsTable from '/snippets/general-monitor-options-table.mdx'; -Learn more about TCP Monitors in [the TCP monitor overview](/detect/uptime-monitoring/tcp-monitors/overview). +Learn more about TCP monitors in [the TCP monitor overview](/detect/uptime-monitoring/tcp-monitors/overview). -Use TCP Monitors to verify connectivity and response times of your TCP services. The examples below show how to configure monitoring for different types of services. +Use TCP monitors to verify connectivity and response times of your TCP services. The examples below show how to configure monitoring for different types of services. -Before creating TCP Monitors, ensure you have: +Before creating TCP monitors, ensure you have: - An initialized Checkly CLI project - Network access to the TCP services you want to monitor @@ -78,7 +78,7 @@ new TcpMonitor("redis-tcp-1", { The TCP Monitoring configuration consists of specific TCP monitoring options and inherited general monitoring options. - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| diff --git a/constructs/telegram-alert-channel.mdx b/constructs/telegram-alert-channel.mdx index 39e170225..53fd349b6 100644 --- a/constructs/telegram-alert-channel.mdx +++ b/constructs/telegram-alert-channel.mdx @@ -54,7 +54,7 @@ const telegramChannel = new TelegramAlertChannel('my-telegramchannel-1', { ## Configuration -### Telegram Alert Channel Options +### Telegram alert channel options Friendly name to recognise the integration. @@ -98,6 +98,6 @@ new TelegramAlertChannel('my-telegramchannel-1', { ``` -### General Alert Channel Options +### General alert channel options diff --git a/constructs/traceroute-monitor.mdx b/constructs/traceroute-monitor.mdx index a9ea303bd..d7150963b 100644 --- a/constructs/traceroute-monitor.mdx +++ b/constructs/traceroute-monitor.mdx @@ -1,20 +1,20 @@ --- title: 'TracerouteMonitor Construct' description: 'Learn how to configure Traceroute monitors with the Checkly CLI.' -sidebarTitle: 'Traceroute Monitor' +sidebarTitle: 'Traceroute monitor' canonical: 'https://www.checklyhq.com/docs/constructs/traceroute-monitor/' --- import GeneralMonitorOptionsTable from '/snippets/general-monitor-options-table.mdx'; -Learn more about Traceroute Monitors in [the Traceroute monitor overview](/detect/uptime-monitoring/traceroute-monitors/overview). +Learn more about Traceroute monitors in [the Traceroute monitor overview](/detect/uptime-monitoring/traceroute-monitors/overview). Traceroute monitors map the network path to a host hop-by-hop, measuring per-hop latency and packet loss, and detecting whether the destination is reached. Use them to monitor path stability and catch routing issues before they affect your users. -Before creating Traceroute Monitors, ensure you have: +Before creating Traceroute monitors, ensure you have: - An initialized Checkly CLI project - A hostname or IP address you want to trace @@ -74,7 +74,7 @@ new TracerouteMonitor('traceroute-db', { Traceroute monitors have their own probe-specific settings, plus the standard monitor options shared across all check types. - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| @@ -207,7 +207,7 @@ Learn more in our docs on [Assertions](/detect/assertions). ### General Monitor Options -Friendly name for your Traceroute Monitor that will be displayed in the Checkly dashboard and used in notifications. +Friendly name for your Traceroute monitor that will be displayed in the Checkly dashboard and used in notifications. **Usage:** @@ -220,7 +220,7 @@ new TracerouteMonitor("my-traceroute", { -How often the Traceroute Monitor should run. Use the `Frequency` enum to set the check interval. +How often the Traceroute monitor should run. Use the `Frequency` enum to set the check interval. **Usage:** @@ -236,7 +236,7 @@ new TracerouteMonitor("my-traceroute", { -Array of [public location codes](/concepts/locations/#public-locations) where the Traceroute Monitor should run from. Use `privateLocations` for [private locations](/platform/private-locations/overview). Multiple locations help detect regional routing differences. +Array of [public location codes](/concepts/locations/#public-locations) where the Traceroute monitor should run from. Use `privateLocations` for [private locations](/platform/private-locations/overview). Multiple locations help detect regional routing differences. **Usage:** @@ -252,7 +252,7 @@ new TracerouteMonitor("global-path-monitor", { -Whether the Traceroute Monitor is enabled and will run according to its schedule. +Whether the Traceroute monitor is enabled and will run according to its schedule. **Usage:** diff --git a/constructs/url-monitor.mdx b/constructs/url-monitor.mdx index 68b1c7809..aed7cd81e 100644 --- a/constructs/url-monitor.mdx +++ b/constructs/url-monitor.mdx @@ -1,7 +1,7 @@ --- title: 'UrlMonitor Construct' description: 'Learn how to configure URL monitors with the Checkly CLI.' -sidebarTitle: 'URL Monitor' +sidebarTitle: 'URL monitor' canonical: 'https://www.checklyhq.com/docs/constructs/url-monitor/' --- @@ -10,13 +10,13 @@ import CheckIntent from '/snippets/check-intent.mdx'; import GeneralMonitorOptionsTable from '/snippets/general-monitor-options-table.mdx'; -Learn more about URL Monitors in [the URL monitor overview](/detect/uptime-monitoring/url-monitors/overview). +Learn more about URL monitors in [the URL monitor overview](/detect/uptime-monitoring/url-monitors/overview). -Use URL Monitors to track basic availability and HTTP status codes of your services and websites. The examples below show how to configure monitoring for different types of HTTP endpoints. +Use URL monitors to track basic availability and HTTP status codes of your services and websites. The examples below show how to configure monitoring for different types of HTTP endpoints. -Before creating URL Monitors, ensure you have: +Before creating URL monitors, ensure you have: - An initialized Checkly CLI project - URLs or HTTP endpoints you want to monitor @@ -73,7 +73,7 @@ new UrlMonitor("advanced-url-monitor", { The URL Monitoring configuration consists of specific URL monitoring options and inherited general monitoring options. - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| diff --git a/constructs/webhook-alert-channel.mdx b/constructs/webhook-alert-channel.mdx index b125c920c..a62f4142b 100644 --- a/constructs/webhook-alert-channel.mdx +++ b/constructs/webhook-alert-channel.mdx @@ -66,7 +66,7 @@ const webhookChannel = new WebhookAlertChannel('webhook-channel-1', { ## Configuration -### Webhook Alert Channel Options +### Webhook alert channel options Target URL for the webhook request. @@ -140,6 +140,6 @@ new WebhookAlertChannel('webhook-channel-1', { Secret token that you can use to validate the authenticity of the webhook and its payload. [Learn more about webhook secrets.](/integrations/alerts/webhooks#webhook-secrets) -### General Alert Channel Options +### General alert channel options diff --git a/detect/overview.mdx b/detect/overview.mdx index 0e797464d..1e505d40d 100644 --- a/detect/overview.mdx +++ b/detect/overview.mdx @@ -13,7 +13,7 @@ Monitor availability and response times across your website and infrastructure -Proactively validate real user interactions with API, browser, and multistep checks +Proactively validate real user interactions with API, browser, and Multistep checks diff --git a/detect/synthetic-monitoring/agentic-checks/migrate.mdx b/detect/synthetic-monitoring/agentic-checks/migrate.mdx index 2cda536e4..0d330c987 100644 --- a/detect/synthetic-monitoring/agentic-checks/migrate.mdx +++ b/detect/synthetic-monitoring/agentic-checks/migrate.mdx @@ -1,7 +1,7 @@ --- title: 'Migrate from Agentic Checks' sidebarTitle: 'Migrate Agentic Checks' -description: 'Replace Agentic Checks with Browser or Multistep Checks and enable automatic repair before December 1, 2026.' +description: 'Replace Agentic Checks with Browser or Multistep checks and enable automatic repair before December 1, 2026.' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/agentic-checks/migrate/' hidden: true --- @@ -10,7 +10,7 @@ hidden: true Agentic Checks are deprecated and will stop running on **December 1, 2026**. Replace each active Agentic Check before that date to keep monitoring its journey. -Create a Browser or Multistep Check for the same journey, verify the replacement, then deactivate the Agentic Check. This guide uses Browser and Multistep Checks because automatic repair can edit their scripts in Checkly. The replacement has its own results and history. +Create a Browser or Multistep check for the same journey, verify the replacement, then deactivate the Agentic Check. This guide uses Browser and Multistep checks because automatic repair can edit their scripts in Checkly. The replacement has its own results and history. You can create the replacement in two ways: @@ -65,7 +65,7 @@ Migrate one journey at a time. If the original prompt covered several unrelated ## Add automatic repair to other checks -You can enable automatic repair on Browser and Multistep Checks you already use. Open a check's **Check intent** settings and select **Initialize from saved check** to get an editable intent suggestion, or enter the intent manually. Review and save the intent, then expand **Automatic Repair** and set **Automatic repair behavior** to **On** and save the check. See [Add intent to an existing check](../../../resolve/automatic-check-repair#add-intent-to-an-existing-check). +You can enable automatic repair on Browser and Multistep checks you already use. Open a check's **Check intent** settings and select **Initialize from saved check** to get an editable intent suggestion, or enter the intent manually. Review and save the intent, then expand **Automatic Repair** and set **Automatic repair behavior** to **On** and save the check. See [Add intent to an existing check](../../../resolve/automatic-check-repair#add-intent-to-an-existing-check). ## AI invocation usage diff --git a/detect/synthetic-monitoring/agentic-checks/overview.mdx b/detect/synthetic-monitoring/agentic-checks/overview.mdx index 5725a2dca..536811ee6 100644 --- a/detect/synthetic-monitoring/agentic-checks/overview.mdx +++ b/detect/synthetic-monitoring/agentic-checks/overview.mdx @@ -43,7 +43,7 @@ Agentic Checks were designed for flows where the expected behavior is clear, but - Authentication or onboarding flows that need contextual checks - AI-powered product flows where the monitor should evaluate whether the user goal was completed, not whether the output matched exact text - Pages where you want the monitor to adapt when implementation details change -- Early monitoring coverage before you invest in a hand-written Browser Check or Playwright Check Suite +- Early monitoring coverage before you invest in a hand-written Browser check or Playwright Check Suite ## Prompt best practices @@ -79,7 +79,7 @@ Each run can produce: - User-facing artifacts collected during the run -For new monitoring, use [API Checks](/detect/synthetic-monitoring/api-checks/overview), [Browser Checks](/detect/synthetic-monitoring/browser-checks/overview), or [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview). [Automatic repair](../../../resolve/automatic-check-repair) can maintain supported checks with a saved intent. +For new monitoring, use [API checks](/detect/synthetic-monitoring/api-checks/overview), [Browser checks](/detect/synthetic-monitoring/browser-checks/overview), or [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview). [Automatic repair](../../../resolve/automatic-check-repair) can maintain supported checks with a saved intent. ## Variables, secrets, and skills diff --git a/detect/synthetic-monitoring/api-checks/api-structure.mdx b/detect/synthetic-monitoring/api-checks/api-structure.mdx index d00a69dcd..2e0988707 100644 --- a/detect/synthetic-monitoring/api-checks/api-structure.mdx +++ b/detect/synthetic-monitoring/api-checks/api-structure.mdx @@ -1,15 +1,15 @@ --- -title: 'API Check Structure' +title: 'API check structure' description: 'Learn how to structure your API checks with Playwright.' sidebarTitle: MaC Structure canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/api-checks/api-structure/' --- -**Monitoring as Code**: Learn more about the [API Check Construct](/constructs/api-check). +**Monitoring as Code**: Learn more about the [API check construct](/constructs/api-check). -## API Check Test Structure +## API check test structure ```typescript import { ApiCheck, AssertionBuilder, Frequency } from 'checkly/constructs' @@ -116,7 +116,7 @@ Validate complex response structures: ## Advanced Features -### Environment Variables +### Environment variables Use variables for dynamic content: ```javascript // Reference environment variables diff --git a/detect/synthetic-monitoring/api-checks/overview.mdx b/detect/synthetic-monitoring/api-checks/overview.mdx index 08d7b1225..87c43c2c9 100644 --- a/detect/synthetic-monitoring/api-checks/overview.mdx +++ b/detect/synthetic-monitoring/api-checks/overview.mdx @@ -1,11 +1,11 @@ --- -title: 'API Checks Overview' +title: 'API checks overview' description: 'Monitor API endpoints with comprehensive HTTP request validation, performance testing, and detailed response analysis.' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/api-checks/overview/' --- -**Monitoring as Code**: Learn more about the [API Check Construct](/constructs/api-check). +**Monitoring as Code**: Learn more about the [API check construct](/constructs/api-check). @@ -23,9 +23,9 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/api-check /> -## What are API Checks? +## What are API checks? -API checks are automated HTTP requests that validate API endpoint functionality by checking status codes, response content, headers, and performance metrics. They simulate real API usage patterns and help catch issues before they impact your users. You can create API checks in the UI, via the [API Check Construct](/constructs/api-check) or by importing your existing Swagger/OpenAPI spec. +API checks are automated HTTP requests that validate API endpoint functionality by checking status codes, response content, headers, and performance metrics. They simulate real API usage patterns and help catch issues before they impact your users. You can create API checks in the UI, via the [API check construct](/constructs/api-check) or by importing your existing Swagger/OpenAPI spec. **API checks are perfect for:** - REST API endpoint monitoring @@ -44,11 +44,11 @@ API checks are automated HTTP requests that validate API endpoint functionality -If you are looking to monitor complex API flows or data processing, you might want to consider using [Multistep Checks](/detect/synthetic-monitoring/multistep-checks/overview). +If you are looking to monitor complex API flows or data processing, you might want to consider using [Multistep checks](/detect/synthetic-monitoring/multistep-checks/overview). -## How API Checks Work +## How API checks work API checks perform comprehensive endpoint validation: @@ -62,7 +62,7 @@ API checks perform comprehensive endpoint validation: API checks are ideal for testing both internal services and external API dependencies your application relies on. -## API Check Results +## API check results API check results will expose key performance and correctness data about the HTTP response received from the target endpoint. diff --git a/detect/synthetic-monitoring/api-checks/quickstart.mdx b/detect/synthetic-monitoring/api-checks/quickstart.mdx index 36feced63..521b551a3 100644 --- a/detect/synthetic-monitoring/api-checks/quickstart.mdx +++ b/detect/synthetic-monitoring/api-checks/quickstart.mdx @@ -1,12 +1,12 @@ --- -title: 'Creating An API Check' +title: 'Creating an API check' description: 'Step-by-step guide to creating your first API check in Checkly using the web UI and CLI.' sidebarTitle: 'Quickstart' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/api-checks/quickstart/' --- -Learn more about all the [API Check capabilities](/detect/synthetic-monitoring/api-checks/overview) in the general overview. +Learn more about all the [API check capabilities](/detect/synthetic-monitoring/api-checks/overview) in the general overview. ![Screenshot of the create API check page](/images/docs/images/api-checks/overview-create-check.png) diff --git a/detect/synthetic-monitoring/api-checks/troubleshooting.mdx b/detect/synthetic-monitoring/api-checks/troubleshooting.mdx index c0ff55f27..7c10379a7 100644 --- a/detect/synthetic-monitoring/api-checks/troubleshooting.mdx +++ b/detect/synthetic-monitoring/api-checks/troubleshooting.mdx @@ -1,5 +1,5 @@ --- -title: 'API Check Troubleshooting' +title: 'API check troubleshooting' description: 'Learn how to troubleshoot API checks with Checkly.' sidebarTitle: Troubleshooting canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/api-checks/troubleshooting/' diff --git a/detect/synthetic-monitoring/browser-checks/examples.mdx b/detect/synthetic-monitoring/browser-checks/examples.mdx index 02e099ae0..783a1db1c 100644 --- a/detect/synthetic-monitoring/browser-checks/examples.mdx +++ b/detect/synthetic-monitoring/browser-checks/examples.mdx @@ -1,6 +1,6 @@ --- -title: 'Browser Check Examples' -description: 'Real-world examples and implementation patterns for monitoring user workflows with Checkly browser checks across different industries and scenarios.' +title: 'Browser check examples' +description: 'Real-world examples and implementation patterns for monitoring user workflows with Checkly Browser checks across different industries and scenarios.' sidebarTitle: 'Examples' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/examples/' --- @@ -726,9 +726,9 @@ test('Accessibility compliance validation', async ({ page }) => { ``` -Browser checks provide comprehensive validation of user experiences. Combine them with API checks and multistep checks for complete application monitoring coverage across all user touchpoints. +Browser checks provide comprehensive validation of user experiences. Combine them with API checks and Multistep checks for complete application monitoring coverage across all user touchpoints. -Use realistic test data and user scenarios in your browser checks to ensure they accurately represent actual user behavior and catch real-world issues. +Use realistic test data and user scenarios in your Browser checks to ensure they accurately represent actual user behavior and catch real-world issues. \ No newline at end of file diff --git a/detect/synthetic-monitoring/browser-checks/file-system.mdx b/detect/synthetic-monitoring/browser-checks/file-system.mdx index 52d86d8b0..8c921845f 100644 --- a/detect/synthetic-monitoring/browser-checks/file-system.mdx +++ b/detect/synthetic-monitoring/browser-checks/file-system.mdx @@ -1,12 +1,12 @@ --- title: File uploads, downloads and the file system -description: "Handle file uploads and downloads in browser checks using Playwright's download event, the Download object, and setInputFiles to validate files end to end." +description: "Handle file uploads and downloads in Browser checks using Playwright's download event, the Download object, and setInputFiles to validate files end to end." sidebarTitle: File system canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/file-system/' --- -You might want to use (binary) files in your browser checks. For example, you might want to upload a file to an upload +You might want to use (binary) files in your Browser checks. For example, you might want to upload a file to an upload form in your webapp. Or, you might want to validate some aspect of a file that is available for download on your app. @@ -201,14 +201,14 @@ test('Save file in directory', async ({ page }) => { Due to this sandbox, certain Node.js variables are adapted to our platform and have values we set for them. The behaviour -is slightly different when creating a browser check in the Web UI or using the Checkly CLI. +is slightly different when creating a Browser check in the Web UI or using the Checkly CLI. -When creating a browser check in the Web UI, the variables are: +When creating a Browser check in the Web UI, the variables are: * `__dirname` will have the value of `/` * `__filename` will have the value of `/script.js` -When creating a browser check using the Checkly CLI the variables are: +When creating a Browser check using the Checkly CLI the variables are: * `__dirname` will have the value of `/` * `__filename` will have the value of the actual file in your code base, relative to the project root. diff --git a/detect/synthetic-monitoring/browser-checks/mac-structure.mdx b/detect/synthetic-monitoring/browser-checks/mac-structure.mdx index dbb52809e..45a84c331 100644 --- a/detect/synthetic-monitoring/browser-checks/mac-structure.mdx +++ b/detect/synthetic-monitoring/browser-checks/mac-structure.mdx @@ -1,16 +1,16 @@ --- -title: 'Browser Check Structure' -description: 'Learn how to structure your Browser Checks with Monitoring as Code.' +title: 'Browser check structure' +description: 'Learn how to structure your Browser checks with Monitoring as Code.' sidebarTitle: MaC Structure canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/mac-structure/' --- import GenericRuntimeVariablesTable from '/snippets/generic-runtime-variables-table.mdx'; -Monitoring as Code works by connecting Playwrighttest files with Checkly constructs to handle the end-to-endconfiguration of your Browser Check. +Monitoring as Code works by connecting Playwrighttest files with Checkly constructs to handle the end-to-endconfiguration of your Browser check. -## Browser Check Construct -The Browser Check construct is used to configure your monitoring settings, such as frequency, locations, and tags. Learn more about the [Browser Check Construct](/constructs/browser-check) +## Browser check construct +The Browser check construct is used to configure your monitoring settings, such as frequency, locations, and tags. Learn more about the [Browser check construct](/constructs/browser-check) ```ts browser-check.ts import { BrowserCheck, Frequency } from 'checkly/constructs' @@ -28,7 +28,7 @@ new BrowserCheck('browser-check-1', { ## Test Script Structure -Checkly uses Playwright to power Browser Checks. [Playwright](https://playwright.dev/docs/intro) is a robust, open-source framework for browser automation and end-to-end web application testing. It enables you to write atomic, reliable tests and easily control interactions within a web page. Browser checks execute automated test scripts in real browsers. +Checkly uses Playwright to power Browser checks. [Playwright](https://playwright.dev/docs/intro) is a robust, open-source framework for browser automation and end-to-end web application testing. It enables you to write atomic, reliable tests and easily control interactions within a web page. Browser checks execute automated test scripts in real browsers. ```typescript login.spec.ts // Use environment-specific URLs and credentials diff --git a/detect/synthetic-monitoring/browser-checks/overview.mdx b/detect/synthetic-monitoring/browser-checks/overview.mdx index 9d571ce66..1af354f7a 100644 --- a/detect/synthetic-monitoring/browser-checks/overview.mdx +++ b/detect/synthetic-monitoring/browser-checks/overview.mdx @@ -1,12 +1,12 @@ --- -title: 'Browser Checks Overview' +title: 'Browser checks overview' description: 'Monitor end-to-end user flows and realistic interactions with automated browser testing using Playwright.' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/overview/' --- -**Monitoring as Code**: Learn more about the [Browser Check Construct](/constructs/browser-check). +**Monitoring as Code**: Learn more about the [Browser check construct](/constructs/browser-check). @@ -24,7 +24,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-c /> -## What are Browser Checks? +## What are Browser checks? Browser checks are automated tests that use real browsers to interact with your web applications. They simulate user journeys like logging in, filling out forms, making purchases, or navigating through complex workflows, ensuring your critical user paths work and perform correctly. @@ -41,7 +41,7 @@ Supported Browsers: - **Mobile Simulation**: Test responsive designs and mobile workflows -## How Browser Checks Work +## How Browser checks work Checkly uses Playwright to power your Browser checks. [Playwright](https://playwright.dev/docs/intro) is a robust, open-source framework for browser automation and end-to-end web application testing. It enables you to write idiomatic, reliable tests and easily control interactions within a web page. Browser checks execute automated test scripts in real browsers: @@ -66,7 +66,7 @@ Create your Playwright test file in the Checkly IDE, then configure the check se Browser checks use Playwright's test framework with a familiar structure. -It works by connecting constructs to handle the configuration of your Browser Check, and then referencing the test file in your repository. +It works by connecting constructs to handle the configuration of your Browser check, and then referencing the test file in your repository. ```ts browser-check.ts import { BrowserCheck, Frequency } from 'checkly/constructs' @@ -108,9 +108,9 @@ test('User login workflow', async ({ page }) => { To learn more about Playwright, see the our [Playwright documentation](/learn/playwright/overview). -## Browser Check Results +## Browser check results -Individual browser check results contain: +Individual Browser check results contain: * A short check summary, including errors broken down by category ![check results browser summary](/images/docs/images/monitoring/check-results-browser-summary.png) diff --git a/detect/synthetic-monitoring/browser-checks/performance-metrics.mdx b/detect/synthetic-monitoring/browser-checks/performance-metrics.mdx index 24065346b..92392f072 100644 --- a/detect/synthetic-monitoring/browser-checks/performance-metrics.mdx +++ b/detect/synthetic-monitoring/browser-checks/performance-metrics.mdx @@ -1,6 +1,6 @@ --- title: Performance & Web Vitals -description: 'Web Vitals for browser checks' +description: 'Web Vitals for Browser checks' sidebarTitle: 'Performance Metrics' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/performance-metrics/' --- @@ -22,7 +22,7 @@ Checkly automatically collect Network Waterfalls & Performance signals (**Web Vi -Checkly only collects tracing and web vitals data if your browser check meets the following criteria: +Checkly only collects tracing and web vitals data if your Browser check meets the following criteria: - It is based on **Playwright**. - It runs on any **runtime above [2021.06](/cli/checkly-runtimes)** diff --git a/detect/synthetic-monitoring/browser-checks/playwright-support.mdx b/detect/synthetic-monitoring/browser-checks/playwright-support.mdx index fd85cf989..398adc77a 100644 --- a/detect/synthetic-monitoring/browser-checks/playwright-support.mdx +++ b/detect/synthetic-monitoring/browser-checks/playwright-support.mdx @@ -1,12 +1,12 @@ --- title: Playwright Support in Checkly -description: "See which Playwright features Checkly's browser checks support, from trace files and video recordings to auto-waiting, locators, and visual regression testing." +description: "See which Playwright features Checkly's Browser checks support, from trace files and video recordings to auto-waiting, locators, and visual regression testing." sidebarTitle: 'Playwright Support' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/playwright-support/' --- -Checkly natively supports running complex browser checks that mimic real user actions using Playwright, the best automation framework. Playwright and Checkly together elevate your monitoring and debugging experience by providing: +Checkly natively supports running complex Browser checks that mimic real user actions using Playwright, the best automation framework. Playwright and Checkly together elevate your monitoring and debugging experience by providing: - Detailed trace files with step-by-step information on your test cases - Video recordings of browser sessions @@ -27,8 +27,8 @@ This is the list of Playwright features that are currently supported. We will up | API testing | Yes | | Custom fixtures | Yes | | Reporters | JSON | -| Typescript | Yes | -| Global configuration | Yes, a subset of playwright config options. | +| TypeScript | Yes | +| Global configuration | Yes, a subset of Playwright config options. | | Visual comparisons | Yes | | Test retry | No, configure a [retry strategy](/communicate/alerts/retries) in the check settings to retry a check. | | Parallelism and sharding | No | @@ -62,7 +62,7 @@ We currently support the following configuration options. We will update this li | `projects` | ❌ | | `webServer` | ❌ | - For more information about the `global` options you can check playwright official documentation [Test configuration](https://playwright.dev/docs/test-configuration) + For more information about the `global` options you can check Playwright official documentation [Test configuration](https://playwright.dev/docs/test-configuration) | Option | Supported | @@ -98,7 +98,7 @@ We currently support the following configuration options. We will update this li | `trace` | ❌ | | `video` | ❌ | - For more information about the `use` options you can check playwright official documentation [Test use options](https://playwright.dev/docs/test-use-options) + For more information about the `use` options you can check Playwright official documentation [Test use options](https://playwright.dev/docs/test-use-options) | Option | Supported | @@ -107,7 +107,7 @@ We currently support the following configuration options. We will update this li | `toHaveScreenshot ` | ✅ | | `toMatchSnapshot ` | ✅ | - For more information about the `expect` options you can check playwright official documentation [Test Expect options](https://playwright.dev/docs/test-configuration#expect-options) + For more information about the `expect` options you can check Playwright official documentation [Test Expect options](https://playwright.dev/docs/test-configuration#expect-options) @@ -288,7 +288,7 @@ test.describe('two tests', () => { - An executed browser check that includes multiple Playwright test cases still counts as a single check run towards your pricing plan's defined limits. + An executed Browser check that includes multiple Playwright test cases still counts as a single check run towards your pricing plan's defined limits. ## Interactions & Navigations diff --git a/detect/synthetic-monitoring/browser-checks/quickstart.mdx b/detect/synthetic-monitoring/browser-checks/quickstart.mdx index 231991dfb..e0ec968aa 100644 --- a/detect/synthetic-monitoring/browser-checks/quickstart.mdx +++ b/detect/synthetic-monitoring/browser-checks/quickstart.mdx @@ -1,6 +1,6 @@ --- -title: 'Creating A Browser Check' -description: 'Get started with Checkly by creating your first Browser Check' +title: 'Creating a Browser check' +description: 'Get started with Checkly by creating your first Browser check' sidebarTitle: 'Quickstart' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/quickstart/' --- @@ -9,12 +9,12 @@ import CliAuth from '/snippets/cli-auth.mdx'; import CliProjectInit from '/snippets/cli-project-init.mdx'; -Learn more about all the [Browser Check capabilities](/detect/synthetic-monitoring/browser-checks/overview) in the general overview. +Learn more about all the [Browser check capabilities](/detect/synthetic-monitoring/browser-checks/overview) in the general overview. -This guide will walk you through creating your first Browser Check with Checkly. +This guide will walk you through creating your first Browser check with Checkly. -Browser Checks are perfect for monitoring realistic user flows within your application or services. If you are looking for monitoring general availability, check out the [Uptime Monitor Quickstart](/detect/uptime-monitoring/url-monitors/quickstart). +Browser checks are perfect for monitoring realistic user flows within your application or services. If you are looking for monitoring general availability, check out the [Uptime Monitor Quickstart](/detect/uptime-monitoring/url-monitors/quickstart). - A Checkly account (sign up at [checklyhq.com](https://checklyhq.com)) @@ -23,7 +23,7 @@ Browser Checks are perfect for monitoring realistic user flows within your appli - + 1. **Head to [Create a Check](https://app.checklyhq.com/accounts/create)** - 2. **Choose from one of the Browser Check templates** to start from a working example + 2. **Choose from one of the Browser check templates** to start from a working example @@ -145,9 +145,9 @@ Once your check is active: Now that you have your first check running: -- **Add API Checks**: Monitor your backend services and APIs -- **Create Check Groups**: Organize related checks together -- **Set up Status Pages**: Share uptime information with users +- **Add API checks**: Monitor your backend services and APIs +- **Create check groups**: Organize related checks together +- **Set up status pages**: Share uptime information with users - **Explore Integrations**: Connect with Slack, PagerDuty, or other tools ## Upgrading to Monitoring as Code diff --git a/detect/synthetic-monitoring/browser-checks/timeouts.mdx b/detect/synthetic-monitoring/browser-checks/timeouts.mdx index cbe2e4d6a..f0023cfd7 100644 --- a/detect/synthetic-monitoring/browser-checks/timeouts.mdx +++ b/detect/synthetic-monitoring/browser-checks/timeouts.mdx @@ -1,5 +1,5 @@ --- -title: 'Browser Check Timeouts' +title: 'Browser check timeouts' description: 'Browser check timeouts.' sidebarTitle: 'Timeouts' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/timeouts/' @@ -17,7 +17,7 @@ There are different kinds of timeouts you will encounter while working with Brow Checkly runs your Browser check code for a maximum of **240 seconds**. Tests that exceed this time will be capped and -time out. Everything in your Browser Check needs to happen within those 240 seconds, no matter what. +time out. Everything in your Browser check needs to happen within those 240 seconds, no matter what. Playwright does offer multiple [configurable timeouts](https://playwright.dev/docs/test-timeouts). Make sure you configure these in a way that prevents your check from hitting the general 240 seconds timeout. @@ -64,7 +64,7 @@ test('add item to wishlist', async ({ page }) => { ### Your check run has reached the maximum run time of 240000 ms. In this case, your script is hitting Checkly's 240s total Browser check timeout. This can't be configured and is in -place to prevent checks from running way longer than acceptable. No assets will be available for review after the check has gone over the maximum run time. If you encounter this, try to make your check shorter by following [best practices](/learn/playwright/writing-tests/). Additionally, to ensure your assets are saved, please set a test timeout lower than the browser check execution timeout. +place to prevent checks from running way longer than acceptable. No assets will be available for review after the check has gone over the maximum run time. If you encounter this, try to make your check shorter by following [best practices](/learn/playwright/writing-tests/). Additionally, to ensure your assets are saved, please set a test timeout lower than the Browser check execution timeout. ### Timeout 20000ms exceeded diff --git a/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx b/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx index 3e77530ae..6d33f46a5 100644 --- a/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx +++ b/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx @@ -1,6 +1,6 @@ --- title: 'Trouble Shotting and Debugging' -description: 'Learn how to troubleshoot browser checks.' +description: 'Learn how to troubleshoot Browser checks.' sidebarTitle: Troubleshooting canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/troubleshooting/' --- diff --git a/detect/synthetic-monitoring/browser-checks/visual-regressions.mdx b/detect/synthetic-monitoring/browser-checks/visual-regressions.mdx index 5b1ea047d..967f8f5a3 100644 --- a/detect/synthetic-monitoring/browser-checks/visual-regressions.mdx +++ b/detect/synthetic-monitoring/browser-checks/visual-regressions.mdx @@ -31,7 +31,7 @@ The TL;DR is that you can: Starting with visual regression testing takes just three easy steps: 1. Add a single `expect(page).toHaveScreenshot()` line of code to - your browser check script, like the example below. + your Browser check script, like the example below. @@ -55,7 +55,7 @@ Starting with visual regression testing takes just three easy steps: -2. Run your browser check. The first time you run it, you will get an error indicating that no golden image / reference +2. Run your Browser check. The first time you run it, you will get an error indicating that no golden image / reference snapshot exists yet. ``` @@ -242,13 +242,13 @@ and deploy any changes either directly from your local machine or from your CI/C In a typical scenario, you would follow the steps below: -1. Create or update a browser check with visual regression or snapshot testing on your local machine. +1. Create or update a Browser check with visual regression or snapshot testing on your local machine. 2. Generate the golden image / reference snapshot(s). ```bash npx checkly test --update-snapshots ``` - The resulting files are stored in a `some-file-prepend.ts-snapshots` folder next to your browser check script. -3. Commit the browser check script and the golden image / reference snapshot(s) to your version control system. + The resulting files are stored in a `some-file-prepend.ts-snapshots` folder next to your Browser check script. +3. Commit the Browser check script and the golden image / reference snapshot(s) to your version control system. 4. Push your code to your CI/CD pipeline. 5. In your CI/CD pipeline, test your checks before deploying. Test results will be uploaded to Checkly's test sessions for review. ```bash diff --git a/detect/synthetic-monitoring/multistep-checks/degraded-states.mdx b/detect/synthetic-monitoring/multistep-checks/degraded-states.mdx index 93d0df5dd..5c93399c9 100644 --- a/detect/synthetic-monitoring/multistep-checks/degraded-states.mdx +++ b/detect/synthetic-monitoring/multistep-checks/degraded-states.mdx @@ -1,5 +1,5 @@ --- -title: Degraded States In Multistep Checks +title: Degraded states in Multistep checks description: "Signal non-critical slowdowns in Multistep checks with the degraded state, using soft assertions and the @checkly/playwright-helpers markCheckAsDegraded helper." sidebarTitle: Degraded States diff --git a/detect/synthetic-monitoring/multistep-checks/examples.mdx b/detect/synthetic-monitoring/multistep-checks/examples.mdx index e2f40529f..8ee16fe9e 100644 --- a/detect/synthetic-monitoring/multistep-checks/examples.mdx +++ b/detect/synthetic-monitoring/multistep-checks/examples.mdx @@ -1,6 +1,6 @@ --- -title: 'Multistep Check Examples' +title: 'Multistep check examples' description: 'Learn how to use Multistep checks with Playwright.' sidebarTitle: Examples canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/multistep-checks/examples/' diff --git a/detect/synthetic-monitoring/multistep-checks/file-system.mdx b/detect/synthetic-monitoring/multistep-checks/file-system.mdx index 6e63b5c71..8cd9edf27 100644 --- a/detect/synthetic-monitoring/multistep-checks/file-system.mdx +++ b/detect/synthetic-monitoring/multistep-checks/file-system.mdx @@ -1,6 +1,6 @@ --- title: Uploading & Downloading Files To The File System -description: "Upload and download binary files in multistep checks with Playwright's request object, hosting files externally and validating them with HTTP requests." +description: "Upload and download binary files in Multistep checks with Playwright's request object, hosting files externally and validating them with HTTP requests." sidebarTitle: File System canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/multistep-checks/file-system/' @@ -97,14 +97,14 @@ test('Save file in directory', async ({ page }) => { Due to this sandbox, certain Node.js variables are adapted to our platform and have values we set for them. The behaviour -is slightly different when creating a browser check in the Web UI or using the Checkly CLI. +is slightly different when creating a Browser check in the Web UI or using the Checkly CLI. -When creating a browser check in the Web UI, the variables are: +When creating a Browser check in the Web UI, the variables are: * `__dirname` will have the value of `/` * `__filename` will have the value of `/script.js` -When creating a browser check using the Checkly CLI the variables are: +When creating a Browser check using the Checkly CLI the variables are: * `__dirname` will have the value of `/` * `__filename` will have the value of the actual file in your code base, relative to the project root. \ No newline at end of file diff --git a/detect/synthetic-monitoring/multistep-checks/multistep-structure.mdx b/detect/synthetic-monitoring/multistep-checks/multistep-structure.mdx index d82929213..de1557359 100644 --- a/detect/synthetic-monitoring/multistep-checks/multistep-structure.mdx +++ b/detect/synthetic-monitoring/multistep-checks/multistep-structure.mdx @@ -1,15 +1,15 @@ --- -title: 'Multistep Check Structure' -description: 'Learn how to structure your multistep checks with Playwright.' +title: 'Multistep check structure' +description: 'Learn how to structure your Multistep checks with Playwright.' sidebarTitle: MaC Structure canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/multistep-checks/multistep-structure/' --- -**Monitoring as Code**: Learn more about the [Multistep Check Construct](/constructs/multistep-check). +**Monitoring as Code**: Learn more about the [Multistep check construct](/constructs/multistep-check). -## Multistep Check Construct +## Multistep check construct ```ts multistep-check.ts import { MultiStepCheck, Frequency } from 'checkly/constructs' diff --git a/detect/synthetic-monitoring/multistep-checks/overview.mdx b/detect/synthetic-monitoring/multistep-checks/overview.mdx index e642ef74e..3024c6984 100644 --- a/detect/synthetic-monitoring/multistep-checks/overview.mdx +++ b/detect/synthetic-monitoring/multistep-checks/overview.mdx @@ -1,5 +1,5 @@ --- -title: 'Multistep Checks Overview' +title: 'Multistep checks overview' description: 'Monitor complex API workflows with sequential requests using Playwright API testing mode for comprehensive end-to-end validation.' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/multistep-checks/overview/' @@ -8,7 +8,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/multistep import GenericRuntimeVariablesTable from '/snippets/generic-runtime-variables-table.mdx'; -**Monitoring as Code**: Learn more about the [Multistep Check Construct](/constructs/multistep-check). +**Monitoring as Code**: Learn more about the [Multistep check construct](/constructs/multistep-check). @@ -26,7 +26,7 @@ import GenericRuntimeVariablesTable from '/snippets/generic-runtime-variables-ta /> -## What are Multistep Checks? +## What are Multistep checks? Multistep checks are API-focused tests that perform multiple sequential HTTP requests within a single check. They're designed to test complete user workflows that span multiple API endpoints, ensuring that complex business processes work correctly from start to finish. Multistep checks use Playwright's `request` fixture. @@ -38,7 +38,7 @@ Multistep checks are API-focused tests that perform multiple sequential HTTP req - Complex business transaction testing - API dependency chain validation -## How Multistep Checks Work +## How Multistep checks work Multistep checks execute a series of API requests in sequence, with the ability to pass data between steps: @@ -81,13 +81,13 @@ As with Browser checks, Checkly runs Multistep checks for a maximum of 240s. Scr ## Built-in Runtime Variables -The Multistep Check [runtime](/platform/runtimes/overview) exposes a set of environment variables (e.g. `process.env.CHECK_NAME`) that indicate what check, check type etc. you are running. +The Multistep check [runtime](/platform/runtimes/overview) exposes a set of environment variables (e.g. `process.env.CHECK_NAME`) that indicate what check, check type etc. you are running. [Learn more about environment variables.](/platform/variables) -## Multistep Check Results +## Multistep check results Multistep check results are navigated using the tree on the left side of the screen. If you are running checks in parallel, first select the location you are interested in. diff --git a/detect/synthetic-monitoring/multistep-checks/quickstart.mdx b/detect/synthetic-monitoring/multistep-checks/quickstart.mdx index e94de3724..26c37211d 100644 --- a/detect/synthetic-monitoring/multistep-checks/quickstart.mdx +++ b/detect/synthetic-monitoring/multistep-checks/quickstart.mdx @@ -1,15 +1,15 @@ --- -title: 'Creating A Multistep Check' -description: 'Step-by-step guide to creating your first multistep check in Checkly for monitoring complex API workflows and business processes.' +title: 'Creating a Multistep check' +description: 'Step-by-step guide to creating your first Multistep check in Checkly for monitoring complex API workflows and business processes.' sidebarTitle: 'Quickstart' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/multistep-checks/quickstart/' --- -Learn more about all the [Multistep Check capabilities](/detect/synthetic-monitoring/multistep-checks/overview) in the general overview. +Learn more about all the [Multistep check capabilities](/detect/synthetic-monitoring/multistep-checks/overview) in the general overview. -Multistep checks allow you to monitor complex API workflows that span multiple endpoints and validate complete business processes. In this comprehensive guide, you'll create your first multistep check to ensure your critical API workflows function correctly end-to-end. +Multistep checks allow you to monitor complex API workflows that span multiple endpoints and validate complete business processes. In this comprehensive guide, you'll create your first Multistep check to ensure your critical API workflows function correctly end-to-end. You'll need a series of API endpoints that work together to complete a business process. Multistep checks excel at testing workflows that require data to flow from one API call to the next. diff --git a/detect/synthetic-monitoring/multistep-checks/troubleshooting.mdx b/detect/synthetic-monitoring/multistep-checks/troubleshooting.mdx index 540799789..bcdf1bf6a 100644 --- a/detect/synthetic-monitoring/multistep-checks/troubleshooting.mdx +++ b/detect/synthetic-monitoring/multistep-checks/troubleshooting.mdx @@ -1,7 +1,7 @@ --- -title: 'Troubleshooting Multistep Checks' -description: 'Learn how to troubleshoot multistep checks.' +title: 'Troubleshooting Multistep checks' +description: 'Learn how to troubleshoot Multistep checks.' sidebarTitle: Troubleshooting canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/multistep-checks/troubleshooting/' --- diff --git a/detect/synthetic-monitoring/multistep-checks/websockets.mdx b/detect/synthetic-monitoring/multistep-checks/websockets.mdx index acad31245..00643930a 100644 --- a/detect/synthetic-monitoring/multistep-checks/websockets.mdx +++ b/detect/synthetic-monitoring/multistep-checks/websockets.mdx @@ -1,6 +1,6 @@ --- title: WebSockets on Multistep checks -description: "Monitor a WebSocket endpoint from a multistep check by scripting a connection, sending messages, and validating the responses you get back." +description: "Monitor a WebSocket endpoint from a Multistep check by scripting a connection, sending messages, and validating the responses you get back." sidebarTitle: WebSockets canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/multistep-checks/websockets/' diff --git a/detect/synthetic-monitoring/overview.mdx b/detect/synthetic-monitoring/overview.mdx index bcacaed65..c6193d982 100644 --- a/detect/synthetic-monitoring/overview.mdx +++ b/detect/synthetic-monitoring/overview.mdx @@ -15,19 +15,19 @@ Synthetic monitoring goes beyond simple uptime checks by proactively validating Checkly provides four check types to comprehensively monitor your applications: - + Monitor individual API endpoints with detailed request/response validation. - + Test complex API workflows with sequential requests and data flow validation. - + Simulate real user interactions with automated browser testing using Playwright. @@ -45,15 +45,15 @@ Migrate your existing Playwright projects and tests to Checkly. Ready to implement comprehensive synthetic monitoring? Choose your starting point based on your monitoring needs: - + Start with backend API monitoring and validation - + Monitor user experiences with automated browser testing - + Test complex workflows with sequential API requests diff --git a/detect/synthetic-monitoring/playwright-checks/custom-dependencies.mdx b/detect/synthetic-monitoring/playwright-checks/custom-dependencies.mdx index 31c61affd..e22cce96f 100644 --- a/detect/synthetic-monitoring/playwright-checks/custom-dependencies.mdx +++ b/detect/synthetic-monitoring/playwright-checks/custom-dependencies.mdx @@ -8,7 +8,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/playwrigh Use the [Checkly CLI](/cli/overview) to turn your Playwright tests into globally distributed monitors. Checkly uses your existing `package.json` dependencies and Playwright configuration. -Playwright Check Suites do not use Checkly runtimes. Browser Checks and Multistep Checks use `runtimeId` to select a managed runtime with fixed Checkly-provided dependencies. Playwright Check Suites install your project dependencies and use `engine` to select the JavaScript engine version. +Playwright Check Suites do not use Checkly runtimes. Browser checks and Multistep checks use `runtimeId` to select a managed runtime with fixed Checkly-provided dependencies. Playwright Check Suites install your project dependencies and use `engine` to select the JavaScript engine version. ## Using JavaScript/Node.js dependencies @@ -209,7 +209,7 @@ Checkly automatically retries transient failures during setup steps. Cache downl **Public Locations**: Dependency caching is **Always ON**. -**Private Locations**: Dependency caching is **OFF by default**. To enable caching and speed up check runs, set `DEPENDENCY_CACHE=CHECKLY_S3` in your [agent configuration](/platform/private-locations/agent-configuration). +**Private locations**: Dependency caching is **OFF by default**. To enable caching and speed up check runs, set `DEPENDENCY_CACHE=CHECKLY_S3` in your [agent configuration](/platform/private-locations/agent-configuration). ## Playwright browser caching @@ -219,12 +219,12 @@ Checkly caches Playwright browsers so that runs don't download them every time. Checkly caches Playwright browsers across all public regions to reduce startup time. When a new Playwright version is available, runs download browsers until Checkly updates the shared cache. -### Browser caching on Private Locations -Checkly caches Playwright browsers on each Private Location agent, grouped by Playwright version. +### Browser caching on private locations +Checkly caches Playwright browsers on each private location agent, grouped by Playwright version. When a matching version exists in cache, Checkly skips the download — reducing startup time and making runs more reliable. -Browser caching requires Private Location agent v8.2.0 or later. +Browser caching requires private location agent v8.2.0 or later. diff --git a/detect/synthetic-monitoring/playwright-checks/environment-variables.mdx b/detect/synthetic-monitoring/playwright-checks/environment-variables.mdx index 5d54efaba..d8ad81fd3 100644 --- a/detect/synthetic-monitoring/playwright-checks/environment-variables.mdx +++ b/detect/synthetic-monitoring/playwright-checks/environment-variables.mdx @@ -1,13 +1,13 @@ --- -title: Playwright Check Suite Environment Variables -sidebarTitle: Environment Variables +title: Playwright Check Suite environment variables +sidebarTitle: Environment variables description: "Customize your Playwright Check Suite runs based on the execution environment." tags: ["synthetic-monitoring", "playwright-checks", "environment-variables"] canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/playwright-checks/environment-variables/' --- - To create and manage environment variables and secrets, including inheritance and where to set them, see the [Environment Variables documentation](/platform/variables). + To create and manage environment variables and secrets, including inheritance and where to set them, see the [environment variables documentation](/platform/variables). ## Built-in variables in Playwright Check Suites diff --git a/detect/synthetic-monitoring/playwright-checks/overview.mdx b/detect/synthetic-monitoring/playwright-checks/overview.mdx index 23e2638db..1da4e625e 100644 --- a/detect/synthetic-monitoring/playwright-checks/overview.mdx +++ b/detect/synthetic-monitoring/playwright-checks/overview.mdx @@ -65,7 +65,7 @@ Control which tests run as monitors using: - **Projects**: Select browser and project configurations from your Playwright config with `pwProjects` - **Tags**: Choose tests marked with specific tags (e.g., `@critical`, `@smoke`) with `pwTags` - **Combinations**: Mix tags and projects for precise control -- **testCommand**: Use `npx playwright test ...` to select the tests you want to create a monitor for, using playwright flags like `--grep-invert` or `--projects` +- **testCommand**: Use `npx playwright test ...` to select the tests you want to create a monitor for, using Playwright flags like `--grep-invert` or `--projects` Configure test selection in your `checkly.config.ts` file: diff --git a/detect/synthetic-monitoring/playwright-checks/performance-metrics.mdx b/detect/synthetic-monitoring/playwright-checks/performance-metrics.mdx index 8fcfb6b1d..9b3ad9290 100644 --- a/detect/synthetic-monitoring/playwright-checks/performance-metrics.mdx +++ b/detect/synthetic-monitoring/playwright-checks/performance-metrics.mdx @@ -117,6 +117,6 @@ Checkly reports these visits honestly rather than showing stale or misleading nu A soft-nav row with mostly empty cells is intentional, not a failure to collect data. Read its INP, and the INP breakdown, for that route's responsiveness. -## Web Vitals for browser checks +## Web Vitals for Browser checks Classic [Browser checks](/detect/synthetic-monitoring/browser-checks/performance-metrics) collect the same Web Vitals with the same scoring. Playwright Check Suites report them per page visit across a whole suite, and add the LCP and INP attribution above. diff --git a/detect/synthetic-monitoring/playwright-monitoring-comparison.mdx b/detect/synthetic-monitoring/playwright-monitoring-comparison.mdx index d0eca292d..83414003a 100644 --- a/detect/synthetic-monitoring/playwright-monitoring-comparison.mdx +++ b/detect/synthetic-monitoring/playwright-monitoring-comparison.mdx @@ -8,7 +8,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/playwrigh import { checkDurations } from '/snippets/check-comparison.mdx' -[MultiStep Checks](/detect/synthetic-monitoring/multistep-checks/overview), [Browser Checks](/detect/synthetic-monitoring/browser-checks/overview), and [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) use Playwright for synthetic monitoring. The different check types vary in capabilities, flexibility, and use cases. +[Multistep checks](/detect/synthetic-monitoring/multistep-checks/overview), [Browser checks](/detect/synthetic-monitoring/browser-checks/overview), and [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) use Playwright for synthetic monitoring. The different check types vary in capabilities, flexibility, and use cases. After logging into the Checkly web application, you can use the built-in editor to write Playwright code to monitor your APIs and sites. **Use MultiStep and Browser checks to get started quickly via the user interface**. Checkly handles code storage, configuration of advanced settings, and dependency updates with [runtimes](/platform/runtimes/overview/). @@ -16,13 +16,13 @@ However, when your monitoring setup needs to scale with your growing project req All Playwright-based checks can be created, updated and configured as code. But, when should you use which? -## When to use MultiStep Checks +## When to use Multistep checks -Choose [MultiStep Checks](/detect/synthetic-monitoring/multistep-checks/overview) when you need to monitor complex API workflows with sequential requests using the familiar Playwright API. MultiStep Check runs are based on a single `spec.ts` file, limited to making HTTP requests (there's no browser available) and **the max check run duration is capped at { checkDurations.multiStep }**. +Choose [Multistep checks](/detect/synthetic-monitoring/multistep-checks/overview) when you need to monitor complex API workflows with sequential requests using the familiar Playwright API. Multistep check runs are based on a single `spec.ts` file, limited to making HTTP requests (there's no browser available) and **the max check run duration is capped at { checkDurations.multiStep }**. -## When to use Browser Checks +## When to use Browser checks -Choose [Browser Checks](/detect/synthetic-monitoring/browser-checks/overview) when you need to monitor end-to-end user flows and realistic interactions with automated browser testing using Playwright. Browser Check runs are based on a single `spec.ts` file, support the headless Chromium/Chrome browser and **the max check run duration is capped at { checkDurations.browser }**. +Choose [Browser checks](/detect/synthetic-monitoring/browser-checks/overview) when you need to monitor end-to-end user flows and realistic interactions with automated browser testing using Playwright. Browser check runs are based on a single `spec.ts` file, support the headless Chromium/Chrome browser and **the max check run duration is capped at { checkDurations.browser }**. ## When to use Playwright Check Suites @@ -36,7 +36,7 @@ Playwright Check Suites are the native way to run your Playwright project in pro ## Feature comparison -| Feature | Playwright Check Suites | Browser Check | MultiStep Check | +| Feature | Playwright Check Suites | Browser check | Multistep check | |-------------------------------------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| | Supports *Monitoring as Code* | Yes | Yes | Yes | | [Test fixtures](https://playwright.dev/docs/test-fixtures) | `page`, `context`, `browser`, `browserName`, `request` | `page`, `context`, `browser`, `browserName`, `request` | `request` | diff --git a/detect/testing/creating-your-first-test.mdx b/detect/testing/creating-your-first-test.mdx index dc1b05ae0..113db93cc 100644 --- a/detect/testing/creating-your-first-test.mdx +++ b/detect/testing/creating-your-first-test.mdx @@ -148,7 +148,7 @@ After deployment, you can: ## Advanced Check Configuration -For more control over your browser checks: +For more control over your Browser checks: ```ts __checks__/advanced-browser.check.ts import { BrowserCheck, Frequency, RetryStrategyBuilder } from 'checkly/constructs' @@ -175,7 +175,7 @@ new BrowserCheck('advanced-check', { 2. **Use Page Object Model**: Organize your tests with reusable page objects 3. **Test Critical User Journeys**: Focus on the most important user flows 4. **Set Appropriate Frequencies**: Don't over-monitor; balance coverage with costs -5. **Use Environment Variables**: Keep sensitive data and URLs configurable +5. **Use environment variables**: Keep sensitive data and URLs configurable 6. **Add Meaningful Assertions**: Test both functionality and performance 7. **Take Screenshots**: Helpful for debugging when tests fail 8. **Monitor APIs and UI**: Combine browser and API checks for comprehensive coverage diff --git a/detect/testing/overview.mdx b/detect/testing/overview.mdx index 24791c5b5..c923313fc 100644 --- a/detect/testing/overview.mdx +++ b/detect/testing/overview.mdx @@ -52,12 +52,12 @@ Create a single test and use it for both pre-production validation and productio Create a [Playwright test](/detect/synthetic-monitoring/playwright-checks/overview) - + Verify that non-HTTP services are reachable by checking connectivity to a host and port. Create a [TCP monitor](/detect/uptime-monitoring/tcp-monitors/overview) - + Check that your DNS records resolve as expected and catch misconfigurations or propagation issues. Create a [DNS monitor](/detect/uptime-monitoring/dns-monitors/overview) diff --git a/detect/testing/playwright-reporter-changelog.mdx b/detect/testing/playwright-reporter-changelog.mdx index e39a868ca..979cd8458 100644 --- a/detect/testing/playwright-reporter-changelog.mdx +++ b/detect/testing/playwright-reporter-changelog.mdx @@ -218,7 +218,7 @@ Learn more about: **Credentials now required** - Reporter requires Checkly credentials (`apiKey` + `accountId`) or explicit `dryRun: true`. Missing credentials now show clear error messages instead of silently skipping upload. - If you're not using Checkly Test Sessions, add `dryRun: true` to your config: + If you're not using Checkly test sessions, add `dryRun: true` to your config: ```typescript reporter: [['@checkly/playwright-reporter', { dryRun: true }]] @@ -300,7 +300,7 @@ Learn more about: - **Broad Playwright support** - Compatible with Playwright versions 1.40 through 1.57+ - **Drop-in JSON replacement** - Fully compatible with Playwright's native JSON reporter output format - **Trace extraction** - Automatically extracts console messages and network requests from Playwright trace files - - **Checkly integration** - Automatic upload to Checkly Test Sessions when credentials are configured + - **Checkly integration** - Automatic upload to Checkly test sessions when credentials are configured - **New `createChecklyReporter()` function** - Better IntelliSense support in `playwright.config.ts` - **Unified `outputDir` option** - Single option for all output files (JSON report, ZIP assets) - **Verbose logging** - Debug mode for troubleshooting report generation diff --git a/detect/testing/playwright-reporter.mdx b/detect/testing/playwright-reporter.mdx index a39f70b12..c8d1d4ae1 100644 --- a/detect/testing/playwright-reporter.mdx +++ b/detect/testing/playwright-reporter.mdx @@ -159,7 +159,7 @@ export default defineConfig({ - `checkly-report.json` - JSON test report - `checkly-report.zip` - ZIP archive with report and assets -### Environment Variables +### Environment variables | Variable | Description | |----------|-------------| @@ -268,7 +268,7 @@ If your Checkly reports don't include traces or videos, ensure that your `playwr **Using UI mode?** The reporter uploads results from UI mode runs, too. Enable [`dryRun`](#dry-run-mode) to skip uploads during local development. -## Understanding Test Sessions +## Understanding test sessions The reporter creates **suite-level test sessions**, not individual test file results. diff --git a/detect/testing/using-env-variables.mdx b/detect/testing/using-env-variables.mdx index 789020e9e..6758d6747 100644 --- a/detect/testing/using-env-variables.mdx +++ b/detect/testing/using-env-variables.mdx @@ -1,7 +1,7 @@ --- -title: Using Environment Variables +title: Using environment variables description: "Pass environment variables to your Checkly tests so a single check can run against staging, preview, or production URLs using the --env flag." -sidebarTitle: Environment Variables +sidebarTitle: Environment variables canonical: 'https://www.checklyhq.com/docs/detect/testing/using-env-variables/' --- diff --git a/detect/uptime-monitoring/dns-monitors/configuration.mdx b/detect/uptime-monitoring/dns-monitors/configuration.mdx index 4907374c1..f03dc5317 100644 --- a/detect/uptime-monitoring/dns-monitors/configuration.mdx +++ b/detect/uptime-monitoring/dns-monitors/configuration.mdx @@ -1,12 +1,12 @@ --- -title: 'DNS Monitor Configuration' +title: 'DNS monitor configuration' description: 'Configure your DNS monitor to verify record resolution.' sidebarTitle: 'Configuration' canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/dns-monitors/configuration/' --- {/* -To configure a DNS monitor using code, learn more about the [DNS Monitor Construct](/constructs/dns-monitor). +To configure a DNS monitor using code, learn more about the [DNS monitor construct](/constructs/dns-monitor). */} ### Basic Setup diff --git a/detect/uptime-monitoring/dns-monitors/overview.mdx b/detect/uptime-monitoring/dns-monitors/overview.mdx index 81564e9e2..486de393b 100644 --- a/detect/uptime-monitoring/dns-monitors/overview.mdx +++ b/detect/uptime-monitoring/dns-monitors/overview.mdx @@ -1,5 +1,5 @@ --- -title: 'DNS Monitors Overview' +title: 'DNS monitors overview' description: 'Monitor the resolution and lookup times of DNS records' sidebarTitle: Overview canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/dns-monitors/overview/' @@ -21,7 +21,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/dns-monitors /> -## What are DNS Monitors? +## What are DNS monitors? DNS monitors check that your DNS records resolve as expected. They help you catch misconfigurations, expired records, or propagation issues before they impact your users. @@ -77,7 +77,7 @@ DNS monitors support the following DNS record types: - **TXT**: Text records (SPF, DKIM, DMARC, etc.) - **HTTPS**: HTTPS service binding records ([RFC 9460](https://www.rfc-editor.org/rfc/rfc9460)) — advertise HTTP/3 (`alpn`), address hints (`ipv4hint`/`ipv6hint`), and Encrypted Client Hello (`ech`) -## DNS Monitor Results +## DNS monitor results Select a specific check run to inspect its results: diff --git a/detect/uptime-monitoring/grpc-monitors/configuration.mdx b/detect/uptime-monitoring/grpc-monitors/configuration.mdx index a1a619555..9cc405b8f 100644 --- a/detect/uptime-monitoring/grpc-monitors/configuration.mdx +++ b/detect/uptime-monitoring/grpc-monitors/configuration.mdx @@ -1,12 +1,12 @@ --- -title: 'gRPC Monitor Configuration' +title: 'gRPC monitor configuration' description: 'Configure your gRPC monitor to verify service availability, health, and response correctness.' sidebarTitle: 'Configuration' canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/grpc-monitors/configuration/' --- -To configure a gRPC monitor using code, learn more about the [gRPC Monitor Construct](/constructs/grpc-monitor). +To configure a gRPC monitor using code, learn more about the [gRPC monitor construct](/constructs/grpc-monitor). ### Basic Setup diff --git a/detect/uptime-monitoring/grpc-monitors/overview.mdx b/detect/uptime-monitoring/grpc-monitors/overview.mdx index b01453bd2..73c8090c2 100644 --- a/detect/uptime-monitoring/grpc-monitors/overview.mdx +++ b/detect/uptime-monitoring/grpc-monitors/overview.mdx @@ -1,15 +1,15 @@ --- -title: 'gRPC Monitors Overview' +title: 'gRPC monitors overview' description: 'Monitor gRPC service availability, health, and response times.' sidebarTitle: Overview canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/grpc-monitors/overview/' --- -**Monitoring as Code**: Learn more about the [gRPC Monitor Construct](/constructs/grpc-monitor). +**Monitoring as Code**: Learn more about the [gRPC monitor construct](/constructs/grpc-monitor). -## What are gRPC Monitors? +## What are gRPC monitors? gRPC monitors verify that your gRPC services are reachable, healthy, and responding correctly. They support two monitoring modes: @@ -23,7 +23,7 @@ Typical use cases include: * Checking that a service starts serving requests after a deployment * Asserting that gRPC status codes and response payloads meet expectations -## How gRPC Monitors Work +## How gRPC monitors work On each run, Checkly: @@ -35,7 +35,7 @@ On each run, Checkly: * **HEALTH mode**: Calls `Check` on `grpc.health.v1.Health`, optionally scoped to a specific service name 5. Evaluates your configured assertions against the response (status code, health status, response message, metadata, or response time) -## gRPC Monitor Results +## gRPC monitor results Select a specific check run to inspect its results: diff --git a/detect/uptime-monitoring/heartbeat-monitors/examples.mdx b/detect/uptime-monitoring/heartbeat-monitors/examples.mdx index 40dc1aaf1..4fae5ca44 100644 --- a/detect/uptime-monitoring/heartbeat-monitors/examples.mdx +++ b/detect/uptime-monitoring/heartbeat-monitors/examples.mdx @@ -21,7 +21,7 @@ Checkly records that a ping arrived, plus its `User-Agent` and `Origin` or `Refe ### Basic cURL Examples -The most common way to ping heartbeat monitors from shell scripts: +The most common way to ping Heartbeat monitors from shell scripts: ```bash GET Request diff --git a/detect/uptime-monitoring/heartbeat-monitors/overview.mdx b/detect/uptime-monitoring/heartbeat-monitors/overview.mdx index f91f71f2d..e4609549c 100644 --- a/detect/uptime-monitoring/heartbeat-monitors/overview.mdx +++ b/detect/uptime-monitoring/heartbeat-monitors/overview.mdx @@ -1,15 +1,15 @@ --- -title: Heartbeat Monitors +title: Heartbeat monitors description: Ensure your automated processes are running as expected. sidebarTitle: Overview canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/heartbeat-monitors/overview/' --- -**Monitoring as Code**: Learn more about the [Heartbeat Monitor Construct](/constructs/heartbeat-monitor). +**Monitoring as Code**: Learn more about the [Heartbeat monitor construct](/constructs/heartbeat-monitor). -Monitor your scheduled jobs, background tasks, and automated processes with Checkly's heartbeat monitoring. Unlike traditional active monitoring, heartbeat monitors work passively—they listen for regular "pings" from your tasks to ensure they're running as expected. +Monitor your scheduled jobs, background tasks, and automated processes with Checkly's heartbeat monitoring. Unlike traditional active monitoring, Heartbeat monitors work passively—they listen for regular "pings" from your tasks to ensure they're running as expected. -## What are Heartbeat Monitors? +## What are Heartbeat monitors? Heartbeat monitors are passive monitoring checks that wait for your automated tasks to report their successful completion. When your scheduled job, backup script, or cron job finishes successfully, it sends a simple HTTP request (a "ping") to Checkly to confirm it ran. @@ -40,11 +40,11 @@ Heartbeat monitors are perfect for: - Database cleanup tasks - File processing workflows -## How Heartbeat Monitoring Works +## How heartbeat monitoring works -The heartbeat monitoring process is straightforward. Once created, your heartbeat monitor provides a unique ping URL. Your tasks should make an HTTP GET or POST request to this URL when they complete successfully. +The heartbeat monitoring process is straightforward. Once created, your Heartbeat monitor provides a unique ping URL. Your tasks should make an HTTP GET or POST request to this URL when they complete successfully. -1. **Create a monitor** - Set up a heartbeat monitor with your expected ping frequency +1. **Create a monitor** - Set up a Heartbeat monitor with your expected ping frequency 2. **Get your ping URL** - Checkly provides a unique URL for your task to ping 3. **Add the ping** - Include a simple HTTP request in your task's success path 4. **Monitor results** - Checkly tracks pings and alerts you if a ping is missed or delayed @@ -97,7 +97,7 @@ You can manually send pings via the Checkly UI. Use this to start the check time ![Manually send a ping via the Checkly UI in the quick menu](/images/docs/images/heartbeat-checks/heartbeat-ping-quick-menu.png) -## Heartbeat Monitor Results +## Heartbeat monitor results Heartbeat monitor results show information about the ping request, like when it was recieved and its source. diff --git a/detect/uptime-monitoring/heartbeat-monitors/quickstart.mdx b/detect/uptime-monitoring/heartbeat-monitors/quickstart.mdx index 3fbdb5e71..5de0cf0a6 100644 --- a/detect/uptime-monitoring/heartbeat-monitors/quickstart.mdx +++ b/detect/uptime-monitoring/heartbeat-monitors/quickstart.mdx @@ -1,15 +1,15 @@ --- -title: 'Creating A Heartbeat Monitor' -description: 'Step-by-step guide to set up your first heartbeat monitor in Checkly. Learn about configuration, timing, alerts, and best practices.' +title: 'Creating a Heartbeat monitor' +description: 'Step-by-step guide to set up your first Heartbeat monitor in Checkly. Learn about configuration, timing, alerts, and best practices.' sidebarTitle: 'Quickstart' canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/heartbeat-monitors/quickstart/' --- -Learn more about all the [Heartbeat Monitor capabilities](/detect/uptime-monitoring/heartbeat-monitors/overview) in the general overview. +Learn more about all the [Heartbeat monitor capabilities](/detect/uptime-monitoring/heartbeat-monitors/overview) in the general overview. -Follow this comprehensive guide to create your first heartbeat monitor in Checkly. We'll walk through each configuration step and explain the best practices to ensure your monitoring is effective. +Follow this comprehensive guide to create your first Heartbeat monitor in Checkly. We'll walk through each configuration step and explain the best practices to ensure your monitoring is effective. -Before creating your heartbeat monitor, make sure you have: +Before creating your Heartbeat monitor, make sure you have: - A Checkly account. Heartbeat monitors are available on all plans; see [pricing](https://www.checklyhq.com/pricing/) for limits - A scheduled job, script, or automated process you want to monitor @@ -41,7 +41,7 @@ Use tags to group related monitors and make them easier to find and manage. ## Step 2: Timing Configuration -The timing configuration is the heart of your heartbeat monitor. You need to specify when you expect pings and how much flexibility to allow. +The timing configuration is the heart of your Heartbeat monitor. You need to specify when you expect pings and how much flexibility to allow. ### Period Setting @@ -51,7 +51,7 @@ The **period** defines how often your task should ping Checkly: - **Weekly jobs**: Set to 7 days - **Hourly jobs**: Set to 1 hour -![Configure period and grace settings for your heartbeat monitor](/images/heartbeat-monitors/getting-started-period-and-grace.png) +![Configure period and grace settings for your Heartbeat monitor](/images/heartbeat-monitors/getting-started-period-and-grace.png) ### Grace Period @@ -106,9 +106,9 @@ This means if your job is supposed to run every 6 hours but runs late at hour 7, ## Step 3: Alert Configuration -Connect your heartbeat monitor to [alert channels](/communicate/alerts/overview) to be notified when pings are missing. +Connect your Heartbeat monitor to [alert channels](/communicate/alerts/overview) to be notified when pings are missing. -### Choosing Alert Channels +### Choosing alert channels **For immediate awareness:** - **Email notifications** - Good for individual monitoring @@ -135,12 +135,12 @@ All alert channels subscribed to the monitor are notified at the same time. ## Step 4: Ping URL and Implementation -Once created, your heartbeat monitor provides a unique ping URL. Your tasks should make an HTTP `GET` or `POST` request to this URL when they complete successfully. +Once created, your Heartbeat monitor provides a unique ping URL. Your tasks should make an HTTP `GET` or `POST` request to this URL when they complete successfully. ## Step 5: Testing Your Setup -Before deploying to production, test your heartbeat monitor: +Before deploying to production, test your Heartbeat monitor: ### Manual Testing diff --git a/detect/uptime-monitoring/icmp-monitors/configuration.mdx b/detect/uptime-monitoring/icmp-monitors/configuration.mdx index 8bff33e78..514b42034 100644 --- a/detect/uptime-monitoring/icmp-monitors/configuration.mdx +++ b/detect/uptime-monitoring/icmp-monitors/configuration.mdx @@ -1,5 +1,5 @@ --- -title: 'ICMP Monitor Configuration' +title: 'ICMP monitor configuration' description: 'Configure your ICMP monitor to verify host reachability and measure network latency.' sidebarTitle: 'Configuration' canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/icmp-monitors/configuration/' diff --git a/detect/uptime-monitoring/icmp-monitors/overview.mdx b/detect/uptime-monitoring/icmp-monitors/overview.mdx index a6b5b4fe0..eaf2869ea 100644 --- a/detect/uptime-monitoring/icmp-monitors/overview.mdx +++ b/detect/uptime-monitoring/icmp-monitors/overview.mdx @@ -1,11 +1,11 @@ --- -title: 'ICMP Monitors Overview' +title: 'ICMP monitors overview' description: 'Monitor host reachability and network latency using ICMP ping.' sidebarTitle: Overview canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/icmp-monitors/overview/' --- -**Monitoring as Code**: Learn more about the [ICMP Monitor Construct](/constructs/icmp-monitor). +**Monitoring as Code**: Learn more about the [ICMP monitor construct](/constructs/icmp-monitor). @@ -23,7 +23,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/icmp-monitor /> -## What are ICMP Monitors? +## What are ICMP monitors? ICMP monitors check if a host is reachable by sending ICMP Echo Requests (pings). Typical use cases include: @@ -55,7 +55,7 @@ round-trip min/avg/max/stddev = 6.573/20.993/49.812/24.958 ms The response appears on the results page as both raw output and parsed JSON. You can use it as a reference to define [assertions](/detect/uptime-monitoring/icmp-monitors/configuration#assertions) for expected values. -## ICMP Monitor Results +## ICMP monitor results Select a specific check run to inspect its results: diff --git a/detect/uptime-monitoring/overview.mdx b/detect/uptime-monitoring/overview.mdx index b08cd10fe..d55bb1d90 100644 --- a/detect/uptime-monitoring/overview.mdx +++ b/detect/uptime-monitoring/overview.mdx @@ -22,32 +22,32 @@ Uptime monitoring is essential for ensuring your applications are always availab ## Types of Uptime Monitors Choose the Uptime Monitor that best fits your monitoring needs: - + Monitor the availability and performance of a specific URL or public endpoint. - + Monitor the availability and performance of TCP connections. - + Verify that DNS records resolve successfully and return the expected values. - + Verify host reachability and measure packet loss. - + Monitor gRPC service availability, health, and response correctness. - + Detect when cron jobs or scheduled tasks fail to run. diff --git a/detect/uptime-monitoring/ssl-monitors/configuration.mdx b/detect/uptime-monitoring/ssl-monitors/configuration.mdx index 978f1142a..490e54495 100644 --- a/detect/uptime-monitoring/ssl-monitors/configuration.mdx +++ b/detect/uptime-monitoring/ssl-monitors/configuration.mdx @@ -1,12 +1,12 @@ --- -title: 'SSL Monitor Configuration' +title: 'SSL monitor configuration' description: 'Configure your SSL monitor to track certificate health, expiry, and TLS security posture.' sidebarTitle: 'Configuration' canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/ssl-monitors/configuration/' --- -To configure an SSL monitor using code, learn more about the [SSL Monitor Construct](/constructs/ssl-monitor). +To configure an SSL monitor using code, learn more about the [SSL monitor construct](/constructs/ssl-monitor). ### Basic Setup diff --git a/detect/uptime-monitoring/ssl-monitors/overview.mdx b/detect/uptime-monitoring/ssl-monitors/overview.mdx index 00ad370b1..e6e410714 100644 --- a/detect/uptime-monitoring/ssl-monitors/overview.mdx +++ b/detect/uptime-monitoring/ssl-monitors/overview.mdx @@ -1,15 +1,15 @@ --- -title: 'SSL Monitor Overview' +title: 'SSL monitor overview' description: 'Monitor TLS certificate health, expiry, and security posture of your HTTPS endpoints.' sidebarTitle: Overview canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/ssl-monitors/overview/' --- -**Monitoring as Code**: Learn more about the [SSL Monitor Construct](/constructs/ssl-monitor). +**Monitoring as Code**: Learn more about the [SSL monitor construct](/constructs/ssl-monitor). -## What are SSL Monitors? +## What are SSL monitors? SSL monitors verify the health of a TLS certificate by connecting to a hostname, completing a full TLS handshake, and inspecting the resulting certificate and negotiated protocol parameters. Typical use cases include: @@ -19,7 +19,7 @@ SSL monitors verify the health of a TLS certificate by connecting to a hostname, * Catching chain trust failures caused by missing intermediate certificates * Alerting on weak or compromised certificate authority usage -## How do SSL Monitors work? +## How do SSL monitors work? Each SSL monitor run performs the following steps: @@ -30,7 +30,7 @@ Each SSL monitor run performs the following steps: 5. **Security baseline evaluation** — On a successful handshake and certificate verification, a configurable rule set evaluates the negotiated protocol (TLS version, cipher suite, CA trust) and produces a per-rule verdict plus an overall **grade** and **verdict** (`pass` / `warn` / `fail`). The baseline is skipped when an earlier step fails (e.g. hostname mismatch or chain untrusted). 6. **Assertions** — Optional assertions are evaluated against the certificate and handshake data -## SSL Monitor Results +## SSL monitor results Select a specific check run to inspect its results: diff --git a/detect/uptime-monitoring/tcp-monitors/configuration.mdx b/detect/uptime-monitoring/tcp-monitors/configuration.mdx index a465e1c41..0c83e3fe7 100644 --- a/detect/uptime-monitoring/tcp-monitors/configuration.mdx +++ b/detect/uptime-monitoring/tcp-monitors/configuration.mdx @@ -1,12 +1,12 @@ --- -title: 'TCP Monitor Configuration' +title: 'TCP monitor configuration' description: 'Configure your TCP monitor to ensure TCP services are reachable and responding as expected.' sidebarTitle: 'Configuration' canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/tcp-monitors/configuration/' --- -To configure a TCP monitor using code, learn more about the [TCP Monitor Construct](/constructs/tcp-monitor). +To configure a TCP monitor using code, learn more about the [TCP monitor construct](/constructs/tcp-monitor). ### Basic Setup diff --git a/detect/uptime-monitoring/tcp-monitors/overview.mdx b/detect/uptime-monitoring/tcp-monitors/overview.mdx index 815c6711d..db8c63a25 100644 --- a/detect/uptime-monitoring/tcp-monitors/overview.mdx +++ b/detect/uptime-monitoring/tcp-monitors/overview.mdx @@ -1,15 +1,15 @@ --- -title: 'TCP Monitors Overview' +title: 'TCP monitors overview' description: 'Monitor the availability and performance of your TCP services.' sidebarTitle: Overview canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/tcp-monitors/overview/' --- -**Monitoring as Code**: Learn more about the [TCP Monitor Construct](/constructs/tcp-monitor). +**Monitoring as Code**: Learn more about the [TCP monitor construct](/constructs/tcp-monitor). -## What are TCP Monitors? +## What are TCP monitors? Use TCP monitors to verify that your non-HTTP services are working as expected. TCP monitors work by establishing a connection to a host and port, then checking the speed and validity of the response. @@ -34,7 +34,7 @@ For example, use these checks to verify that: /> -## How TCP Monitoring Works +## How TCP monitoring works TCP monitors perform connection-level checks: @@ -42,7 +42,7 @@ TCP monitors perform connection-level checks: 2. **Port Verification** - Confirms the service is listening on the specified port 3. **Response Validation** - Optionally validates service responses based on your configured assertions -## TCP Monitor Results +## TCP monitor results Select a specific check run to review its results: @@ -72,7 +72,7 @@ This happens because [AWS blocks outbound traffic on port 25 by default to preve **Workarounds:** -* Run the check from a [Private Location](/platform/private-locations/overview) where port 25 is allowed +* Run the check from a [private location](/platform/private-locations/overview) where port 25 is allowed * Use an alternative SMTP port such as 587 or 465 if supported diff --git a/detect/uptime-monitoring/tcp-monitors/quickstart.mdx b/detect/uptime-monitoring/tcp-monitors/quickstart.mdx index 28312ca7b..1d4700c61 100644 --- a/detect/uptime-monitoring/tcp-monitors/quickstart.mdx +++ b/detect/uptime-monitoring/tcp-monitors/quickstart.mdx @@ -1,12 +1,12 @@ --- -title: 'Creating A TCP Monitor' +title: 'Creating a TCP monitor' description: 'Step-by-step guide to set up your first TCP monitor and ensure your network services are always available.' sidebarTitle: 'Quickstart' canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/tcp-monitors/quickstart/' --- -Learn more about all the [TCP Monitor capabilities](/detect/uptime-monitoring/tcp-monitors/overview) in the general overview. +Learn more about all the [TCP monitor capabilities](/detect/uptime-monitoring/tcp-monitors/overview) in the general overview. This guide walks you through creating your first TCP monitor to check the availability of your network services, databases, or any TCP-based application. diff --git a/detect/uptime-monitoring/traceroute-monitors/configuration.mdx b/detect/uptime-monitoring/traceroute-monitors/configuration.mdx index de734c413..7830d9244 100644 --- a/detect/uptime-monitoring/traceroute-monitors/configuration.mdx +++ b/detect/uptime-monitoring/traceroute-monitors/configuration.mdx @@ -1,12 +1,12 @@ --- -title: 'Traceroute Monitor Configuration' +title: 'Traceroute monitor configuration' description: 'Configure your Traceroute monitor to map network paths and detect routing issues, latency, and packet loss.' sidebarTitle: 'Configuration' canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/traceroute-monitors/configuration/' --- -To configure a Traceroute monitor using code, learn more about the [Traceroute Monitor Construct](/constructs/traceroute-monitor). +To configure a Traceroute monitor using code, learn more about the [Traceroute monitor construct](/constructs/traceroute-monitor). ### Basic Setup diff --git a/detect/uptime-monitoring/traceroute-monitors/overview.mdx b/detect/uptime-monitoring/traceroute-monitors/overview.mdx index f358fef63..11b2ae5d0 100644 --- a/detect/uptime-monitoring/traceroute-monitors/overview.mdx +++ b/detect/uptime-monitoring/traceroute-monitors/overview.mdx @@ -1,15 +1,15 @@ --- -title: 'Traceroute Monitors Overview' +title: 'Traceroute monitors overview' description: 'Map the network path to any host and detect routing issues, high-latency hops, and packet loss.' sidebarTitle: Overview canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/traceroute-monitors/overview/' --- -**Monitoring as Code**: Learn more about the [Traceroute Monitor Construct](/constructs/traceroute-monitor). +**Monitoring as Code**: Learn more about the [Traceroute monitor construct](/constructs/traceroute-monitor). -## What are Traceroute Monitors? +## What are Traceroute monitors? Traceroute monitors map the network path between a Checkly location and your target host, recording every router hop along the way and measuring per-hop latency and packet loss. Typical use cases include: @@ -18,7 +18,7 @@ Traceroute monitors map the network path between a Checkly location and your tar * Verifying that the destination is reachable end-to-end, beyond just confirming that a port accepts connections * Continuously monitoring path stability across regions over time -## How do Traceroute Monitors work? +## How do Traceroute monitors work? A Traceroute monitor executes the following steps on each run: @@ -41,7 +41,7 @@ A Traceroute monitor executes the following steps on each run: The default port is protocol-dependent everywhere — web UI, CLI, and API: `443` for TCP and `33434` for UDP/SCTP. `33434` is a high, typically-closed port: UDP and SCTP arrival is only confirmed when the destination returns an ICMP Destination Unreachable, which requires the probed port to be closed. Avoid setting an open port (like `443`) for UDP/SCTP probes — it would never confirm arrival. -## Traceroute Monitor Results +## Traceroute monitor results Select a specific check run to inspect its results: @@ -73,7 +73,7 @@ Learn more in our documentation on [Results](/concepts/results). **How to fix**: 1. Switch the probe protocol — try `ICMP` if the host responds to ping, or `UDP` for a connectionless probe 2. For TCP probes, change the port to one that is explicitly open on the target (e.g. `80` or `22`). For UDP/SCTP, keep a *closed* port — arrival is only confirmed by an ICMP Destination Unreachable reply -3. Confirm reachability at the application layer with an [API Monitor](/detect/synthetic-monitoring/overview) or [TCP Monitor](/detect/uptime-monitoring/tcp-monitors/overview) targeting the same host and port +3. Confirm reachability at the application layer with an [API Monitor](/detect/synthetic-monitoring/overview) or [TCP monitor](/detect/uptime-monitoring/tcp-monitors/overview) targeting the same host and port diff --git a/detect/uptime-monitoring/url-monitors/configuration.mdx b/detect/uptime-monitoring/url-monitors/configuration.mdx index a14ef7fe8..230da618b 100644 --- a/detect/uptime-monitoring/url-monitors/configuration.mdx +++ b/detect/uptime-monitoring/url-monitors/configuration.mdx @@ -1,5 +1,5 @@ --- -title: 'URL Monitor Configuration' +title: 'URL monitor configuration' description: 'Configure your URL monitor to ensure your HTTP-based services are always available.' sidebarTitle: 'Configuration' canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/url-monitors/configuration/' @@ -129,7 +129,7 @@ Configure follow-up alerts after initial failure notification: | **Maximum reminders** | Number of follow-up alerts (0 = no reminders) | | **Reminder interval** | Time between reminders (only if maximum reminders > 0) | -#### Alert Channels +#### Alert channels Define where notifications are sent when checks fail or recover. Additional channels can be configured in global notification settings. diff --git a/detect/uptime-monitoring/url-monitors/overview.mdx b/detect/uptime-monitoring/url-monitors/overview.mdx index 09fbd58d8..70491a21a 100644 --- a/detect/uptime-monitoring/url-monitors/overview.mdx +++ b/detect/uptime-monitoring/url-monitors/overview.mdx @@ -1,14 +1,14 @@ --- -title: 'URL Monitors Overview' +title: 'URL monitors overview' description: 'Monitor websites and apps to verify their availability and performance.' sidebarTitle: Overview canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/url-monitors/overview/' --- -**Monitoring as Code**: Learn more about the [URL Monitor Construct](/constructs/url-monitor). +**Monitoring as Code**: Learn more about the [URL monitor construct](/constructs/url-monitor). -## What are URL Monitors? +## What are URL monitors? URL monitors track the availability of your HTTP-based services by sending requests to specified URLs and validating avaliability and performance. @@ -34,7 +34,7 @@ URL monitors track the availability of your HTTP-based services by sending reque * Checking that your SSL certificate is still valid * Confirming that a public pricing endpoint is reachable for customers -## How URL Monitors Work +## How URL monitors work URL monitors send HTTP requests to specified URLs and validate availability and performance. They can be configured to check for specific status codes and response times while running from multiple global locations. @@ -61,7 +61,7 @@ Schedule your monitor to run at the frequency you want. -## URL Monitor Results +## URL monitor results URL monitor results show details about each request and help you understand if your endpoint was available and performing as expected at the time of the check. @@ -102,5 +102,5 @@ Learn more in our documentation on [Results](/concepts/results). -For monitoring as code workflows, use the URL Monitor construct to version control your monitoring configuration and deploy alongside your application code. [Learn about URL Monitor Construct →](/constructs/url-monitor) +For monitoring as code workflows, use the URL monitor construct to version control your monitoring configuration and deploy alongside your application code. [Learn about URL monitor construct →](/constructs/url-monitor) diff --git a/detect/uptime-monitoring/url-monitors/quickstart.mdx b/detect/uptime-monitoring/url-monitors/quickstart.mdx index 49344fddd..775607c38 100644 --- a/detect/uptime-monitoring/url-monitors/quickstart.mdx +++ b/detect/uptime-monitoring/url-monitors/quickstart.mdx @@ -1,12 +1,12 @@ --- -title: 'Creating A URL Monitor' +title: 'Creating a URL monitor' description: 'Step-by-step guide to set up your first URL monitor and ensure your websites and APIs are always accessible.' sidebarTitle: 'Quickstart' canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/url-monitors/quickstart/' --- -Learn more about all the [URL Monitor capabilities](/detect/uptime-monitoring/url-monitors/overview) in the general overview. +Learn more about all the [URL monitor capabilities](/detect/uptime-monitoring/url-monitors/overview) in the general overview. This guide walks you through creating your first URL monitor to check the availability and performance of your websites, APIs, or any HTTP-based service. diff --git a/guides/agentic-workflows.mdx b/guides/agentic-workflows.mdx index 20cbd73fb..906c60b3a 100644 --- a/guides/agentic-workflows.mdx +++ b/guides/agentic-workflows.mdx @@ -253,7 +253,7 @@ new UrlMonitor("base-url-monitor", { ## Set up API monitoring -For a solid monitoring strategy uptime monitoring is only the first step. [API Checks](/detect/synthetic-monitoring/api-checks/overview) go beyond uptime monitoring by validating response payloads with assertions. +For a solid monitoring strategy uptime monitoring is only the first step. [API checks](/detect/synthetic-monitoring/api-checks/overview) go beyond uptime monitoring by validating response payloads with assertions. To create complex assertions, target AI to analyze your source code to generate meaningful assertions automatically. diff --git a/guides/claude-code-monitoring.mdx b/guides/claude-code-monitoring.mdx index d56dc0c63..42b43388c 100644 --- a/guides/claude-code-monitoring.mdx +++ b/guides/claude-code-monitoring.mdx @@ -2,7 +2,7 @@ title: In-Depth Monitoring With Checkly and Claude Code sidebarTitle: Using Checkly and Claude Code description: - By integrating AI into your development workflow, you can generate valid Checkly constructs—including URL monitors and Playwright-based browser checks—with minimal effort. + By integrating AI into your development workflow, you can generate valid Checkly constructs—including URL monitors and Playwright-based Browser checks—with minimal effort. author: Nočnica Mellifera avatar: 'images/avatars/nica-mellifera.png' tags: @@ -58,7 +58,7 @@ npx checkly skills install --target claude After this you'll need to exit and restart Claude Code for it to pick up the skill. -## Create new URL Monitors +## Create new URL monitors We'll start with something easy. A URL monitor that will check an HTTP endpoint and alert if it doesn't receive the right status code. With the context set from the section above, try a command like: @@ -147,7 +147,7 @@ __checks__/book-detail-visibility.spec.ts *Like always with the `checkly test` command, this test isn't running from our workstation but rather from the Checkly's monitoring infrastructure.* -Next we'll want to create a `.check.ts` file for this browser check, which sets some check-specific settings and assigns the check's logical ID. +Next we'll want to create a `.check.ts` file for this Browser check, which sets some check-specific settings and assigns the check's logical ID. ```{title="Prompt:"} Write a .check.ts file for book-detail-visibility that runs the check from a US and EU region and defines a linear retry strategy. @@ -224,7 +224,7 @@ With this check created, let's add the following lines to your updated `CLAUDE.m Pro tip: from the Claude Code prompt, just hit octothorp "#" to add to Claude's memory. Each entry will be a new line in `CLAUDE.md`. -### 3. Use Claude Code to create multiple Browser Checks +### 3. Use Claude Code to create multiple Browser checks Now that we've got a working test and, let's let Claude Code create another check for us: @@ -379,7 +379,7 @@ Once we're happy with what will be deployed, it's time to run `npx checkly deplo ## Conclusion -AI-assisted coding tools like Claude Code can significantly accelerate the creation and deployment of monitoring checks with Checkly's Monitoring as Code approach. By integrating AI into your development workflow, you can generate valid Checkly constructs—including URL monitors and Playwright-based browser checks—with minimal effort. One of the superpowers that an AI workflow can unlock is the *mass updating of many files in your project.* Updating a large number of test files can go much faster with the help of Claude Code. +AI-assisted coding tools like Claude Code can significantly accelerate the creation and deployment of monitoring checks with Checkly's Monitoring as Code approach. By integrating AI into your development workflow, you can generate valid Checkly constructs—including URL monitors and Playwright-based Browser checks—with minimal effort. One of the superpowers that an AI workflow can unlock is the *mass updating of many files in your project.* Updating a large number of test files can go much faster with the help of Claude Code. While AI can handle much of the boilerplate work, human oversight remains essential for ensuring best practices, refining assertions, and maintaining high-quality monitoring scripts. By combining AI efficiency with developer expertise, teams can achieve comprehensive monitoring coverage in minutes rather than days. @@ -399,7 +399,7 @@ To learn more about Checkly's capabilities, explore these resources: - [Generating end-to-end tests with AI and Playwright MCP](https://www.checklyhq.com/blog/generate-end-to-end-tests-with-ai-and-playwright/) - Stefan's blog post makes a great starter for generalized Playwright development with an AI toolkit. - [Checkly CLI Documentation](/cli/overview) – Learn how to manage checks as code right from your command line. -- [Playwright Testing Guide](https://www.checklyhq.com/learn/playwright/) – Best practices for writing reliable browser checks. +- [Playwright Testing Guide](https://www.checklyhq.com/learn/playwright/) – Best practices for writing reliable Browser checks. - [What is monitoring as code?](https://www.checklyhq.com/guides/monitoring-as-code/) — A comprehensive guide to infrastructure-as-code principles for monitoring. - [Checkly Community Slack](https://checklyhq.com/slack) – Join discussions and get support from the Checkly team and other users. diff --git a/guides/communicate-availability.mdx b/guides/communicate-availability.mdx index 571c628d5..55c4c38ae 100644 --- a/guides/communicate-availability.mdx +++ b/guides/communicate-availability.mdx @@ -1,6 +1,6 @@ --- title: A status page backed by real monitors -sidebarTitle: Build Real-Time Status Pages +sidebarTitle: Build real-time status pages description: Build a public status page in code whose components go red when the checks that test them fail, and read and update its incidents from your coding agent with the Checkly MCP server. canonical: 'https://www.checklyhq.com/docs/guides/communicate-availability/' --- @@ -50,7 +50,7 @@ A status page is only as honest as what drives it. Drive each component with a c The tag on each check is the contract between the check and the status page. Use one tag per component, and do not reuse it for anything else. -The storefront component is backed by a search flow. Run it as a Playwright Check Suite or a Browser Check. Both use the same test file: +The storefront component is backed by a search flow. Run it as a Playwright Check Suite or a Browser check. Both use the same test file: diff --git a/guides/global-monitoring.mdx b/guides/global-monitoring.mdx index 9f21ada24..80eebd8f3 100644 --- a/guides/global-monitoring.mdx +++ b/guides/global-monitoring.mdx @@ -203,7 +203,7 @@ In a parallel check, every location runs at every interval, and each one is a ch | Homepage from around the world | 13 | 5 minutes | 156 | | Checkout from three continents | 3 | 10 minutes | 18 | -Spend the width where it is cheap. URL, TCP, DNS, and ICMP monitors run in milliseconds, so run them from the core set or wider: they are what finds a regional path problem. API checks follow the core set. Browser checks and Playwright check suites take seconds to minutes per run, so one location per continent with meaningful revenue is enough to prove the flow works there. +Spend the width where it is cheap. URL, TCP, DNS, and ICMP monitors run in milliseconds, so run them from the core set or wider: they are what finds a regional path problem. API checks follow the core set. Browser checks and Playwright Check Suites take seconds to minutes per run, so one location per continent with meaningful revenue is enough to prove the flow works there. Even three locations create more chances for one noisy path to page someone. Two settings turn that around. Retry in the same region, so a flaky path is confirmed rather than papered over. Then alert only when a percentage of locations agree. diff --git a/guides/keyword-monitoring.mdx b/guides/keyword-monitoring.mdx index f4099c01f..c9ac8ec73 100644 --- a/guides/keyword-monitoring.mdx +++ b/guides/keyword-monitoring.mdx @@ -108,7 +108,7 @@ Adding `.first()` makes the error go away and the check useless: it passes as lo ## Step 3: Run it on a schedule -Run the test as a Playwright Check Suite, or as a Browser Check if you prefer one file per check. Both use the same spec file. +Run the test as a Playwright Check Suite, or as a Browser check if you prefer one file per check. Both use the same spec file. @@ -209,7 +209,7 @@ Change the title back before you deploy again. ## Reference -- [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) and [Browser Checks](/detect/synthetic-monitoring/browser-checks/overview) +- [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) and [Browser checks](/detect/synthetic-monitoring/browser-checks/overview) - [Assertions in Playwright](/learn/playwright/assertions) and [locators](/learn/playwright/selectors) - [`BrowserCheck`](/constructs/browser-check) and [project configuration](/constructs/project) - [Checkly Skills](/ai/skills) diff --git a/guides/monitoring-an-openapi-spec.mdx b/guides/monitoring-an-openapi-spec.mdx index cfe52fdb3..ea3ab3fad 100644 --- a/guides/monitoring-an-openapi-spec.mdx +++ b/guides/monitoring-an-openapi-spec.mdx @@ -242,7 +242,7 @@ As we look to increase our endpoint coverage across our APIs, we might want to e - Learn end-to-end monitoring with puppeteer and playwright to test key website flows. + Learn end-to-end monitoring with puppeteer and Playwright to test key website flows. diff --git a/guides/monitoring-ecommerce-apps-using-playwright.mdx b/guides/monitoring-ecommerce-apps-using-playwright.mdx index 707d1cd4e..fe6459f9f 100644 --- a/guides/monitoring-ecommerce-apps-using-playwright.mdx +++ b/guides/monitoring-ecommerce-apps-using-playwright.mdx @@ -180,7 +180,7 @@ export default defineConfig({ ## Step 4: Define the monitor -Install the CLI if this repository does not have it yet, then describe the monitor next to your Playwright config. A Playwright Check Suite runs the whole suite with your config and shows one test case per spec. A Browser Check runs a single spec file on its own. Pick one. +Install the CLI if this repository does not have it yet, then describe the monitor next to your Playwright config. A Playwright Check Suite runs the whole suite with your config and shows one test case per spec. A Browser check runs a single spec file on its own. Pick one. ```bash Terminal npm install --save-dev checkly @@ -239,7 +239,7 @@ new BrowserCheck('shop-checkout-browser-check', { -The base URL is a check-level environment variable in both paths. A staging monitor is the same entry with a different `SHOP_URL`, and the tests never change. The Browser Check path needs a copy of the checkout spec that opens `process.env.SHOP_URL` itself, kept in `checks/checkout.spec.ts` in the sample. +The base URL is a check-level environment variable in both paths. A staging monitor is the same entry with a different `SHOP_URL`, and the tests never change. The Browser check path needs a copy of the checkout spec that opens `process.env.SHOP_URL` itself, kept in `checks/checkout.spec.ts` in the sample. ## Step 5: Run it on Checkly, then deploy @@ -290,7 +290,7 @@ The suite now runs every ten minutes from both locations, and every later deploy ## Same thing in Terraform -If your team manages infrastructure with Terraform, the checkout flow is one `checkly_check` resource: a Browser Check with the self-contained spec and the same `SHOP_URL` variable. +If your team manages infrastructure with Terraform, the checkout flow is one `checkly_check` resource: a Browser check with the self-contained spec and the same `SHOP_URL` variable. ```terraform terraform/main.tf # Provider block as in the Terraform overview, then: diff --git a/guides/monitoring-ecommerce-apps-using-terraform.mdx b/guides/monitoring-ecommerce-apps-using-terraform.mdx index 9accea63e..88e57a863 100644 --- a/guides/monitoring-ecommerce-apps-using-terraform.mdx +++ b/guides/monitoring-ecommerce-apps-using-terraform.mdx @@ -1,14 +1,14 @@ --- title: Monitor a shop with Terraform sidebarTitle: Monitoring a Shop with Terraform -description: Declare a shop's whole monitoring stack in Terraform with the Checkly provider, from the alert channel and check group to Browser Checks loaded from spec files and an API check with body assertions. +description: Declare a shop's whole monitoring stack in Terraform with the Checkly provider, from the alert channel and check group to Browser checks loaded from spec files and an API check with body assertions. canonical: 'https://www.checklyhq.com/docs/guides/monitoring-ecommerce-apps-using-terraform/' --- import GuideAgentIntro from '/snippets/guide-agent-intro.mdx' import { CopyPromptButton } from '/snippets/copy-prompt-button.jsx' -By the end of this guide, your shop's monitoring lives in five Terraform resources: an email alert channel, a check group that owns locations, retries, and alerting, two Browser Checks loaded from Playwright spec files, and an API check that asserts on the response body. +By the end of this guide, your shop's monitoring lives in five Terraform resources: an email alert channel, a check group that owns locations, retries, and alerting, two Browser checks loaded from Playwright spec files, and an API check that asserts on the response body. ```text Terminal # checkly_alert_channel.shop_email will be created @@ -182,9 +182,9 @@ resource "checkly_check_group_v2" "shop" { `checkly_check_group_v2` changes nothing about its checks unless you ask it to. Each `enforce_` block you add takes that setting away from the checks and applies the group's value instead. Here the group runs every check from N. Virginia and Ireland in parallel, retries a failed run up to twice from a different region, and emails you as soon as one run still fails after its retries. -The `SHOP_URL` variable reaches every Browser Check in the group. Point the whole stack at a staging shop with `terraform plan -var="shop_url="`, without touching a check. +The `SHOP_URL` variable reaches every Browser check in the group. Point the whole stack at a staging shop with `terraform plan -var="shop_url="`, without touching a check. -## Step 4: Monitor the shop's flows with Browser Checks +## Step 4: Monitor the shop's flows with Browser checks Keep each flow in its own Playwright spec file. The file is the check's script, and you can run it locally before Terraform ever sees it. @@ -244,7 +244,7 @@ Running 2 tests using 2 workers 2 passed (1.3s) ``` -Now turn every spec into a check. A `for_each` over a map creates one Browser Check per entry, and `file()` reads the spec as the check's script: +Now turn every spec into a check. A `for_each` over a map creates one Browser check per entry, and `file()` reads the spec as the check's script: ```terraform browser.tf # One Browser Check per spec file in scripts/. To monitor another flow, diff --git a/guides/monitoring-the-stripe-api.mdx b/guides/monitoring-the-stripe-api.mdx index 4ff985be5..7bfdac8b7 100644 --- a/guides/monitoring-the-stripe-api.mdx +++ b/guides/monitoring-the-stripe-api.mdx @@ -13,7 +13,7 @@ canonical: 'https://www.checklyhq.com/docs/guides/monitoring-the-stripe-api/' ## The rise of APIs -With the rise of the [Jamstack](https://jamstack.org/), the already broadly used web APIs have been brought further into the spotlight and explicitly named as cornerstone of a new way of building web applications. In the Jamstack paradigm, applications rely on APIs returning structured data (JSON or XML) when queried via a build process or Javascript-based frontend. +With the rise of the [Jamstack](https://jamstack.org/), the already broadly used web APIs have been brought further into the spotlight and explicitly named as cornerstone of a new way of building web applications. In the Jamstack paradigm, applications rely on APIs returning structured data (JSON or XML) when queried via a build process or JavaScript-based frontend. The API calls might be aimed at internal services or at third-parties handling complex flows such as content management, authentication, merchant services and more. An example of third-party API could be [Stripe](https://stripe.com/), which acts as payment infrastructure for a multitude of businesses. @@ -73,7 +73,7 @@ curl https://api.stripe.com/v1/customers \ -G ``` -If we chose to set up a call using Javascript, for example, we could achieve the same call as in the first case above using [axios](https://github.com/axios/axios): +If we chose to set up a call using JavaScript, for example, we could achieve the same call as in the first case above using [axios](https://github.com/axios/axios): ```js Stripe.js const { default: axios } = require("axios"); @@ -346,7 +346,7 @@ Response time limits enable us to set different thresholds to decide exactly whi Checkly is highly programmable and allows users to run scripts before and after the main HTTP request of an API check. -![programmable setup scripts](/images/guides/images/guides-checkly-setup.png "Setup and teardown methods are fully scriptable using NodeJS") +![programmable setup scripts](/images/guides/images/guides-checkly-setup.png "Setup and teardown methods are fully scriptable using Node.js") Setup scripts run before our check and give us access to properties like the URL, headers and query parameters, enabling us to set up all the prerequisites for a successful request. Some examples could be: @@ -372,7 +372,7 @@ As we increase our monitoring coverage across our APIs, we can also increase the - Learn end-to-end monitoring with playwright to test key website flows. + Learn end-to-end monitoring with Playwright to test key website flows. diff --git a/guides/overview.mdx b/guides/overview.mdx index cbba5f736..e6c788a4a 100644 --- a/guides/overview.mdx +++ b/guides/overview.mdx @@ -52,7 +52,7 @@ Create, configure, and update your monitoring through prompts to your coding age -Set up Claude Code to generate and deploy URL monitors and browser checks for your services +Set up Claude Code to generate and deploy URL monitors and Browser checks for your services @@ -87,7 +87,7 @@ Browse, search, add to cart, and checkout as one Playwright Check Suite with saf -Declare the alert channel, group, browser checks, and API check for a shop in Terraform +Declare the alert channel, group, Browser checks, and API check for a shop in Terraform diff --git a/guides/playwright-testing-to-monitoring.mdx b/guides/playwright-testing-to-monitoring.mdx index db9c90281..d0f89d478 100644 --- a/guides/playwright-testing-to-monitoring.mdx +++ b/guides/playwright-testing-to-monitoring.mdx @@ -131,7 +131,7 @@ Install the CLI if this repository does not have it yet, then describe the monit npm install --save-dev checkly ``` -A Playwright Check Suite reuses your Playwright config and runs a whole project. A Browser Check runs a single spec file with Checkly's own Playwright setup. Pick one. +A Playwright Check Suite reuses your Playwright config and runs a whole project. A Browser check runs a single spec file with Checkly's own Playwright setup. Pick one. @@ -181,7 +181,7 @@ new BrowserCheck('shop-checkout-browser-check', { -The Check Suite path needs nothing else: the `pwProjects` entry selects the `monitoring` project, and the suite runs every ten minutes from Virginia and Ireland. The Browser Check path needs a copy of the spec with `page.goto('https://danube-web.shop/')`, because there is no `playwright.config.ts` to supply `baseURL`. The sample keeps that copy in `checks/checkout.spec.ts`. +The Check Suite path needs nothing else: the `pwProjects` entry selects the `monitoring` project, and the suite runs every ten minutes from Virginia and Ireland. The Browser check path needs a copy of the spec with `page.goto('https://danube-web.shop/')`, because there is no `playwright.config.ts` to supply `baseURL`. The sample keeps that copy in `checks/checkout.spec.ts`. Prefer to have your coding agent write this file? The [Playwright Check Suite quickstart](/detect/synthetic-monitoring/playwright-checks/quickstart) has a prompt that inspects your Playwright config and generates the `checkly.config.ts`. diff --git a/guides/reading-traces.mdx b/guides/reading-traces.mdx index 4890c90c6..8d9fc0070 100644 --- a/guides/reading-traces.mdx +++ b/guides/reading-traces.mdx @@ -289,7 +289,7 @@ The agent calls `list-check-stats` with the failing filter to find the check, `g ## Next -[Monitor a checkout flow](/guides/monitoring-ecommerce-apps-using-playwright): now that you can debug one, build a full checkout monitor with the Playwright Check Suite and a Browser Check side by side. +[Monitor a checkout flow](/guides/monitoring-ecommerce-apps-using-playwright): now that you can debug one, build a full checkout monitor with the Playwright Check Suite and a Browser check side by side. ## Reference diff --git a/guides/sdlc-monitoring.mdx b/guides/sdlc-monitoring.mdx index d693521a3..b0ea28656 100644 --- a/guides/sdlc-monitoring.mdx +++ b/guides/sdlc-monitoring.mdx @@ -14,7 +14,7 @@ By the end of this guide, your pull requests will test their preview URL before Passing URL monitor and browser check with the Production environment, repository, branch, and commit recorded -The [sample project](https://github.com/checkly/docs/tree/main/samples/guides/checks-on-deploy) monitors the Danube shop with one URL monitor and one Browser Check. +The [sample project](https://github.com/checkly/docs/tree/main/samples/guides/checks-on-deploy) monitors the Danube shop with one URL monitor and one Browser check. @@ -77,7 +77,7 @@ new BrowserCheck('deploy-shop-browser', { }) ``` -The URL monitor reads the local variable when the CLI builds it. The Browser Check reads the remote variable when Playwright runs: +The URL monitor reads the local variable when the CLI builds it. The Browser check reads the remote variable when Playwright runs: ```typescript __checks__/shop.spec.ts import { test, expect } from '@playwright/test' @@ -89,7 +89,7 @@ test('shop displays books', async ({ page }) => { }) ``` -Both [Browser Checks](/detect/synthetic-monitoring/browser-checks/overview) and [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) work with this deployment pattern. This sample uses a Browser Check. For a target behind your firewall, see [private locations](/platform/private-locations/overview). +Both [Browser checks](/detect/synthetic-monitoring/browser-checks/overview) and [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) work with this deployment pattern. This sample uses a Browser check. For a target behind your firewall, see [private locations](/platform/private-locations/overview). From the sample directory, test and deploy the production defaults: @@ -223,7 +223,7 @@ The Action supplies commit metadata from the event. Checkout uses the same SHA, For local runs, the CLI reads git metadata from your checkout and `repoUrl` from the project config. Uncommitted edits are tested, but the recorded SHA still identifies the current commit. Commit your checks before using that SHA to reproduce a run. -`CHECKLY_RUN_SOURCE` describes what started a run, not its environment or commit. In Playwright Check Suites, recorded CLI tests use `TEST_RECORD`, recorded triggers use `TRIGGER_RECORD`, and scheduled runs use `SCHEDULER`. A GitHub Action running `trigger` is still `TRIGGER_RECORD`; `DEPLOYMENT` denotes a Checkly deployment hook. This sample's Browser Check did not expose that variable, so it logs the target URL instead. +`CHECKLY_RUN_SOURCE` describes what started a run, not its environment or commit. In Playwright Check Suites, recorded CLI tests use `TEST_RECORD`, recorded triggers use `TRIGGER_RECORD`, and scheduled runs use `SCHEDULER`. A GitHub Action running `trigger` is still `TRIGGER_RECORD`; `DEPLOYMENT` denotes a Checkly deployment hook. This sample's Browser check did not expose that variable, so it logs the target URL instead. ## Verify it works diff --git a/guides/setup-scripts-for-apis.mdx b/guides/setup-scripts-for-apis.mdx index 6bbba9416..44bc5c906 100644 --- a/guides/setup-scripts-for-apis.mdx +++ b/guides/setup-scripts-for-apis.mdx @@ -248,6 +248,6 @@ if (response.statusCode >= 200 && response.statusCode < 300) { - Learn end-to-end monitoring with puppeteer and playwright to test key website flows. + Learn end-to-end monitoring with puppeteer and Playwright to test key website flows. diff --git a/integrations/alerts/slack.mdx b/integrations/alerts/slack.mdx index fc6cf4e25..5c9ddff0d 100644 --- a/integrations/alerts/slack.mdx +++ b/integrations/alerts/slack.mdx @@ -22,7 +22,7 @@ You can add any **#public-channel-name** or **@username** for Direct Messages. E For each check and / or monitor, the Slack alert message contains key information, a possible root cause analysis and key actions like rerunning the check. -![A slack message showing a failed alert](/images/docs/images/alerting/slack-failed-check.png) +![A Slack message showing a failed alert](/images/docs/images/alerting/slack-failed-check.png) The root cause analysis uses AI to analyze your logs, traces, test source code, error information and other artefacts available to Checkly. Be aware that AI can make mistakes so outputs should be verified independently. @@ -32,7 +32,7 @@ For each check and / or monitor, the Slack alert message contains key informatio From the recovered Slack message, you can see the timestamp as well as a link to the check itself. -![A slack message showing a recovered alert](/images/docs/images/alerting/slack-recovered-check.png) +![A Slack message showing a recovered alert](/images/docs/images/alerting/slack-recovered-check.png) ## Migrating from the deprecated Slack webhook alert channels diff --git a/integrations/alerts/webhooks.mdx b/integrations/alerts/webhooks.mdx index 807bfc2fc..d1282844d 100644 --- a/integrations/alerts/webhooks.mdx +++ b/integrations/alerts/webhooks.mdx @@ -270,9 +270,9 @@ This means that for checks on a 1 minute schedule, there is a potential overlap The following examples give an idea how to integrate Checkly with 3rd party alerting and issue tracking systems. -### OpsGenie +### Opsgenie -You can create an OpsGenie +You can create an Opsgenie alert by POST-ing the following body @@ -284,13 +284,13 @@ alert by POST-ing the following body } ``` -to the OpsGenie `alerts` API endpoint +to the Opsgenie `alerts` API endpoint ``` https://{{OPSGENIE_API_KEY}}@api.opsgenie.com/v2/alerts ``` -Or you can add the OpsGenie API key in the headers, e.g. +Or you can add the Opsgenie API key in the headers, e.g. ``` Authorization: GenieKey {{OPSGENIE_API_KEY}} @@ -314,7 +314,7 @@ This is an example of a full alert body: } ``` -In case you would like different teams to be responsible for different Check Groups, you could add a `CHECK_GROUP_TEAM` variable with a different value for each Group, then modify the above snippet with the following: +In case you would like different teams to be responsible for different check groups, you could add a `CHECK_GROUP_TEAM` variable with a different value for each Group, then modify the above snippet with the following: ```json "responders": [ diff --git a/integrations/ci-cd/github/deployments.mdx b/integrations/ci-cd/github/deployments.mdx index 9dfdb73f7..5416aa8b9 100644 --- a/integrations/ci-cd/github/deployments.mdx +++ b/integrations/ci-cd/github/deployments.mdx @@ -61,7 +61,7 @@ The API supports GitHub deployment triggers. To configure the Checkly Vercel int If you omit both deployment filters, every successful deployment reported for the repository can trigger a run, including production deployments. Set `environmentRegexFilter` or `environmentUrlRegexFilter` when you only want to run checks against specific environments. -You can use deployment environment URLs with API, URL, browser, and multi-step checks. API and URL checks replace the host in the configured request URL. Browser and multi-step checks receive the deployment URL through the `ENVIRONMENT_URL` environment variable. +You can use deployment environment URLs with API, URL, Browser, and Multistep checks. API and URL checks replace the host in the configured request URL. Browser and Multistep checks receive the deployment URL through the `ENVIRONMENT_URL` environment variable. To change or remove a trigger created through the API, open the check or check group in Checkly and use its **CI/CD** settings. @@ -88,7 +88,7 @@ Notice we only replace the **host** part, not the URL path or any query paramete ### Browser checks & environment URLs -For browser checks, the environment URL is exposed as the `ENVIRONMENT_URL` environment variable. This means you can use that +For Browser checks, the environment URL is exposed as the `ENVIRONMENT_URL` environment variable. This means you can use that variable in your code to replace any hardcoded URL you might have, i.e.: diff --git a/integrations/ci-cd/vercel/deployment-protection.mdx b/integrations/ci-cd/vercel/deployment-protection.mdx index 2a83bda74..4c613fd49 100644 --- a/integrations/ci-cd/vercel/deployment-protection.mdx +++ b/integrations/ci-cd/vercel/deployment-protection.mdx @@ -1,6 +1,6 @@ --- title: Vercel Deployment Protection -description: "Let Checkly's browser checks reach protected Vercel preview and production deployments by passing a Protection Bypass for Automation secret in your tests." +description: "Let Checkly's Browser checks reach protected Vercel preview and production deployments by passing a Protection Bypass for Automation secret in your tests." sidebarTitle: Deployment Protection canonical: 'https://www.checklyhq.com/docs/integrations/ci-cd/vercel/deployment-protection/' --- @@ -70,7 +70,7 @@ You can tweak this setting in the Vercel dashboard under *Settings > General > D #### How to make this work with Checkly? 1. You can completely disable Standard Protection in the Vercel dashboard. This will make your deployments publicly accessible. -2. You can add some extra code to a browser check to actually log in to Vercel. Here is an example of how that would work +2. You can add some extra code to a Browser check to actually log in to Vercel. Here is an example of how that would work if you are authenticating using GitHub. Note: if you have 2FA enabled on your GitHub account, this will not work. @@ -116,7 +116,7 @@ test('visit protected deployment', async ({ page }) => { You will have to supply your GitHub username and password as environment variables (e.g. `GITHUB_USER` and `GITHUB_PASSWORD` in -the code example) to your Checkly account or as part of the [browser check's environment variables](/platform/variables). +the code example) to your Checkly account or as part of the [Browser check's environment variables](/platform/variables). ### Only Preview Deployments @@ -186,7 +186,7 @@ explore bypassing 2FA using the `otpauth` library. [Check our blog post for more ## Password Protection Vercel's [Password Protection](https://vercel.com/docs/concepts/deployments/deployment-protection#password-protection) is a paid addon that allows you to set a dedicated password for your deployments and specifically bypass protection for E2E tests / automation. -You can accomplish this using the resources referenced in the docs for [browser checks](/detect/synthetic-monitoring/browser-checks/examples#username--password-login) +You can accomplish this using the resources referenced in the docs for [Browser checks](/detect/synthetic-monitoring/browser-checks/examples#username--password-login) or [API checks](/detect/synthetic-monitoring/api-checks/setup-and-teardown). diff --git a/integrations/ci-cd/vercel/overview.mdx b/integrations/ci-cd/vercel/overview.mdx index 6cf8eb2d1..0919523c1 100644 --- a/integrations/ci-cd/vercel/overview.mdx +++ b/integrations/ci-cd/vercel/overview.mdx @@ -10,7 +10,7 @@ If you are using Vercel to develop, preview, and ship your application, you can Checkly offers two integrations for Vercel users: - Marketplace Integration, **for managing your Checkly account and users**. With the native integration, user access and billing is managed through Vercel. If you are new to Vercel's native integrations you can read more about them on the [Vercel documentation page](https://vercel.com/docs/integrations#native-integrations). - Connected Integration, **to monitor your preview and production deployments**. The connected integration can be installed stand-alone or on top of the native integration and helps you by: - - Automatically creating a pre-scripted browser check to catch any errors and failed requests as your web page loads. + - Automatically creating a pre-scripted Browser check to catch any errors and failed requests as your web page loads. - Enabling you to run checks against preview and production deployments on Vercel. @@ -113,7 +113,7 @@ With API checks, we automatically replace the hostname part of your request URL Notice we only replace the host part, not the URL path or any query parameters. -Just like for browser checks, the check will run on deploy against our preview environment, while also still running on a schedule against production. +Just like for Browser checks, the check will run on deploy against our preview environment, while also still running on a schedule against production. ### How Checkly checks maps to Vercel checks @@ -143,8 +143,8 @@ Vercel deployment in two ways because the Reliability part and Performance part | Checkly | Vercel | Blocking heuristic | |---------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| API Check | Reliability Check | Blocks deployment when it fails due to > 399 HTTP response codes, assertions and other API check specific features. | -| Browser Check | Reliability Check | Blocks deployment when it fails due to > 399 HTTP response codes on the main HTML document, syntax errors in the script, or assertions using the `expect` or `assert` libraries in the browser check script. | +| API check | Reliability Check | Blocks deployment when it fails due to > 399 HTTP response codes, assertions and other API check specific features. | +| Browser check | Reliability Check | Blocks deployment when it fails due to > 399 HTTP response codes on the main HTML document, syntax errors in the script, or assertions using the `expect` or `assert` libraries in the Browser check script. | | | Performance Check | Blocks deployment when a degradation is registered in the aggregate **Virtual Experience Score** based on Web Vitals. Read below for more details. | diff --git a/integrations/iac/pulumi/best-practices.mdx b/integrations/iac/pulumi/best-practices.mdx index 3b0ba29b5..e339f433c 100644 --- a/integrations/iac/pulumi/best-practices.mdx +++ b/integrations/iac/pulumi/best-practices.mdx @@ -86,7 +86,7 @@ apiChecks.forEach(check => { Never commit API keys, passwords, or other sensitive information directly in your Pulumi code or version control. -**Use Environment Variables:** +**Use environment variables:** ```javascript // Good: Use environment variables new checkly.Check('authenticated-api', { @@ -233,7 +233,7 @@ new checkly.Check('admin-dashboard', { ### Assertion Best Practices -**Comprehensive API Checks:** +**Comprehensive API checks:** ```javascript new checkly.Check('comprehensive-api-check', { request: { diff --git a/integrations/iac/pulumi/ci-cd.mdx b/integrations/iac/pulumi/ci-cd.mdx index 7726736e3..e341d0680 100644 --- a/integrations/iac/pulumi/ci-cd.mdx +++ b/integrations/iac/pulumi/ci-cd.mdx @@ -724,7 +724,7 @@ workflows: ### Secret Management - + **Secure Storage** - Use CI/CD platform secret management - Never hardcode secrets in pipeline files diff --git a/integrations/iac/pulumi/examples.mdx b/integrations/iac/pulumi/examples.mdx index f5c3071f0..ba67ac9b0 100644 --- a/integrations/iac/pulumi/examples.mdx +++ b/integrations/iac/pulumi/examples.mdx @@ -8,7 +8,7 @@ canonical: 'https://www.checklyhq.com/docs/integrations/iac/pulumi/examples/' This page provides comprehensive examples of how to use the Checkly Pulumi provider to create various types of monitoring checks and configurations. -## Basic API Checks +## Basic API checks ### Simple GET Request @@ -150,7 +150,7 @@ new checkly.Check('post-api-check', { -## Browser Checks +## Browser checks ### Basic Page Load Check @@ -292,7 +292,7 @@ new checkly.Check('login-flow-check', { -## Check Groups +## Check groups ### Organizing Related Checks @@ -411,9 +411,9 @@ new checkly.Check('metrics-check', { -## Alert Channels +## Alert channels -### Email Alert Channel +### Email alert channel @@ -490,7 +490,7 @@ new checkly.Check('monitored-api', { -### Slack Alert Channel +### Slack alert channel diff --git a/integrations/iac/pulumi/setup.mdx b/integrations/iac/pulumi/setup.mdx index ae6e7220c..c489ff46c 100644 --- a/integrations/iac/pulumi/setup.mdx +++ b/integrations/iac/pulumi/setup.mdx @@ -149,7 +149,7 @@ yarn add @checkly/pulumi ## Step 5: Configure Authentication -### Option 1: Environment Variables (Recommended for Development) +### Option 1: Environment variables (recommended for development) Add to your shell profile (`.bashrc`, `.zshrc`, etc.): diff --git a/integrations/iac/terraform/alerting.mdx b/integrations/iac/terraform/alerting.mdx index 0034f0f64..3ec814700 100644 --- a/integrations/iac/terraform/alerting.mdx +++ b/integrations/iac/terraform/alerting.mdx @@ -1,6 +1,6 @@ --- title: 'Alert channels and settings for Terraform' -sidebarTitle: 'Alert Channels' +sidebarTitle: 'Alert channels' description: 'Configure alert settings and alert channels for your Terraform-managed monitoring setup' canonical: 'https://www.checklyhq.com/docs/integrations/iac/terraform/alerting/' --- @@ -92,7 +92,7 @@ resource "checkly_alert_channel" "email_ac" { } ``` -Checkly supports a variety of alert channels, from email and SMS to Pagerduty and custom webhooks. For all available alert channels, see the corresponding [resource page](https://registry.terraform.io/providers/checkly/checkly/latest/docs/resources/alert_channel). +Checkly supports a variety of alert channels, from email and SMS to PagerDuty and custom webhooks. For all available alert channels, see the corresponding [resource page](https://registry.terraform.io/providers/checkly/checkly/latest/docs/resources/alert_channel). ### Alert channel subscriptions diff --git a/integrations/iac/terraform/checks-groups.mdx b/integrations/iac/terraform/checks-groups.mdx index e78650e28..f86a79f28 100644 --- a/integrations/iac/terraform/checks-groups.mdx +++ b/integrations/iac/terraform/checks-groups.mdx @@ -1,7 +1,7 @@ --- title: 'Checks and groups for Terraform' sidebarTitle: 'Checks & Groups' -description: 'Create and manage browser checks, API checks, heartbeat monitors, and check groups using Terraform' +description: 'Create and manage Browser checks, API checks, Heartbeat monitors, and check groups using Terraform' canonical: 'https://www.checklyhq.com/docs/integrations/iac/terraform/checks-groups/' --- @@ -14,7 +14,7 @@ but also have their own unique ones. The type of your check is controlled using ### Browser checks -For example, a browser check can look as follows: +For example, a Browser check can look as follows: ```terraform resource "checkly_check" "e2e-login" { @@ -118,7 +118,7 @@ resource "checkly_check" "get-books" { ### Heartbeat monitors -For example, a heartbeat monitor can look as follows: +For example, a Heartbeat monitor can look as follows: ```terraform resource "checkly_heartbeat_monitor" "send-weekly-digest-v-2" { @@ -134,7 +134,7 @@ resource "checkly_heartbeat_monitor" "send-weekly-digest-v-2" { } ``` -Upon applying your terraform configuration changes, you will be returned a read-only key value for the heartbeat ping token. The token is stored in your `tfstate` file. +Upon applying your Terraform configuration changes, you will be returned a read-only key value for the heartbeat ping token. The token is stored in your `tfstate` file. ### Multistep checks @@ -163,7 +163,7 @@ For example, a Multistep check can look as follows: ``` -### Tcp Monitors +### TCP monitors TCP monitors verify the availability and responsiveness of services running on specific ports, ensuring they are reachable and operating within acceptable response time thresholds. diff --git a/integrations/iac/terraform/dashboards.mdx b/integrations/iac/terraform/dashboards.mdx index 4ad0c45cf..1b035b67f 100644 --- a/integrations/iac/terraform/dashboards.mdx +++ b/integrations/iac/terraform/dashboards.mdx @@ -33,4 +33,4 @@ You can see all the configuration options for checks, as well as more examples, > Available as of `v1.6.6` -You can control your dashboards private/public status via Terraform by setting the `is_private` boolean to `true`. If activated, upon applying your terraform configuration changes, you will be returned a `read-only` `key` value for the dashboard which represents the password you can use to login via the browser. The password is stored in your `tfstate` file. +You can control your dashboards private/public status via Terraform by setting the `is_private` boolean to `true`. If activated, upon applying your Terraform configuration changes, you will be returned a `read-only` `key` value for the dashboard which represents the password you can use to login via the browser. The password is stored in your `tfstate` file. diff --git a/integrations/iac/terraform/environment-variables.mdx b/integrations/iac/terraform/environment-variables.mdx index 565cc1fba..11cef3144 100644 --- a/integrations/iac/terraform/environment-variables.mdx +++ b/integrations/iac/terraform/environment-variables.mdx @@ -1,6 +1,6 @@ --- -title: 'Environment Variables in Terraform' -sidebarTitle: 'Environment Variables' +title: 'Environment variables in Terraform' +sidebarTitle: 'Environment variables' description: 'Manage environment variables to reduce duplication in your monitoring setup' canonical: 'https://www.checklyhq.com/docs/integrations/iac/terraform/environment-variables/' --- diff --git a/integrations/iac/terraform/maintenance-windows.mdx b/integrations/iac/terraform/maintenance-windows.mdx index c026cd708..198e32d85 100644 --- a/integrations/iac/terraform/maintenance-windows.mdx +++ b/integrations/iac/terraform/maintenance-windows.mdx @@ -1,6 +1,6 @@ --- title: 'Service maintenance windows in Terraform' -sidebarTitle: 'Service Maintenance Windows' +sidebarTitle: 'Service maintenance windows' description: 'Schedule planned maintenance windows to prevent checks from running during specific times' canonical: 'https://www.checklyhq.com/docs/integrations/iac/terraform/maintenance-windows/' --- diff --git a/integrations/iac/terraform/overview.mdx b/integrations/iac/terraform/overview.mdx index fc57b8658..c32f0a13c 100644 --- a/integrations/iac/terraform/overview.mdx +++ b/integrations/iac/terraform/overview.mdx @@ -92,9 +92,9 @@ commands will detect it and remind you to do so if necessary. You can now start adding resources to your file. You can check the official documentation to see [available parameters](https://registry.terraform.io/providers/checkly/checkly/latest/docs/resources/check) for each resource type. -## Your first browser check +## Your first Browser check -As an example, you could add a basic browser check resource at the bottom of your `main.tf`. +As an example, you could add a basic Browser check resource at the bottom of your `main.tf`. ```terraform main.tf resource "checkly_check" "browser-check-1" { @@ -128,7 +128,7 @@ EOT ## Applying changes -You can now have Terraform apply your changes on Checkly by running `terraform apply`. Terraform will draft a plan and ask you to confirm by typing `yes`. Once that is done, Terraform will go ahead and create the resources you have specified (one browser check, so far) for you. +You can now have Terraform apply your changes on Checkly by running `terraform apply`. Terraform will draft a plan and ask you to confirm by typing `yes`. Once that is done, Terraform will go ahead and create the resources you have specified (one Browser check, so far) for you. ```bash Terminal $ terraform apply diff --git a/integrations/iac/terraform/parameterized-resources.mdx b/integrations/iac/terraform/parameterized-resources.mdx index a2bcf6a28..a8ef2cf22 100644 --- a/integrations/iac/terraform/parameterized-resources.mdx +++ b/integrations/iac/terraform/parameterized-resources.mdx @@ -9,7 +9,7 @@ There are cases where you might want to declare a single, parameterized resource ## File-based parameterization -You can use a combination of the [`for_each` meta-argument](https://www.terraform.io/language/meta-arguments/for_each) and the [fileset function](https://www.terraform.io/language/functions/fileset) to your advantage, for example when creating browser checks that share all their settings apart from their script: +You can use a combination of the [`for_each` meta-argument](https://www.terraform.io/language/meta-arguments/for_each) and the [fileset function](https://www.terraform.io/language/functions/fileset) to your advantage, for example when creating Browser checks that share all their settings apart from their script: ```terraform resource "checkly_check" "browser-check" { @@ -34,6 +34,6 @@ resource "checkly_check" "browser-check" { } ``` -This will create as many browser checks running each minute as there are files in the `./scripts` folder in your project's path. +This will create as many Browser checks running each minute as there are files in the `./scripts` folder in your project's path. > Aside from checks, these constructs can be useful for a variety of resources like alert channels and more. diff --git a/integrations/iac/terraform/testing-scripts-locally.mdx b/integrations/iac/terraform/testing-scripts-locally.mdx index 6e1589dcc..932921d61 100644 --- a/integrations/iac/terraform/testing-scripts-locally.mdx +++ b/integrations/iac/terraform/testing-scripts-locally.mdx @@ -1,15 +1,15 @@ --- title: 'Testing Terraform scripts locally' sidebarTitle: 'Testing Scripts Locally' -description: 'Run Playwright Test scripts locally for faster development and debugging of browser checks' +description: 'Run Playwright Test scripts locally for faster development and debugging of Browser checks' canonical: 'https://www.checklyhq.com/docs/integrations/iac/terraform/testing-scripts-locally/' --- -Having the possibility to run Playwright Test scripts for your browser checks locally will allow you to develop them faster and with more confidence. +Having the possibility to run Playwright Test scripts for your Browser checks locally will allow you to develop them faster and with more confidence. ## Enabling local script execution -You can easily enable local execution by storing your browser check scripts in local folders and passing the path to the right script: +You can easily enable local execution by storing your Browser check scripts in local folders and passing the path to the right script: ```terraform resource "checkly_check" "e2e-checkout" { diff --git a/integrations/incident-management/opsgenie.mdx b/integrations/incident-management/opsgenie.mdx index d30014bcc..fc809e360 100644 --- a/integrations/incident-management/opsgenie.mdx +++ b/integrations/incident-management/opsgenie.mdx @@ -44,7 +44,7 @@ create a new Opsgenie channel. 5. Choose a name for your Opsgenie channel, paste your **API Key** and select your Opsgenie region (`EU` for EU based customers, `US` for the rest of the world). - > 💡 In OpsGenie you can configure other options like + > 💡 In Opsgenie you can configure other options like [alert priority](https://docs.opsgenie.com/docs/alert-priority-settings). > 💡 On Checkly, you can specify which [check events](/communicate/alerts/channels) will be sent over to Opsgenie. diff --git a/integrations/incident-management/pagerduty.mdx b/integrations/incident-management/pagerduty.mdx index 9c0377e6d..a820f1b43 100644 --- a/integrations/incident-management/pagerduty.mdx +++ b/integrations/incident-management/pagerduty.mdx @@ -13,21 +13,21 @@ import AlertChannelSecrets from '/snippets/alert-channel-secrets-callout.mdx'; The PagerDuty channel's `serviceKey` (integration key) accepts environment-variable references — e.g. `{{PAGERDUTY_SERVICE_KEY}}` — so you can store the integration key as an account secret instead of inline in the channel config. -Checkly integrates with [Pagerduty](https://pagerduty.com) and can deliver all failure and recovery events -to your Pagerduty account. After setting up the integration, Checkly will: +Checkly integrates with [PagerDuty](https://pagerduty.com) and can deliver all failure and recovery events +to your PagerDuty account. After setting up the integration, Checkly will: -1. Trigger alerts in Pagerduty when a check fails. +1. Trigger alerts in PagerDuty when a check fails. 2. Resolve alerts when a check recovers. 3. Trigger alerts when a check degrades or an SSL certificate is about to expire, if you enable these notification events. -Setup is as simple as following the three-step Pagerduty connect process. You can add as many Pagerduty channels as +Setup is as simple as following the three-step PagerDuty connect process. You can add as many PagerDuty channels as you wish. 1. Click **Alert channels** in the left sidebar (under **Communicate**) to open your [alert settings](https://app.checklyhq.com/alerts/settings), then click the **Add more channels** button and select **PagerDuty**. ![setup checkly pagerduty integration step 1](/images/docs/images/integrations/pagerduty_step1.png) -2. Clicking the **Alert with Pagerduty** button will take you to a Pagerduty Connect screen. Provide your credentials and click -**Sign In** to allow Checkly to connect with Pagerduty. +2. Clicking the **Alert with Pagerduty** button will take you to a PagerDuty Connect screen. Provide your credentials and click +**Sign In** to allow Checkly to connect with PagerDuty. ![set up checkly pagerduty integration step 2](/images/docs/images/integrations/pagerduty_step2.png) 3. On the next screen you can hook up Checkly to one or more existing services. If you select multiple services, we will @@ -35,12 +35,12 @@ create multiple dedicated channels so you have more flexibility of muting, editi Click **Connect** to save your settings and redirect you back to Checkly. ![set up checkly pagerduty integration step 3](/images/docs/images/integrations/pagerduty_step3.png) -4. Back in Checkly, you should see your Pagerduty **integration credentials** reflected in the alert settings. Don't forget +4. Back in Checkly, you should see your PagerDuty **integration credentials** reflected in the alert settings. Don't forget to hit **Create PagerDuty channel**. ![set up checkly pagerduty integration step 4](/images/docs/images/integrations/pagerduty_step4.png) -5. Checkly will trigger an incident in Pagerduty when checks fail and also mark them as resolved when the checks are passing again. +5. Checkly will trigger an incident in PagerDuty when checks fail and also mark them as resolved when the checks are passing again. ![set up checkly pagerduty integration step 5](/images/docs/images/integrations/pagerduty_step5.png) ## PagerDuty Best Practices diff --git a/integrations/observability/coralogix.mdx b/integrations/observability/coralogix.mdx index 9b16b947e..4b8c1c995 100644 --- a/integrations/observability/coralogix.mdx +++ b/integrations/observability/coralogix.mdx @@ -1,20 +1,20 @@ --- title: 'Export Metrics & Data via Coralogix' -description: 'Deep integration with Coralogix for Open Telemetry tracing, RUM monitoring, and alert notifications' +description: 'Deep integration with Coralogix for OpenTelemetry tracing, RUM monitoring, and alert notifications' sidebarTitle: 'Coralogix' canonical: 'https://www.checklyhq.com/docs/integrations/observability/coralogix/' --- Checkly deeply integrates with [Coralogix](https://coralogix.com/) in three ways: -1. Checkly can automatically instrument all check executions with **Open Telemetry tracing** and send the data to Coralogix +1. Checkly can automatically instrument all check executions with **OpenTelemetry tracing** and send the data to Coralogix as traces. 2. Checkly can automatically instrument your Browser checks with **Coralogix RUM (Real User Monitoring)**. 3. Checkly can send **alert notifications** when checks pass and/or fail to **Coralogix Logs**. -## Open Telemetry tracing integration +## OpenTelemetry tracing integration -To set up the Open Telemetry tracing integration, first enable the Coralogix integration in your Checkly account in the +To set up the OpenTelemetry tracing integration, first enable the Coralogix integration in your Checkly account in the [integrations section](https://app.checklyhq.com/settings/account/integrations). ![coralogix otel integration](/images/docs/images/integrations/coralogix/cx_otel_int1.png) @@ -73,7 +73,7 @@ and forward to Coralogix using an OpenTelemetry Collector. ## RUM integration -In addition to the Open Telemetry tracing, Checkly can also send RUM data to Coralogix for all Browser checks. This enables +In addition to the OpenTelemetry tracing, Checkly can also send RUM data to Coralogix for all Browser checks. This enables tracking your Playwright-powered checks to be recorded as (semi) real users, so you can compare and contrast the performance between synthetic and real users. @@ -90,7 +90,7 @@ Copy and paste the integration key into Checkly. > Only the integration key is needed for the Checkly integration. -5. As Checkly automatically injects the Coralogix RUM SDK to each browser check run, uploading and setting up the SourceMap is not required. You can **skip** the **Install & setup Browser SDK Package** step and finish the set up there. +5. As Checkly automatically injects the Coralogix RUM SDK to each Browser check run, uploading and setting up the SourceMap is not required. You can **skip** the **Install & setup Browser SDK Package** step and finish the set up there. If you are targeting multiple applications with your checks, you can override the global application name by adding the environment variable `CORALOGIX_RUM_APP_NAME` to your Browser check. You can find the Browser check specific environment @@ -101,7 +101,7 @@ After enabling the RUM integration, Checkly will start sending RUM data to Coral > Note that you do not need to install the RUM SDK in your application, Checkly will automatically inject the necessary > JavaScript snippet into your Browser checks. However, if you have installed the SDK we will use the existing installation and not inject the snippet. -## Alert Channel → Coralogix Logs integration +## Alert channel → Coralogix Logs integration You can set up Coralogix as an alert channel destination, so Coralogix receives any alert notifications you have set up as logs. Note that you can use this integration separately from the other two integrations mentioned above. diff --git a/integrations/observability/prometheus-v2.mdx b/integrations/observability/prometheus-v2.mdx index 2aa81e939..74f05c34f 100644 --- a/integrations/observability/prometheus-v2.mdx +++ b/integrations/observability/prometheus-v2.mdx @@ -74,8 +74,8 @@ The following metrics are available to monitor checks: | `checkly_dns_monitor_timing_seconds` | Histogram | The total duration of the DNS monitor. | | `checkly_grpc_monitor_timing_seconds` | Histogram | The timing phases of the gRPC monitor, including DNS resolution, connection, and total RPC duration. | | `checkly_grpc_monitor_status_code` | Gauge | The gRPC status code returned on the latest run (`0` = OK). | -| `checkly_traceroute_monitor_timing_seconds` | Histogram | The timing phases of the traceroute monitor, including DNS resolution and final hop latency. | -| `checkly_traceroute_monitor_hops` | Gauge | The total number of hops for the traceroute monitor. | +| `checkly_traceroute_monitor_timing_seconds` | Histogram | The timing phases of the Traceroute monitor, including DNS resolution and final hop latency. | +| `checkly_traceroute_monitor_hops` | Gauge | The total number of hops for the Traceroute monitor. | | `checkly_traceroute_monitor_destination_reached` | Gauge | Whether the traceroute reached its destination on the latest run (`1`) or not (`0`). | | `checkly_ssl_monitor_days_until_expiry` | Gauge | The average days remaining until the certificate checked by the SSL monitor expires, over the current scrape window. | | `checkly_ssl_monitor_handshake_seconds` | Histogram | The TLS handshake duration of the SSL monitor. | @@ -87,7 +87,7 @@ The following metrics are available to monitor checks: | `checkly_multistep_check_duration_seconds` | Histogram | The total check duration. This includes all requests done and any waits. | | `checkly_playwright_check_duration_seconds` | Histogram | The total duration of the Playwright Check Suite. | | `checkly_heartbeat_last_success_timestamp_seconds` | Gauge | The Unix timestamp of the last successful heartbeat ping. A value of `0` means no successful ping has ever been received. | -| `checkly_heartbeat_expected_interval_seconds` | Gauge | The configured maximum interval between heartbeat pings, in seconds. Derived from the heartbeat monitor's period and period unit settings. | +| `checkly_heartbeat_expected_interval_seconds` | Gauge | The configured maximum interval between heartbeat pings, in seconds. Derived from the Heartbeat monitor's period and period unit settings. | | `checkly_time_to_ssl_expiry_seconds` | Gauge | The amount of time remaining before the SSL certificate of the monitored domain expires. See the [SSL certificate expiration docs](/communicate/alerts/ssl-expiration) for more information on monitoring SSL certificates with checks. | The `checkly_check_status` and `checkly_check_result_total` metrics contain a `status` label with values `passing`, `failing`, and `degraded`. @@ -132,7 +132,7 @@ In addition, the check metrics all contain the following labels: 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. Heartbeat metrics (`checkly_heartbeat_last_success_timestamp_seconds`, `checkly_heartbeat_expected_interval_seconds`, and heartbeat entries in `checkly_check_result_total`) also do not have a `location` label, since heartbeat monitors receive pings rather than running from specific locations. All other [check metrics](#check-metrics) will have the `location` label added. +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. Heartbeat metrics (`checkly_heartbeat_last_success_timestamp_seconds`, `checkly_heartbeat_expected_interval_seconds`, and heartbeat entries in `checkly_check_result_total`) also do not have a `location` label, since Heartbeat monitors receive pings rather than running from specific locations. 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: @@ -210,7 +210,7 @@ sum by(type) (rate(checkly_browser_check_web_vitals_seconds_sum{name="Check Name [Heartbeat monitors](/detect/uptime-monitoring/heartbeat-monitors/overview) are passive checks that wait for your scheduled jobs and automated processes to send a ping. The Prometheus exporter includes heartbeat checks in the standard `checkly_check_status` and `checkly_check_result_total` metrics, plus two heartbeat-specific gauges designed for [dead man's switch](https://en.wikipedia.org/wiki/Dead_man%27s_switch) alerting. - **`checkly_heartbeat_last_success_timestamp_seconds`** — The Unix timestamp of the last successful ping, searched across the entire event history (no time window). A value of `0` means no successful ping has ever been received — this immediately triggers a dead man's switch alert since `time() - 0` produces a very large value. -- **`checkly_heartbeat_expected_interval_seconds`** — The maximum expected time between pings, derived from the heartbeat monitor's configured period and period unit (e.g., `5 minutes` = `300` seconds). Use this as a threshold for alerting. +- **`checkly_heartbeat_expected_interval_seconds`** — The maximum expected time between pings, derived from the Heartbeat monitor's configured period and period unit (e.g., `5 minutes` = `300` seconds). Use this as a threshold for alerting. ### How heartbeats map to `checkly_check_result_total` @@ -220,7 +220,7 @@ Heartbeat checks contribute to `checkly_check_result_total` using a 1-hour count |----------------|--------------------------| | `passing` | `RECEIVED`, `EARLY`, `GRACE`, `LATE` — any ping that arrived | | `failing` | `FAILING` — no ping received before the grace period expired | -| `degraded` | Always `0` — heartbeat monitors do not have a degraded state | +| `degraded` | Always `0` — Heartbeat monitors do not have a degraded state | ### Dead Man's Switch PromQL Examples @@ -248,27 +248,27 @@ Show how long ago each heartbeat was last seen: time() - checkly_heartbeat_last_success_timestamp_seconds ``` -## Private Location Metrics +## Private location metrics -The Prometheus exporter also contains metrics for monitoring [Private Locations](/platform/private-locations/overview). These metrics can be used to ensure that your Private Locations have enough Checkly Agent instances running to execute all of your checks, and to drive [agent autoscaling](/platform/private-locations/autoscaling). +The Prometheus exporter also contains metrics for monitoring [private locations](/platform/private-locations/overview). These metrics can be used to ensure that your private locations have enough Checkly Agent instances running to execute all of your checks, and to drive [agent autoscaling](/platform/private-locations/autoscaling). -The following metrics are available to monitor Private Locations: +The following metrics are available to monitor private locations: | Metric | Type | Description | |--------|------|-------------| -| `checkly_private_location_queue_size` | Gauge | The number of check runs scheduled to the Private Location and waiting to be executed. A high value indicates that checks are becoming backlogged and that you may need to [scale your Checkly Agents](/platform/private-locations/scaling-redundancy). | -| `checkly_private_location_oldest_scheduled_check_run` | Gauge | The age in seconds of the oldest check run job scheduled to the Private Location queue. A high value indicates that checks are becoming backlogged. | -| `checkly_private_location_queue_duration_ms` | Gauge | The scheduling delay in milliseconds for check runs routed through a Private Location, by queue and `stat`. Derived from the last 2 minutes of check run data. Used to evaluate whether sufficient agent capacity is provisioned for the Private Location. | -| `checkly_private_location_agent_count` | Gauge | The number of agents connected for the Private Location. | -| `checkly_private_location_check_runs` | Gauge | The count of check runs in the Private Location, broken down by lifecycle state via the `state` label and by routing queue via the `queue` label. Used as the signal for [autoscaling Checkly Agents](/platform/private-locations/autoscaling). | +| `checkly_private_location_queue_size` | Gauge | The number of check runs scheduled to the private location and waiting to be executed. A high value indicates that checks are becoming backlogged and that you may need to [scale your Checkly Agents](/platform/private-locations/scaling-redundancy). | +| `checkly_private_location_oldest_scheduled_check_run` | Gauge | The age in seconds of the oldest check run job scheduled to the private location queue. A high value indicates that checks are becoming backlogged. | +| `checkly_private_location_queue_duration_ms` | Gauge | The scheduling delay in milliseconds for check runs routed through a private location, by queue and `stat`. Derived from the last 2 minutes of check run data. Used to evaluate whether sufficient agent capacity is provisioned for the private location. | +| `checkly_private_location_agent_count` | Gauge | The number of agents connected for the private location. | +| `checkly_private_location_check_runs` | Gauge | The count of check runs in the private location, broken down by lifecycle state via the `state` label and by routing queue via the `queue` label. Used as the signal for [autoscaling Checkly Agents](/platform/private-locations/autoscaling). | -The Private Location metrics all contain the following labels: +The private location metrics all contain the following labels: | Label | Description | | ------|-------------| -| `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_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. | `checkly_private_location_check_runs` additionally carries a `queue` label (`uptime` or `main`) and a `state` label. The `state` values relevant for autoscaling are: diff --git a/learn/incidents/anatomy-of-a-status-page.mdx b/learn/incidents/anatomy-of-a-status-page.mdx index 902cfccf4..d6355bf0e 100644 --- a/learn/incidents/anatomy-of-a-status-page.mdx +++ b/learn/incidents/anatomy-of-a-status-page.mdx @@ -1,7 +1,7 @@ --- -title: Anatomy of a Status Page | Checkly Guide -displayTitle: Anatomy of a Status Page -sidebarTitle: Anatomy of a Status Page +title: Anatomy of a status page | Checkly Guide +displayTitle: Anatomy of a status page +sidebarTitle: Anatomy of a status page description: Discover what makes a status page users trust - automated monitoring, clear visuals, service groupings, and more. date: 2025-04-08 author: Nocnica Mellifera @@ -57,7 +57,7 @@ The basic technical requirements (fast loading pages, manual edits permitted, et **3. Clear infographics** - a status page should be able to take complex historical data and turn it into a clear history for the viewer. Some kind of graphing library should represent high level status data visually. -**4. Incidents should be organized into services** - for Checkly’s Status Pages, all alerts are [classified ahead of time into services](/communicate/status-pages/overview#services). We don’t want to present our product as a monolith, nor should we print inscrutable internal labels. With this organization, we can present sections on a single status page, or multiple separate status pages with groupings of services. +**4. Incidents should be organized into services** - for Checkly’s status pages, all alerts are [classified ahead of time into services](/communicate/status-pages/overview#services). We don’t want to present our product as a monolith, nor should we print inscrutable internal labels. With this organization, we can present sections on a single status page, or multiple separate status pages with groupings of services. **5. Subscription service** - Users should subscribe to only the pages they care about. @@ -65,4 +65,4 @@ The basic technical requirements (fast loading pages, manual edits permitted, et In short, a good status page keeps users informed and builds trust. It must be clear, reliable, and easy to use. Users want quick updates, simple labels, and the ability to subscribe. On the tech side, it needs automated monitoring, independent hosting, and clear visuals. By meeting these needs, your status page will help users stay updated and reduce frustration. -**Further reading:** [A guide to Checkly’s Status Pages](/communicate/status-pages/overview) \ No newline at end of file +**Further reading:** [A guide to Checkly’s status pages](/communicate/status-pages/overview) \ No newline at end of file diff --git a/learn/incidents/mttr-challenges.mdx b/learn/incidents/mttr-challenges.mdx index 03187ccbe..85f6fc662 100644 --- a/learn/incidents/mttr-challenges.mdx +++ b/learn/incidents/mttr-challenges.mdx @@ -61,7 +61,7 @@ Once an issue is detected, the next step is to stop the customer pain by impleme - Providing engineers with actionable data and context in alerts. For example, linking alerts to dashboards that show affected services or customers can help engineers prioritize and resolve issues more efficiently. - Linking alerts with deeper root cause information. While it’s critical to show ‘who is affected and how,’ it’s also supremely important to give some indication of what’s happening internal to our services so that our engineers are not stuck sorting through backend logs trying to match time stamps. For example, Checkly Traces links backend traces with synthetic monitoring data, to show application internals related to any user-facing issue. -- Easy rollbacks. Whether it’s deploying rolled back code right from source control with (for example) GitHub actions, or feature flagging to disable a new feature that’s causing trouble, it’s critical that on-call teams are empowered to get the service back to a working state by rolling back the clock. +- Easy rollbacks. Whether it’s deploying rolled back code right from source control with (for example) GitHub Actions, or feature flagging to disable a new feature that’s causing trouble, it’s critical that on-call teams are empowered to get the service back to a working state by rolling back the clock. With these tools an on-call team can get the system working for users quickly, followed by a longer period of root cause analysis and postmortem. diff --git a/learn/incidents/overview.mdx b/learn/incidents/overview.mdx index 7e3ed1f2b..8aaddec1a 100644 --- a/learn/incidents/overview.mdx +++ b/learn/incidents/overview.mdx @@ -25,7 +25,7 @@ Further, expectations about uptime have gone from ‘best practices’ to ‘bin Incident Response in the software industry refers to a time-critical response to some kind of availability incident. What makes a good status page? Learn user expectations and technical requirements diff --git a/learn/incidents/reduce-mttd.mdx b/learn/incidents/reduce-mttd.mdx index 44577d95e..1748ad5bd 100644 --- a/learn/incidents/reduce-mttd.mdx +++ b/learn/incidents/reduce-mttd.mdx @@ -49,7 +49,7 @@ Many of the points listed in this article will revolve around making sure that a - Take alert fatigue seriously — false positives (alerts when there was no problem) should trigger investigations and fixes just like false negatives (undetected outages). - Set retry policies — requests sometimes fail via the internet. Set a reasonable [retry policy](/communicate/alerts/overview) on your checks so you’re not generating false alarms. - Use smart tests — using the [auto-waiting](https://www.checklyhq.com/learn/playwright/waits-and-timeouts/) and intelligent user-centric assertions of Playwright will help ensure your tests aren’t too strict and therefore flaky (generating lots of false positives). -- Route alerts intelligently — use a tool like Rootly or Pagerduty to make sure only the right people are getting alerts. +- Route alerts intelligently — use a tool like Rootly or PagerDuty to make sure only the right people are getting alerts. If you take these steps, you can help ensure that a human being is reading all the alerts they receive. The other points included in this article will also help reduce how many alerts your engineers get that they can safely ignore. diff --git a/learn/incidents/root-cause-with-traces.mdx b/learn/incidents/root-cause-with-traces.mdx index d2f6dbb0a..b94328cf8 100644 --- a/learn/incidents/root-cause-with-traces.mdx +++ b/learn/incidents/root-cause-with-traces.mdx @@ -59,7 +59,7 @@ Example trace showing a failed payment process: Proactively test critical user journeys with: -- Scripted browser checks (e.g., login → add to cart → checkout) +- Scripted Browser checks (e.g., login → add to cart → checkout) - API test sequences with assertions - Geographic performance testing @@ -83,7 +83,7 @@ When combined, these approaches: | --- | --- | --- | | Tracing | Jaeger, Tempo, Honeycomb | Visualize request flows | | Synthetic | Checkly, Synthetics | Test user journeys proactively | -| Alerting | Rootly, OpsGenie | Route incidents effectively | +| Alerting | Rootly, Opsgenie | Route incidents effectively | ### 3. Analyze Incidents diff --git a/learn/incidents/slo-sla-sli.mdx b/learn/incidents/slo-sla-sli.mdx index 892e47fe3..e0d438ea7 100644 --- a/learn/incidents/slo-sla-sli.mdx +++ b/learn/incidents/slo-sla-sli.mdx @@ -165,9 +165,9 @@ By setting these SLIs, SLOs, and SLAs, the company not only commits to deliverin ## **How Checkly Can Help You Hit Your SLAs** -[Checkly](https://www.checklyhq.com/) focuses on Synthetic Monitoring to track how well websites, applications, and APIs work. Its goal is to help [meet Service Level Agreements (SLAs)](https://www.checklyhq.com/blog/how-to-monitor-all-the-nines-of-your-service-level-agreements/) with customers with its features such as API checks, browser checks, heartbeat monitoring, etc. +[Checkly](https://www.checklyhq.com/) focuses on Synthetic Monitoring to track how well websites, applications, and APIs work. Its goal is to help [meet Service Level Agreements (SLAs)](https://www.checklyhq.com/blog/how-to-monitor-all-the-nines-of-your-service-level-agreements/) with customers with its features such as API checks, Browser checks, heartbeat monitoring, etc. -### **API Checks** +### **API checks** [API checks](https://www.checklyhq.com/blog/what-is-api-monitoring/) monitor vital API endpoints frequently from various global locations. They allow for the validation of response codes and bodies to ensure accuracy, while also keeping an eye on response times to maintain a quick and efficient experience. Additionally, the feature of receiving instant alerts when any monitoring checks indicate a failure provides the assurance needed for maintaining smooth API operations. This proactive approach to monitoring ensures that APIs function seamlessly, enhancing reliability and user satisfaction. @@ -184,23 +184,23 @@ Checkly’s API checks can help you achieve your SLAs through: - **Performance Tracking:** Checkly tracks the performance of your APIs over time, offering insights into trends and potential areas of improvement. This data can help you optimize your services to not only meet but exceed SLA expectations regarding response times and reliability. - **Detailed Reporting:** The platform provides detailed reports and dashboards that give visibility into API health, performance metrics, and historical data. These insights can be used to demonstrate compliance with SLAs during audits and reviews with stakeholders. -### **Browser Checks** +### **Browser checks** -On the other hand, Checkly’s Playwright-based [browser checks](/detect/synthetic-monitoring/browser-checks/overview) mimic user actions to make sure key processes work smoothly, and the heartbeat feature checks if systems are running properly. These capabilities enable the monitoring of response times, uptime, functionality, and internal systems performance. This comprehensive monitoring supports SLAs in keeping services healthy and running efficiently. +On the other hand, Checkly’s Playwright-based [Browser checks](/detect/synthetic-monitoring/browser-checks/overview) mimic user actions to make sure key processes work smoothly, and the heartbeat feature checks if systems are running properly. These capabilities enable the monitoring of response times, uptime, functionality, and internal systems performance. This comprehensive monitoring supports SLAs in keeping services healthy and running efficiently. ![a checkly dashboard](/images/learn/images/sla-02.png) -Checkly’s browser checks can help you achieve your SLAs through: +Checkly’s Browser checks can help you achieve your SLAs through: -- **Real User Simulation:** Checkly's browser checks use real browsers to simulate user actions, such as clicking links, filling out forms, and navigating through web pages. This allows you to test and monitor the end-to-end user experience, ensuring that your application meets SLA requirements for functionality and user satisfaction. -- **Global Coverage:** By running browser checks from multiple locations worldwide, you can ensure that your web application delivers a consistent user experience across different geographical regions. This is particularly important for SLAs that specify performance standards across diverse user bases. +- **Real User Simulation:** Checkly's Browser checks use real browsers to simulate user actions, such as clicking links, filling out forms, and navigating through web pages. This allows you to test and monitor the end-to-end user experience, ensuring that your application meets SLA requirements for functionality and user satisfaction. +- **Global Coverage:** By running Browser checks from multiple locations worldwide, you can ensure that your web application delivers a consistent user experience across different geographical regions. This is particularly important for SLAs that specify performance standards across diverse user bases. - **Performance Metrics:** Checkly provides detailed performance metrics, such as page load times, which are crucial for meeting SLAs related to website speed and responsiveness. Monitoring these metrics allows you to identify and address performance bottlenecks before they affect user satisfaction. - **Visual Regression Testing:** You can use Checkly to perform [visual regression testing](https://www.checklyhq.com/blog/visual-regression-testing-with-playwright/), which ensures that your web application's visual elements render correctly across different browsers and devices. This helps maintain a high-quality user interface, in line with SLA standards for usability and design. -- **Error Detection and Alerting:** Checkly alerts you in real-time if a browser check fails, enabling you to quickly identify and resolve issues such as broken links, malfunctioning features, or downtime. This rapid response capability is essential for adhering to SLAs that stipulate minimal downtime and quick issue resolution. -- **Customizable Check Intervals:** You can configure the frequency of your browser checks to match the criticality of different application components. For example, you might run checks on key user flows every few minutes to ensure high availability and performance, aligning with stringent SLA requirements. +- **Error Detection and Alerting:** Checkly alerts you in real-time if a Browser check fails, enabling you to quickly identify and resolve issues such as broken links, malfunctioning features, or downtime. This rapid response capability is essential for adhering to SLAs that stipulate minimal downtime and quick issue resolution. +- **Customizable Check Intervals:** You can configure the frequency of your Browser checks to match the criticality of different application components. For example, you might run checks on key user flows every few minutes to ensure high availability and performance, aligning with stringent SLA requirements. - **Reporting and Insights:** Checkly provides comprehensive reports and dashboards that offer insights into the historical performance and reliability of your web application. These insights can be used to demonstrate compliance with SLAs during stakeholder reviews and to identify areas for improvement. -*To find out more about Checkly’s browser checks & how to get started, check out [this article](/detect/synthetic-monitoring/browser-checks/overview).* +*To find out more about Checkly’s Browser checks & how to get started, check out [this article](/detect/synthetic-monitoring/browser-checks/overview).* ### **Checkly Best Practices** diff --git a/learn/monitoring/api-monitoring.mdx b/learn/monitoring/api-monitoring.mdx index 5d9550a52..879b5146a 100644 --- a/learn/monitoring/api-monitoring.mdx +++ b/learn/monitoring/api-monitoring.mdx @@ -77,7 +77,7 @@ The next step is to choose an API monitoring tool that will best support your ne Checkly’s [API monitoring tool](https://www.checklyhq.com/product/api-monitoring/) is an optimal solution for companies keen to develop and integrate an effective API monitoring flow into their existing development and maintenance processes. -Checkly enables you to streamline the API monitoring process. You can start by creating or importing HTTP requests for the endpoints you want to monitor, then specify assertions against the response (and response time). There are ample opportunities to customize [setup and teardown](/detect/synthetic-monitoring/api-checks/setup-and-teardown) [using scripts](/guides/setup-scripts-for-apis) to fetch OAuth tokens or help clean test data. Checkly has data centers in twenty locations worldwide, from which it can run API checks up to every ten seconds. This is crucial to get a comprehensive and accurate picture of the health of your APIs. Finally, depending on your workflow, [Checkly also integrates with services such as Slack](/communicate/alerts/channels), email, and Pagerduty to notify and alert you of any incidents. +Checkly enables you to streamline the API monitoring process. You can start by creating or importing HTTP requests for the endpoints you want to monitor, then specify assertions against the response (and response time). There are ample opportunities to customize [setup and teardown](/detect/synthetic-monitoring/api-checks/setup-and-teardown) [using scripts](/guides/setup-scripts-for-apis) to fetch OAuth tokens or help clean test data. Checkly has data centers in twenty locations worldwide, from which it can run API checks up to every ten seconds. This is crucial to get a comprehensive and accurate picture of the health of your APIs. Finally, depending on your workflow, [Checkly also integrates with services such as Slack](/communicate/alerts/channels), email, and PagerDuty to notify and alert you of any incidents. ## API Monitoring as Code @@ -101,9 +101,9 @@ By default, you have access to a free Team trial which expires after 14 days, so ### Step 2: Create a New Check -Once you've signed up and logged in, you can proceed to a [Browser Check](/detect/synthetic-monitoring/browser-checks/overview), API Check or use the CLI script. +Once you've signed up and logged in, you can proceed to a [Browser check](/detect/synthetic-monitoring/browser-checks/overview), API check or use the CLI script. -Let’s play around with the API Check. On your dashboard, click the "API Check" tab (you can toggle between tabs). You should see an interface like this: +Let’s play around with the API check. On your dashboard, click the "API Check" tab (you can toggle between tabs). You should see an interface like this: ![A diagram of dependencies](/images/learn/images/api-monitoring-03.png) @@ -151,7 +151,7 @@ Monitoring frequency determines how often Checkly will send requests to your API You can choose from various intervals like every minute or custom intervals based on your needs. You can also add assertions and limits to validate specific response criteria like status codes or response time. -### Step 5: Define Alert Channels +### Step 5: Define alert channels Alert channels allow you to receive notifications when issues or errors are detected during API monitoring. Checkly supports multiple alert channels including email, phone calls, SMS, Slack, Discord, Telegram, PagerDuty, Webhooks and more. Configure the desired alert channels and provide relevant contact information. diff --git a/learn/monitoring/end-to-end-monitoring.mdx b/learn/monitoring/end-to-end-monitoring.mdx index d00380259..cba654579 100644 --- a/learn/monitoring/end-to-end-monitoring.mdx +++ b/learn/monitoring/end-to-end-monitoring.mdx @@ -1,6 +1,6 @@ --- title: What is End to End Monitoring? An Overview with Examples -description: Learn end-to-end monitoring with playwright to test key website flows. Follow our guide that gets you up and running in 10 minutes. +description: Learn end-to-end monitoring with Playwright to test key website flows. Follow our guide that gets you up and running in 10 minutes. tags: Playwright sidebarTitle: What is End-to-End Monitoring? canonical: 'https://www.checklyhq.com/docs/learn/monitoring/end-to-end-monitoring/' @@ -157,7 +157,7 @@ We can move our scripts to separate checks to keep them [independent](/learn/pla ![checkly dashboard screenshot](/images/guides/images/guides-checkly-dashboard.png "Checkly's dashboard") -As soon as a check runs red, we are alerted in real time and can **intervene before the issue impacts our users**. Alerting can be set up with all the industry-standard channels like Pagerduty, Opsgenie, Slack, email, SMS and more. +As soon as a check runs red, we are alerted in real time and can **intervene before the issue impacts our users**. Alerting can be set up with all the industry-standard channels like PagerDuty, Opsgenie, Slack, email, SMS and more. ![checkly alerting screenshot](/images/guides/images/guides-checkly-alerting.png "Alert channels on Checkly") @@ -251,7 +251,7 @@ Once this setup is complete, log in to your Checkly account via the CLI using th `npx checkly login` You can choose to log in from the browser or in your terminal. After logging in, you'll be able to update Checkly Checks from your local machine as long as you're connected to the internet. Step 3: Writing Your Monitoring Scripts -In your development environment, write JavaScript/TypeScript tests for your code updates, similar to unit tests. We typically write Playwright tests in `.spec.ts` files. The `.check.ts` files configure checks, such as API checks and heartbeat monitors. +In your development environment, write JavaScript/TypeScript tests for your code updates, similar to unit tests. We typically write Playwright tests in `.spec.ts` files. The `.check.ts` files configure checks, such as API checks and Heartbeat monitors. Consider a scenario where you want to monitor the title of the Checkly documentation and take a screenshot of the page. To do this, replace the code in the `homepage.spec.ts` with the following: ```javascript homepage.spec.ts @@ -276,7 +276,7 @@ This test uses the `page.goto` method to navigate to the specified URL (`https:/ Then we use the `expect` function to assert that the HTTP status code of the response is less than 400. This is a way to ensure that the page is loaded successfully without any HTTP errors. `page.title()` retrieves the title of the page and compares it with the expected title ('Introduction to Checkly | Checkly') using the `expect` function. This ensures that the page title matches the expected value. Finally, we take a screenshot of the page and save it as 'homepage.jpg'. -Step 4: Running Test Sessions +Step 4: Running test sessions Now that we have our test scripts ready, let's execute them. Run the following command in the terminal of your project repository to test your checks against Checkly's infrastructure: `npx checkly test` You can review the test session with full logging, videos and traces in the Checkly web interface. diff --git a/learn/monitoring/frontend-monitoring.mdx b/learn/monitoring/frontend-monitoring.mdx index 3bea527bf..55b5bd247 100644 --- a/learn/monitoring/frontend-monitoring.mdx +++ b/learn/monitoring/frontend-monitoring.mdx @@ -49,7 +49,7 @@ RUM tracks actual user interactions with your application, offering insights int ![A diagram of the Real User Monitoring model](/images/learn/images/frontend-monitoring-01.png) -*A diagram of the Real User Monitoring model, with in-page Javascript reporting from a user's device to an observability service.* +*A diagram of the Real User Monitoring model, with in-page JavaScript reporting from a user's device to an observability service.* However this approach has several challenges: @@ -57,7 +57,7 @@ However this approach has several challenges: - Rum can impact browser performance for users. - Transmitting data for every user every time is quite expensive, both for you the service provider and for the user’s browser performance and network bandwidth. The suggested solution for this known issue is to sample randomly: when a user starts a session on your site, they’re randomly assigned whether that session will be tracked in detail and transmitted to your observability service. This raises the issue of missing key failures: when a key client reports an error on your site, but no data was captured, you’re stuck trying to replicate an issue with only a user description. - Difficulty finding patterns - user behavior is inherently inconsistent. It’s often very difficult to identify connected failures or trends based on multiple users’ inconsistent behavior. The situation is similar to the sampling problem: we’re left trying to guess what happened based on sketchy information. -- Complex implementation - from loading a javascript package to track user experience in the browser, to endpoints to collect that information, and a system to find patterns in stochastic user behavior, RUM is a complex technical challenge with extensive technical lift. If you’re trying to create a DIY solution for RUM, you’ll find that [CORS: Cross-Origin Request Blocked](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors) errors are the first of many challenges. +- Complex implementation - from loading a JavaScript package to track user experience in the browser, to endpoints to collect that information, and a system to find patterns in stochastic user behavior, RUM is a complex technical challenge with extensive technical lift. If you’re trying to create a DIY solution for RUM, you’ll find that [CORS: Cross-Origin Request Blocked](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors) errors are the first of many challenges. **Synthetic Monitoring** @@ -73,7 +73,7 @@ Synthetic monitoring solves many of the problems listed above with RUM: ![A diagram of the Synthetic Monitoring model](/images/learn/images/frontend-monitoring-02.png) -*A diagram of the Synthetic Monitoring model, with an observability service like checkly sending requests to your production service. SREs and Ops engineers can then view reports and receives alerts the moment a problem is detected.* +*A diagram of the Synthetic Monitoring model, with an observability service like Checkly sending requests to your production service. SREs and Ops engineers can then view reports and receives alerts the moment a problem is detected.* **Application Performance Monitoring (APM)** diff --git a/learn/monitoring/monitoring-as-code.mdx b/learn/monitoring/monitoring-as-code.mdx index 3dda06916..ffa414854 100644 --- a/learn/monitoring/monitoring-as-code.mdx +++ b/learn/monitoring/monitoring-as-code.mdx @@ -124,7 +124,7 @@ MaC also simplifies scaling uptime monitoring across multiple regions. By deploy ### **UI Functionality** -MaC allows you to simulate and test user interactions with your web application. For example, you can create browser checks to validate critical workflows like logging in, completing a checkout, or performing a search. +MaC allows you to simulate and test user interactions with your web application. For example, you can create Browser checks to validate critical workflows like logging in, completing a checkout, or performing a search. These automated tests ensure that every step—loading pages, submitting forms, and rendering elements—works as expected. They catch issues early, safeguarding functionality and user satisfaction. @@ -213,7 +213,7 @@ MaC makes it easy to monitor performance across regions, simulating user experie 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. -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. +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. This proactive approach ensures your critical automation workflows are reliable and resilient. @@ -237,13 +237,13 @@ Checkly’s compatibility with CI/CD pipelines ensures monitoring is embedded in ### Native Playwright Support -With native Playwright support, Checkly enables you to directly use existing Playwright scripts as browser checks. This integration allows you to monitor complex user workflows—such as logins, form submissions, or multi-step transactions—without needing to rewrite tests. +With native Playwright support, Checkly enables you to directly use existing Playwright scripts as Browser checks. This integration allows you to monitor complex user workflows—such as logins, form submissions, or multi-step transactions—without needing to rewrite tests. Your monitoring aligns with your application logic, offering precise, actionable insights into the user experience. ### **Alert Management via Code** -A strong alerting strategy ensures critical issues are addressed promptly while minimizing noise for your team. With Checkly, you can configure alerting integrations like [PagerDuty](/integrations/incident-management/pagerduty) or [OpsGenie](/integrations/incident-management/opsgenie) directly in your codebase. This approach allows you to: +A strong alerting strategy ensures critical issues are addressed promptly while minimizing noise for your team. With Checkly, you can configure alerting integrations like [PagerDuty](/integrations/incident-management/pagerduty) or [Opsgenie](/integrations/incident-management/opsgenie) directly in your codebase. This approach allows you to: - Define alert thresholds, escalation paths, and severity levels as part of your monitoring setup. - Automatically deploy and update alerting configurations alongside your application changes. diff --git a/learn/monitoring/synthetic-monitoring.mdx b/learn/monitoring/synthetic-monitoring.mdx index b82cff499..fbd227b25 100644 --- a/learn/monitoring/synthetic-monitoring.mdx +++ b/learn/monitoring/synthetic-monitoring.mdx @@ -139,7 +139,7 @@ While multiple Observability vendors offer limited site pings as part of a large Checkly offers rich options for scheduling tests on a cadence, including [scheduling checks from multiple regions](https://www.checklyhq.com/blog/parallel-scheduling/), and offers the most complete answer to ‘how is our service performing for all our users? ### Monitoring as Code -At Checkly, we’ve pioneered Monitoring as Code to help shift observability left and unite testing and monitoring in the SDLC. With MaC, you can reuse real, end-to-end Playwright tests as monitors, configure alerting and thresholds with code, and deploy Dashboards and Status Pages to communicate your application’s health with internal and external stakeholders. +At Checkly, we’ve pioneered Monitoring as Code to help shift observability left and unite testing and monitoring in the SDLC. With MaC, you can reuse real, end-to-end Playwright tests as monitors, configure alerting and thresholds with code, and deploy dashboards and status pages to communicate your application’s health with internal and external stakeholders. ## Conclusion Synthetic monitoring forms the foundation of shipping a seamless user experience. It is a safety net for development and DevOps teams, allowing them to innovate confidently. By integrating synthetic monitoring with a MaC approach, we create a bridge between testing and monitoring, fostering a collaborative environment that enhances the overall health of your application. diff --git a/learn/monitoring/transaction-monitoring.mdx b/learn/monitoring/transaction-monitoring.mdx index 2a42a15fb..61d87202a 100644 --- a/learn/monitoring/transaction-monitoring.mdx +++ b/learn/monitoring/transaction-monitoring.mdx @@ -58,7 +58,7 @@ The synthetic transaction engine executes predefined scripts, mimicking user int **Scripting Language** -A flexible scripting language allows testers to define transactions. Languages like JavaScript, Python, or typescript are commonly used, with support for [integrating APIs](https://www.checklyhq.com/blog/what-is-api-monitoring/), [handling cookies](https://www.checklyhq.com/learn/playwright/authentication/), and [managing dynamic content](https://www.checklyhq.com/learn/playwright/iframe-interaction/). +A flexible scripting language allows testers to define transactions. Languages like JavaScript, Python, or TypeScript are commonly used, with support for [integrating APIs](https://www.checklyhq.com/blog/what-is-api-monitoring/), [handling cookies](https://www.checklyhq.com/learn/playwright/authentication/), and [managing dynamic content](https://www.checklyhq.com/learn/playwright/iframe-interaction/). **Test Execution Scheduler** @@ -114,7 +114,7 @@ Synthetic monitoring tracks key performance metrics like response time, latency, While it’s nice to imagine our service or website as self-contained, albeit with multiple internal microservices, the modern web app has more dependencies than ever, including dependencies on third party services all the way to the front end. A missing npm package or a service outage from Intercom can all cause our user experience to shift in unpredictable ways. Detecting any problems with third-party services before your users do is one of the many benefits of synthetic transaction monitoring. Some useful checks to add: - End-to-end testing of key user transaction to make sure, for example, that users can find items, add them to a cart, and check out on your e-commerce service. -- [Visual regression tests](https://www.checklyhq.com/blog/visual-regression-testing-with-playwright/) to make sure third-party javascript add ons haven’t caused problems for your front end experience. +- [Visual regression tests](https://www.checklyhq.com/blog/visual-regression-testing-with-playwright/) to make sure third-party JavaScript add ons haven’t caused problems for your front end experience. - Synthetics checks pointed directly at the third party services. If responses from the your payment provider are often unreliable, set up a monitor (and an alert) to know as soon as it has a chance to affect your users. **Compliance** @@ -138,7 +138,7 @@ When [retries are set up correctly](/communicate/alerts/overview), we should onl **Tool Integration Needs** -Integrating synthetic monitoring tools with existing systems can pose challenges, especially if the ecosystem includes multiple platforms and technologies. Seamless integration is crucial for accurate monitoring and efficient workflows, but it often requires customization and ongoing maintenance. As ‘table stakes’ your synthetic transaction monitoring tool should make its results available on a shared dashboqard, and route alerts intelligently either natively or through integration with tools like [Rootly](/integrations/incident-management/rootly) and [Pagerduty](/integrations/incident-management/pagerduty). Ideally your synthetic monitoring could automatically connect back end tracing that was started by a synthetics request. With [Checkly Traces](/resolve/traces/how-it-works), you can do just that: integrate back end traces with synthetic transaction monitoring, adding insight into the root cause of errors. +Integrating synthetic monitoring tools with existing systems can pose challenges, especially if the ecosystem includes multiple platforms and technologies. Seamless integration is crucial for accurate monitoring and efficient workflows, but it often requires customization and ongoing maintenance. As ‘table stakes’ your synthetic transaction monitoring tool should make its results available on a shared dashboqard, and route alerts intelligently either natively or through integration with tools like [Rootly](/integrations/incident-management/rootly) and [PagerDuty](/integrations/incident-management/pagerduty). Ideally your synthetic monitoring could automatically connect back end tracing that was started by a synthetics request. With [Checkly Traces](/resolve/traces/how-it-works), you can do just that: integrate back end traces with synthetic transaction monitoring, adding insight into the root cause of errors. By understanding these benefits and challenges, organizations can better implement synthetic transaction monitoring as part of a balanced observability strategy. @@ -150,7 +150,7 @@ Synthetic transaction monitoring begins with a clear understanding of what your **Crafting Realistic Test Scenarios** -Design test scenarios that mimic real-world user interactions as closely as possible. This includes simulating different devices, browsers, and network conditions to ensure comprehensive coverage. In playwright, use the [user agent](https://www.checklyhq.com/learn/playwright/challenging-flows/#bot-detection) and [viewport](https://www.checklyhq.com/learn/playwright/taking-screenshots/#generating-and-saving-screenshots) settings to simulate different scenarios. +Design test scenarios that mimic real-world user interactions as closely as possible. This includes simulating different devices, browsers, and network conditions to ensure comprehensive coverage. In Playwright, use the [user agent](https://www.checklyhq.com/learn/playwright/challenging-flows/#bot-detection) and [viewport](https://www.checklyhq.com/learn/playwright/taking-screenshots/#generating-and-saving-screenshots) settings to simulate different scenarios. **Prioritizing Business-Critical Transactions** diff --git a/learn/opentelemetry/context-propagation.mdx b/learn/opentelemetry/context-propagation.mdx index 9036c35eb..8fff0672b 100644 --- a/learn/opentelemetry/context-propagation.mdx +++ b/learn/opentelemetry/context-propagation.mdx @@ -91,7 +91,7 @@ At Checkly, we had a problem. We wanted to let our users connect data on the bac ![A checkly dashboard](/images/learn/images/context-propagation-02.png) -*Users of checkly data can see relevant backend performance data, but don’t send any timespans that aren’t necessary.* +*Users of Checkly data can see relevant backend performance data, but don’t send any timespans that aren’t necessary.* This is just one example of how context propagation is a key superpower for OpenTelemetry. diff --git a/learn/opentelemetry/how-to-instrument.mdx b/learn/opentelemetry/how-to-instrument.mdx index abc57fd6d..475c2891a 100644 --- a/learn/opentelemetry/how-to-instrument.mdx +++ b/learn/opentelemetry/how-to-instrument.mdx @@ -34,7 +34,7 @@ Auto-instrumentation eliminates the need for manual code changes by **injecting 2. **Coverage for Standard Libraries**: Many popular libraries and frameworks come with built-in support for auto-instrumentation. 3. **Consistency**: Ensures consistent telemetry for common operations, reducing the risk of missing critical observability data. - Auto-instrumentation may not offer the same level of granularity or customization as manual instrumentation. Automatic instrumentation can produce unnecessarily ‘noisy’ instrumentation, as just one example the NodeJS auto-instrumentation can produce traces with [hundreds of file system spans](https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1344) that can even overrun available memory. + Auto-instrumentation may not offer the same level of granularity or customization as manual instrumentation. Automatic instrumentation can produce unnecessarily ‘noisy’ instrumentation, as just one example the Node.js auto-instrumentation can produce traces with [hundreds of file system spans](https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1344) that can even overrun available memory. Finally, auto-instrumentation won’t generally produce useful results if something really unusual is happening inside your application. At base, automatic instrumentation assumes that your service is some kind of online application handling requests and sending responses. If that’s not the case, for example if your application is a machine learning system processing through a database and taking over 48 hours to produce results, you may get less useful information. In these cases, you may want to look into manually reporting [OpenTelemetry metrics](/learn/opentelemetry/metrics). diff --git a/learn/opentelemetry/what-is-the-otel-collector.mdx b/learn/opentelemetry/what-is-the-otel-collector.mdx index 53c6a879f..ee2c36939 100644 --- a/learn/opentelemetry/what-is-the-otel-collector.mdx +++ b/learn/opentelemetry/what-is-the-otel-collector.mdx @@ -82,7 +82,7 @@ receivers: - targets: ['0.0.0.0:8888'] ``` -There are a large number of receivers for multiple formats of data coming in to an OpenTelemetry system. Note that, sadly, not all Prometheus data can be translated 1:1 into OTLP. The Prometheus receiver on Github is [currently listed as a work in progress](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/prometheusreceiver/README.md). +There are a large number of receivers for multiple formats of data coming in to an OpenTelemetry system. Note that, sadly, not all Prometheus data can be translated 1:1 into OTLP. The Prometheus receiver on GitHub is [currently listed as a work in progress](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/prometheusreceiver/README.md). ### Processors diff --git a/learn/playwright/assertions.mdx b/learn/playwright/assertions.mdx index 7fdbe3d04..c7db73c6a 100644 --- a/learn/playwright/assertions.mdx +++ b/learn/playwright/assertions.mdx @@ -140,7 +140,7 @@ test("SpaceX-API Dragon Capsules & Next Launch", async ({ request }) => { }) ``` -`degraded` using `@checkly/playwright-helpers` states are currently only available for [Multistep Checks](/detect/synthetic-monitoring/multistep-checks/overview) and [Browser Checks](/detect/synthetic-monitoring/browser-checks/overview). +`degraded` using `@checkly/playwright-helpers` states are currently only available for [Multistep checks](/detect/synthetic-monitoring/multistep-checks/overview) and [Browser checks](/detect/synthetic-monitoring/browser-checks/overview). In this case if the response has a `200` status code but the API response time is more than 200 milliseconds, the status of this check will be degraded and the slow API response time will be included as a failed step. If the response came back as a non-200 status (indicating an error) then the check would be 'failed,' whether or not `markCheckAsDegraded` was called. You can [configure alert channels](https://www.checklyhq.com/docs/communicate/alerts/channels#managing-alert-channels) to notify you when a check has degraded. @@ -254,7 +254,7 @@ Implementing best practices can make your tests more reliable and easier to main - **Test Granularity**: Structure tests to cover distinct, isolated behaviors, making debugging easier. The choice between one 'super test' and 5 or 10 smaller tests should always go with the more granular option. Since [tests can be run in parallel](https://www.checklyhq.com/learn/playwright/testing-in-parallel/), it's likely that better test granularity will also improve test execution time. - **Create Concise Statements**: Keep assertions simple and focused. Asserting that five different page components is an indicator that you're testing multiple ideas with one test, and want to consider either breaking up your test or should at least have multiple steps. -- **Use Descriptive Messages**: Adding clear messages to assertions helps identify failures quickly. It's also good to use [test steps](https://www.checklyhq.com/blog/improve-your-playwright-documentation-with-steps/) to add more description to the exact phase where the test failed. Read further to see how to [add test steps programmatically with Typescript decorators](https://www.checklyhq.com/blog/playwright-test-steps-with-typescript-decorators/). +- **Use Descriptive Messages**: Adding clear messages to assertions helps identify failures quickly. It's also good to use [test steps](https://www.checklyhq.com/blog/improve-your-playwright-documentation-with-steps/) to add more description to the exact phase where the test failed. Read further to see how to [add test steps programmatically with TypeScript decorators](https://www.checklyhq.com/blog/playwright-test-steps-with-typescript-decorators/). - **Parameterize Assertions**: Use variables for assertion parameters to improve test readability and maintainability. - **Leverage Libraries**: Utilize existing libraries for common assertions where possible. Note that if you're running tests on a cadence, a full set of libraries may not be available in your execution environment. - **Be Specific**: Make sure your assertions are as targeted as possible to avoid false positives. Bet on auto-waiting and web-first assertions. Even a change from checking if a text label has the needed text with [`.toContain()`](https://playwright.dev/docs/api/class-genericassertions#generic-assertions-to-contain-1) rather than `toBe()` can improve the reliability of a page monitor. diff --git a/learn/playwright/bypass-totp.mdx b/learn/playwright/bypass-totp.mdx index 069aea54d..b7a4254f0 100644 --- a/learn/playwright/bypass-totp.mdx +++ b/learn/playwright/bypass-totp.mdx @@ -58,7 +58,7 @@ This encoded URL includes: - a secret (`SECRET`) - the issuer (`GitHub`) -**The essential piece to logging in and automating the TOTP flow is the provided secret.** You can access this secret in the Github UI by clicking 'enter this text code' to view the plain text version of the secret. +**The essential piece to logging in and automating the TOTP flow is the provided secret.** You can access this secret in the GitHub UI by clicking 'enter this text code' to view the plain text version of the secret. ![a two-factor secret](/images/samples/images/totp-2.jpeg) @@ -141,7 +141,7 @@ const totp = new OTPAuth.TOTP({ }) ``` -And fill Github’s passcode input field with a newly generated token! +And fill GitHub’s passcode input field with a newly generated token! ```js // generate the passcode when filling the input field diff --git a/learn/playwright/codegen.mdx b/learn/playwright/codegen.mdx index 7bfdbefcc..632d165a7 100644 --- a/learn/playwright/codegen.mdx +++ b/learn/playwright/codegen.mdx @@ -1,7 +1,7 @@ --- title: Record Automation Scripts Using Playwright Codegen description: "Generate Playwright scripts automatically with the codegen command, recording your browser interactions into editable test code with user-first locators." -subTitle: Automatically record playwright tests with codegen +subTitle: Automatically record Playwright tests with codegen date: 2025-02-20 author: Nočnica Mellifera githubUser: serverless-mom @@ -84,7 +84,7 @@ this will generate a `.toContainText(` assertion in the inspector Note that the assertions created by codegen are fairly basic, and while they could be the whole basis for a test suite, it’s a great idea to learn about [Playwright assertions](https://www.checklyhq.com/learn/playwright/assertions/) and write more complex ones yourself. You can write any calculable value into an assertion, so the sky is the limit. -### Step 4: Write tests in Java, Python, .Net or Javascript - Choose Your Target Environment +### Step 4: Write tests in Java, Python, .Net or JavaScript - Choose Your Target Environment After you're done interacting with the website, you can choose the target environment for your script. Playwright allows you to generate scripts in various languages, such as JavaScript, Python, or Playwright's own test framework. diff --git a/learn/playwright/steps-decorators.mdx b/learn/playwright/steps-decorators.mdx index 0c2eb281d..dce16c9af 100644 --- a/learn/playwright/steps-decorators.mdx +++ b/learn/playwright/steps-decorators.mdx @@ -1,5 +1,5 @@ --- -title: Self-documenting tests - add automatic Playwright steps with Typescript Decorators +title: Self-documenting tests - add automatic Playwright steps with TypeScript Decorators description: "Structure complex Playwright tests with a single @step TypeScript decorator, replacing repetitive test.step calls to make reports easier to scan." subTitle: Understand tests better with steps date: 2024-11-15 diff --git a/learn/playwright/testing-apis.mdx b/learn/playwright/testing-apis.mdx index 70ed40913..4c1e5ac8d 100644 --- a/learn/playwright/testing-apis.mdx +++ b/learn/playwright/testing-apis.mdx @@ -105,7 +105,7 @@ test('the GraphQL API works', async ({ request }) => { }) ``` -This version requires that you provide a JSON file with the expected response (that response.json file that's imported at the top). That's not ideal, instead, let's use playwright's snapshot tool so that we can take an initial snapshot of the JSON and compare later runs to that initial version. We'll replace the line: +This version requires that you provide a JSON file with the expected response (that response.json file that's imported at the top). That's not ideal, instead, let's use Playwright's snapshot tool so that we can take an initial snapshot of the JSON and compare later runs to that initial version. We'll replace the line: `expect(body).toEqual(countryData)` with @@ -150,7 +150,7 @@ By running multiple small API requests from within Playwright, you can verify th The dashboard for a Checkly API check, complete with response times, failures and retries, and checks run from multiple locations -As a bonus, Checkly’s API checks are cheaper to run than browser checks. +As a bonus, Checkly’s API checks are cheaper to run than Browser checks. ## Conclusion diff --git a/learn/playwright/testing-pyramid.mdx b/learn/playwright/testing-pyramid.mdx index 4c4281946..cf3ccff15 100644 --- a/learn/playwright/testing-pyramid.mdx +++ b/learn/playwright/testing-pyramid.mdx @@ -186,7 +186,7 @@ At base, the advantage of end-to-end testing is that it answers the real questio ### From E2E Testing to E2E Monitoring -If we agree on the importance of end-to-end testing, it begs the question if testing should stop after deploy time. Thousands of unforseen interactions can break a production service even after the code is tested post-deployment, and our users are certainly using the service all the time. Shouldn’t our testing also continue after the code is out? For end-to-end testing on a cadence, there’s Checkly, which uses the power of playwright to test your sites, services, and APIs around the clock. [Get started today](https://www.checklyhq.com/docs/)! +If we agree on the importance of end-to-end testing, it begs the question if testing should stop after deploy time. Thousands of unforseen interactions can break a production service even after the code is tested post-deployment, and our users are certainly using the service all the time. Shouldn’t our testing also continue after the code is out? For end-to-end testing on a cadence, there’s Checkly, which uses the power of Playwright to test your sites, services, and APIs around the clock. [Get started today](https://www.checklyhq.com/docs/)! ## What problem is the testing pyramid trying to solve? diff --git a/platform/allowlisting-traffic.mdx b/platform/allowlisting-traffic.mdx index 74fda8606..94da9c2fe 100644 --- a/platform/allowlisting-traffic.mdx +++ b/platform/allowlisting-traffic.mdx @@ -68,14 +68,14 @@ You can then [set the Cookie header](/detect/synthetic-monitoring/api-checks/con > You can set the header at group-level using [API check defaults](/platform/groups#headers--query-parameters) to have it applied to every API check in the group. -### Allowlisting browser checks with user agents +### Allowlisting Browser checks with user agents -To allowlist browser checks, allow traffic with user agent containing `Checkly/`, with `` being your shortened Checkly ID or another chosen value. +To allowlist Browser checks, allow traffic with user agent containing `Checkly/`, with `` being your shortened Checkly ID or another chosen value. -You will then be able to set up the matching user agent in your browser checks using Playwright's [`userAgent`](https://playwright.dev/docs/emulation#user-agent) property. +You will then be able to set up the matching user agent in your Browser checks using Playwright's [`userAgent`](https://playwright.dev/docs/emulation#user-agent) property. - + ```ts user-agent.spec.ts import { test } from '@playwright/test' @@ -103,7 +103,7 @@ test('my user agent test', async ({ page }) => { -### Allowlisting Playwright check suites with user agents +### Allowlisting Playwright Check Suites with user agents You can configure the user agent globally in your `playwright.config.ts` file to ensure all your Playwright tests use the Checkly user agent. @@ -167,7 +167,7 @@ export default defineConfig({ ## Filtering Google Analytics -You might want to filter Checkly traffic in Google Analytics to prevent Checkly browser checks from skewing your results. +You might want to filter Checkly traffic in Google Analytics to prevent Checkly Browser checks from skewing your results. If you are using Google Analytics 4 or newer, Checkly traffic is [already being excluded](https://support.google.com/analytics/answer/9888366?hl=en) as it is recognized as coming from a known bot-traffic source. diff --git a/platform/dynamic-secret-scrubbing.mdx b/platform/dynamic-secret-scrubbing.mdx index 5ae32c6bc..345e23c54 100644 --- a/platform/dynamic-secret-scrubbing.mdx +++ b/platform/dynamic-secret-scrubbing.mdx @@ -14,7 +14,7 @@ Set environment variables with the `CHECKLY_SECRET_*` prefix and the runtime wil ## How it works -Currently, dynamic secret scrubbing is only supported for Browser and Multi-Step Checks. +Currently, dynamic secret scrubbing is only supported for Browser and Multistep checks. Assign values to `process.env.CHECKLY_SECRET_*` in your check code: @@ -49,7 +49,7 @@ process.env.CHECKLY_SECRET_PAYMENT_KEY = await vault.get('payment-api-key') ## Limitations -- **Check types**: Only works in browser and multistep checks +- **Check types**: Only works in Browser and Multistep checks - **Value format**: Must be a string (empty strings, `null`, `undefined`, numbers, objects, and arrays are ignored) - **Size limit**: Values cannot exceed 128KB (~128,000 characters) - **Pattern-based detection**: Scrubbing works by detecting code and output structures. Complex or unconventional Playwright usage may fall outside of this detection. Follow the documented patterns for reliable scrubbing. diff --git a/platform/groups.mdx b/platform/groups.mdx index 276b5a854..67fa0d51b 100644 --- a/platform/groups.mdx +++ b/platform/groups.mdx @@ -95,9 +95,9 @@ A common scenario for having two levels of setup scripts is the following: ### Variables You can set both variables and secrets for a Group of checks. -For browser and multistep checks, you can set variables at the check level. See [browser check variables and secrets](/platform/variables) for more details. +For Browser and Multistep checks, you can set variables at the check level. See [Browser check variables and secrets](/platform/variables) for more details. -Secrets are fully supported starting with runtime version 2024.09 and later. For [Private Locations](/platform/private-locations/overview), secrets are available in agent version `3.3.4` and later, and for the [CLI](/cli/overview), in version `4.9.0` and later. +Secrets are fully supported starting with runtime version 2024.09 and later. For [private locations](/platform/private-locations/overview), secrets are available in agent version `3.3.4` and later, and for the [CLI](/cli/overview), in version `4.9.0` and later. #### Variable hierarchy @@ -121,7 +121,7 @@ that variable to be overridden at the group level or check level. ### Testing & Runtimes - **Testing:** Run checks in this group as E2E tests locally or from CI/CD pipelines -- **Runtimes:** Set the JavaScript runtime environment for browser checks and scripts if different from account default +- **Runtimes:** Set the JavaScript runtime environment for Browser checks and scripts if different from account default diff --git a/platform/ip-information.mdx b/platform/ip-information.mdx index 0cadae1ba..77872f715 100644 --- a/platform/ip-information.mdx +++ b/platform/ip-information.mdx @@ -11,9 +11,9 @@ canonical: 'https://www.checklyhq.com/docs/platform/ip-information/' Checkly supports both IPv4 and IPv6. We have a dual stack setup, meaning that we can reach both IPv4 and IPv6 addresses from our check runtime. -Note that for most workloads (API checks, browser checks, etc.) the IPv6 stack is preferred over IPv4. This means that if your endpoint is reachable over IPv6, we will use that. If not, we will fall back to IPv4. +Note that for most workloads (API checks, Browser checks, etc.) the IPv6 stack is preferred over IPv4. This means that if your endpoint is reachable over IPv6, we will use that. If not, we will fall back to IPv4. -You can actually influence this behaviour in a browser check by passing the `--host-resolver-rules` flag to a `chromium` instance. In the code example below, we force the browser to use IPv4, whereas the host `dual.tlund.se` is reachable over both IPv4 and IPv6. +You can actually influence this behaviour in a Browser check by passing the `--host-resolver-rules` flag to a `chromium` instance. In the code example below, we force the browser to use IPv4, whereas the host `dual.tlund.se` is reachable over both IPv4 and IPv6. ```ts resolver.spec.ts import { test, chromium } from '@playwright/test' diff --git a/platform/manage-secrets-at-scale.mdx b/platform/manage-secrets-at-scale.mdx index 72b549147..209f15b26 100644 --- a/platform/manage-secrets-at-scale.mdx +++ b/platform/manage-secrets-at-scale.mdx @@ -13,7 +13,7 @@ This prevents every check execution from receiving a large account-wide secret s - A Checkly Monitoring as Code project using a current version of the Checkly CLI. - A secrets manager that your CI/CD workload can authenticate to. - Permission to deploy the checks and groups that will use the secrets. - - Runtime `2024.09` or later. Private Locations require agent `3.3.4` or later. + - Runtime `2024.09` or later. Private locations require agent `3.3.4` or later. ## Understand the names in these examples @@ -132,7 +132,7 @@ new ApiCheck('payments-admin-health', { }) ``` -Inside Browser, Multi-Step, Playwright, and API setup or teardown scripts, read the deployed value with `process.env.PAYMENTS_ADMIN_TOKEN` instead. +Inside Browser, Multistep, Playwright, and API setup or teardown scripts, read the deployed value with `process.env.PAYMENTS_ADMIN_TOKEN` instead. ## Treat the deployment as authoritative @@ -162,4 +162,4 @@ Use the guide for your secrets manager: - [Azure Key Vault](/integrations/ci-cd/github/secrets/azure-key-vault) - [HashiCorp Vault](/integrations/ci-cd/github/secrets/hashicorp-vault) -For Browser and Multi-Step checks that must retrieve credentials while the check is running, see [Dynamic Secret Scrubbing](/platform/dynamic-secret-scrubbing). Runtime retrieval is a separate pattern with different check-type support. +For Browser and Multistep checks that must retrieve credentials while the check is running, see [Dynamic Secret Scrubbing](/platform/dynamic-secret-scrubbing). Runtime retrieval is a separate pattern with different check-type support. diff --git a/platform/private-locations/agent-configuration.mdx b/platform/private-locations/agent-configuration.mdx index c30c57218..48cf9c690 100644 --- a/platform/private-locations/agent-configuration.mdx +++ b/platform/private-locations/agent-configuration.mdx @@ -4,13 +4,13 @@ description: "Configure the Checkly Agent for a private location with environmen canonical: 'https://www.checklyhq.com/docs/platform/private-locations/agent-configuration/' --- -The Checkly Agent is a container that you need to deploy to run a Private Location in Checkly. The agent needs to be deployed on your infrastructure and executes checks on behalf of the Checkly application. For installation details, [check the getting started guide](/platform/private-locations/overview). +The Checkly Agent is a container that you need to deploy to run a private location in Checkly. The agent needs to be deployed on your infrastructure and executes checks on behalf of the Checkly application. For installation details, [check the getting started guide](/platform/private-locations/overview). The Checkly Agent has several environment variables that can be configured: Variable|Description ---|--- -`API_KEY`|API key for the Private Location in which the agent will serve. The API key is shown in the web app once, when initially creating a Private Location. +`API_KEY`|API key for the private location in which the agent will serve. The API key is shown in the web app once, when initially creating a private location. `HTTPS_PROXY`|HTTPS proxy configuration for the outbound connection to the Checkly API, used for agent management and monitoring. `https://user:password@127.0.0.1:8080` `HTTP_PROXY`|HTTP proxy configuration for the outbound connection to the Checkly API, used for agent management and monitoring. Used if the proxy server does not accept HTTPS connections. `http://user:password@127.0.0.1:8080` `JOB_CONCURRENCY`|(Default: 1, max: 10) Number of concurrent Browser, Multistep and Playwright checks that are run by the agent. Not used by the [uptime image](/platform/private-locations/agent-images#uptime-image). @@ -115,16 +115,16 @@ docker run --rm -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtow ## Rotating API keys -API keys can be rotated as necessary in order to maintain good security practices or in case a key is lost or compromised. A Private Location can have two active API keys. To rotate the API keys: +API keys can be rotated as necessary in order to maintain good security practices or in case a key is lost or compromised. A private location can have two active API keys. To rotate the API keys: -1. Click **Private locations** in the left sidebar (under **Configuration**) to open the [Private Locations page](https://app.checklyhq.com/accounts/private-locations). -2. Click the edit icon on the Private Location you want to update. -3. There will only be a single API key in place on a new Private Location. Click Add new API key to add the second key. +1. Click **Private locations** in the left sidebar (under **Configuration**) to open the [Private locations page](https://app.checklyhq.com/accounts/private-locations). +2. Click the edit icon on the private location you want to update. +3. There will only be a single API key in place on a new private location. Click Add new API key to add the second key. 4. The new API key will appear. Click the copy icon to copy it to your clipboard and save it somewhere secure. ![new key](/images/docs/images/private-locations/new_key.png) -5. Click Save to close the dialog. You can now see the trailing characters of the two defined API keys in the list of Private Locations. +5. Click Save to close the dialog. You can now see the trailing characters of the two defined API keys in the list of private locations. ![two keys](/images/docs/images/private-locations/two_keys.png) @@ -134,7 +134,7 @@ API keys can be rotated as necessary in order to maintain good security practice docker run -e API_KEY="pl_...." -d checkly/agent:latest ``` -7. Make sure the new agents are running properly. You can check the agent count on the Private Locations page, or check your container logs. Remove the old agent containers: +7. Make sure the new agents are running properly. You can check the agent count on the Private locations page, or check your container logs. Remove the old agent containers: ```bash Terminal docker stop @@ -142,9 +142,9 @@ docker stop If you lose track of which agent containers are using the old API key, you can use the `docker inspect ` command and look for the `API_KEY` variable in the output. -8. Now that your new agents are in place, remove the old API key. Click the edit icon in the Private Location again. +8. Now that your new agents are in place, remove the old API key. Click the edit icon in the private location again. 9. Click the delete icon next to the old API key (verified by the shown trailing characters) then click the confirmation. -10. Click Save to close the dialog. You will now only see the new API key listed for the Private Location. +10. Click Save to close the dialog. You will now only see the new API key listed for the private location. ## Trusting Enterprise TLS Certificates diff --git a/platform/private-locations/agent-images.mdx b/platform/private-locations/agent-images.mdx index a515c2e3f..e938bf7b6 100644 --- a/platform/private-locations/agent-images.mdx +++ b/platform/private-locations/agent-images.mdx @@ -49,7 +49,7 @@ It supports URL, DNS, TCP and ICMP monitors. Concurrency is controlled by `AGENT ## Dev Image -If any of the checks you run on Private Locations rely on npm packages with native code, those packages need to be compiled during installation. +If any of the checks you run on private locations rely on npm packages with native code, those packages need to be compiled during installation. The standard agent is optimized for size and doesn’t ship with build tools. In those cases, you’ll need to use the dev image instead. diff --git a/platform/private-locations/autoscaling.mdx b/platform/private-locations/autoscaling.mdx index f39945ec0..3a8e68f10 100644 --- a/platform/private-locations/autoscaling.mdx +++ b/platform/private-locations/autoscaling.mdx @@ -1,6 +1,6 @@ --- title: 'Autoscaling' -description: 'Autoscale Checkly Agents in a Private Location with KEDA based on queued and in-flight check runs.' +description: 'Autoscale Checkly Agents in a private location with KEDA based on queued and in-flight check runs.' canonical: 'https://www.checklyhq.com/docs/platform/private-locations/autoscaling/' --- @@ -16,7 +16,7 @@ Scale Checkly Agent pods automatically in relation to live load. This page cover ## The signal -Checkly exposes the `checkly_private_location_check_runs` gauge through the Prometheus V2 exporter. Filtered by `state` and a `private_location_slug_name`, it provides the count of pending and currently-executing check runs in a single Private Location — the signal you drive replica count from. +Checkly exposes the `checkly_private_location_check_runs` gauge through the Prometheus V2 exporter. Filtered by `state` and a `private_location_slug_name`, it provides the count of pending and currently-executing check runs in a single private location — the signal you drive replica count from. The relevant `state` values are: @@ -24,7 +24,7 @@ The relevant `state` values are: - `inflight` — the check run is currently being executed by an agent. -The gauge is aggregated on a ~1 minute interval, so checks that start and finish within that window may be excluded — their impact on Private Location capacity is negligible. +The gauge is aggregated on a ~1 minute interval, so checks that start and finish within that window may be excluded — their impact on private location capacity is negligible. ## KEDA `ScaledObject` @@ -65,7 +65,7 @@ spec: query: sum(checkly_private_location_check_runs{queue="main", state=~"queued|inflight", private_location_slug_name=""}) ``` -The query is scoped to a single Private Location by `private_location_slug_name`, so create one `ScaledObject` per Private Location. It counts only the `main` queue: uptime monitors and API checks run on the `uptime` queue, which the agent processes with `AGENT_WORKER_COUNT` workers instead of `JOB_CONCURRENCY` slots. +The query is scoped to a single private location by `private_location_slug_name`, so create one `ScaledObject` per private location. It counts only the `main` queue: uptime monitors and API checks run on the `uptime` queue, which the agent processes with `AGENT_WORKER_COUNT` workers instead of `JOB_CONCURRENCY` slots. If you deploy agents with the [Checkly agent Helm chart](https://github.com/checkly/helm-charts/tree/main/charts/agent), template the `ScaledObject` alongside your chart values so the autoscaler ships with the deployment. @@ -90,8 +90,8 @@ For example, with `threshold: "1"`, `minReplicaCount: 2`, `maxReplicaCount: 10`: ## Tuning the bounds - **`threshold`** — set it to match the agent's `JOB_CONCURRENCY`. The default `JOB_CONCURRENCY` is `1`, so leave `threshold: "1"`. A higher value packs more checks per pod and can cause scheduling delays for long-running checks. -- **`minReplicaCount`** — keep at `2` or higher so a single agent failure doesn't take the Private Location offline. See [Scaling and Redundancy](/platform/private-locations/scaling-redundancy). -- **`maxReplicaCount`** — must exceed your expected peak queued + in-flight check runs. If the cap is too low, queued check runs accumulate above it and are dropped once the queue TTL expires: 10 minutes for the main queue on current agents, 6 minutes for uptime monitors and for Private Locations still running an older agent. +- **`minReplicaCount`** — keep at `2` or higher so a single agent failure doesn't take the private location offline. See [Scaling and Redundancy](/platform/private-locations/scaling-redundancy). +- **`maxReplicaCount`** — must exceed your expected peak queued + in-flight check runs. If the cap is too low, queued check runs accumulate above it and are dropped once the queue TTL expires: 10 minutes for the main queue on current agents, 6 minutes for uptime monitors and for private locations still running an older agent. If you set `minReplicaCount: 0` to scale to zero when idle, [`cooldownPeriod`](https://keda.sh/docs/latest/reference/scaledobject-spec/#cooldownperiod) becomes important — it controls how long KEDA waits after the trigger goes inactive before scaling the deployment down to zero. @@ -131,7 +131,7 @@ Maximum runtime by check type: sum(checkly_private_location_check_runs{queue="main", state=~"queued|inflight", private_location_slug_name=""}) ``` -3. Schedule a burst of checks against the Private Location and watch the replica count climb toward `maxReplicaCount`, then settle back to `minReplicaCount` once the burst clears. +3. Schedule a burst of checks against the private location and watch the replica count climb toward `maxReplicaCount`, then settle back to `minReplicaCount` once the burst clears. ## See also diff --git a/platform/private-locations/change-log.mdx b/platform/private-locations/change-log.mdx index 4269e9ce5..066728974 100644 --- a/platform/private-locations/change-log.mdx +++ b/platform/private-locations/change-log.mdx @@ -123,8 +123,8 @@ Learn more about: -- Added support for cancelling running Playwright check suites -- Playwright check suites can run in different NodeJs or Bun versions (22, 24, 26 or Bun 1.3) +- Added support for cancelling running Playwright Check Suites +- Playwright Check Suites can run in different Node.js or Bun versions (22, 24, 26 or Bun 1.3) @@ -193,9 +193,9 @@ Updated packages: - - Added support for running [ICMP](/detect/uptime-monitoring/icmp-monitors/overview) and [DNS monitors](/detect/uptime-monitoring/dns-monitors/overview) on Private Locations + - Added support for running [ICMP](/detect/uptime-monitoring/icmp-monitors/overview) and [DNS monitors](/detect/uptime-monitoring/dns-monitors/overview) on private locations - Introduced the [uptime agent image](/platform/private-locations/agent-images#uptime-image), a lightweight version of the agent for running uptime monitors (URL, DNS, TCP, ICMP) only - - Added [external observability](/platform/private-locations/agent-configuration#external-observability) for Private Location agents to capture runtime errors + - Added [external observability](/platform/private-locations/agent-configuration#external-observability) for private location agents to capture runtime errors - Error-level events can be reported to Checkly to help detect crashes, bugs, and environment-related issues - Only limited technical metadata is collected (error message, stack trace, agent version, platform, Go runtime) - Sensitive data such as API keys, environment variables, check configuration, URLs, headers, and response bodies is never sent @@ -239,7 +239,7 @@ Updated packages: Added Checkly environment variables and configuration to [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview). See the docs on [Playwright Check Suites environment variables](/detect/synthetic-monitoring/playwright-checks/environment-variables): - - Adds support for `CHECKLY` to all checkly triggered runs: scheduled checks and test sessions triggered through either `npx checkly test`, `npx checkly trigger` or `npx checkly pw-test` + - Adds support for `CHECKLY` to all Checkly triggered runs: scheduled checks and test sessions triggered through either `npx checkly test`, `npx checkly trigger` or `npx checkly pw-test` - Includes the environment variable `CI` as true only for test session triggered runs diff --git a/platform/private-locations/kubernetes-deployment.mdx b/platform/private-locations/kubernetes-deployment.mdx index 92e2a13ca..7aca4e349 100644 --- a/platform/private-locations/kubernetes-deployment.mdx +++ b/platform/private-locations/kubernetes-deployment.mdx @@ -8,7 +8,7 @@ We advise running any production-grade Checkly Agent deployments on a container ## Prerequisites -- You've [created a Private Location](/platform/private-locations/overview) and have an API key +- You've [created a private location](/platform/private-locations/overview) and have an API key - You have a running Kubernetes cluster - [Helm](https://helm.sh/) is installed diff --git a/platform/private-locations/overview.mdx b/platform/private-locations/overview.mdx index 2111ac714..19a79a74f 100644 --- a/platform/private-locations/overview.mdx +++ b/platform/private-locations/overview.mdx @@ -1,6 +1,6 @@ --- -title: 'Getting started with Private Locations' -description: 'Monitor internal systems and test from custom locations using Checkly Private Locations. Run checks from within your own infrastructure with the lightweight Checkly Agent.' +title: 'Getting started with private locations' +description: 'Monitor internal systems and test from custom locations using Checkly private locations. Run checks from within your own infrastructure with the lightweight Checkly Agent.' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/platform/private-locations/overview/' --- @@ -10,18 +10,18 @@ canonical: 'https://www.checklyhq.com/docs/platform/private-locations/overview/' -**Owner** or **Admin** permissions are required to create, edit, and delete Private Locations. +**Owner** or **Admin** permissions are required to create, edit, and delete private locations. -A Private Location is a monitoring location that you manage by simply deploying a lightweight Checkly Agent. +A private location is a monitoring location that you manage by simply deploying a lightweight Checkly Agent. -Running a check from a Private Location allows you to: +Running a check from a private location allows you to: - **Monitor internal systems**: Test the performance and reliability of applications and APIs that are only accessible from within your network (e.g., development environments, intranet tools) - **Test from anywhere**: Test the performance and reliability of applications and APIs from different parts of the world. Install your Checkly Agent(s) for location-based performance insights, that we don't cover with our [Global Locations](/concepts/locations) -Configure your checks to use your Private Location and that's it. As long as you have at least one operational Checkly Agent, checks will run in your Private Location. [Adding more agents](/platform/private-locations/scaling-redundancy) will distribute the load and improve resilience automatically. +Configure your checks to use your private location and that's it. As long as you have at least one operational Checkly Agent, checks will run in your private location. [Adding more agents](/platform/private-locations/scaling-redundancy) will distribute the load and improve resilience automatically. ## Requirements @@ -29,12 +29,12 @@ Here are the requirements before you get started: - A container runtime (we test using Docker, but other runtimes should work) - Outbound internet access for the Agent to https://agent.checklyhq.com (proxy configuration is supported) -- Access to your API or browser-based applications and services from the Private Location network -- Owner or Admin permissions (required to create, edit, and delete Private Locations) +- Access to your API or browser-based applications and services from the private location network +- Owner or Admin permissions (required to create, edit, and delete private locations) -## Configuring a Private Location +## Configuring a private location -1. Navigate to the [Private Locations page](https://app.checklyhq.com/private-locations) and click "New private location" +1. Navigate to the [Private locations page](https://app.checklyhq.com/private-locations) and click "New private location" ![private locations screen](/images/docs/images/private-locations/pl_started_1.png) @@ -54,7 +54,7 @@ docker run -e API_KEY="pl_...." -d checkly/agent:latest ``` -5. Refresh the Private Locations page in the Checkly app and you will see a count of the number of running agents. +5. Refresh the Private locations page in the Checkly app and you will see a count of the number of running agents. ![agent running](/images/docs/images/private-locations/pl_started_4.png) @@ -63,9 +63,9 @@ docker run -e API_KEY="pl_...." -d checkly/agent:latest ![select private location](/images/docs/images/private-locations/pl_started_5.png) -## Using Private Locations with the CLI +## Using private locations with the CLI -With the [Checkly CLI](/cli/overview), you can configure any check to run on a Private Location by adding the slug name to the `privateLocations` array. For example, with an [ApiCheck construct](/constructs/api-check): +With the [Checkly CLI](/cli/overview), you can configure any check to run on a private location by adding the slug name to the `privateLocations` array. For example, with an [ApiCheck construct](/constructs/api-check): ```ts {title="api.check.ts"} import { ApiCheck } from 'checkly/constructs' @@ -83,13 +83,13 @@ new ApiCheck('hello-api-1', { }) ``` -## Unavailable Private Locations +## Unavailable private locations If a private location has checks assigned but no Checkly agents connected in the last 10 to 20 minutes, it will be flagged as unavailable. Checkly will email account owners and admins when this happens. While a location is unavailable, no checks will be scheduled to run on it. When a location becomes available, check scheduling and execution will resume automatically. -## Using Playwright Check Suites in Private Locations +## Using Playwright Check Suites in private locations We recommend to update the Checkly agent regularly. @@ -99,7 +99,7 @@ Please use a minimum container size of 2 CPU cores and 4 GB of RAM when running ## Next Steps -Once your first agent is running, explore these topics to start using Private Locations in production: +Once your first agent is running, explore these topics to start using private locations in production: diff --git a/platform/private-locations/proxy-setup.mdx b/platform/private-locations/proxy-setup.mdx index 73b20d563..8f6ac5aa1 100644 --- a/platform/private-locations/proxy-setup.mdx +++ b/platform/private-locations/proxy-setup.mdx @@ -1,6 +1,6 @@ --- title: 'Proxy Setup' -description: 'Configure HTTP proxies for Checkly Private Locations in enterprise environments. Set up proxy routing for both agent management traffic and check execution.' +description: 'Configure HTTP proxies for Checkly private locations in enterprise environments. Set up proxy routing for both agent management traffic and check execution.' canonical: 'https://www.checklyhq.com/docs/platform/private-locations/proxy-setup/' --- @@ -12,24 +12,24 @@ setup. > Note you can also define a proxy for management traffic from your private location to the Checkly API where we ingest > your telemetry and management events. See [the environment variables available to the Checkly Agent container](/platform/private-locations/agent-configuration) -## Setting an HTTP proxy for your Private Location +## Setting an HTTP proxy for your private location We recommend storing the URL of your proxy in a [global environment variable](https://app.checklyhq.com/environment-variables) -so you can easily reuse it in your Private Location configuration and checks. In the example below we store it as `PROXY_URL` +so you can easily reuse it in your private location configuration and checks. In the example below we store it as `PROXY_URL` ![private location proxy url](/images/docs/images/private-locations/proxy_private_locations_1.png) -After this, you can reference this variable using `{{PROXY_URL}}` in the Private Location configuration. +After this, you can reference this variable using `{{PROXY_URL}}` in the private location configuration. ![private location proxy url](/images/docs/images/private-locations/proxy_private_locations_2.png) ## Using an HTTP proxy -With the setup complete, any API check or URL monitor which uses that Private Location will automatically inherit the proxy configuration for outgoing traffic. Other uptime monitors (TCP, DNS, ICMP, traceroute, gRPC and SSL) don't use the proxy. +With the setup complete, any API check or URL monitor which uses that private location will automatically inherit the proxy configuration for outgoing traffic. Other uptime monitors (TCP, DNS, ICMP, traceroute, gRPC and SSL) don't use the proxy. ## Using an HTTP proxy with Browser checks -You can enable your proxy directly in your browser checks via a few extra lines of code, using the `process.env.PROXY_URL` +You can enable your proxy directly in your Browser checks via a few extra lines of code, using the `process.env.PROXY_URL` notation and Playwright Test's `test.use()` method: @@ -65,5 +65,5 @@ test('Go to google.com', async ({ page }) => { -This is all that is required for a browser check to proxy all outbound network connections via your designated HTTP proxy. +This is all that is required for a Browser check to proxy all outbound network connections via your designated HTTP proxy. Check out both the Playwright [networking docs](https://playwright.dev/docs/network#http-proxy) and the Chromium [network settings docs](https://www.chromium.org/developers/design-documents/network-settings/) for some more information. diff --git a/platform/private-locations/scaling-redundancy.mdx b/platform/private-locations/scaling-redundancy.mdx index c6d3de6d8..9ddde2cab 100644 --- a/platform/private-locations/scaling-redundancy.mdx +++ b/platform/private-locations/scaling-redundancy.mdx @@ -1,21 +1,21 @@ --- title: 'Scaling and Redundancy' -description: 'Plan capacity, implement redundancy, and scale Checkly Private Locations for production workloads.' +description: 'Plan capacity, implement redundancy, and scale Checkly private locations for production workloads.' canonical: 'https://www.checklyhq.com/docs/platform/private-locations/scaling-redundancy/' --- -At least two running Checkly Agents per Private Location are recommended for redundancy. Agents are stateless and can be scaled horizontally as needed. You can add additional agents to a location at any time and remove them +At least two running Checkly Agents per private location are recommended for redundancy. Agents are stateless and can be scaled horizontally as needed. You can add additional agents to a location at any time and remove them as necessary. -If one Checkly Agent fails, the other agents in the same Private Location will continue to run the checks assigned to that location. Even checks that are currently in progress on an agent that fails will be rerun by another agent after a timeout period of 300 seconds. +If one Checkly Agent fails, the other agents in the same private location will continue to run the checks assigned to that location. Even checks that are currently in progress on an agent that fails will be rerun by another agent after a timeout period of 300 seconds. There are two cases where checks assigned to a location could fail to run: -1. All the agents in the Private Location have failed. -2. There is insufficient agent capacity in the Private Location. +1. All the agents in the private location have failed. +2. There is insufficient agent capacity in the private location. -**Checks will stay queued for up to 10 minutes** waiting for an available agent. Uptime monitors, and all checks on Private Locations that still run an older agent version, stay queued for 6 minutes. If there are no agents available or the available +**Checks will stay queued for up to 10 minutes** waiting for an available agent. Uptime monitors, and all checks on private locations that still run an older agent version, stay queued for 6 minutes. If there are no agents available or the available agents are so busy that they cannot process all the pending checks in that timeframe, the pending checks older than that will be lost. Agents can be scaled up and scaled out. Scaling up means adding additional CPU and memory allocations to existing agent @@ -37,7 +37,7 @@ Location, the formula (rounded down) is: For example: if your container has 8GB of memory allocated, you should set `JOB_CONCURRENCY` to 5 (8GB / 1.5GB per check). -If your Private Location is only running API checks or uptime monitors, for example on the +If your private location is only running API checks or uptime monitors, for example on the [uptime image](/platform/private-locations/agent-images#uptime-image), size `AGENT_WORKER_COUNT` instead: `AGENT_WORKER_COUNT = Container memory allocation (GB) / 0.15` @@ -46,13 +46,13 @@ For example: if your container has 1GB of memory allocated, you should set `AGEN ## Scale out -To determine the number of agents you need in a Private Location you first need to know the number of checks assigned to +To determine the number of agents you need in a private location you first need to know the number of checks assigned to the location and their frequency. API checks can be scheduled as frequently as every 10 seconds and Browser checks as frequently as every 1 minute. -Based on your configuration, you should be able to estimate how many checks will run per minute in your Private Location. +Based on your configuration, you should be able to estimate how many checks will run per minute in your private location. API checks have a maximum running time of 30 seconds, Browser checks 4 minutes. This means that in the worst case scenario, -a checkly agent can run two API checks per minute per `AGENT_WORKER_COUNT` slot, or 1 Browser check per 4 minutes per +a Checkly agent can run two API checks per minute per `AGENT_WORKER_COUNT` slot, or 1 Browser check per 4 minutes per `JOB_CONCURRENCY` slot. In an average configuration this will be higher and API checks are generally faster than Browser checks. Once you have an idea of how many checks will be running and you know the per-agent concurrency limit based on the diff --git a/platform/reporting/analytics-api.mdx b/platform/reporting/analytics-api.mdx index ecd34ee77..7cdf295a6 100644 --- a/platform/reporting/analytics-api.mdx +++ b/platform/reporting/analytics-api.mdx @@ -28,7 +28,7 @@ There are several endpoints, with one for each check or monitor type. | `/v1/analytics/api-checks/{checkId}` | Returns metrics for API checks | [Learn more](/api-reference/analytics/api-checks) | | `/v1/analytics/browser-checks/{checkId}` | Returns metrics for Browser checks | [Learn more](/api-reference/analytics/browser-checks) | | `/v1/analytics/multistep-checks/{id}` | Returns metrics for Multistep checks | [Learn more](/api-reference/analytics/multistep-checks) | -| `/v1/analytics/playwright-checks/{id}` | Returns metrics for Playwright check suites | [Learn more](/api-reference/analytics/playwright-checks) | +| `/v1/analytics/playwright-checks/{id}` | Returns metrics for Playwright Check Suites | [Learn more](/api-reference/analytics/playwright-checks) | | `/v1/analytics/dns/{id}` | Returns metrics for DNS monitors | [Learn more](/api-reference/analytics/dns-monitors) | | `/v1/analytics/url-monitors/{id}` | Returns metrics for URL monitors | [Learn more](/api-reference/analytics/url-monitors) | | `/v1/analytics/tcp-checks/{id}` | Returns metrics for TCP monitors | [Learn more](/api-reference/analytics/tcp-checks) | @@ -149,7 +149,7 @@ data (`TTFB_p50` and `TTFB_p90`) for the last 7 days grouping by page. > You **must** add the `X-Checkly-Account` and `Authorization` headers to authenticate. -## Creating a Grafana Dashboard +## Creating a Grafana dashboard Following these instructions you'll learn how to use the Analytics API within a [Grafana](https://grafana.com/) dashboard: diff --git a/platform/reporting/overview.mdx b/platform/reporting/overview.mdx index 89f76ff7d..0bcce9afd 100644 --- a/platform/reporting/overview.mdx +++ b/platform/reporting/overview.mdx @@ -9,7 +9,7 @@ The reporting dashboard provides comprehensive insights into your monitoring per ![Reporting Dashboard](/images/docs/images/reporting/dashboard.png) -## Dashboard Overview +## Dashboard overview The reporting dashboard lists your checks, 25 per page, with key performance metrics at a glance. Use this view to: diff --git a/platform/runtimes/overview.mdx b/platform/runtimes/overview.mdx index 2106907de..969cf55e2 100644 --- a/platform/runtimes/overview.mdx +++ b/platform/runtimes/overview.mdx @@ -5,7 +5,7 @@ sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/platform/runtimes/overview/' --- -Checkly lets you use JavaScript code in your [Browser checks](/detect/synthetic-monitoring/browser-checks/overview), [MultiStep Checks](/detect/synthetic-monitoring/multistep-checks/overview), and optional [setup and teardown scripts](/detect/synthetic-monitoring/api-checks/setup-and-teardown) for API checks. +Checkly lets you use JavaScript code in your [Browser checks](/detect/synthetic-monitoring/browser-checks/overview), [Multistep checks](/detect/synthetic-monitoring/multistep-checks/overview), and optional [setup and teardown scripts](/detect/synthetic-monitoring/api-checks/setup-and-teardown) for API checks. This JavaScript code executes in a runtime environment that is managed by Checkly. This environment includes a specific Node.js version, Playwright version, browser binaries, and selected npm packages. We call these managed environments **runtimes**. diff --git a/platform/runtimes/runtime-specification.mdx b/platform/runtimes/runtime-specification.mdx index 5f61580b1..5e2c1c04e 100644 --- a/platform/runtimes/runtime-specification.mdx +++ b/platform/runtimes/runtime-specification.mdx @@ -10,7 +10,7 @@ By default, all Checkly runners (the isolated environments where checks execute) ## Resource limitations -### Browser and Multistep Checks +### Browser and Multistep checks Browser and Multistep checks can use up to `2.7 GiB` of memory and `1678m` [milli-CPU units](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#meaning-of-cpu). This limit applies to all processes spawned by the check, including the browser, the test framework, and the test code itself. The limit is enforced by the runner and is not configurable. @@ -57,7 +57,7 @@ import * as path from 'path' - util - zlib -See the built-in module documentation on the official Node.js site (please see below which runtime includes what NodeJS version): +See the built-in module documentation on the official Node.js site (please see below which runtime includes what Node.js version): - [24.x](https://nodejs.org/dist/latest-v24.x/docs/api/) - [22.x](https://nodejs.org/dist/latest-v22.x/docs/api/) @@ -460,7 +460,7 @@ The main updates are Playwright 1.32.1, faker 7.6.0 and the addition of date-fns Node.js Version: `v16.20.2` -The main updates are Playwright 1.28.0, Node.js v16.20.2 and Typescript support. We are dropping support for Puppeteer. +The main updates are Playwright 1.28.0, Node.js v16.20.2 and TypeScript support. We are dropping support for Puppeteer. - [@faker-js/faker](https://npmjs.com/package/@faker-js/faker/v/5.5.3) 5.5.3 - [@opentelemetry/api](https://npmjs.com/package/@opentelemetry/api/v/1.0.4) 1.0.4 diff --git a/platform/secrets.mdx b/platform/secrets.mdx index 7fcd199e8..7ddc6ab17 100644 --- a/platform/secrets.mdx +++ b/platform/secrets.mdx @@ -135,7 +135,7 @@ The power of Secrets lies in making security invisible to your monitoring logic ## Alternative: Dynamic Secret Detection -For browser checks and multistep checks, you can also use dynamic secret detection. This approach allows you to retrieve secrets at runtime (from external vaults like Azure Key Vault, AWS Secrets Manager, etc.) and have them automatically scrubbed from logs and traces. +For Browser checks and Multistep checks, you can also use dynamic secret detection. This approach allows you to retrieve secrets at runtime (from external vaults like Azure Key Vault, AWS Secrets Manager, etc.) and have them automatically scrubbed from logs and traces. ```javascript // Example: Retrieve from external vault at runtime diff --git a/platform/variables.mdx b/platform/variables.mdx index 5eb97e5ac..9bacc0a96 100644 --- a/platform/variables.mdx +++ b/platform/variables.mdx @@ -1,6 +1,6 @@ --- title: 'Environment variables and secrets' -sidebarTitle: 'Environment Variables' +sidebarTitle: 'Environment variables' description: 'Store and manage common configuration values across your checks' canonical: 'https://www.checklyhq.com/docs/platform/variables/' --- @@ -16,7 +16,7 @@ There are two ways to store configuration information in Checkly: Variables and * **Secrets** allow you to store sensitive data for use in checks. Once saved, secrets are never shown in the UI or in logs and cannot be accessed via the CLI or API. -Secrets are fully supported starting with runtime version 2024.09 and later. For [Private Locations](/platform/private-locations/overview/), secrets are available in agent version `3.3.4` and later, and for the [CLI](/cli/overview/), in version `4.9.0` and later. +Secrets are fully supported starting with runtime version 2024.09 and later. For [private locations](/platform/private-locations/overview/), secrets are available in agent version `3.3.4` and later, and for the [CLI](/cli/overview/), in version `4.9.0` and later. @@ -86,8 +86,8 @@ be overridden at the check level. How variables are accessed depends on where you're accessing them from: -* In [Browser](/detect/synthetic-monitoring/browser-checks/mac-structure#environment-variables), [Multistep](/detect/synthetic-monitoring/multistep-checks/overview#built-in-runtime-variables), and [API Check setup/teardown scripts](/detect/synthetic-monitoring/api-checks/setup-and-teardown#built-in-variables), use the standard Node.js `process.env.VARIABLE_NAME` notation. -* In [API Check requests](/detect/synthetic-monitoring/api-checks/configuration#accessing-environment-variables), use Handlebars/Moustache templating delimiters, i.e. `{{VARIABLE_NAME}}` +* In [Browser](/detect/synthetic-monitoring/browser-checks/mac-structure#environment-variables), [Multistep](/detect/synthetic-monitoring/multistep-checks/overview#built-in-runtime-variables), and [API check setup/teardown scripts](/detect/synthetic-monitoring/api-checks/setup-and-teardown#built-in-variables), use the standard Node.js `process.env.VARIABLE_NAME` notation. +* In [API check requests](/detect/synthetic-monitoring/api-checks/configuration#accessing-environment-variables), use Handlebars/Moustache templating delimiters, i.e. `{{VARIABLE_NAME}}` * In [webhook alert channels](/integrations/alerts/webhooks#template-variables), also use the Handlebar/Moustache format, i.e. `{{VARIABLE_NAME}}` diff --git a/quickstart.mdx b/quickstart.mdx index 302615fed..c3f2c170b 100644 --- a/quickstart.mdx +++ b/quickstart.mdx @@ -102,7 +102,7 @@ The steps below use the Checkly CLI directly so you can build and deploy your mo - Checks are code. The scaffolded `__checks__/homepage.spec.ts` is a [Browser Check](/detect/synthetic-monitoring/browser-checks/quickstart): a standard `@playwright/test` file that Checkly runs as a monitor. Edit it to load a page and assert on what matters: + Checks are code. The scaffolded `__checks__/homepage.spec.ts` is a [Browser check](/detect/synthetic-monitoring/browser-checks/quickstart): a standard `@playwright/test` file that Checkly runs as a monitor. Edit it to load a page and assert on what matters: ```ts homepage.spec.ts @@ -128,7 +128,7 @@ The steps below use the Checkly CLI directly so you can build and deploy your mo ``` - Checkly turns every `*.spec.ts` file in a `__checks__` folder into a Browser Check through the `browserChecks.testMatch` pattern in your `checkly.config.ts`. To monitor an endpoint instead, edit `__checks__/api.check.ts`, which defines an [API Check](/detect/synthetic-monitoring/api-checks/quickstart). For every construct and option, see the [Constructs reference](/constructs/overview). + Checkly turns every `*.spec.ts` file in a `__checks__` folder into a Browser check through the `browserChecks.testMatch` pattern in your `checkly.config.ts`. To monitor an endpoint instead, edit `__checks__/api.check.ts`, which defines an [API check](/detect/synthetic-monitoring/api-checks/quickstart). For every construct and option, see the [Constructs reference](/constructs/overview). @@ -192,7 +192,7 @@ The steps below use the Checkly CLI directly so you can build and deploy your mo - Import the channels you defined and set them as defaults in your `checkly.config.ts` so every check, including your Browser Check, uses them. This example assumes you defined both, so import only the channels you created: + Import the channels you defined and set them as defaults in your `checkly.config.ts` so every check, including your Browser check, uses them. This example assumes you defined both, so import only the channels you created: ```ts checkly.config.ts import { defineConfig } from 'checkly' diff --git a/resolve/ai-root-cause-analysis/overview.mdx b/resolve/ai-root-cause-analysis/overview.mdx index 8a593159f..3246d0f3d 100644 --- a/resolve/ai-root-cause-analysis/overview.mdx +++ b/resolve/ai-root-cause-analysis/overview.mdx @@ -22,7 +22,7 @@ Rocky AI — Checkly's Agent — can automatically analyze, categorize and summa /> -Using any available artifacts like error message, user code, check description, logs, metrics, trace routes, Open Telemetry traces, packet captures, Playwright traces, screenshots and other evidence, it will quickly assess what the impact is of a failure and what the underlying (possible) root cause is. It will also provide a suggested code fix for any check based on (Playwright) code. +Using any available artifacts like error message, user code, check description, logs, metrics, trace routes, OpenTelemetry traces, packet captures, Playwright traces, screenshots and other evidence, it will quickly assess what the impact is of a failure and what the underlying (possible) root cause is. It will also provide a suggested code fix for any check based on (Playwright) code. ## Getting Started with Rocky AI Root Cause Analysis @@ -109,7 +109,7 @@ Root cause: The check is calling a ... For API, Browser, Multistep, and Playwright Checks, the **Check intent** card beside the analysis lets you select **Define intent** or **Edit intent** to open the check's settings. Use it to record the outcomes the check must prove and behavior a repair must preserve. Intent informs root cause analysis independently of whether you enable automatic repair. -For Browser and Multistep Checks, select **Repair with AI** on a completed analysis to attempt a script fix. See [Start a manual repair](../automatic-check-repair#start-a-manual-repair) for prerequisites, repair history, and restoring the original script. +For Browser and Multistep checks, select **Repair with AI** on a completed analysis to attempt a script fix. See [Start a manual repair](../automatic-check-repair#start-a-manual-repair) for prerequisites, repair history, and restoring the original script. ## Key Capabilities diff --git a/resolve/automatic-check-repair.mdx b/resolve/automatic-check-repair.mdx index 12c5fdf6d..a3ed8fbd9 100644 --- a/resolve/automatic-check-repair.mdx +++ b/resolve/automatic-check-repair.mdx @@ -1,17 +1,17 @@ --- title: 'Automatic check repair' sidebarTitle: 'Automatic Repair' -description: 'Configure automatic repair, start a manual attempt, and restore a Browser or Multistep Check script.' +description: 'Configure automatic repair, start a manual attempt, and restore a Browser or Multistep check script.' canonical: 'https://www.checklyhq.com/docs/resolve/automatic-check-repair/' --- -Automatic repair can attempt to fix a Browser or Multistep Check when its script fails because of a check issue. A check intent states the goal, required outcomes, and guardrails that a repair must preserve. A failed check is not automatically repaired just because this setting is on; Rocky AI first needs a repairable failure and a valid intent. +Automatic repair can attempt to fix a Browser or Multistep check when its script fails because of a check issue. A check intent states the goal, required outcomes, and guardrails that a repair must preserve. A failed check is not automatically repaired just because this setting is on; Rocky AI first needs a repairable failure and a valid intent. Repair tests the proposed script before saving it to the running check. For a check managed as code, repair can also create a GitHub pull request to keep its source file in sync. Review, merge, and deploy that change so a later deployment does not overwrite the repair. -- A saved Browser or Multistep Check with at least one public execution location +- A saved Browser or Multistep check with at least one public execution location - [Edit checks and Repair checks with Rocky permissions](/admin/team-management/permissions) (`checks:update` and `check-repairs:create`) - Rocky AI enabled, with access to check repair and AI invocations available for analysis and repair - For Monitoring as Code configuration: Checkly CLI 9.4.0 or later @@ -31,7 +31,7 @@ An AI-generated check already has an intent. Review it before enabling repair. R ## Add intent to an existing check -For an existing Browser or Multistep Check, select **Initialize from saved check** in the **Check intent** section. Checkly reads the saved script and dependencies and suggests an intent. Review the suggestion, edit its goal and outcomes if needed, then save the check. The suggestion is not saved and repair is not enabled just by selecting the button. +For an existing Browser or Multistep check, select **Initialize from saved check** in the **Check intent** section. Checkly reads the saved script and dependencies and suggests an intent. Review the suggestion, edit its goal and outcomes if needed, then save the check. The suggestion is not saved and repair is not enabled just by selecting the button. You can also write the intent yourself. Use this option when the script does not express all of the business requirements a repair must preserve. For example, a script might check that a page loads while the actual goal also requires a signed-in user to see the correct account. @@ -39,10 +39,10 @@ You can also write the intent yourself. Use this option when the script does not You can also define `intent` and enable repair with `aiAutoRepairEnabled` in your [Monitoring as Code](../cli/overview) configuration using the Checkly CLI. Keep the goal, required outcomes, and guardrails alongside your check definition. For a check the CLI manages, a deploy writes what the code declares, like every other property, so a value set only in Checkly is cleared by the next deploy of code that does not set it. Before that happens, the deploy plan lists the value and can [update your code with it](../cli/checkly-deploy#updating-your-code-with-changes-made-in-checkly). See the General Check Options in the [Browser Check](../constructs/browser-check#general-check-options) and [Multistep Check](../constructs/multistep-check#general-check-options) construct references for the `intent` schema and a complete configuration example. -Use your existing Browser or Multistep Check test file in these examples. +Use your existing Browser or Multistep check test file in these examples. - + ```ts import { BrowserCheck } from "checkly/constructs" @@ -71,7 +71,7 @@ new BrowserCheck("dashboard-browser", { ``` - + ```ts import { MultiStepCheck } from "checkly/constructs" diff --git a/resolve/traces/import/missing-spans.mdx b/resolve/traces/import/missing-spans.mdx index a611c5f13..dcfe7338f 100644 --- a/resolve/traces/import/missing-spans.mdx +++ b/resolve/traces/import/missing-spans.mdx @@ -31,7 +31,7 @@ Missing spans can happen due to various reasons. Whether you're sending data to #### Sampling in the OpenTelemetry Collector - * **Step 1**. Make sure that you're filtering out non-checkly spans: + * **Step 1**. Make sure that you're filtering out non-Checkly spans: ```yaml processors: @@ -89,8 +89,8 @@ Ensure the right Authorization keys and endpoints are in use. OTEL_EXPORTER_OTLP_ENDPOINT="https://otel.eu-west-1.checklyhq.com" ``` -### Checkly Private Location setup - When setting up Traces with a [Checkly Private Location](/platform/private-locations/overview): +### Checkly private location setup + When setting up Traces with a [Checkly private location](/platform/private-locations/overview): * **Step 1**. Ensure your [Checkly Agent](https://hub.docker.com/r/checkly/agent) version is at least 3.3.5. * **Step 2**. Review your internal Firewall rules: diff --git a/resolve/traces/import/open-telemetry.mdx b/resolve/traces/import/open-telemetry.mdx index f4bf600b5..c6e4aceb8 100644 --- a/resolve/traces/import/open-telemetry.mdx +++ b/resolve/traces/import/open-telemetry.mdx @@ -13,7 +13,7 @@ a little setting up, but it's worth it. * An OpenTelemetry collector running and configured. -If you need to set up OpenTelemetry for the first time, please use [the Open Telemetry Collector getting started documentation](https://opentelemetry.io/docs/collector/installation/). +If you need to set up OpenTelemetry for the first time, please use [the OpenTelemetry Collector getting started documentation](https://opentelemetry.io/docs/collector/installation/). ## Step 1: Update your config @@ -54,7 +54,7 @@ service: ``` ## Step 2: Restart your collector -Grab your **OTel API key** in the *Send traces* section of the [Open Telemetry Integration page in the Checkly app](https://app.checklyhq.com/settings/account/open-telemetry). +Grab your **OTel API key** in the *Send traces* section of the [OpenTelemetry Integration page in the Checkly app](https://app.checklyhq.com/settings/account/open-telemetry). Now, export your API key in your shell by setting the `CHECKLY_OTEL_API_KEY` environment variable. ```bash Terminal diff --git a/resolve/traces/overview.mdx b/resolve/traces/overview.mdx index adba6b4a2..1b6e8d0f6 100644 --- a/resolve/traces/overview.mdx +++ b/resolve/traces/overview.mdx @@ -67,9 +67,9 @@ See the built-in variables for [Browser checks](/detect/synthetic-monitoring/bro ## Works hand-in-hand with Rocky AI -Checkly Traces automatically integrates with Rocky AI, helping you automatically analyze root causes of check failures. [Rocky AI Root Cause Analysis](/resolve/ai-root-cause-analysis/overview) can search, fetch and interpret Open Telemetry (OTeL) traces ingested by Checkly Traces and use it as a piece of "evidence" in determining why and where a check failed.\ +Checkly Traces automatically integrates with Rocky AI, helping you automatically analyze root causes of check failures. [Rocky AI Root Cause Analysis](/resolve/ai-root-cause-analysis/overview) can search, fetch and interpret OpenTelemetry (OTeL) traces ingested by Checkly Traces and use it as a piece of "evidence" in determining why and where a check failed.\ \ -A simple example. Your API or Playwright check fails with a 500 error. Luckily your backend is instrumented with Open Telemetry and sends a trace indicating an issue with a downstream database, 3rd party service, proxy etc. Now, Rocky AI automatically pulls these OTeL traces into its context window and correlates it with your failing check. \ +A simple example. Your API or Playwright check fails with a 500 error. Luckily your backend is instrumented with OpenTelemetry and sends a trace indicating an issue with a downstream database, 3rd party service, proxy etc. Now, Rocky AI automatically pulls these OTeL traces into its context window and correlates it with your failing check. \ \ Here's an actual example from Checkly's own backend. diff --git a/snippets/check-intent.mdx b/snippets/check-intent.mdx index 4dba37cd2..0085e74e1 100644 --- a/snippets/check-intent.mdx +++ b/snippets/check-intent.mdx @@ -2,7 +2,7 @@ Describe what your check is intended to verify and the behavior that should be preserved. Checkly uses intent for root cause analysis across all check types. It is separate from `description` and does not replace executable assertions. Left unset, or set to `null`, the check has no intent. -Intent is used for [automatic repair](/resolve/automatic-check-repair) only for Browser and Multistep Checks. +Intent is used for [automatic repair](/resolve/automatic-check-repair) only for Browser and Multistep checks. The object accepts the following fields: @@ -19,7 +19,7 @@ Each constraint has a required `type` and `statement`: Each `statement` must contain 1–1,000 characters after trimming. You can specify at most 20 constraints of each type. The CLI trims leading and trailing whitespace from the goal and statements and rejects unknown fields. -For example, configure intent on a Browser Check: +For example, configure intent on a Browser check: ```ts import { BrowserCheck } from "checkly/constructs" diff --git a/snippets/general-monitor-options-table.mdx b/snippets/general-monitor-options-table.mdx index 839fd1a35..e52cddd4f 100644 --- a/snippets/general-monitor-options-table.mdx +++ b/snippets/general-monitor-options-table.mdx @@ -8,7 +8,7 @@ | `frequency` | `Frequency` | ❌ | `EVERY_10M` | How often to run your monitor | | `group` | `CheckGroupV1` `CheckGroupV2` | ❌ | - | The CheckGroup this monitor belongs to | | `locations` | `string[]` | ❌ | `[]` | Array of public location codes | -| `privateLocations` | `string[]` | ❌ | `[]` | Array of Private Location slugs | +| `privateLocations` | `string[]` | ❌ | `[]` | Array of private location slugs | | `muted` | `boolean` | ❌ | `false` | Whether alert notifications are muted | | `tags` | `string[]` | ❌ | `[]` | Array of tags to organize monitors | | `testOnly` | `boolean` | ❌ | `false` | Only run with test, not during deploy | diff --git a/what-is-checkly.mdx b/what-is-checkly.mdx index b17e81c74..0d05a8e0a 100644 --- a/what-is-checkly.mdx +++ b/what-is-checkly.mdx @@ -27,7 +27,7 @@ Checkly is an Application Reliability platform that enables teams to **test, mon Checkly has three core capabilities: - **Detect**: Testing, Uptime Monitoring, and Synthetic Monitoring with Playwright. -- **Communicate**: Customizable Alerting, Dashboards, & Status Pages for clear communication. +- **Communicate**: Customizable alerting, dashboards, & status pages for clear communication. - **Resolve**: Distributed full-stack tracing and AI-powered incident analysis and context. ## Why Checkly? From 7bc19001f4a06a36b2f15e999cf2475001414c9c Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Fri, 30 Oct 2026 14:35:26 -0400 Subject: [PATCH 2/3] docs: keep feature-name capitals in six 'use X' sentences Co-Authored-By: Claude Opus 5.5 --- constructs/maintenance-window.mdx | 2 +- constructs/private-location.mdx | 2 +- constructs/status-page-service.mdx | 2 +- detect/testing/creating-your-first-test.mdx | 2 +- integrations/iac/pulumi/best-practices.mdx | 2 +- platform/private-locations/overview.mdx | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/constructs/maintenance-window.mdx b/constructs/maintenance-window.mdx index b2705ab71..8cdc2f8af 100644 --- a/constructs/maintenance-window.mdx +++ b/constructs/maintenance-window.mdx @@ -9,7 +9,7 @@ canonical: 'https://www.checklyhq.com/docs/constructs/maintenance-window/' Learn more about maintenance windows in [the maintenance windows documentation](/communicate/maintenance-windows/overview). -Use maintenance windows to schedule planned maintenance periods that prevent your checks from running and triggering alerts during expected downtime. +Use Maintenance Windows to schedule planned maintenance periods that prevent your checks from running and triggering alerts during expected downtime. diff --git a/constructs/private-location.mdx b/constructs/private-location.mdx index 36d025c0d..841d9a094 100644 --- a/constructs/private-location.mdx +++ b/constructs/private-location.mdx @@ -9,7 +9,7 @@ canonical: 'https://www.checklyhq.com/docs/constructs/private-location/' Learn more about private locations in [the private locations overview](/platform/private-locations/overview). -Use private locations to run checks from your own infrastructure, VPCs, or isolated networks. With a private location, you can monitor internal services and applications not accessible from the public internet. +Use Private Locations to run checks from your own infrastructure, VPCs, or isolated networks. With a private location, you can monitor internal services and applications not accessible from the public internet. Before creating private locations, ensure you have: diff --git a/constructs/status-page-service.mdx b/constructs/status-page-service.mdx index 6674ad9a2..5d5cac415 100644 --- a/constructs/status-page-service.mdx +++ b/constructs/status-page-service.mdx @@ -12,7 +12,7 @@ canonical: 'https://www.checklyhq.com/docs/constructs/status-page-service/' Learn more about status pages in [the status pages overview](/communicate/status-pages/overview). -Use status page services to allow monitors and checks to trigger incidents and to be displayed on status pages. Services represent individual components or systems that you want to show uptime information for. +Use Status Page Services to allow monitors and checks to trigger incidents and to be displayed on status pages. Services represent individual components or systems that you want to show uptime information for. diff --git a/detect/testing/creating-your-first-test.mdx b/detect/testing/creating-your-first-test.mdx index 113db93cc..3c4a7faf4 100644 --- a/detect/testing/creating-your-first-test.mdx +++ b/detect/testing/creating-your-first-test.mdx @@ -175,7 +175,7 @@ new BrowserCheck('advanced-check', { 2. **Use Page Object Model**: Organize your tests with reusable page objects 3. **Test Critical User Journeys**: Focus on the most important user flows 4. **Set Appropriate Frequencies**: Don't over-monitor; balance coverage with costs -5. **Use environment variables**: Keep sensitive data and URLs configurable +5. **Use Environment Variables**: Keep sensitive data and URLs configurable 6. **Add Meaningful Assertions**: Test both functionality and performance 7. **Take Screenshots**: Helpful for debugging when tests fail 8. **Monitor APIs and UI**: Combine browser and API checks for comprehensive coverage diff --git a/integrations/iac/pulumi/best-practices.mdx b/integrations/iac/pulumi/best-practices.mdx index 8fd7631d8..f654ea2e5 100644 --- a/integrations/iac/pulumi/best-practices.mdx +++ b/integrations/iac/pulumi/best-practices.mdx @@ -90,7 +90,7 @@ apiChecks.forEach(check => { Never commit API keys, passwords, or other sensitive information directly in your Pulumi code or version control. -**Use environment variables:** +**Use Environment Variables:** ```javascript // Good: Use environment variables new checkly.Check('authenticated-api', { diff --git a/platform/private-locations/overview.mdx b/platform/private-locations/overview.mdx index 19a79a74f..c46637f4a 100644 --- a/platform/private-locations/overview.mdx +++ b/platform/private-locations/overview.mdx @@ -99,7 +99,7 @@ Please use a minimum container size of 2 CPU cores and 4 GB of RAM when running ## Next Steps -Once your first agent is running, explore these topics to start using private locations in production: +Once your first agent is running, explore these topics to start using Private Locations in production: From c07b75b8c8e5f7b84e1e89ee410966d3b17728ee Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Fri, 30 Oct 2026 14:42:22 -0400 Subject: [PATCH 3/3] docs: sentence case for headings and titles Convert the remaining title-case Markdown headings, frontmatter title and sidebarTitle values, and Card/Step/Tab/Accordion title props to sentence case. Letter case only: no rewording, slugs, hrefs or anchors changed. Kept as is: product and feature names, check and monitor types (Browser check, URL monitor), third-party names, acronyms, quoted text, inline code, YoutubeEmbed titles and generated API reference pages. Co-Authored-By: Claude Opus 5.5 --- admin/changing-your-email-password.mdx | 2 +- admin/creating-api-key.mdx | 2 +- admin/deleting-your-account.mdx | 2 +- admin/team-management/adding-team-members.mdx | 2 +- admin/team-management/custom-roles.mdx | 4 +- .../team-management/managing-team-members.mdx | 2 +- .../multi-factor-authentication.mdx | 4 +- admin/team-management/overview.mdx | 26 +++--- admin/team-management/single-sign-on.mdx | 4 +- ai/markdown-access.mdx | 4 +- ai/mcp-server.mdx | 2 +- ai/mcp-server/setup.mdx | 2 +- ai/mcp-server/troubleshooting.mdx | 2 +- ai/overview.mdx | 6 +- ai/plugin.mdx | 2 +- ai/rocky-ai.mdx | 12 +-- ai/skills.mdx | 2 +- api-reference/overview.mdx | 2 +- changelog/changelog.mdx | 8 +- cli/attaching-git-metadata.mdx | 2 +- cli/checkly-account.mdx | 8 +- cli/checkly-alert-channels.mdx | 14 ++-- cli/checkly-api.mdx | 4 +- cli/checkly-assets.mdx | 10 +-- cli/checkly-checks.mdx | 20 ++--- cli/checkly-deploy.mdx | 6 +- cli/checkly-destroy.mdx | 8 +- cli/checkly-env.mdx | 12 +-- cli/checkly-import.mdx | 18 ++-- cli/checkly-incidents.mdx | 18 ++-- cli/checkly-init.mdx | 14 ++-- cli/checkly-login.mdx | 10 +-- cli/checkly-logout.mdx | 12 +-- cli/checkly-members.mdx | 8 +- cli/checkly-pw-test.mdx | 16 ++-- cli/checkly-rca.mdx | 12 +-- cli/checkly-runtimes.mdx | 14 ++-- cli/checkly-skills.mdx | 6 +- cli/checkly-status-pages.mdx | 10 +-- cli/checkly-switch.mdx | 10 +-- cli/checkly-sync-playwright.mdx | 10 +-- cli/checkly-test-sessions.mdx | 10 +-- cli/checkly-test.mdx | 6 +- cli/checkly-trigger.mdx | 10 +-- cli/checkly-whoami.mdx | 4 +- cli/dependencies.mdx | 4 +- cli/importing.mdx | 4 +- cli/installation.mdx | 2 +- cli/monitoring-pull-requests.mdx | 2 +- cli/overview.mdx | 4 +- communicate/alerts/channels.mdx | 14 ++-- communicate/alerts/configuration.mdx | 42 +++++----- communicate/alerts/notification-log.mdx | 4 +- communicate/alerts/overview.mdx | 8 +- communicate/alerts/retries.mdx | 2 +- communicate/alerts/ssl-expiration.mdx | 4 +- communicate/dashboards/configuration.mdx | 10 +-- communicate/dashboards/custom-css.mdx | 2 +- communicate/dashboards/incidents.mdx | 2 +- communicate/overview.mdx | 8 +- communicate/status-pages/custom-domain.mdx | 2 +- communicate/status-pages/incidents.mdx | 2 +- .../status-pages/password-protection.mdx | 4 +- .../status-pages/subscriber-notifications.mdx | 4 +- .../moving-from-puppeteer-to-playwright.mdx | 8 +- .../frameworks/playwright-vs-cypress.mdx | 36 ++++---- .../frameworks/playwright-vs-selenium.mdx | 2 +- comparisons/monitoring-tools/overview.mdx | 8 +- comparisons/observability-tools/overview.mdx | 8 +- comparisons/overview.mdx | 2 +- comparisons/status-pages/overview.mdx | 2 +- comparisons/testing-tools/overview.mdx | 8 +- concepts/checks.mdx | 8 +- concepts/locations.mdx | 6 +- concepts/metrics.mdx | 44 +++++----- concepts/monitoring-as-code.mdx | 2 +- concepts/overview.mdx | 10 +-- concepts/results.mdx | 2 +- concepts/scheduling.mdx | 16 ++-- constructs/agentic-check.mdx | 4 +- constructs/alert-escalation-policy.mdx | 6 +- constructs/api-check.mdx | 8 +- constructs/browser-check.mdx | 4 +- constructs/check-group-v2.mdx | 14 ++-- constructs/check-group.mdx | 10 +-- constructs/dashboard.mdx | 6 +- constructs/dns-monitor.mdx | 10 +-- constructs/dynamic-monitor-creation.mdx | 2 +- constructs/email-alert-channel.mdx | 2 +- constructs/grpc-monitor.mdx | 10 +-- constructs/heartbeat-monitor.mdx | 32 ++++---- constructs/icmp-monitor.mdx | 10 +-- constructs/incident-trigger.mdx | 8 +- constructs/incidentio-alert-channel.mdx | 2 +- constructs/including-checks.mdx | 4 +- constructs/maintenance-window.mdx | 14 ++-- constructs/msteams-alert-channel.mdx | 2 +- constructs/multistep-check.mdx | 8 +- constructs/opsgenie-alert-channel.mdx | 2 +- constructs/overview.mdx | 12 +-- constructs/pagerduty-alert-channel.mdx | 2 +- constructs/phone-call-alert-channel.mdx | 4 +- constructs/playwright-check.mdx | 6 +- constructs/private-location.mdx | 26 +++--- constructs/project.mdx | 18 ++-- constructs/retry-strategy.mdx | 38 ++++----- constructs/slack-alert-channel.mdx | 4 +- constructs/slack-app-alert-channel.mdx | 2 +- constructs/sms-alert-channel.mdx | 2 +- constructs/ssl-monitor.mdx | 22 ++--- constructs/status-page-service.mdx | 8 +- constructs/status-page-v3-automation-rule.mdx | 4 +- constructs/status-page-v3-component.mdx | 4 +- constructs/status-page-v3.mdx | 4 +- constructs/status-page.mdx | 4 +- constructs/tcp-monitor.mdx | 34 ++++---- constructs/telegram-alert-channel.mdx | 2 +- constructs/traceroute-monitor.mdx | 10 +-- constructs/url-monitor.mdx | 38 ++++----- constructs/webhook-alert-channel.mdx | 2 +- detect/assertions.mdx | 2 +- detect/overview.mdx | 26 +++--- .../agentic-checks/configuration.mdx | 2 +- .../agentic-checks/overview.mdx | 4 +- .../api-checks/api-structure.mdx | 22 ++--- .../api-checks/client-certificates.mdx | 2 +- .../api-checks/configuration.mdx | 4 +- .../api-checks/openapi-spec.mdx | 8 +- .../api-checks/response-limits.mdx | 2 +- .../api-checks/setup-and-teardown.mdx | 4 +- .../api-checks/troubleshooting.mdx | 6 +- .../browser-checks/degraded.mdx | 10 +-- .../browser-checks/examples.mdx | 44 +++++----- .../browser-checks/mac-structure.mdx | 4 +- .../browser-checks/overview.mdx | 18 ++-- .../browser-checks/performance-metrics.mdx | 16 ++-- .../browser-checks/playwright-support.mdx | 28 +++---- .../browser-checks/quickstart.mdx | 14 ++-- .../browser-checks/troubleshooting.mdx | 16 ++-- .../browser-checks/visual-regressions.mdx | 12 +-- .../multistep-checks/degraded-states.mdx | 10 +-- .../multistep-checks/examples.mdx | 4 +- .../multistep-checks/file-system.mdx | 4 +- .../multistep-checks/multistep-structure.mdx | 26 +++--- .../multistep-checks/overview.mdx | 14 ++-- .../multistep-checks/troubleshooting.mdx | 8 +- .../multistep-checks/websockets.mdx | 8 +- detect/synthetic-monitoring/overview.mdx | 8 +- .../playwright-checks/add-to-group.mdx | 4 +- .../playwright-checks/configuration.mdx | 2 +- .../playwright-checks/dependencies.mdx | 10 +-- .../playwright-checks/internal-registries.mdx | 4 +- .../playwright-checks/overview.mdx | 14 ++-- .../playwright-checks/quickstart.mdx | 18 ++-- .../playwright-checks/test-organization.mdx | 8 +- .../playwright-checks/timeouts.mdx | 2 +- .../playwright-monitoring-comparison.mdx | 4 +- detect/testing/creating-your-first-test.mdx | 26 +++--- detect/testing/overview.mdx | 8 +- .../testing/playwright-reporter-changelog.mdx | 4 +- detect/testing/playwright-reporter.mdx | 34 ++++---- .../dns-monitors/configuration.mdx | 28 +++---- .../dns-monitors/overview.mdx | 2 +- .../grpc-monitors/configuration.mdx | 14 ++-- .../heartbeat-monitors/configuration.mdx | 4 +- .../heartbeat-monitors/examples.mdx | 52 ++++++------ .../heartbeat-monitors/overview.mdx | 6 +- .../heartbeat-monitors/quickstart.mdx | 34 ++++---- .../icmp-monitors/configuration.mdx | 10 +-- .../icmp-monitors/overview.mdx | 2 +- detect/uptime-monitoring/overview.mdx | 6 +- .../ssl-monitors/configuration.mdx | 14 ++-- .../ssl-monitors/overview.mdx | 4 +- .../tcp-monitors/configuration.mdx | 8 +- .../tcp-monitors/quickstart.mdx | 8 +- .../traceroute-monitors/configuration.mdx | 10 +-- .../traceroute-monitors/overview.mdx | 2 +- .../url-monitors/configuration.mdx | 14 ++-- .../url-monitors/overview.mdx | 12 +-- .../url-monitors/quickstart.mdx | 10 +-- guides/agent-driven-repair.mdx | 2 +- guides/agentic-workflows.mdx | 4 +- guides/alerting.mdx | 2 +- guides/api-monitoring.mdx | 2 +- guides/claude-code-monitoring.mdx | 16 ++-- guides/global-monitoring.mdx | 2 +- guides/keyword-monitoring.mdx | 2 +- guides/monitoring-an-openapi-spec.mdx | 6 +- ...toring-ecommerce-apps-using-playwright.mdx | 2 +- ...itoring-ecommerce-apps-using-terraform.mdx | 2 +- guides/monitoring-the-stripe-api.mdx | 6 +- guides/playwright-testing-to-monitoring.mdx | 2 +- guides/reading-traces.mdx | 2 +- guides/sdlc-monitoring.mdx | 2 +- guides/setup-scripts-for-apis.mdx | 6 +- guides/structuring-a-checkly-project.mdx | 2 +- guides/uptime-monitoring.mdx | 2 +- index.mdx | 4 +- integrations/alerts/discord.mdx | 10 +-- integrations/alerts/email.mdx | 4 +- integrations/alerts/gitlab_alerts.mdx | 4 +- integrations/alerts/msteams.mdx | 2 +- integrations/alerts/phone-calls.mdx | 4 +- integrations/alerts/slack.mdx | 6 +- integrations/alerts/sms.mdx | 2 +- integrations/alerts/telegram.mdx | 18 ++-- integrations/alerts/webhooks.mdx | 12 +-- integrations/ci-cd/gitlab/overview.mdx | 2 +- integrations/ci-cd/jenkins/overview.mdx | 4 +- integrations/ci-cd/overview.mdx | 6 +- .../ci-cd/vercel/deployment-protection.mdx | 12 +-- integrations/ci-cd/vercel/managing-plan.mdx | 4 +- integrations/ci-cd/vercel/overview.mdx | 6 +- integrations/iac/pulumi/best-practices.mdx | 82 +++++++++---------- integrations/iac/pulumi/ci-cd.mdx | 44 +++++----- integrations/iac/pulumi/examples.mdx | 24 +++--- integrations/iac/pulumi/overview.mdx | 6 +- integrations/iac/pulumi/setup.mdx | 60 +++++++------- integrations/iac/terraform/checks-groups.mdx | 2 +- integrations/iac/terraform/ci-cd.mdx | 2 +- .../iac/terraform/command-line-triggers.mdx | 2 +- integrations/iac/terraform/dashboards.mdx | 2 +- .../iac/terraform/parameterized-resources.mdx | 2 +- .../iac/terraform/testing-scripts-locally.mdx | 2 +- .../incident-management/firehydrant.mdx | 2 +- integrations/incident-management/ilert.mdx | 2 +- .../incident-management/incidentio.mdx | 2 +- integrations/incident-management/opsgenie.mdx | 2 +- .../incident-management/pagerduty.mdx | 4 +- integrations/incident-management/rootly.mdx | 2 +- integrations/incident-management/spike.mdx | 2 +- .../incident-management/splunk-on-call.mdx | 2 +- integrations/observability/coralogix.mdx | 4 +- integrations/observability/prometheus-v2.mdx | 14 ++-- integrations/observability/prometheus.mdx | 2 +- learn/incidents/anatomy-of-a-status-page.mdx | 12 +-- .../automation-incident-response.mdx | 16 ++-- learn/incidents/detection-best-practices.mdx | 16 ++-- learn/incidents/dora-metrics.mdx | 12 +-- .../incident-assessment-severity.mdx | 28 +++---- learn/incidents/incident-communication.mdx | 6 +- .../incident-management-challenges.mdx | 16 ++-- .../incidents/modern-root-cause-analysis.mdx | 8 +- learn/incidents/mttr-challenges.mdx | 18 ++-- learn/incidents/on-call-schedule.mdx | 26 +++--- learn/incidents/overview.mdx | 14 ++-- learn/incidents/playbooks.mdx | 8 +- learn/incidents/postmortems.mdx | 26 +++--- learn/incidents/reduce-mttd.mdx | 8 +- learn/incidents/root-cause-with-traces.mdx | 26 +++--- learn/incidents/slo-sla-sli.mdx | 56 ++++++------- learn/incidents/what-is-incident-response.mdx | 10 +-- learn/kubernetes/centralized-logging.mdx | 14 ++-- learn/kubernetes/events.mdx | 12 +-- learn/kubernetes/klog.mdx | 24 +++--- learn/kubernetes/logging-best-practices.mdx | 24 +++--- learn/kubernetes/monitoring-challenges.mdx | 18 ++-- learn/kubernetes/node-problem-detector.mdx | 16 ++-- learn/kubernetes/operators-metrics.mdx | 10 +-- learn/kubernetes/overview.mdx | 6 +- learn/kubernetes/structured-logging.mdx | 32 ++++---- learn/monitoring/api-monitoring.mdx | 32 ++++---- learn/monitoring/end-to-end-monitoring.mdx | 16 ++-- learn/monitoring/frontend-monitoring.mdx | 28 +++---- learn/monitoring/https-for-app-developers.mdx | 10 +-- learn/monitoring/intro-to-sdlc.mdx | 4 +- learn/monitoring/metrics-every-team-needs.mdx | 14 ++-- learn/monitoring/monitoring-as-code.mdx | 50 +++++------ learn/monitoring/overview.mdx | 18 ++-- learn/monitoring/real-user-monitoring.mdx | 22 ++--- learn/monitoring/synthetic-monitoring.mdx | 44 +++++----- learn/monitoring/tcp-and-ssl.mdx | 16 ++-- learn/monitoring/transaction-monitoring.mdx | 24 +++--- .../monitoring/web-application-monitoring.mdx | 22 ++--- learn/monitoring/what-is-tcp.mdx | 54 ++++++------ learn/opentelemetry/context-propagation.mdx | 24 +++--- .../getting-started-with-observability.mdx | 14 ++-- learn/opentelemetry/how-to-instrument.mdx | 6 +- learn/opentelemetry/logs.mdx | 40 ++++----- learn/opentelemetry/metrics.mdx | 16 ++-- .../otel-agent-management-protocol.mdx | 10 +-- learn/opentelemetry/otel-filtering.mdx | 14 ++-- learn/opentelemetry/overview.mdx | 8 +- learn/opentelemetry/trace-api.mdx | 8 +- learn/opentelemetry/traces.mdx | 14 ++-- .../what-is-the-otel-collector.mdx | 16 ++-- learn/overview.mdx | 12 +-- learn/playwright/assertions.mdx | 34 ++++---- learn/playwright/authentication.mdx | 8 +- learn/playwright/bypass-totp.mdx | 4 +- learn/playwright/challenging-flows.mdx | 2 +- learn/playwright/checkout-testing-guide.mdx | 2 +- learn/playwright/clicking-typing-hovering.mdx | 2 +- learn/playwright/codegen.mdx | 20 ++--- learn/playwright/debugging-errors.mdx | 2 +- learn/playwright/debugging-with-ai-agents.mdx | 2 +- learn/playwright/debugging.mdx | 2 +- learn/playwright/error-click-not-executed.mdx | 2 +- learn/playwright/error-element-not-found.mdx | 2 +- .../playwright/error-element-not-visible.mdx | 2 +- learn/playwright/error-target-closed.mdx | 2 +- learn/playwright/error-wait-not-respected.mdx | 2 +- learn/playwright/file-download.mdx | 2 +- learn/playwright/generating-pdfs.mdx | 2 +- learn/playwright/google-login-automation.mdx | 4 +- learn/playwright/handling-test-data.mdx | 2 +- ...ow-to-parameterize-playwright-projects.mdx | 2 +- learn/playwright/how-to-set-up-locally.mdx | 2 +- learn/playwright/iframe-interaction.mdx | 2 +- learn/playwright/intercept-requests.mdx | 4 +- learn/playwright/login-automation.mdx | 2 +- .../playwright/microsoft-login-automation.mdx | 4 +- learn/playwright/mock-api.mdx | 18 ++-- learn/playwright/multitab-flows.mdx | 2 +- learn/playwright/navigation.mdx | 2 +- learn/playwright/overview.mdx | 14 ++-- learn/playwright/performance.mdx | 6 +- learn/playwright/scraping-behind-login.mdx | 2 +- learn/playwright/script-recorders.mdx | 2 +- learn/playwright/selectors.mdx | 16 ++-- learn/playwright/steps-decorators.mdx | 6 +- learn/playwright/taking-screenshots.mdx | 2 +- learn/playwright/test-fixtures.mdx | 24 +++--- learn/playwright/testing-apis.mdx | 4 +- learn/playwright/testing-coupons.mdx | 2 +- learn/playwright/testing-file-uploads.mdx | 2 +- learn/playwright/testing-in-parallel.mdx | 12 +-- learn/playwright/testing-pyramid.mdx | 12 +-- learn/playwright/user-signup-automation.mdx | 2 +- learn/playwright/web-scraping.mdx | 2 +- learn/playwright/what-is-playwright.mdx | 6 +- learn/playwright/writing-tests.mdx | 2 +- platform/allowlisting-traffic.mdx | 6 +- platform/data-storage.mdx | 4 +- platform/dynamic-secret-scrubbing.mdx | 4 +- platform/groups.mdx | 16 ++-- platform/ip-information.mdx | 4 +- platform/managing-false-positives.mdx | 18 ++-- platform/network-diagnostic-tools.mdx | 4 +- .../private-locations/agent-configuration.mdx | 12 +-- platform/private-locations/agent-images.mdx | 16 ++-- platform/private-locations/change-log.mdx | 4 +- .../kubernetes-deployment.mdx | 2 +- platform/private-locations/overview.mdx | 10 +-- platform/private-locations/proxy-setup.mdx | 2 +- .../private-locations/scaling-redundancy.mdx | 2 +- platform/reporting/overview.mdx | 26 +++--- platform/runtimes/overview.mdx | 2 +- platform/runtimes/runtime-specification.mdx | 4 +- platform/secrets.mdx | 24 +++--- platform/variables.mdx | 2 +- platform/views.mdx | 2 +- quickstart.mdx | 2 +- resolve/ai-root-cause-analysis/overview.mdx | 10 +-- resolve/automatic-check-repair.mdx | 2 +- resolve/overview.mdx | 12 +-- resolve/traces/export/dash0.mdx | 2 +- resolve/traces/export/grafana-tempo.mdx | 2 +- resolve/traces/export/honeycomb.mdx | 2 +- resolve/traces/export/new-relic.mdx | 2 +- resolve/traces/export/to-chronosphere.mdx | 2 +- resolve/traces/how-it-works.mdx | 12 +-- resolve/traces/import/https-grpc.mdx | 2 +- resolve/traces/import/missing-spans.mdx | 8 +- resolve/traces/import/open-telemetry.mdx | 2 +- resolve/traces/import/overview.mdx | 4 +- resolve/traces/instrumentation/nextjs.mdx | 2 +- resolve/traces/overview.mdx | 16 ++-- what-is-checkly.mdx | 12 +-- 369 files changed, 1846 insertions(+), 1846 deletions(-) diff --git a/admin/changing-your-email-password.mdx b/admin/changing-your-email-password.mdx index d67eaeccc..b5931ced9 100644 --- a/admin/changing-your-email-password.mdx +++ b/admin/changing-your-email-password.mdx @@ -1,7 +1,7 @@ --- title: "Changing your email or password in Checkly" description: "Learn how to change your email address or password in your Checkly account" -sidebarTitle: "Changing Email or Password" +sidebarTitle: "Changing email or password" canonical: 'https://www.checklyhq.com/docs/admin/changing-your-email-password/' --- diff --git a/admin/creating-api-key.mdx b/admin/creating-api-key.mdx index b0ff4af52..5ec5e9e5e 100644 --- a/admin/creating-api-key.mdx +++ b/admin/creating-api-key.mdx @@ -1,7 +1,7 @@ --- title: "Creating an API key in Checkly" description: "Learn how to create and manage user and service API keys for the Checkly API and CLI" -sidebarTitle: "Creating an API Key" +sidebarTitle: "Creating an API key" canonical: 'https://www.checklyhq.com/docs/admin/creating-api-key/' --- diff --git a/admin/deleting-your-account.mdx b/admin/deleting-your-account.mdx index dbc53e253..aa30f850f 100644 --- a/admin/deleting-your-account.mdx +++ b/admin/deleting-your-account.mdx @@ -1,7 +1,7 @@ --- title: "Deleting your Checkly account" description: "Learn how to permanently delete your Checkly account" -sidebarTitle: "Deleting Your Account" +sidebarTitle: "Deleting your account" canonical: 'https://www.checklyhq.com/docs/admin/deleting-your-account/' --- diff --git a/admin/team-management/adding-team-members.mdx b/admin/team-management/adding-team-members.mdx index c19af5ae8..a1adadb61 100644 --- a/admin/team-management/adding-team-members.mdx +++ b/admin/team-management/adding-team-members.mdx @@ -1,7 +1,7 @@ --- title: "Adding team members to your Checkly account" description: "Learn how to invite team members to join your Checkly account and manage team collaboration" -sidebarTitle: "Adding Team Members" +sidebarTitle: "Adding team members" canonical: 'https://www.checklyhq.com/docs/admin/team-management/adding-team-members/' --- diff --git a/admin/team-management/custom-roles.mdx b/admin/team-management/custom-roles.mdx index ce1a4067a..f24620f9d 100644 --- a/admin/team-management/custom-roles.mdx +++ b/admin/team-management/custom-roles.mdx @@ -1,7 +1,7 @@ --- title: "Custom roles" description: "Beta documentation for creating custom roles and assigning them to members, invitations, and service API keys." -sidebarTitle: "Custom Roles" +sidebarTitle: "Custom roles" tag: "Beta" canonical: 'https://www.checklyhq.com/docs/admin/team-management/custom-roles/' --- @@ -12,7 +12,7 @@ Custom roles are in beta and are not generally available. This documentation app A custom role is a named set of permissions that you pick one by one. Custom roles sit next to the [built-in roles](/admin/team-management/overview#team-member-roles). You can assign them to members, invitations, and [service API keys](/admin/creating-api-key#service-api-keys). -## The Roles page +## The roles page **Account settings > Roles** lists your account's custom roles. It shows once custom roles are turned on for your account. Each row has the role's name and description, how many permissions it grants, and how many members, pending invitations, and service API keys hold it. Click a role's name to open it. diff --git a/admin/team-management/managing-team-members.mdx b/admin/team-management/managing-team-members.mdx index 136bd8132..8df11c714 100644 --- a/admin/team-management/managing-team-members.mdx +++ b/admin/team-management/managing-team-members.mdx @@ -1,7 +1,7 @@ --- title: "Managing team members" description: "Find members in your Checkly account, change their roles or remove them several at a time, resend or remove pending invitations, change your own role, and leave an account." -sidebarTitle: "Managing Team Members" +sidebarTitle: "Managing team members" canonical: 'https://www.checklyhq.com/docs/admin/team-management/managing-team-members/' --- diff --git a/admin/team-management/multi-factor-authentication.mdx b/admin/team-management/multi-factor-authentication.mdx index 928932470..14011f6c9 100644 --- a/admin/team-management/multi-factor-authentication.mdx +++ b/admin/team-management/multi-factor-authentication.mdx @@ -1,7 +1,7 @@ --- -title: "Multi-Factor Authentication in Checkly" +title: "Multi-factor authentication in Checkly" description: "Learn how to set up and manage multi-factor authentication for enhanced account security" -sidebarTitle: "Multi-Factor Auth" +sidebarTitle: "Multi-factor auth" canonical: 'https://www.checklyhq.com/docs/admin/team-management/multi-factor-authentication/' --- diff --git a/admin/team-management/overview.mdx b/admin/team-management/overview.mdx index bdd1d98c8..42250ad38 100644 --- a/admin/team-management/overview.mdx +++ b/admin/team-management/overview.mdx @@ -1,5 +1,5 @@ --- -title: "Admin Overview" +title: "Admin overview" description: "Comprehensive guide to managing your Checkly account, team members, security, and integrations" sidebarTitle: "Overview" canonical: 'https://www.checklyhq.com/docs/admin/team-management/overview/' @@ -7,7 +7,7 @@ canonical: 'https://www.checklyhq.com/docs/admin/team-management/overview/' This section covers all aspects of administering your Checkly account, from managing team members and permissions to setting up advanced security features and API access. -## Team Member Roles +## Team member roles Checkly has five built-in roles: **Owner**, **Admin**, **Read & Write**, **Read & Run**, and **Read Only**. Each role inherits all permissions from the roles below it. If [custom roles](/admin/team-management/custom-roles) (beta) are enabled for your account, you can also define roles with the permissions you pick. @@ -32,7 +32,7 @@ Each account has one Owner. The account creator is the Owner until they [transfe Your account role grants permissions for actions on resources. Use the [permissions reference](/admin/team-management/permissions) to find each permission’s ID, name in the role editor, description, and how to request access. -### Choosing the Right Role +### Choosing the right role | Role | Best for | |------|----------| @@ -42,25 +42,25 @@ Your account role grants permissions for actions on resources. Use the [permissi | **Read & Run** | QA engineers or CI/CD pipelines that run tests but shouldn't modify configuration | | **Read Only** | Stakeholders who need visibility into monitoring status | -### Adding Team Members +### Adding team members Learn how to invite new users to your account. [Learn more about adding team members](/admin/team-management/adding-team-members) -### Managing Team Members +### Managing team members Change members' roles, remove members and invitations, change your own role, or leave an account. [Learn more about managing team members](/admin/team-management/managing-team-members) -### Transferring Ownership +### Transferring ownership **Owners** can transfer ownership to another team member from the [General](https://app.checklyhq.com/settings/account/general) section in account settings. Click "Transfer ownership" and follow the instructions. Your role will change to **Admin** after the transfer. If the current Owner is no longer at your company or can no longer access Checkly, reach out to [support@checklyhq.com](mailto:support@checklyhq.com) and we can transfer ownership for you. To verify that you're authorized to request the change, we'll ask you to provide a previous Checkly receipt or invoice. -## Account Management +## Account management ### Account name @@ -68,7 +68,7 @@ The account Owner can change the account name from the [General](https://app.che ![set account name](/images/docs/images/teams/account_name.png) -### Email and Password Changes +### Email and password changes Manage your login credentials and account information securely. @@ -76,21 +76,21 @@ Manage your login credentials and account information securely. ## Security -### Multi-Factor Authentication +### Multi-factor authentication Add an extra layer of security to your account with MFA using authenticator apps. [Set up multi-factor authentication](/admin/team-management/multi-factor-authentication) -### Single Sign-On (SSO) +### Single sign-on (SSO) For enterprise customers, Checkly supports SSO integration with your existing identity provider. [Learn about SSO options](/admin/team-management/single-sign-on) -## API Access +## API access -### Creating API Keys +### Creating API keys Generate API keys for programmatic access to your Checkly account through the REST API and CLI. @@ -100,6 +100,6 @@ Generate API keys for programmatic access to your Checkly account through the RE - **User API Keys** - Tied to individual users with inherited permissions - **Service API Keys** - Account-level keys for CI/CD and automation (Starter, Team, and Enterprise plans) -## Getting Help +## Getting help If you need assistance with any administrative tasks or have questions about account management, please contact [Checkly Support](mailto:support@checklyhq.com). diff --git a/admin/team-management/single-sign-on.mdx b/admin/team-management/single-sign-on.mdx index 46ece65d3..7e6017e37 100644 --- a/admin/team-management/single-sign-on.mdx +++ b/admin/team-management/single-sign-on.mdx @@ -1,7 +1,7 @@ --- -title: "Single Sign-on in Checkly" +title: "Single sign-on in Checkly" description: "Overview of Single Sign-On (SSO) in Checkly for enterprise customers, including setting up the connection and other frequently asked questions" -sidebarTitle: "Single Sign-On" +sidebarTitle: "Single sign-on" canonical: 'https://www.checklyhq.com/docs/admin/team-management/single-sign-on/' --- diff --git a/ai/markdown-access.mdx b/ai/markdown-access.mdx index 65210d3da..429000477 100644 --- a/ai/markdown-access.mdx +++ b/ai/markdown-access.mdx @@ -1,7 +1,7 @@ --- -title: 'Markdown Access' +title: 'Markdown access' description: 'Access Checkly documentation as markdown to use with AI assistants and coding agents.' -sidebarTitle: 'Markdown Access' +sidebarTitle: 'Markdown access' canonical: 'https://www.checklyhq.com/docs/ai/markdown-access/' --- diff --git a/ai/mcp-server.mdx b/ai/mcp-server.mdx index 9eb1ef72d..716dc115e 100644 --- a/ai/mcp-server.mdx +++ b/ai/mcp-server.mdx @@ -1,5 +1,5 @@ --- -title: 'Checkly MCP Server' +title: 'Checkly MCP server' description: 'Connect MCP clients to Checkly to inspect checks, test sessions, RCA, result assets, status pages, incidents, and account context.' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/ai/mcp-server/' diff --git a/ai/mcp-server/setup.mdx b/ai/mcp-server/setup.mdx index ab6af30bc..17b0cf97f 100644 --- a/ai/mcp-server/setup.mdx +++ b/ai/mcp-server/setup.mdx @@ -1,5 +1,5 @@ --- -title: 'Set up the Checkly MCP Server' +title: 'Set up the Checkly MCP server' description: 'Choose an authentication method, connect an MCP client, select an account, and verify the Checkly MCP Server connection.' sidebarTitle: 'Setup' canonical: 'https://www.checklyhq.com/docs/ai/mcp-server/setup/' diff --git a/ai/mcp-server/troubleshooting.mdx b/ai/mcp-server/troubleshooting.mdx index 5af711ad2..0e5daa26b 100644 --- a/ai/mcp-server/troubleshooting.mdx +++ b/ai/mcp-server/troubleshooting.mdx @@ -1,5 +1,5 @@ --- -title: 'Troubleshoot the Checkly MCP Server' +title: 'Troubleshoot the Checkly MCP server' description: 'Resolve common Checkly MCP Server setup, authentication, account selection, and tool access issues.' sidebarTitle: 'Troubleshooting' canonical: 'https://www.checklyhq.com/docs/ai/mcp-server/troubleshooting/' diff --git a/ai/overview.mdx b/ai/overview.mdx index f639f92ec..61664a1b0 100644 --- a/ai/overview.mdx +++ b/ai/overview.mdx @@ -1,5 +1,5 @@ --- -title: 'AI Agents & Coding Assistants' +title: 'AI agents & coding assistants' description: 'Use AI agents and coding assistants with Checkly Skills and the Checkly MCP Server.' sidebarTitle: 'Overview' keywords: ['mcp', 'ai', 'generate checks', 'agents', 'context'] @@ -52,7 +52,7 @@ Install [Checkly Skills](/ai/skills) or connect the [Checkly MCP Server](/ai/mcp For coding agents with repo and code access. Author Monitoring as Code with the Checkly CLI. - + For desktop or sandboxed agents. Live access to Checkly account data and remote actions. @@ -77,7 +77,7 @@ For desktop or sandboxed agents. Live access to Checkly account data and remote Every Checkly documentation page is available as markdown, and an `llms.txt` index lists them all. Both make it easy to pull the exact docs your agent needs into its context. - + Append `.md` to any docs URL, request markdown with content negotiation, or copy a page as markdown. diff --git a/ai/plugin.mdx b/ai/plugin.mdx index 76f107660..c844e716e 100644 --- a/ai/plugin.mdx +++ b/ai/plugin.mdx @@ -1,5 +1,5 @@ --- -title: 'Checkly Plugin for AI Coding Agents' +title: 'Checkly plugin for AI coding agents' description: 'Install the Checkly plugin to give your AI coding agent Checkly monitoring skills and Playwright best practices in a single package.' sidebarTitle: 'Plugin' canonical: 'https://www.checklyhq.com/docs/ai/plugin/' diff --git a/ai/rocky-ai.mdx b/ai/rocky-ai.mdx index 5fcdf868b..f17c99c85 100644 --- a/ai/rocky-ai.mdx +++ b/ai/rocky-ai.mdx @@ -7,17 +7,17 @@ canonical: 'https://www.checklyhq.com/docs/ai/rocky-ai/' Rocky AI is Checkly's AI agent. Rocky AI can help you automatically determine user impact and root cause on any failing check using error messages, code, metrics, OTeL traces, trace routes, packet captures: essentially all artefact generated by a check or test. -## Rocky AI Capabilities +## Rocky AI capabilities ### AI Assistant Use the [AI Assistant](./ai-assistant) to plan monitoring and create checks and monitors with a generated check intent. -### Automatic Check Repair +### Automatic check repair Set an intent and enable [automatic repair](../resolve/automatic-check-repair) for a Browser or Multistep check. -### Root Cause and User Impact Analysis +### Root cause and user impact analysis - **User Impact**: Rocky AI analyzes the failure and provides you with a list of impacted user groups and features. - **Root Cause**: Rocky AI analyzes the failure and provides you with a root cause analysis. @@ -25,7 +25,7 @@ Set an intent and enable [automatic repair](../resolve/automatic-check-repair) f [**Learn More**](/resolve/ai-root-cause-analysis/overview) -## Consumption and Invocations +## Consumption and invocations Each root cause analysis uses one AI invocation from your plan's allowance, whether it starts automatically or manually. Sending the same analysis to multiple alert channels still uses only one invocation. An automatic check repair uses one additional invocation. Each AI Assistant conversation uses one invocation on its first run. Later messages in that conversation use no more invocations. **Initialize from saved check** does not use an invocation. @@ -35,14 +35,14 @@ When your invocation quota is reached, no overages are charged. Invocations refr By default, Rocky AI automatically analyzes every new error group, which consumes invocations. You can disable automatic analysis in the [AI settings](https://app.checklyhq.com/accounts/rocky-ai) to only use invocations for manual analyses. -## Data Privacy and Security +## Data privacy and security - All AI features are designed to operate on the data you provide or the data generated by your checks. This data is already stored in Checkly, and we do not send any additional data to third-party AI providers. - Values of secret [environment variables](/platform/variables) are scrubbed from check results when the check runs, before the results are stored and before Rocky AI reads them. - We do not train any custom models on your data. - Any data used by the AI features is processed in real-time and not stored for future training. -## Built-in and Custom Models +## Built-in and custom models By default, Checkly uses OpenAI's GPT-6.1 Sol model for AI features. You can also bring your own model (BYOM) by selecting a custom model in the [AI settings](https://app.checklyhq.com/accounts/rocky-ai). diff --git a/ai/skills.mdx b/ai/skills.mdx index 34f319d09..65d4cecd4 100644 --- a/ai/skills.mdx +++ b/ai/skills.mdx @@ -59,7 +59,7 @@ Provide the necessary Checkly context and let your AI agent of choice do the res Using Checkly, you can now control your monitoring setup with AI agents without needing a specific MCP server or API for your monitoring. Tell your agent what you want to do and it will access the necessary context and use the CLI to manage your monitoring setup effectively. -## Skill Details +## Skill details Create and manage monitoring checks, alert channels, dashboards, status pages, and other Checkly constructs using the CLI. diff --git a/api-reference/overview.mdx b/api-reference/overview.mdx index f4676d003..bf7cc2829 100644 --- a/api-reference/overview.mdx +++ b/api-reference/overview.mdx @@ -35,7 +35,7 @@ curl -H "Authorization: Bearer [apiKey]" -H "X-Checkly-Account: [accountId]" [More information about managing API keys](/admin/creating-api-key), including service API keys. -## Rate Limits +## Rate limits The Checkly Public API uses rate limits to help manage the sheer volume of requests we receive. The rate limit is characterized by allowing a maximum number of requests within a time interval. diff --git a/changelog/changelog.mdx b/changelog/changelog.mdx index d0e0d67ac..ef017b386 100644 --- a/changelog/changelog.mdx +++ b/changelog/changelog.mdx @@ -5,10 +5,10 @@ description: Stay up to date with product updates and release notes across Check canonical: 'https://www.checklyhq.com/docs/changelog/changelog/' --- -## Available Changelogs +## Available changelogs -### Private Locations +### Private locations @@ -129,7 +129,7 @@ npx checkly account plan -o md -### Plan Examples +### Plan examples ```bash Terminal # Show account plan summary (metered limits + flag count) @@ -154,7 +154,7 @@ npx checkly account plan --disabled npx checkly account plan BROWSER_CHECKS ``` -### JSON Response +### JSON response The `--output=json` format returns a structured response useful for programmatic access and AI agents. @@ -195,7 +195,7 @@ Key fields: - **`locations.all`** — filter to entries where `available` is `true` to get valid locations for your checks. Respect `maxPerCheck` as the upper bound per check. - **`entitlements`** — metered entitlements include a `quantity` limit. Disabled entitlements include `requiredPlan` and `upgradeUrl`. -## Related Commands +## Related commands - [`checkly members`](/cli/checkly-members) - List and manage account members - [`checkly skills manage`](/cli/checkly-skills#checkly-skills-manage-resource) - Account management context for AI agents diff --git a/cli/checkly-alert-channels.mdx b/cli/checkly-alert-channels.mdx index 5ebe6022e..df7c1eb20 100644 --- a/cli/checkly-alert-channels.mdx +++ b/cli/checkly-alert-channels.mdx @@ -50,7 +50,7 @@ npx checkly alert-channels list [options] | `--page, -p` | - | Page number. Default: `1`. | | `--output, -o` | - | Output format: `table`, `json`, or `md`. Default: `table`. | -### List Options +### List options @@ -90,7 +90,7 @@ npx checkly alert-channels list -o md -### List Examples +### List examples ```bash Terminal # List the first page of alert channels @@ -125,7 +125,7 @@ npx checkly alert-channels get [options] |--------|----------|-------------| | `--output, -o` | - | Output format: `detail`, `json`, or `md`. Default: `detail`. | -### Get Options +### Get options @@ -140,7 +140,7 @@ npx checkly alert-channels get 12345 -o md -### Get Examples +### Get examples ```bash Terminal # View alert channel details and subscriptions @@ -179,7 +179,7 @@ npx checkly alert-channels logs [options] If you omit `--from` and `--to`, the command returns logs from the preceding 24 hours. An explicit time window can span at most 24 hours. -### Logs Options +### Logs options @@ -255,7 +255,7 @@ npx checkly alert-channels logs 12345 -o md -### Logs Examples +### Logs examples ```bash Terminal # List recent notification logs for an alert channel @@ -287,7 +287,7 @@ The `list` and `logs` commands return JSON in a stable pagination envelope when } ``` -## Related Commands +## Related commands - [`checkly checks`](/cli/checkly-checks) - List and inspect checks - [`checkly api`](/cli/checkly-api) - Make authenticated Checkly API requests diff --git a/cli/checkly-api.mdx b/cli/checkly-api.mdx index d9f26d819..327a6f814 100644 --- a/cli/checkly-api.mdx +++ b/cli/checkly-api.mdx @@ -180,13 +180,13 @@ npx checkly api /v1/checks --verbose ... ``` -## Related Commands +## Related commands These commands are commonly used alongside `checkly api`. - [`checkly login`](/cli/checkly-login) - Sign in to your Checkly account - [`checkly whoami`](/cli/checkly-whoami) - Display current account and user information -## API Reference +## API reference For available endpoints, see the [Checkly API reference](/api-reference/overview). diff --git a/cli/checkly-assets.mdx b/cli/checkly-assets.mdx index 4241e7f33..7d4731fcd 100644 --- a/cli/checkly-assets.mdx +++ b/cli/checkly-assets.mdx @@ -56,7 +56,7 @@ npx checkly assets list --result-id= (--check-id= | --test- | `--view` | - | Human output view: `table` or `tree`. Ignored with `--output json`. Default: `table`. | | `--output, -o` | - | Output format: `table`, `json`, or `md`. Default: `table`. | -### List Options +### List options @@ -144,7 +144,7 @@ npx checkly assets list --result-id= --check-id= -o md -### List Examples +### List examples ```bash Terminal # List all assets for a check result @@ -192,7 +192,7 @@ npx checkly assets download --result-id= (--check-id= | --t Pass `--type` or `--asset` to select which assets to download. Use `--type all` to download all assets for the result. -### Download Options +### Download options @@ -303,7 +303,7 @@ npx checkly assets download --result-id= --check-id= --type -### Download Examples +### Download examples ```bash Terminal # Download all assets for a check result @@ -328,7 +328,7 @@ npx checkly assets download --result-id= --check-id= --type npx checkly assets download --result-id= --check-id= --type=all --output=json ``` -## Related Commands +## Related commands - [`checkly test-sessions`](/cli/checkly-test-sessions) - Inspect recorded test sessions and their results - [`checkly checks`](/cli/checkly-checks) - List, inspect, and analyze checks and their results diff --git a/cli/checkly-checks.mdx b/cli/checkly-checks.mdx index 8ab507db4..44e7d20f5 100644 --- a/cli/checkly-checks.mdx +++ b/cli/checkly-checks.mdx @@ -57,7 +57,7 @@ npx checkly checks list [options] | `--hide-id` | - | Hide check IDs in table output. | | `--output, -o` | - | Output format: `table`, `json`, or `md`. Default: `table`. | -### List Options +### List options @@ -162,7 +162,7 @@ npx checkly checks list -o md -### List Examples +### List examples ```bash Terminal # List all checks with default settings @@ -214,7 +214,7 @@ Without a selector, the command runs all eligible checks in your account. By def | `--[no-]fail-on-no-matching` | - | Fail when no checks match. Enabled by default. | | `--output, -o` | - | Output format: `table`, `json`, or `md`. Default: `table`. | -### Run Examples +### Run examples ```bash Terminal # Run one deployed check and wait for its result @@ -268,7 +268,7 @@ npx checkly checks get [options] | `--filter-status` | - | Only include runs with this status in stats: `success` or `failure`. | | `--output, -o` | - | Output format: `detail`, `json`, or `md`. Default: `detail`. | -### Get Options +### Get options @@ -419,7 +419,7 @@ npx checkly checks get -o md -### Get Examples +### Get examples ```bash Terminal # View check details, recent results, and stats @@ -478,7 +478,7 @@ npx checkly checks stats [checkIds...] [options] | `--type` | - | Filter by check type. | | `--output, -o` | - | Output format: `table`, `json`, or `md`. Default: `table`. | -### Stats Options +### Stats options @@ -571,7 +571,7 @@ npx checkly checks stats -o md -### Stats Examples +### Stats examples ```bash Terminal # Show stats for all checks (last 24 hours) @@ -622,7 +622,7 @@ npx checkly checks delete [options] | `--force, -f` | - | Skip the confirmation prompt. | | `--dry-run` | - | Preview what would happen without deleting the check. | -### Delete Options +### Delete options @@ -649,7 +649,7 @@ npx checkly checks delete 12345 --dry-run -### Delete Examples +### Delete examples ```bash Terminal # Delete a check with a confirmation prompt @@ -662,7 +662,7 @@ npx checkly checks delete 12345 --dry-run npx checkly checks delete 12345 --force ``` -## Related Commands +## Related commands - [`checkly status-pages`](/cli/checkly-status-pages) - List and inspect status pages - [`checkly trigger`](/cli/checkly-trigger) - Run deployed checks in a test session without affecting monitoring state diff --git a/cli/checkly-deploy.mdx b/cli/checkly-deploy.mdx index 5c891e60d..85f34f1c4 100644 --- a/cli/checkly-deploy.mdx +++ b/cli/checkly-deploy.mdx @@ -187,7 +187,7 @@ There is no flag for the choice, and the `confirmation_required` envelope does n When Checkly cannot provide a plan, the CLI warns that it could not get one, for example `Could not check what this deploy would change` or `Checkly has deploy plans switched off at the moment`, and deploys without one, which is what a deploy with `--no-plan` does on purpose. Without a plan, a deploy that deletes removed resources finds them with a dry run and lists them in the confirmation; with `--preserve-resources` nothing is listed. Either way the code bundle is uploaded only after you confirm. `--plan-token`, `--prune-unmanaged-relations` and `--fail-on-drift` need a plan and are refused without one. -## Command Options +## Command options @@ -584,7 +584,7 @@ Successfully deployed project "Website Monitoring" to account "Monitoring as Cod Detach-on-deploy requires a recent Checkly backend. Against older backends, `--preserve-resources` still keeps your resources, but the deploy output may report them as permanently deleted rather than as kept in your account. -## Git Integration +## Git integration When you deploy a project, you can attach Git-specific information so changes to any resources are displayed in the Checkly web UI with the correct commit, branch, and author information. @@ -592,7 +592,7 @@ The Checkly CLI evaluates Git information from your local or CI environment on a -## Related Commands +## Related commands - [`checkly login`](/cli/checkly-login) - Log in to your Checkly account - [`checkly test`](/cli/checkly-test) - Test your setup before deployment diff --git a/cli/checkly-destroy.mdx b/cli/checkly-destroy.mdx index 3b788b4f6..1c6b4a1b6 100644 --- a/cli/checkly-destroy.mdx +++ b/cli/checkly-destroy.mdx @@ -29,7 +29,7 @@ npx checkly destroy [options] | `--force, -f` | - | Force mode. Skips the confirmation dialog. | | `--preserve-resources` | - | Delete only the project, detaching its resources so they remain in your Checkly account. | -## Command Options +## Command options @@ -86,7 +86,7 @@ $ npx checkly destroy --preserve-resources --force -## What Gets Destroyed +## What gets destroyed The `destroy` command removes the all the resources managed by the specified project. These resources could include: @@ -99,7 +99,7 @@ The `destroy` command removes the all the resources managed by the specified pro When run with `--preserve-resources`, only the project itself is deleted. All of the above resources remain in your Checkly account as regular account-level resources and are no longer tracked by the CLI. -## Safety Considerations +## Safety considerations By default, the command prompts for confirmation: @@ -110,7 +110,7 @@ $ npx checkly destroy Please confirm by typing the project name "Website Monitoring": ``` -## Related Commands +## Related commands - [`checkly deploy`](/cli/checkly-deploy) - Deploy resources to Checkly - [`checkly test`](/cli/checkly-test) - Test your setup before deployment diff --git a/cli/checkly-env.mdx b/cli/checkly-env.mdx index b3d2478a0..90f879ee7 100644 --- a/cli/checkly-env.mdx +++ b/cli/checkly-env.mdx @@ -171,9 +171,9 @@ npx checkly env rm ENVIRONMENT npx checkly env rm OLD_VARIABLE --force ``` -## Variable Types +## Variable types -### Regular Variables +### Regular variables Standard key-value pairs visible to all team members: @@ -181,7 +181,7 @@ Standard key-value pairs visible to all team members: npx checkly env add ENVIRONMENT "production" ``` -### Locked Variables +### Locked variables Locked environment variables can only be accessed by team members with "Read & Write" access or above. @@ -197,7 +197,7 @@ Once saved, secrets are never shown in the UI or in logs. The secret value canno npx checkly env add API_SECRET "super-secret-key" --secret ``` -## Variable Scope +## Variable scope Environment variables managed by `checkly env` are **global** and available to: @@ -207,7 +207,7 @@ Environment variables managed by `checkly env` are **global** and available to: For check-specific or group-specific variables, use the web UI or configure them directly in your monitoring-as-code setup. -## Best Practices +## Best practices 1. **Use secrets for sensitive data** like API keys, passwords, and tokens 2. **Lock internal variables** that shouldn't be visible to read-only users @@ -215,7 +215,7 @@ For check-specific or group-specific variables, use the web UI or configure them 4. **Document variables** and their purposes for team collaboration 5. **Regular cleanup** of unused variables to maintain security -## Related Commands +## Related commands - [`checkly test`](/cli/checkly-test) - Test your setup before deployment - [`checkly deploy`](/cli/checkly-deploy) - Deploy your Checkly configuration diff --git a/cli/checkly-import.mdx b/cli/checkly-import.mdx index 80ef6af7c..62e2eadcd 100644 --- a/cli/checkly-import.mdx +++ b/cli/checkly-import.mdx @@ -60,7 +60,7 @@ Prefix a resource with `!` to exclude it, for example `!check:2ce8...`. | `--root` | - | Root folder in which to write generated code files. Default: `__checks__`. | | `--preview` | - | Preview generated code without creating an import plan. | -## Command Options +## Command options @@ -111,11 +111,11 @@ npx checkly import plan --preview -## Import Workflow +## Import workflow The import process follows a three-phase workflow for safe resource migration: -### 1. Plan Generation +### 1. Plan generation Analyze your account, generate an import plan and create code files for your resources. @@ -123,7 +123,7 @@ Analyze your account, generate an import plan and create code files for your res npx checkly import plan ``` -### 2. Plan Application +### 2. Plan application Apply the generated plan and link the imported resources to your CLI project, but keeps the mapping in a pending state. @@ -131,7 +131,7 @@ npx checkly import plan npx checkly import apply ``` -### 3. Plan Commitment +### 3. Plan commitment Commit the applied changes and mark resources as CLI-managed. @@ -169,23 +169,23 @@ Cancel a generated plan that hasn't been committed to discard any pending import npx checkly import cancel ``` -## Best Practices +## Best practices -### Before Importing +### Before importing 1. **Rely on version control and git** to track changes 2. **Review your account** resources to understand what will be imported 3. **Plan directory structure** using `--root` if needed 4. **Import specific resources** using `resource-type:id` syntax -### After Importing +### After importing 1. **Review generated code** for accuracy and style consistency 2. **Test imported checks** using `checkly test` 3. **Commit to version control** to track changes 4. **Deploy to verify** everything works as expected -## Related Commands +## Related commands - [`checkly deploy`](/cli/checkly-deploy) - Deploy imported resources - [`checkly test`](/cli/checkly-test) - Test imported checks locally diff --git a/cli/checkly-incidents.mdx b/cli/checkly-incidents.mdx index 821f19805..32d53cf6b 100644 --- a/cli/checkly-incidents.mdx +++ b/cli/checkly-incidents.mdx @@ -57,7 +57,7 @@ npx checkly incidents list [options] | `--status` | - | Filter by incident status: `open`, `resolved`, or `all`. Default: `open`. | | `--output, -o` | - | Output format: `table`, `json`, or `md`. Default: `table`. | -### List Options +### List options @@ -111,7 +111,7 @@ npx checkly incidents list -o md -### List Examples +### List examples ```bash Terminal # List all open incidents (default) @@ -151,7 +151,7 @@ npx checkly incidents create [options] | `--force, -f` | - | Skip the confirmation prompt. | | `--dry-run` | - | Preview what would happen without executing. | -### Create Options +### Create options @@ -237,7 +237,7 @@ npx checkly incidents create --status-page-id= --title="..." --output=json -### Create Examples +### Create examples ```bash Terminal # Create a minor incident affecting all services @@ -278,7 +278,7 @@ npx checkly incidents update [options] | `--force, -f` | - | Skip the confirmation prompt. | | `--dry-run` | - | Preview what would happen without executing. | -### Update Options +### Update options @@ -341,7 +341,7 @@ npx checkly incidents update --message="..." --output=json -### Update Examples +### Update examples ```bash Terminal # Post an investigating update @@ -383,7 +383,7 @@ npx checkly incidents resolve [options] | `--force, -f` | - | Skip the confirmation prompt. | | `--dry-run` | - | Preview what would happen without executing. | -### Resolve Options +### Resolve options @@ -421,7 +421,7 @@ npx checkly incidents resolve --output=json -### Resolve Examples +### Resolve examples ```bash Terminal # Resolve an incident with default message @@ -434,7 +434,7 @@ npx checkly incidents resolve --message="Database connection pool issue res npx checkly incidents resolve --no-notify-subscribers ``` -## Related Commands +## Related commands - [`checkly status-pages`](/cli/checkly-status-pages) - List and inspect status pages - [`checkly checks`](/cli/checkly-checks) - List and inspect checks diff --git a/cli/checkly-init.mdx b/cli/checkly-init.mdx index 07361552a..7a8795f94 100644 --- a/cli/checkly-init.mdx +++ b/cli/checkly-init.mdx @@ -30,7 +30,7 @@ npx checkly init [options] |--------|----------|-------------| | `--target, -t` | - | Install the Checkly skill for a specific AI agent platform. | -## Command Options +## Command options @@ -45,7 +45,7 @@ npx checkly init -t cursor -## What to Expect +## What to expect The `init` command detects your project context and adjusts its flow: @@ -54,7 +54,7 @@ The `init` command detects your project context and adjusts its flow: - **Playwright detected** — provides context-aware setup that accounts for your existing test infrastructure. - **Existing Checkly project** — refreshes your agent skill to the latest version. -### AI-Assisted Setup +### AI-assisted setup When you choose the AI-assisted path (or pass `--target`), the command: @@ -65,7 +65,7 @@ When you choose the AI-assisted path (or pass `--target`), the command: The starter prompt gives your AI agent all the context it needs about your project and Checkly's capabilities. Copy it into your agent's chat to start creating checks. -### Manual Setup +### Manual setup When you choose the manual path, the command: @@ -73,7 +73,7 @@ When you choose the manual path, the command: 2. Installs dependencies 3. Optionally copies example checks (API, browser, heartbeat, URL monitor) into a `__checks__` directory -### CI Mode +### CI mode In CI environments, the command runs non-interactively and outputs setup instructions. The CLI detects CI from `CI=true` and, since CLI v10.0.0, from the variables that CI providers set, such as GitHub Actions, GitLab CI, Jenkins, TeamCity and AWS CodeBuild. Set `CI=false` to turn CI detection off, or set `CHECKLY_CLI_MODE` to choose the mode yourself. A detected AI agent takes precedence over CI. @@ -94,7 +94,7 @@ npx checkly init --target=claude CI=true npx checkly init ``` -## Next Steps +## Next steps After initialization, the typical workflow is: @@ -102,7 +102,7 @@ After initialization, the typical workflow is: 2. **Test** — `npx checkly test` to dry-run your checks 3. **Deploy** — `npx checkly deploy` to deploy checks to Checkly -## Related Commands +## Related commands - [`checkly skills`](/cli/checkly-skills) - Print project context and install agent skills - [`checkly login`](/cli/checkly-login) - Log in to your Checkly account diff --git a/cli/checkly-login.mdx b/cli/checkly-login.mdx index 97e9692cb..5e5b5ffb3 100644 --- a/cli/checkly-login.mdx +++ b/cli/checkly-login.mdx @@ -55,7 +55,7 @@ To create checks for a project, run `npx checkly init`. | `--no-browser` | Only print the URL and code; don't try to open a browser. Setting `CHECKLY_NO_BROWSER=1` does the same, e.g. on headless hosts. | | `--wait` | For AI agents: wait until you approve the code an earlier run showed, instead of returning at once. | -## Authentication Flow +## Authentication flow The login process will: @@ -71,7 +71,7 @@ Commands that need authentication start the same login when no credentials are s When the CLI runs under an AI agent, `checkly login` prints a JSON line with the URL and code for the agent to pass on to you, and exits instead of waiting. The agent then runs `npx checkly login --wait`, which returns as soon as you've approved the login in the browser, so you don't have to tell the agent when you're done. If you have several accounts, the agent asks you which one to use. In CI, set [environment variables](/cli/authentication#from-ci) instead. -### New Users +### New users If you don't have a Checkly account: @@ -79,7 +79,7 @@ If you don't have a Checkly account: 2. Complete account registration 3. Return to the CLI - you'll be automatically logged in -### Existing Users +### Existing users If you already have an account: @@ -87,7 +87,7 @@ If you already have an account: 2. Complete any two-factor authentication if enabled 3. Return to the CLI - authentication will complete automatically -## Authentication Storage +## Authentication storage After successful login, the CLI stores authentication tokens locally in: @@ -117,7 +117,7 @@ You can also switch accounts later using [`checkly switch`](/cli/checkly-switch) While `CHECKLY_API_KEY` is set, `checkly login` refuses to run; remove it to log in. With only `CHECKLY_ACCOUNT_ID` set, `checkly login` uses that account without asking and stores no default. -## Related Commands +## Related commands - [`checkly logout`](/cli/checkly-logout) - Sign out of your Checkly account - [`checkly whoami`](/cli/checkly-whoami) - Display current account information diff --git a/cli/checkly-logout.mdx b/cli/checkly-logout.mdx index d0138881d..529a4b4cf 100644 --- a/cli/checkly-logout.mdx +++ b/cli/checkly-logout.mdx @@ -30,7 +30,7 @@ In a terminal, the CLI asks you to confirm first. When there's no terminal to an |--------|----------|-------------| | `--force, -f` | - | Force mode. Skips the confirmation dialog. | -## Command Options +## Command options @@ -54,16 +54,16 @@ See you soon! 👋 ``` -## What Happens During Logout +## What happens during logout -### Session Invalidation +### Session invalidation The logout process will: 1. **Remove local tokens** from your machine 2. **Require re-authentication** for future CLI usage -### Token Removal +### Token removal The command removes authentication tokens stored locally in: @@ -73,11 +73,11 @@ The command removes authentication tokens stored locally in: The same directory holds a `config.json` with the selected account ID and name, which is cleared as well. -## After Logout +## After logout Once logged out, you'll need to run [`checkly login`](/cli/checkly-login) before using other CLI commands that require authentication. -## Related Commands +## Related commands - [`checkly login`](/cli/checkly-login) - Authenticate with your Checkly account - [`checkly whoami`](/cli/checkly-whoami) - Display current account information diff --git a/cli/checkly-members.mdx b/cli/checkly-members.mdx index 94852e36d..c8fd31f93 100644 --- a/cli/checkly-members.mdx +++ b/cli/checkly-members.mdx @@ -57,7 +57,7 @@ npx checkly members [options] | `--hide-id` | - | Hide member and invite IDs in formatted output. | | `--output, -o` | - | Output format: `table`, `json`, or `md`. Default: `table`. | -### List Examples +### List examples ```bash Terminal # List members and pending invites @@ -120,7 +120,7 @@ npx checkly members update --role= [options] | `--dry-run` | - | Preview the change without updating the member. | | `--output, -o` | - | Output format: `table`, `json`, or `md`. Default: `table`. | -### Update Examples +### Update examples ```bash Terminal # Update a member by email and confirm interactively @@ -163,7 +163,7 @@ npx checkly members delete [options] | `--force, -f` | - | Skip the confirmation prompt. | | `--dry-run` | - | Preview the deletion without removing the member. | -### Delete Examples +### Delete examples ```bash Terminal # Delete a member by email and confirm interactively @@ -179,7 +179,7 @@ npx checkly members delete alex@example.com --dry-run npx checkly members delete alex@example.com --force ``` -## Related Commands +## Related commands - [`checkly account`](/cli/checkly-account) - View plan entitlements and limits - [`checkly whoami`](/cli/checkly-whoami) - Display the current account and user diff --git a/cli/checkly-pw-test.mdx b/cli/checkly-pw-test.mdx index 46d87d47f..59d2fc14f 100644 --- a/cli/checkly-pw-test.mdx +++ b/cli/checkly-pw-test.mdx @@ -20,7 +20,7 @@ Before using `checkly pw-test`, ensure you have: -## Basic Usage +## Basic usage Use `--` to separate Checkly flags from Playwright test options. @@ -29,7 +29,7 @@ npx checkly pw-test [checkly options] -- [playwright options] ``` - + Define `checkly pw-test` specific options before the `--` separator: @@ -53,7 +53,7 @@ Define `checkly pw-test` specific options before the `--` separator: | `--verbose` | - | Always show the full logs of the checks. | - + Define Playwright test runner flags after the `--` separator: @@ -68,7 +68,7 @@ Define Playwright test runner flags after the `--` separator: -### Checkly Command Options +### Checkly command options @@ -328,7 +328,7 @@ npx checkly pw-test --verbose -### Common Playwright Test Options +### Common Playwright Test options The `pw-test` command reuses your `playwright.config` settings. To overwrite these values from the command line, [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) supports most [Playwright test runner options](https://playwright.dev/docs/test-cli). @@ -373,7 +373,7 @@ npx checkly pw-test -- --grep-invert="flaky|unstable" -## Playwright Configuration vs. Applied Command Line Options +## Playwright configuration vs. Applied command line options [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) and the `pw-test` command read and parse your existing `playwright.config` to apply your configuration. @@ -448,7 +448,7 @@ npx checkly pw-test -- --project=chromium --project=firefox npx checkly pw-test -- test.spec.ts ``` -## Key Features +## Key features - Your Playwright configuration applies automatically (traces, videos, screenshots) - Test sessions are recorded by default with full logs, traces, and videos @@ -464,7 +464,7 @@ Press Ctrl+C during a `checkly pw-test` run to cancel the See [Cancellation](/concepts/cancellation) for the full flow. -## Related Commands +## Related commands - [`checkly test`](/cli/checkly-test) - Test your setup before deployment - [`checkly deploy`](/cli/checkly-deploy) - Deploy your Checkly configuration diff --git a/cli/checkly-rca.mdx b/cli/checkly-rca.mdx index 62d4437c5..b1aa4c636 100644 --- a/cli/checkly-rca.mdx +++ b/cli/checkly-rca.mdx @@ -58,7 +58,7 @@ npx checkly rca run [options] *Pass either `--error-group` or `--test-session-error-group`. -### Run Options +### Run options @@ -130,7 +130,7 @@ npx checkly rca run -e -o md -### Run Examples +### Run examples ```bash Terminal # Trigger an RCA and wait for the result @@ -172,7 +172,7 @@ npx checkly rca get [options] | `--watch, -w` | - | Wait for the analysis to complete if still generating. | | `--output, -o` | - | Output format: `detail`, `json`, or `md`. Default: `detail`. | -### Get Options +### Get options @@ -202,7 +202,7 @@ npx checkly rca get -o md -### Get Examples +### Get examples ```bash Terminal # Retrieve a completed RCA @@ -215,7 +215,7 @@ npx checkly rca get rca-xyz-789 --watch npx checkly rca get rca-xyz-789 --output=json ``` -## RCA Output +## RCA output A completed root cause analysis includes: @@ -226,7 +226,7 @@ A completed root cause analysis includes: - **Evidence** — supporting artifacts from the analysis - **Reference links** — relevant external resources -## Related Commands +## Related commands - [`checkly checks`](/cli/checkly-checks) - List, inspect, and analyze checks (includes error groups) - [`checkly test-sessions`](/cli/checkly-test-sessions) - Inspect recorded test sessions and test session error groups diff --git a/cli/checkly-runtimes.mdx b/cli/checkly-runtimes.mdx index 2b2858d52..cb3cf5d6a 100644 --- a/cli/checkly-runtimes.mdx +++ b/cli/checkly-runtimes.mdx @@ -40,9 +40,9 @@ Example output: ... ``` -## Runtime Information +## Runtime information -### Runtime Versions +### Runtime versions Each runtime environment includes: @@ -51,7 +51,7 @@ Each runtime environment includes: - **Playwright version** for browser automation - **Built-in packages** and their versions -### Package Availability +### Package availability Common packages included in Checkly runtimes: @@ -63,7 +63,7 @@ Common packages included in Checkly runtimes: ## Configuration -### Setting Runtime in Configuration +### Setting runtime in configuration Specify a runtime version in your `checkly.config.ts`: @@ -104,7 +104,7 @@ const syntheticGroup = new CheckGroupV2('check-group-synthetics', { }) ``` -### Runtime Compatibility +### Runtime compatibility When selecting a runtime, consider: @@ -116,7 +116,7 @@ When selecting a runtime, consider: Use the latest runtime for new projects to benefit from the newest features and security updates. -## Runtime Updates +## Runtime updates Checkly regularly updates runtimes with: - **Security patches** for Node.js and dependencies @@ -126,7 +126,7 @@ Checkly regularly updates runtimes with: Check the [Checkly changelog](https://feedback.checklyhq.com/changelog) for runtime update announcements. -## Related Commands +## Related commands - [`checkly test`](/cli/checkly-test) - Test checks with current runtime - [`checkly deploy`](/cli/checkly-deploy) - Deploy checks to specified runtime diff --git a/cli/checkly-skills.mdx b/cli/checkly-skills.mdx index 44353f277..f27e53b21 100644 --- a/cli/checkly-skills.mdx +++ b/cli/checkly-skills.mdx @@ -157,7 +157,7 @@ npx checkly skills install --path | `--path, -p` | - | Custom target directory to install the skill into. | | `--force, -f` | - | Overwrite existing SKILL.md without confirmation. | -### Install Options +### Install options @@ -196,7 +196,7 @@ npx checkly skills install --force -### Install Examples +### Install examples ```bash Terminal # Install for Claude Code @@ -212,7 +212,7 @@ npx checkly skills install --path=./agents npx checkly skills install --target=claude --force ``` -## Related Commands +## Related commands - [`checkly account`](/cli/checkly-account) - View and manage your Checkly account - [`checkly checks`](/cli/checkly-checks) - List, inspect, and analyze checks diff --git a/cli/checkly-status-pages.mdx b/cli/checkly-status-pages.mdx index 7d633cde3..410e5c158 100644 --- a/cli/checkly-status-pages.mdx +++ b/cli/checkly-status-pages.mdx @@ -50,7 +50,7 @@ npx checkly status-pages list [options] | `--compact` | - | Show one row per status page instead of per service. | | `--output, -o` | - | Output format: `table`, `json`, or `md`. Default: `table`. | -### List Options +### List options @@ -102,7 +102,7 @@ npx checkly status-pages list -o md -### List Examples +### List examples ```bash Terminal # List all status pages with services expanded @@ -140,7 +140,7 @@ npx checkly status-pages get [options] |--------|----------|-------------| | `--output, -o` | - | Output format: `detail`, `json`, or `md`. Default: `detail`. | -### Get Options +### Get options @@ -155,7 +155,7 @@ npx checkly status-pages get -o md -### Get Examples +### Get examples ```bash Terminal # View status page details with cards and services @@ -165,7 +165,7 @@ npx checkly status-pages get 12345 npx checkly status-pages get 12345 --output=json ``` -## Related Commands +## Related commands - [`checkly checks`](/cli/checkly-checks) - List and inspect checks - [`checkly whoami`](/cli/checkly-whoami) - Display current account information diff --git a/cli/checkly-switch.mdx b/cli/checkly-switch.mdx index 6d841c730..787a1a965 100644 --- a/cli/checkly-switch.mdx +++ b/cli/checkly-switch.mdx @@ -38,7 +38,7 @@ Without a terminal to answer the menu, `checkly switch` lists the accounts inste While `CHECKLY_ACCOUNT_ID` is set, commands use that account instead of the default; `checkly switch` still changes the default and warns. See [Working with several accounts](/cli/authentication#working-with-several-accounts). -## Command Options +## Command options @@ -54,7 +54,7 @@ npx checkly switch -a="a43....." ## Examples - + ```bash Terminal # Standard account switching @@ -69,7 +69,7 @@ npx checkly switch ``` - + ```bash Terminal # Verbose account switching with details @@ -86,13 +86,13 @@ Account switched to Staging (a43.....) ## Troubleshooting -### Account Not Listed +### Account not listed If an expected account doesn't appear: - Verify you have active access to that account - Check that your user hasn't been removed from the account - Try logging out and back in to refresh account permissions -## Related Commands +## Related commands - [`checkly login`](/cli/checkly-login) - Sign in to your Checkly account - [`checkly whoami`](/cli/checkly-whoami) - Display current account information diff --git a/cli/checkly-sync-playwright.mdx b/cli/checkly-sync-playwright.mdx index 540d743b2..9ba51f8c7 100644 --- a/cli/checkly-sync-playwright.mdx +++ b/cli/checkly-sync-playwright.mdx @@ -29,7 +29,7 @@ Copy supported Playwright configuration settings to your Checkly config automati npx checkly sync-playwright ``` -## Supported Playwright Configuration +## Supported Playwright configuration The `sync-playwright` command parses your existing `playwright.config` file and extracts `global`, `use` and `expect` settings. @@ -57,7 +57,7 @@ export default defineConfig({ The following Playwright config values are supported and will be synced: - + | Option | Supported | |------------------|-----------| @@ -79,7 +79,7 @@ The following Playwright config values are supported and will be synced: | `webServer` | ❌ | - + | Option | Supported | |----------------------|-----------| @@ -118,7 +118,7 @@ The following Playwright config values are supported and will be synced: - + | Option | Supported | |---------------------|-----------| @@ -129,7 +129,7 @@ The following Playwright config values are supported and will be synced: -## Related Commands +## Related commands - [`checkly test`](/cli/checkly-test) - Test with synchronized configuration - [`checkly deploy`](/cli/checkly-deploy) - Deploy with updated settings diff --git a/cli/checkly-test-sessions.mdx b/cli/checkly-test-sessions.mdx index 14e8f5483..ee0d2b22e 100644 --- a/cli/checkly-test-sessions.mdx +++ b/cli/checkly-test-sessions.mdx @@ -61,7 +61,7 @@ npx checkly test-sessions list [options] | `--error-group` | - | Filter by test-session error group ID. | | `--output, -o` | - | Output format: `table`, `json`, or `md`. Default: `table`. | -### List Options +### List options @@ -213,7 +213,7 @@ npx checkly test-sessions list -o md -### List Examples +### List examples ```bash Terminal # List recent test sessions @@ -262,7 +262,7 @@ npx checkly test-sessions get [options] | `--watch, -w` | - | Watch a running test session until it completes before rendering. | | `--output, -o` | - | Output format: `detail`, `json`, or `md`. Default: `detail`. | -### Get Options +### Get options @@ -343,7 +343,7 @@ npx checkly test-sessions get -o md -### Get Examples +### Get examples ```bash Terminal # View a recorded test session @@ -362,7 +362,7 @@ npx checkly test-sessions get --error-group= npx checkly test-sessions get --output=json ``` -## Related Commands +## Related commands - [`checkly trigger`](/cli/checkly-trigger) - Trigger deployed checks as a test session - [`checkly test`](/cli/checkly-test) - Test local checks as a test session diff --git a/cli/checkly-test.mdx b/cli/checkly-test.mdx index e0c044cc2..37a8f9c0f 100644 --- a/cli/checkly-test.mdx +++ b/cli/checkly-test.mdx @@ -11,7 +11,7 @@ The `checkly test` command executes all checks in your project on the Checkly cl -## Basic Usage +## Basic usage The basic command runs all checks in your project as a test run without deploying them to your account as monitors. @@ -42,7 +42,7 @@ npx checkly test [arguments] [options] | `--verbose, -v` | - | Always show the full logs of the checks. | | `--[no-]verify-runtime-dependencies` | - | Return an error if checks import dependencies that are not supported by the selected runtime. | -## Command Options +## Command options @@ -474,7 +474,7 @@ To start checks without waiting for them, use `--detach`. The CLI then exits as See [Cancellation](/concepts/cancellation) for the full flow. -## Related Commands +## Related commands - [`checkly pw-test`](/cli/checkly-pw-test) - Run Playwright tests in the Checkly cloud - [`checkly trigger`](/cli/checkly-trigger) - Run deployed checks on-demand diff --git a/cli/checkly-trigger.mdx b/cli/checkly-trigger.mdx index d810af4b2..67f277e08 100644 --- a/cli/checkly-trigger.mdx +++ b/cli/checkly-trigger.mdx @@ -39,7 +39,7 @@ npx checkly trigger [options] | `--timeout` | - | A timeout (in seconds) to wait for each check to make progress once it starts running: report a retry attempt or its result. Checks that have not started yet get up to 900 additional seconds for server-side scheduling. | | `--verbose, -v` | - | Always show the full logs of the checks. | -## Command Options +## Command options @@ -420,7 +420,7 @@ npx checkly trigger --timeout 1200 Default: 600 seconds (10 minutes). Adjust based on your longest-running checks. -## Key Differences from `checkly test` +## Key differences from `checkly test` `npx checkly test` and `npx checkly trigger` serve different purposes in the Checkly ecosystem. Here's a comparison of their key features: @@ -432,9 +432,9 @@ Default: 600 seconds (10 minutes). Adjust based on your longest-running checks. | **Snapshots** | Can update snapshots | Cannot update snapshots | | **Dependencies** | Requires local project | Works independently | -## Use Cases +## Use cases -### Pre-deployment Validation +### Pre-deployment validation Run your deployed checks before promoting code to production: ```bash Terminal @@ -455,7 +455,7 @@ To start checks without waiting for them, use `--detach`. The CLI then exits as See [Cancellation](/concepts/cancellation) for the full flow. -## Related Commands +## Related commands - [`checkly deploy`](/cli/checkly-deploy) - Deploy your Checkly configuration - [`checkly test`](/cli/checkly-test) - Test your setup before deployment diff --git a/cli/checkly-whoami.mdx b/cli/checkly-whoami.mdx index a446cd092..10e774cf9 100644 --- a/cli/checkly-whoami.mdx +++ b/cli/checkly-whoami.mdx @@ -73,7 +73,7 @@ npx checkly whoami --output json `accountSource` is `login` (your stored login and default account), `account_override` (`CHECKLY_ACCOUNT_ID` picks the account for your login) or `environment` (API key credentials from `CHECKLY_API_KEY`). `defaultAccount` is `null` when no default is stored, and for API key credentials, which don't use it. -### Not Authenticated +### Not authenticated In a terminal or under an AI agent, `whoami` starts [`checkly login`](/cli/checkly-login) first when no credentials are stored. Elsewhere, such as in CI, it fails: @@ -83,7 +83,7 @@ npx checkly whoami Error: Run `npx checkly login` or set `CHECKLY_API_KEY` & `CHECKLY_ACCOUNT_ID` in your environment or .env file. ``` -## Related Commands +## Related commands - [`checkly login`](/cli/checkly-login) - Sign in to your Checkly account - [`checkly logout`](/cli/checkly-logout) - Sign out of your Checkly account diff --git a/cli/dependencies.mdx b/cli/dependencies.mdx index 117601709..1d9272142 100644 --- a/cli/dependencies.mdx +++ b/cli/dependencies.mdx @@ -1,7 +1,7 @@ --- title: Using npm packages and local dependencies description: "Use npm packages and local JavaScript or TypeScript files in your checks, and see how dependencies differ between Checkly runtimes and Playwright Check Suites." -sidebarTitle: npm & Local Dependencies +sidebarTitle: npm & local dependencies canonical: 'https://www.checklyhq.com/docs/cli/dependencies/' --- @@ -46,7 +46,7 @@ Playwright Check Suites do not use Checkly runtimes. Instead, Checkly installs y Use the `engine` field to override the JavaScript engine version for a Playwright Check Suite. `engine` does not select a Checkly runtime or a fixed package set. -## Local Dependencies +## Local dependencies Your checks can also import other JavaScript and TypeScript files as dependencies. This is useful for defining helper functions to be reused across multiple checks. diff --git a/cli/importing.mdx b/cli/importing.mdx index a04fa6a0c..b7899f445 100644 --- a/cli/importing.mdx +++ b/cli/importing.mdx @@ -1,7 +1,7 @@ --- -title: 'Importing existing Checks into your CLI project' +title: 'Importing existing checks into your CLI project' description: 'Learn how to import checks from the UI into the CLI' -sidebarTitle: 'Importing Resources From the UI' +sidebarTitle: 'Importing resources from the UI' canonical: 'https://www.checklyhq.com/docs/cli/importing/' --- diff --git a/cli/installation.mdx b/cli/installation.mdx index c85474d9d..8d4e57be5 100644 --- a/cli/installation.mdx +++ b/cli/installation.mdx @@ -103,7 +103,7 @@ Your checks only load with the `checkly` package your project installs, because Set `CHECKLY_NO_DELEGATION=1` to turn off the hand-off. Older global installs, and any install with the hand-off turned off, fail on projects that have their own `checkly` package with `Unable to create a construct ... outside a Checkly CLI project`. -## Using a Proxy Server +## Using a proxy server The CLI respects the common proxy environment variables for any outbound traffic, like running `npx checkly test` or `npx checkly deploy`. Because the CLI connects over HTTPS, set `HTTPS_PROXY` (or `ALL_PROXY`). `HTTP_PROXY` alone isn't used for these connections. Use `NO_PROXY` to bypass the proxy for specific hosts. diff --git a/cli/monitoring-pull-requests.mdx b/cli/monitoring-pull-requests.mdx index 8fe93f471..db4a57e41 100644 --- a/cli/monitoring-pull-requests.mdx +++ b/cli/monitoring-pull-requests.mdx @@ -1,6 +1,6 @@ --- title: 'Manage monitoring through pull requests' -sidebarTitle: 'Monitoring Through Pull Requests' +sidebarTitle: 'Monitoring through pull requests' description: 'Export monitoring from the UI, review and test a GitHub pull request, then deploy the merged code with the Checkly CLI.' canonical: 'https://www.checklyhq.com/docs/cli/monitoring-pull-requests/' --- diff --git a/cli/overview.mdx b/cli/overview.mdx index a413a84ab..3e1b6e401 100644 --- a/cli/overview.mdx +++ b/cli/overview.mdx @@ -59,7 +59,7 @@ Open up [your Checkly dashboard](https://app.checklyhq.com) and you should see y For a custom installation check out [our installation docs](/cli/installation/). -## Using Agents, AI IDEs and Copilots +## Using agents, AI IDEs and copilots Checkly is designed to work with Agents, AI IDEs, and Copilots. You can use your preferred provider to generate code for API checks, Browser checks and all other constructs. @@ -68,7 +68,7 @@ checks, Browser checks and all other constructs. Install Checkly Skills and let AI agents generate Checkly monitoring code for you. - + Connect desktop or sandboxed agents to live Checkly account data and actions. diff --git a/communicate/alerts/channels.mdx b/communicate/alerts/channels.mdx index 415a33cbe..048310383 100644 --- a/communicate/alerts/channels.mdx +++ b/communicate/alerts/channels.mdx @@ -11,7 +11,7 @@ Alert channels determine **how** alert notifications reach your team when checks ## Available alert channels -### Communication Platforms +### Communication platforms - [Email](/integrations/alerts/email) - [Slack](/integrations/alerts/slack) - [Discord](/integrations/alerts/discord) @@ -21,7 +21,7 @@ Alert channels determine **how** alert notifications reach your team when checks - [Microsoft Teams](/integrations/alerts/msteams) - [GitLab Alerts](/integrations/alerts/gitlab_alerts) -### Incident Management +### Incident management - [PagerDuty](/integrations/incident-management/pagerduty) - [Opsgenie](/integrations/incident-management/opsgenie) - [FireHydrant](/integrations/incident-management/firehydrant) @@ -32,12 +32,12 @@ Alert channels determine **how** alert notifications reach your team when checks - [Spike.sh](/integrations/incident-management/spike) - [StatusPage](/integrations/incident-management/statuspage) -### Custom Integrations +### Custom integrations - [Webhooks](/integrations/alerts/webhooks) ## Managing alert channels -### Channel Configuration Overview +### Channel configuration overview Configure channels with flexible subscription and filtering options: @@ -48,15 +48,15 @@ Configure channels with flexible subscription and filtering options: Choose your notification method and provide connection details - + Select which types of events should trigger notifications - + Choose which checks and check groups use this channel - + Verify the channel works correctly with test notifications diff --git a/communicate/alerts/configuration.mdx b/communicate/alerts/configuration.mdx index 1168fb88b..332219be8 100644 --- a/communicate/alerts/configuration.mdx +++ b/communicate/alerts/configuration.mdx @@ -1,5 +1,5 @@ --- -title: 'Alert Configuration' +title: 'Alert configuration' description: 'Complete guide to configuring alert settings, escalation strategies, retry mechanisms, and threshold alerting in Checkly for optimal incident response.' sidebarTitle: 'Configuration' canonical: 'https://www.checklyhq.com/docs/communicate/alerts/configuration/' @@ -9,24 +9,24 @@ canonical: 'https://www.checklyhq.com/docs/communicate/alerts/configuration/' Alert configuration controls **when** and **how often** you receive notifications when checks fail, degrade, or recover. Proper configuration minimizes alert fatigue while ensuring critical issues receive immediate attention. -## Configuration Hierarchy +## Configuration hierarchy Checkly provides a three-tier configuration system that allows for flexible alert management across your organization: - + - Applied to all checks unless overridden - Organization-wide defaults - Simplifies management at scale - Consistent baseline behavior - + - Override account defaults for checks within Groups - Team-based alert preferences - Service-specific requirements - Departmental escalation policies - + - Fine-tune specific check behavior - Handle special requirements - Debug and testing scenarios @@ -35,7 +35,7 @@ Checkly provides a three-tier configuration system that allows for flexible aler -### Configuration Inheritance +### Configuration inheritance Understanding how settings cascade through the hierarchy: 1. **Group-level settings** take highest precedence when the group has **Group override for alert settings** enabled. They replace the alert settings of every check in the group. @@ -50,9 +50,9 @@ Groups created with the public API `/v1/check-groups` endpoint or the CLI `Check Runs you [cancel](/concepts/cancellation) never trigger alerts. No failure, degraded, or recovery notification is sent for a cancelled run, regardless of the settings above. -## Alert Configuration +## Alert configuration -### Account-Level +### Account-level Configure organization-wide defaults that apply to all checks: @@ -69,14 +69,14 @@ Configure organization-wide defaults that apply to all checks: - Scalability: Easy to manage large numbers of checks -### Group-Level +### Group-level Configure alerts for teams and service categories: ![Group-level alert settings](/images/docs/images/alerting/alert-settings-group.png) -### Group Override +### Group override Configure how group settings interact with individual checks: **If checked, Group settings override individual check settings** @@ -93,7 +93,7 @@ Configure how group settings interact with individual checks: -### Check-Level +### Check-level Fine-tune alerting for specific checks with unique requirements: @@ -105,7 +105,7 @@ Fine-tune alerting for specific checks with unique requirements: Start with conservative alert settings and gradually tune based on your team's response patterns and service reliability characteristics. Too many alerts can be worse than too few. -## Escalation Configuration +## Escalation configuration **Monitoring as Code**: Learn more about [configuring escalation strategies for your Checkly constructs](/constructs/alert-escalation-policy). @@ -128,7 +128,7 @@ The escalation box allows you to decide when an alert should be triggered. We gi -### Run-Based Escalation +### Run-based escalation Get alerted when a check has failed a number of times consecutively. We call this a *Run Based* escalation. Note that failed checks retried from a different region are not considered "consecutive". @@ -160,7 +160,7 @@ from a different region are not considered "consecutive". -### Time-Based Escalation +### Time-based escalation We alert you when a check is still failing after a period of time, regardless of the amount of check runs that are failing. This option should mostly be used when checks are run very regularly, i.e. once every minute or five minutes. @@ -190,7 +190,7 @@ This option should mostly be used when checks are run very regularly, i.e. once - Network-dependent services -### Location-Based Escalation +### Location-based escalation This option can be selected in addition to the run or time-based escalation settings and only affect checks running in [parallel](/concepts/scheduling#parallel) with two or more locations selected. When enabled, alerts will only be sent when the specified percentage of locations are failing. Use this setting to reduce alert noise and fatigue for services that can handle being unavailable from some locations before action is required. @@ -215,7 +215,7 @@ When enabled, alerts will only be sent when the specified percentage of location - Accommodates CDN and geo-distributed services - Filters out single-location network problems -## Reminder Configuration +## Reminder configuration Configure follow-up notifications for unresolved incidents. @@ -236,19 +236,19 @@ Configure follow-up notifications for unresolved incidents. Checkly automatically manages reminder lifecycle: - + Primary alert sent to configured channels when escalation threshold is met - + Reminder countdown begins based on configuration - + Follow-up alerts sent at configured intervals - + All pending reminders cancelled when check recovers @@ -257,7 +257,7 @@ All pending reminders cancelled when check recovers When a check failure is resolved, we cancel any outstanding reminders so you don't get mixed signals. -## Muting and Temporary Controls +## Muting and temporary controls Toggling the "mute" checkbox on a check stops the sending of all alerts but keeps the check running. This is useful when your check might be flapping or showing other unpredictable behavior. Just mute the alerts but keep the check going while diff --git a/communicate/alerts/notification-log.mdx b/communicate/alerts/notification-log.mdx index 2c6909043..76b63ff90 100644 --- a/communicate/alerts/notification-log.mdx +++ b/communicate/alerts/notification-log.mdx @@ -1,7 +1,7 @@ --- -title: 'Alert Notification Log' +title: 'Alert notification log' description: "Browse and filter the Alert Notification Log to troubleshoot failed alert deliveries, inspect status codes, and see the exact configuration used per channel." -sidebarTitle: 'Notification Log' +sidebarTitle: 'Notification log' canonical: 'https://www.checklyhq.com/docs/communicate/alerts/notification-log/' --- diff --git a/communicate/alerts/overview.mdx b/communicate/alerts/overview.mdx index 9737c03a9..6fbe2e23c 100644 --- a/communicate/alerts/overview.mdx +++ b/communicate/alerts/overview.mdx @@ -1,5 +1,5 @@ --- -title: 'Alerting With Checkly' +title: 'Alerting with Checkly' description: 'Comprehensive alerting and retry strategies to minimize false positives and ensure reliable incident response when your checks fail or recover.' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/communicate/alerts/overview/' @@ -19,7 +19,7 @@ Checkly alerts you when your checks or monitors transition between states such a - Location-based failure filtering -## Alert Settings +## Alert settings The [alert settings screen](https://app.checklyhq.com/alerts/settings) gives you the options to tailor when, how and how often you want to be alerted when a check fails at the Account Level. This is also sometimes referred to as **threshold alerting**. For example: @@ -63,7 +63,7 @@ After adding the channels, you either **edit** or **delete** them, or change whi > If you are using [Terraform](/integrations/iac/terraform/overview) or the [CLI](/cli/overview), you will need to specify alert channel subscriptions _explicitly_ for each check / group. -## Alert States +## Alert states Sending out alert notifications like emails and Slack hooks depends on four factors: 1. The **alert state** of the check, e.g. "passing", "degraded" or "failing". @@ -76,7 +76,7 @@ We can even add a fifth factor: if the check is muted, no alerts are send out at > Note: Browser checks can be marked as degraded from your script with `markCheckAsDegraded`. See [degraded state for Browser checks](/detect/synthetic-monitoring/browser-checks/degraded). -### States & Transitions +### States & transitions The following table shows all states and their transitions. There are some exceptions to some of the more complex states, as the history or "vector" of the state transition influences how we alert. diff --git a/communicate/alerts/retries.mdx b/communicate/alerts/retries.mdx index 2b2240eba..64706ce49 100644 --- a/communicate/alerts/retries.mdx +++ b/communicate/alerts/retries.mdx @@ -1,6 +1,6 @@ --- -title: 'Alert Retries' +title: 'Alert retries' description: "Use retries to guard against flaky failures and alert fatigue, choosing between scheduled retry strategies for checks, check groups, and test sessions." sidebarTitle: 'Retries' canonical: 'https://www.checklyhq.com/docs/communicate/alerts/retries/' diff --git a/communicate/alerts/ssl-expiration.mdx b/communicate/alerts/ssl-expiration.mdx index d726a4332..e394761c2 100644 --- a/communicate/alerts/ssl-expiration.mdx +++ b/communicate/alerts/ssl-expiration.mdx @@ -1,7 +1,7 @@ --- -title: 'SSL Certificate Expiration Alerts' +title: 'SSL certificate expiration alerts' description: "Get alerted up to 30 days before an SSL certificate expires. Checkly checks your certificate hourly and can notify any alert channel at your chosen threshold." -sidebarTitle: 'SSL Alerts' +sidebarTitle: 'SSL alerts' canonical: 'https://www.checklyhq.com/docs/communicate/alerts/ssl-expiration/' --- diff --git a/communicate/dashboards/configuration.mdx b/communicate/dashboards/configuration.mdx index 1fd008f04..0411732a1 100644 --- a/communicate/dashboards/configuration.mdx +++ b/communicate/dashboards/configuration.mdx @@ -47,7 +47,7 @@ Once your dashboard is ready, you can share it with anyone using its URL. -## Basic Settings +## Basic settings - **Title:** Add a title like "ACME status dash". This is separate from your Checkly URL or custom domain. - **Description:** Add a clarifying text to explain to visitors what they are looking at. @@ -73,7 +73,7 @@ Typically, a company name works best, e.g. `acme.checkly-dashboards.com` /> -## Custom Domain +## Custom domain You can host your dashboard under your own domain. To make this work, you need to do two things: @@ -125,11 +125,11 @@ your DNS. You will see a notice similar to the one below. /> -## Access Control +## Access control By default, Checkly dashboards are public and visible to anyone who knows the URL. You can set a dashboard to private, limiting access to users with a password or Checkly account. -### Enabling Authentication +### Enabling authentication Private dashboards are only available on certain plans. For more details, see our [Pricing page](https://www.checklyhq.com/pricing). @@ -156,7 +156,7 @@ Checkly account login is only available to Enterprise customers. If visiting via the `https://[dashboardId].checkly-dashboards.com` domain, you can also select "Login with Checkly" and sign in with your existing Checkly account via any of the supported methods (i.e. Google, GitHub, Username and Password). This is an Enterprise-only feature. -## Look and Feel +## Look and feel - **Logo:** Display your company logo (or any image) on the top left side of your dashboard. - **Logo link:** Add a clickable destination URL for your logo. When visitors click the logo, they’ll be redirected to your specified website (typically your company homepage). diff --git a/communicate/dashboards/custom-css.mdx b/communicate/dashboards/custom-css.mdx index bbab25b41..194243bfc 100644 --- a/communicate/dashboards/custom-css.mdx +++ b/communicate/dashboards/custom-css.mdx @@ -32,7 +32,7 @@ Editing works like this. Custom CSS is only available on certain plans. For more details, see our [Pricing page](https://www.checklyhq.com/pricing). -### CSS Classes +### CSS classes The following table lists the CSS classes available for customizing your dashboard appearance: diff --git a/communicate/dashboards/incidents.mdx b/communicate/dashboards/incidents.mdx index a9e9af67b..2fa735e99 100644 --- a/communicate/dashboards/incidents.mdx +++ b/communicate/dashboards/incidents.mdx @@ -1,5 +1,5 @@ --- -title: 'Incident & Maintenance messages' +title: 'Incident & maintenance messages' description: "Communicate outages and planned maintenance to your audience by publishing incidents on a Checkly dashboard, turning it into a status page." sidebarTitle: 'Incidents' canonical: 'https://www.checklyhq.com/docs/communicate/dashboards/incidents/' diff --git a/communicate/overview.mdx b/communicate/overview.mdx index 8e4198f10..2a627306c 100644 --- a/communicate/overview.mdx +++ b/communicate/overview.mdx @@ -24,14 +24,14 @@ Create custom views of your monitoring data for teams and stakeholders Schedule and communicate planned maintenance to reduce alert noise -## Key Benefits +## Key benefits - **Multi-Channel Alerting** — Send notifications through email, SMS, Slack, webhooks, and more to ensure critical issues reach the right people. - **Transparent Status Communication** — Build trust with users through branded status pages that provide real-time system status and incident updates. - **Customizable dashboards** — Create tailored views of monitoring data that match your team's workflow and stakeholder needs. - **Intelligent Alert Management** — Reduce alert fatigue with escalation policies, maintenance windows, and smart notification routing. -## How It Works +## How it works @@ -63,12 +63,12 @@ Plan and communicate scheduled maintenance: -## Getting Started +## Getting started Ready to start communicating monitoring insights? Choose the approach that best fits your current needs: - + Begin with instant notifications for critical issues diff --git a/communicate/status-pages/custom-domain.mdx b/communicate/status-pages/custom-domain.mdx index d8a15f21b..56736faf7 100644 --- a/communicate/status-pages/custom-domain.mdx +++ b/communicate/status-pages/custom-domain.mdx @@ -1,7 +1,7 @@ --- title: "Custom domain" description: "Add a custom domain to your status page." -sidebarTitle: "Custom Domain" +sidebarTitle: "Custom domain" canonical: 'https://www.checklyhq.com/docs/communicate/status-pages/custom-domain/' --- diff --git a/communicate/status-pages/incidents.mdx b/communicate/status-pages/incidents.mdx index 8f232a06b..c936f2394 100644 --- a/communicate/status-pages/incidents.mdx +++ b/communicate/status-pages/incidents.mdx @@ -1,5 +1,5 @@ --- -title: 'Incident Management' +title: 'Incident management' description: 'Guide to creating, managing, and automating incidents on Checkly status pages including subscriber notifications and incident backfilling capabilities.' sidebarTitle: 'Incidents' canonical: 'https://www.checklyhq.com/docs/communicate/status-pages/incidents/' diff --git a/communicate/status-pages/password-protection.mdx b/communicate/status-pages/password-protection.mdx index 41349d43d..cab586331 100644 --- a/communicate/status-pages/password-protection.mdx +++ b/communicate/status-pages/password-protection.mdx @@ -1,7 +1,7 @@ --- -title: 'Password Protection' +title: 'Password protection' description: 'Restrict access to your status page so only authorized users can view your service health and incidents.' -sidebarTitle: 'Password Protection' +sidebarTitle: 'Password protection' canonical: 'https://www.checklyhq.com/docs/communicate/status-pages/password-protection/' --- diff --git a/communicate/status-pages/subscriber-notifications.mdx b/communicate/status-pages/subscriber-notifications.mdx index ffaa7e9d5..2c56f664b 100644 --- a/communicate/status-pages/subscriber-notifications.mdx +++ b/communicate/status-pages/subscriber-notifications.mdx @@ -1,7 +1,7 @@ --- -title: 'Subscriber Notifications' +title: 'Subscriber notifications' description: 'Configure subscriber notifications.' -sidebarTitle: 'Subscriber Notifications' +sidebarTitle: 'Subscriber notifications' canonical: 'https://www.checklyhq.com/docs/communicate/status-pages/subscriber-notifications/' --- diff --git a/comparisons/frameworks/moving-from-puppeteer-to-playwright.mdx b/comparisons/frameworks/moving-from-puppeteer-to-playwright.mdx index 199b345dd..bb99cbec3 100644 --- a/comparisons/frameworks/moving-from-puppeteer-to-playwright.mdx +++ b/comparisons/frameworks/moving-from-puppeteer-to-playwright.mdx @@ -1,5 +1,5 @@ --- -title: The Complete Guide to Migrating from Puppeteer to Playwright +title: The complete guide to migrating from Puppeteer to Playwright description: >- The switch from Puppeteer to Playwright is easy. But is it worth it? And how exactly does one migrate existing scripts from one tool to another? What are the required code-level changes, and what new features and approaches does the switch enable? author: Giovanni Rago @@ -284,7 +284,7 @@ The [Playwright Trace Viewer](https://playwright.dev/docs/trace-viewer) allows y ![playwright trace inspection](/images/guides/images/guides-migration-playwright-trace-viewer.png "Trace inspection with Trave Viewer") -### Test Generator +### Test generator You can use the [Playwright Test Generator](https://playwright.dev/docs/codegen) to record interactions in your browser. The output will be a full-fledged script ready to review and execute. @@ -304,7 +304,7 @@ This reveals additional information about the check execution, including: > [Browser checks](/detect/synthetic-monitoring/browser-checks/overview) run on Chromium or Chrome. To test in Firefox and WebKit, use [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview). -## Read More +## Read more
@@ -315,7 +315,7 @@ This reveals additional information about the check execution, including: Learn end-to-end monitoring with puppeteer and Playwright to test key website flows. - + OpenAPI and Swagger help users design and document APIs in a way that is readable from both humans and machines.
diff --git a/comparisons/frameworks/playwright-vs-cypress.mdx b/comparisons/frameworks/playwright-vs-cypress.mdx index 6328a67d4..ee9ce066b 100644 --- a/comparisons/frameworks/playwright-vs-cypress.mdx +++ b/comparisons/frameworks/playwright-vs-cypress.mdx @@ -25,7 +25,7 @@ This distinction is important when you compare these solutions, with Playwright Playwright is a tool focused on developer productivity with more robust built-in features, the ability to use async/await, built in parallelization, a much lighter weight in CI. Playwright is also less opinionated because it doesn’t have to be, you can use it however you want. Playwright can [monitor your APIs](https://www.checklyhq.com/learn/playwright/testing-apis/) just as well as it can your frontend web pages. Scraping content for a LLM model? Check! Have a nested app in an iframe you want to test? Go wild! *Three different browser sessions in the same chat instance? Sounds cool! Re-use your tests to monitor production? Absolutely.* -## Playwright Key Features +## Playwright key features - Supports multiple languages: JavaScript, TypeScript, Python, Java, C# - Create tests without writing any code with their test generator - Cross-platform testing (Windows, macOS, Linux) @@ -47,7 +47,7 @@ Titles have changed, entire departments have been lost to restructures, responsi The main areas where Cypress loses now used to be where they won; community trust, focus on developer productivity and rapid feature development. It’s not that those things don’t matter to Cypress any longer, but their attention has clearly shifted to solving enterprise problems. We can talk about [blocking npm packages](https://currents.dev/posts/v13-blocking), or [paywalling features](https://docs.cypress.io/guides/cloud/test-replay) that create parity with Playwright, but that would be a distraction. What really matters is velocity and practicality. A solution without parity to its top competitor, that requires the largest machines in CI and is still slower to run; is neither efficient nor practical unless you’re already using it. -## Cypress Key Features +## Cypress key features - JavaScript and TypeScript support (limited to web apps) - Native test runner with interactive GUI - Provides automatic waits, retry logic, and time travel debugging @@ -58,14 +58,14 @@ The main areas where Cypress loses now used to be where they won; community trus - Strong documentation - Direct access to browser internals, enabling state manipulation -## **Playwright vs Cypress: Architectural Differences** +## **Playwright vs Cypress: Architectural differences** -### **Overview of Architectures** +### **Overview of architectures** The architectural differences between Playwright and Cypress reflect distinct design philosophies and impact how each tool interacts with browsers and testing workflows. Playwright leverages the **Chrome DevTools Protocol (CDP)** to automate browsers directly, while Cypress runs within the browser’s execution loop via a custom Electron-based app. These design choices affect browser support, performance, parallelization, and test writing practices. -### **Playwright Architecture** +### **Playwright architecture** - **CDP-based**: Playwright interacts with browsers using the Chrome DevTools Protocol, which is natively supported by major browsers (Chromium, Firefox, WebKit). This allows it to control the browser externally without modifying the browser’s native execution loop. - **Separate Node Process**: Since Playwright runs outside the browser’s execution loop, it requires an external process (Node.js) to orchestrate tests. This design is more similar to Selenium’s WebDriver model, although Selenium 4 now also supports CDP. - **Language Flexibility**: Playwright’s architecture allows multi-language support, including JavaScript, TypeScript, Python, Java, and C#. It can also integrate with other frameworks like RobotFramework. @@ -75,7 +75,7 @@ The architectural differences between Playwright and Cypress reflect distinct de -### **Cypress Architecture** +### **Cypress architecture** - **Electron-based App**: Cypress runs as a native JavaScript app embedded within an Electron browser. This architecture means tests and Cypress’s custom library run **within the browser’s execution loop**, directly injecting code into the test browser. - **Tight Browser Integration**: This direct integration allows Cypress to manipulate browser behavior (e.g., automatic waits and retries) but limits support to JavaScript and transpiled languages. It also complicates browser support—Safari, for instance, is not currently supported. - **Single Process Control**: Cypress uses a combination of Node.js and its custom library for test execution, but the bulk of the test control happens in the browser, limiting flexibility compared to Playwright’s external Node process. @@ -85,7 +85,7 @@ The architectural differences between Playwright and Cypress reflect distinct de -### **Impact of Architectural Differences** +### **Impact of architectural differences** 1. **Browser and Platform Support** - Playwright supports all modern browsers (Chromium, Firefox, WebKit) and can run on multiple operating systems with little configuration (sidenote: Checkly Browser checks run on Chromium, the default, or Chrome. [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) can also run Firefox and WebKit projects. [Read more about supported browsers](/detect/synthetic-monitoring/browser-checks/overview#what-are-browser-checks)). @@ -108,11 +108,11 @@ The architectural differences between Playwright and Cypress reflect distinct de -### **Which Architecture Fits Your Needs?** +### **Which architecture fits your needs?** - **Choose Playwright** if you need cross-browser support, parallelism, and multi-language flexibility. Its architecture is more scalable for complex, multi-layered applications that demand realistic, real-world testing. - **Choose Cypress** if your focus is on quick feedback during frontend development, and you prefer a highly interactive testing experience embedded within the browser. Cypress is ideal for teams already working in a JavaScript/TypeScript environment with limited browser requirements. -## Playwright vs Cypress: Key Differences Comparison +## Playwright vs Cypress: Key differences comparison | Feature | Playwright | Cypress | |------------------------|--------------------------------------------|--------------------------------------| @@ -129,10 +129,10 @@ The architectural differences between Playwright and Cypress reflect distinct de -## Playwright vs Cypress Examples +## Playwright vs Cypress examples At the highest level, Playwright and Cypress tests look very similar when writing a basic tests. Differences only really become visible when you make two asynchronous requests with assertions. -### Playwright Example +### Playwright example ```ts import { test, expect } from '@playwright/test' @@ -149,7 +149,7 @@ test('Multiple API Requests Test', async ({ request }) => { Playwright uses the standard `await` syntax used in the rest of Node.js. -### Cypress Example +### Cypress example ```js describe('Multiple API Requests Test', () => { it('should return valid status codes for two API requests', () => { @@ -171,31 +171,31 @@ Further, Cypress asynchrony may not act as expected if we're used to asynchrony -## Playwright vs Cypress: Pros & Cons +## Playwright vs Cypress: Pros & cons -### Playwright Pros +### Playwright pros - Supports more browsers, including Firefox and Safari/WebKit - Suitable for complex web apps with [API](https://www.checklyhq.com/learn/playwright/testing-apis/), UI, and [visual testing](/detect/synthetic-monitoring/browser-checks/visual-regressions) combined - Superior parallelism and scalability for larger test suites - Works on multiple platforms -### Playwright Cons +### Playwright cons - More complex setup for beginners - Larger learning curve compared to Cypress - Requires deeper configuration to utilize full power -### Cypress Pros +### Cypress pros - User-friendly interface, easy for beginners - GUI with real-time updates during tests - Great for frontend testing -### Cypress Cons +### Cypress cons - Limited to Chromium-based browsers - Struggles with large-scale parallelism - No native support for multi-language tests -## Playwright vs Cypress: Which Solution is Better for You? +## Playwright vs Cypress: Which solution is better for you? - Choose Playwright if you need to test across multiple browsers, require advanced parallelism, or need to include API and component testing in your workflow. It’s better suited for complex, large-scale projects with multiple stakeholders. If you've been told 'that's hard to test with Cypress' there's no doubt you can do it in Playwright. - Choose Cypress if your focus is frontend testing, or you are working on web apps that run primarily in Chrome/Edge. Cypress is more user-friendly for teams without extensive testing experience and offers quick startup time with fewer configurations. diff --git a/comparisons/frameworks/playwright-vs-selenium.mdx b/comparisons/frameworks/playwright-vs-selenium.mdx index 847a5c413..285393a2b 100644 --- a/comparisons/frameworks/playwright-vs-selenium.mdx +++ b/comparisons/frameworks/playwright-vs-selenium.mdx @@ -1,5 +1,5 @@ --- -title: Playwright vs Selenium - Detailed Comparison for 2026 +title: Playwright vs Selenium - Detailed comparison for 2026 subTitle: Key features, and pros & cons of each framework description: Compare Playwright and Selenium by language and browser support, waiting, test tooling, debugging, and mobile testing, with side-by-side examples. date: 2026-09-27 diff --git a/comparisons/monitoring-tools/overview.mdx b/comparisons/monitoring-tools/overview.mdx index 10e3a42d6..717ee764d 100644 --- a/comparisons/monitoring-tools/overview.mdx +++ b/comparisons/monitoring-tools/overview.mdx @@ -1,14 +1,14 @@ --- -title: "Monitoring Tools Overview" +title: "Monitoring tools overview" description: "Compare Checkly with popular monitoring and APM solutions" canonical: 'https://www.checklyhq.com/docs/comparisons/monitoring-tools/overview/' --- -# Monitoring Tools Overview +# Monitoring tools overview This section provides detailed comparisons between Checkly and popular monitoring and application performance management (APM) tools. Learn how Checkly fits into your monitoring stack. -## Available Comparisons +## Available comparisons Coming soon - detailed comparisons with popular monitoring tools including: @@ -23,7 +23,7 @@ Coming soon - detailed comparisons with popular monitoring tools including: - Grafana - Prometheus -## Why Compare Monitoring Tools? +## Why compare monitoring tools? Understanding how Checkly compares to other monitoring solutions helps you: diff --git a/comparisons/observability-tools/overview.mdx b/comparisons/observability-tools/overview.mdx index 3c5cf7eed..db2e8cee1 100644 --- a/comparisons/observability-tools/overview.mdx +++ b/comparisons/observability-tools/overview.mdx @@ -1,14 +1,14 @@ --- -title: "Observability Tools Overview" +title: "Observability tools overview" description: "Compare Checkly with popular observability and tracing platforms" canonical: 'https://www.checklyhq.com/docs/comparisons/observability-tools/overview/' --- -# Observability Tools Overview +# Observability tools overview This section provides detailed comparisons between Checkly and popular observability platforms. Understand how Checkly's synthetic monitoring complements your observability stack. -## Available Comparisons +## Available comparisons Coming soon - detailed comparisons with popular observability tools including: @@ -23,7 +23,7 @@ Coming soon - detailed comparisons with popular observability tools including: - Splunk - Sumo Logic -## Why Compare Observability Tools? +## Why compare observability tools? Understanding how Checkly fits with observability platforms helps you: diff --git a/comparisons/overview.mdx b/comparisons/overview.mdx index 7e39fa97c..d8ab8e77a 100644 --- a/comparisons/overview.mdx +++ b/comparisons/overview.mdx @@ -1,5 +1,5 @@ --- -title: 'Comparisons Overview' +title: 'Comparisons overview' description: 'Display inline code and code blocks' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/comparisons/overview/' diff --git a/comparisons/status-pages/overview.mdx b/comparisons/status-pages/overview.mdx index 7ce61e0ea..c2ebbc550 100644 --- a/comparisons/status-pages/overview.mdx +++ b/comparisons/status-pages/overview.mdx @@ -8,7 +8,7 @@ canonical: 'https://www.checklyhq.com/docs/comparisons/status-pages/overview/' This section provides detailed comparisons between Checkly's status page functionality and dedicated status page providers. Learn how to choose the right status page solution for your needs. -## Available Comparisons +## Available comparisons Coming soon - detailed comparisons with popular status page services including: diff --git a/comparisons/testing-tools/overview.mdx b/comparisons/testing-tools/overview.mdx index 1cebce36f..6b7d5935c 100644 --- a/comparisons/testing-tools/overview.mdx +++ b/comparisons/testing-tools/overview.mdx @@ -1,14 +1,14 @@ --- -title: "Testing Tools Overview" +title: "Testing tools overview" description: "Compare Checkly with popular testing frameworks and tools" canonical: 'https://www.checklyhq.com/docs/comparisons/testing-tools/overview/' --- -# Testing Tools Overview +# Testing tools overview This section provides detailed comparisons between Checkly and popular testing tools and frameworks. Understand how Checkly complements or replaces different testing approaches. -## Available Comparisons +## Available comparisons Coming soon - detailed comparisons with popular testing tools including: @@ -23,7 +23,7 @@ Coming soon - detailed comparisons with popular testing tools including: - Postman - Insomnia -## Why Compare Testing Tools? +## Why compare testing tools? Understanding how Checkly compares to other testing tools helps you: diff --git a/concepts/checks.mdx b/concepts/checks.mdx index b1b772eb2..16ec76114 100644 --- a/concepts/checks.mdx +++ b/concepts/checks.mdx @@ -1,5 +1,5 @@ --- -title: 'What are Checks?' +title: 'What are checks?' description: 'Checks are automated tests that monitor your application on a schedule.' sidebarTitle: 'Checks' canonical: 'https://www.checklyhq.com/docs/concepts/checks/' @@ -10,7 +10,7 @@ Checks experience your application the same way real users would—clicking butt This lets you catch issues early, maintain confidence in your deployments, and ensure your critical systems are working as expected. -## Types of Checks +## Types of checks Checkly's flexible offering includes several types of Checks, each designed for different levels of complexity and testing scenarios: @@ -110,7 +110,7 @@ Run entire Playwright test suites and projects as production monitors without co Checkly also offers [SSL monitors](/detect/uptime-monitoring/ssl-monitors/overview) for certificate validity and expiry, [gRPC monitors](/detect/uptime-monitoring/grpc-monitors/overview), and [Traceroute monitors](/detect/uptime-monitoring/traceroute-monitors/overview). -## How Checks Execute +## How checks execute ![monitoring and alerting pipeline](/images/docs/images/monitoring/monitoring-alerting-pipeline.svg) @@ -124,7 +124,7 @@ Teardown scripts are run *before* any assertions are validated 7. Alerts are sent out in requested channels when the sequence is complete. It's considered complete when the check run was successful or the final attempt was executed. We will send alerts only if the final attempt has failed and your [alert escalation settings](/communicate/alerts/configuration#escalation-configuration) are met (no alerts sent for the initial attempts) -## Code-First Philosophy +## Code-first philosophy All check types at Checkly have a Construct or API endpoint - meaning you can use Checkly to bring your monitoring process right into your repository. We call this [Monitoring as Code](/concepts/monitoring-as-code). diff --git a/concepts/locations.mdx b/concepts/locations.mdx index 8a685b5c4..83ade5d10 100644 --- a/concepts/locations.mdx +++ b/concepts/locations.mdx @@ -7,7 +7,7 @@ canonical: 'https://www.checklyhq.com/docs/concepts/locations/' **Locations** represent the global vantage points from which Checkly tests and monitors your applications. You can configure your tests and checks to run from an ever growing amount of global locations. Leveraging global infrastructure allows us to measure what the user experience is in different parts of the world. -## What are Locations? +## What are locations? Think of **Locations** as your monitoring outposts distributed around the globe. Each Location represents a geographic point where Checkly can execute your Checks, simulating the experience of users in that region. This geographic distribution is crucial because it reveals how your application performs for users regardless of where they're accessing it from. You can select one or more data center locations to run your checks from. On the Hobby and Starter plans, you can select up to 3 locations from North Virginia, North California, Frankfurt, London, Singapore and Sydney. We advise to always select at least 2 locations. There are two reasons for this: @@ -15,7 +15,7 @@ You can select one or more data center locations to run your checks from. On the * Retrying: if your check fails, we will execute its retry strategy where you have the option to retry from a different location. Checks running in parallel always retry from the same location. -## Public Locations +## Public locations You can configure your run checks to run from an ever growing amount of global locations. Leveraging global infrastructure allows us to measure what the user experience is in different parts of the world. @@ -41,5 +41,5 @@ Bahrain (me-south-1) is no longer available. Checks don't run there, even if it' **Private locations** extend this concept to your own infrastructure. A **private location** is a monitoring location that you manage by simply deploying a lightweight Checkly Agent. Running a check from a **private location** allows you to monitor internal systems and test the performance and reliability of applications and APIs that are only accessible from within your network. > Learn more about [private locations](/platform/private-locations/overview) to monitor your private and segregated applications and APIs. -## Locations as User Experience Proxies +## Locations as user experience proxies Ultimately, Locations are about empathy for your users. They ensure that your monitoring perspective matches your users' reality. A user in Tokyo may have a vastly different experience than someone in New York, and **Locations** help you understand and optimize for these differences. They transform monitoring from a single-perspective activity into a truly global understanding of application performance and reliability. \ No newline at end of file diff --git a/concepts/metrics.mdx b/concepts/metrics.mdx index e6637efad..92e75b768 100644 --- a/concepts/metrics.mdx +++ b/concepts/metrics.mdx @@ -7,11 +7,11 @@ canonical: 'https://www.checklyhq.com/docs/concepts/metrics/' Checkly tracks a comprehensive set of metrics across all check types to provide insights into the performance, reliability, and user experience of your applications and services. This page explains common metrics, what they measure, and which check types support them. -## Response Time Metrics +## Response time metrics Response time metrics measure how quickly your services respond to requests, providing crucial insights into performance and user experience. -### Average Response Time +### Average response time **What it measures:** The arithmetic mean response time across all check executions within the selected time period. @@ -25,7 +25,7 @@ Response time metrics measure how quickly your services respond to requests, pro - Setting SLA thresholds
-### 95th Percentile Response Time (P95) +### 95th percentile response time (P95) **What it measures:** The response time value below which 95% of all requests fall. This metric filters out the slowest 5% of requests to give you a more realistic view of typical user experience. @@ -39,7 +39,7 @@ Response time metrics measure how quickly your services respond to requests, pro - Identifying performance outliers -### 99th Percentile Response Time (P99) +### 99th percentile response time (P99) **What it measures:** The response time value below which 99% of all requests fall. This metric helps identify the worst-case performance experienced by users. @@ -52,7 +52,7 @@ Response time metrics measure how quickly your services respond to requests, pro - Optimizing for the most demanding scenarios -### Median Response Time (P50) +### Median response time (P50) **What it measures:** The middle value of all response times when sorted from fastest to slowest. Half of all requests complete faster than this time, and half complete slower. @@ -66,7 +66,7 @@ Response time metrics measure how quickly your services respond to requests, pro - Performance trend analysis -### Minimum Response Time +### Minimum response time **What it measures:** The fastest response time recorded during the selected time period. @@ -80,7 +80,7 @@ Response time metrics measure how quickly your services respond to requests, pro - Network latency analysis -### Maximum Response Time +### Maximum response time **What it measures:** The slowest response time recorded during the selected time period. @@ -94,11 +94,11 @@ Response time metrics measure how quickly your services respond to requests, pro - Performance regression detection -## Success Rate Metrics +## Success rate metrics Success rate metrics measure the reliability and availability of your services. -### Success Rate +### Success rate **What it measures:** The percentage of check executions that completed successfully according to the defined success criteria (e.g., HTTP 2xx status codes, successful script execution). @@ -112,7 +112,7 @@ Success rate metrics measure the reliability and availability of your services. - Alerting on service degradation -## Web Vitals (Browser-Specific) +## Web Vitals (browser-specific) Core Web Vitals are a set of metrics defined by Google that measure real-world user experience for loading performance, interactivity, and visual stability. @@ -170,11 +170,11 @@ Playwright Check Suites also collect Web Vitals (LCP, CLS, INP, FCP, TTFB and TB **Unit:** Milliseconds **Available for:** Browser checks only -## ICMP-Specific Metrics +## ICMP-specific metrics These metrics are specific to ICMP monitors, which verify host reachability and measure network performance using ICMP Echo Requests (pings). -### Average Ping Latency +### Average ping latency **What it measures:** The average round-trip time (RTT) across all received ICMP Echo Reply packets within a check run. @@ -186,7 +186,7 @@ These metrics are specific to ICMP monitors, which verify host reachability and - Comparing latency across regions -### Minimum Ping Latency +### Minimum ping latency **What it measures:** The fastest round-trip time recorded across all received packets within a check run. @@ -196,7 +196,7 @@ These metrics are specific to ICMP monitors, which verify host reachability and - Understanding best-case network performance -### Maximum Ping Latency +### Maximum ping latency **What it measures:** The slowest round-trip time recorded across all received packets within a check run. @@ -207,7 +207,7 @@ These metrics are specific to ICMP monitors, which verify host reachability and - Setting timeout and alerting thresholds -### Ping Latency Standard Deviation +### Ping latency standard deviation **What it measures:** The variability of round-trip times across all received packets within a check run. Higher values indicate less consistent network performance (jitter). @@ -217,7 +217,7 @@ These metrics are specific to ICMP monitors, which verify host reachability and - Measuring network stability and jitter -### Packet Loss +### Packet loss **What it measures:** The percentage of ICMP Echo Request packets that did not receive a reply. @@ -228,7 +228,7 @@ These metrics are specific to ICMP monitors, which verify host reachability and - Triggering degraded or failed states via [packet loss thresholds](/detect/uptime-monitoring/icmp-monitors/configuration#packet-loss-limits) -### P95 Ping Latency +### P95 ping latency **What it measures:** The 95th percentile of average ping latency across check runs within the selected time period. @@ -239,7 +239,7 @@ These metrics are specific to ICMP monitors, which verify host reachability and - Filtering out outlier spikes for a realistic performance view -### P95 Packet Loss +### P95 packet loss **What it measures:** The 95th percentile of packet loss across check runs within the selected time period. @@ -250,9 +250,9 @@ These metrics are specific to ICMP monitors, which verify host reachability and - Identifying persistent vs. intermittent packet loss -## Additional Metrics by Check Type +## Additional metrics by check type -### TCP Connection Time +### TCP connection time **What it measures:** The time required to establish a TCP connection to the target host and port. @@ -266,7 +266,7 @@ These metrics are specific to ICMP monitors, which verify host reachability and - Infrastructure health monitoring -### DNS Resolution Time +### DNS resolution time **What it measures:** The time required to resolve the hostname to an IP address via DNS lookup. @@ -280,7 +280,7 @@ These metrics are specific to ICMP monitors, which verify host reachability and - Geographic performance analysis -### SSL Handshake Time +### SSL handshake time **What it measures:** The time required to complete the SSL/TLS handshake process for secure connections. diff --git a/concepts/monitoring-as-code.mdx b/concepts/monitoring-as-code.mdx index 828fa0057..01d6dcd54 100644 --- a/concepts/monitoring-as-code.mdx +++ b/concepts/monitoring-as-code.mdx @@ -14,7 +14,7 @@ With MaC, you can define, version, and maintain your monitoring infrastructure a To get started with Monitoring as Code, see our [Constructs](/constructs/overview) section or [CLI](/cli/overview) section. -## Core Principles of Monitoring as Code +## Core principles of Monitoring as Code **Declarative Configuration**: Define your monitors, alerts, and status pages, and more in code files using structured formats (JSON, YAML, TypeScript). diff --git a/concepts/overview.mdx b/concepts/overview.mdx index a950db97a..9b1bae0dd 100644 --- a/concepts/overview.mdx +++ b/concepts/overview.mdx @@ -1,5 +1,5 @@ --- -title: 'Core Concepts Overview' +title: 'Core concepts overview' description: 'Learn about the core concepts of Checkly' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/concepts/overview/' @@ -7,18 +7,18 @@ canonical: 'https://www.checklyhq.com/docs/concepts/overview/' Organization in Checkly refers to how you structure and manage your monitoring setup through Groups and hierarchical organization. Groups allow you to organize your checks and centralize settings like base URLs, headers, variables and other properties a collection of checks can share. -## What is Organization? +## What is organization? Think of Organization as the filing system for your monitoring infrastructure. Just as you wouldn't want all your code files in a single directory, you don't want hundreds of Checks scattered without structure. Organization provides the frameworks—primarily through Groups—to create logical boundaries, share common configurations, and manage complexity as your monitoring grows. Good Organization transforms monitoring from a collection of individual tests into a coherent system that reflects your application architecture and team responsibilities. It makes monitoring more maintainable, discoverable, and aligned with how your teams actually work. -## Groups as Organizational Units +## Groups as organizational units Example use cases for groups are organizing your checks around different applications, teams, or functional areas. Use the CheckGroupV2 construct to organize your Checks into groups. This comes with the following benefits: Your Checks are organized in a folder in the Checkly web UI. You can trigger all Checks in a group from the web UI and via a command line trigger. Groups serve multiple organizational purposes simultaneously. They act as configuration templates, execution units, and logical containers. Some group settings combine with the check's own settings: group tags are added to the check's tags, the group runtime applies only when the check has none set, and a check is deactivated or muted when either the check or its group is. Group alert settings replace the check's alert settings when the group defines them. -## Flexible Configuration Inheritance +## Flexible configuration inheritance For groups created in the Checkly UI, with the public API `/v2/check-groups` endpoint or with the CLI `CheckGroupV2` construct, group-level overrides for scheduling strategy, locations, retries and alert settings are optional. By default, these Groups act like folders, with zero config shared, giving you more flexibility. Groups created with the `/v1/check-groups` endpoint or the CLI `CheckGroupV1` construct always apply their own alert, retry and scheduling settings. This evolution allows Groups to serve different organizational needs—they can be strict configuration templates that enforce consistency, or they can be loose organizational containers that simply provide structure without imposing shared settings. -## Scaling Through Organization +## Scaling through organization As you can see, groups in their current incarnation are mostly handy configuration buckets for common properties. In the future we will expand the group features to make them smarter. Effective Organization becomes more critical as teams and applications grow. It enables delegation of monitoring responsibilities, clear ownership boundaries, and the ability to manage monitoring complexity through logical decomposition. Organization ensures that monitoring scales with your infrastructure rather than becoming a maintenance burden. \ No newline at end of file diff --git a/concepts/results.mdx b/concepts/results.mdx index 914d2617c..088a6add5 100644 --- a/concepts/results.mdx +++ b/concepts/results.mdx @@ -15,7 +15,7 @@ Each time a Check executes—whether it's testing an API endpoint, clicking thro Playwright Check Suite runs can also be [cancelled](/concepts/cancellation) while they are in progress. Cancelled results are excluded from availability and performance metrics. -## Understanding Result Data +## Understanding result data You can select any check on the main Checkly dashboard to get an overview of the results they have produced so far. diff --git a/concepts/scheduling.mdx b/concepts/scheduling.mdx index 958402d3f..0ce6893ff 100644 --- a/concepts/scheduling.mdx +++ b/concepts/scheduling.mdx @@ -5,7 +5,7 @@ sidebarTitle: 'Scheduling' canonical: 'https://www.checklyhq.com/docs/concepts/scheduling/' --- -## Scheduling Strategies +## Scheduling strategies Checkly provides two scheduling strategies for running checks: **Round-robin** or **Parallel scheduling**. To select a scheduling strategy go to ‘Scheduling and locations’ when creating or editing a check. @@ -23,9 +23,9 @@ 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. -## Best Practices +## Best practices -### Frequency Guidelines by Service Criticality +### Frequency guidelines by service criticality **Critical Production Services:** @@ -44,7 +44,7 @@ Use **Parallel Scheduling** to reduce detection times for regional outages and r - **Examples**: Documentation sites, internal tools, dev environments - **Rationale**: Monitor availability without excessive overhead -### Frequency Guidelines by Service Type +### Frequency guidelines by service type **E-commerce Sites:** - **Homepage**: Every 1 minute (critical for revenue) @@ -64,7 +64,7 @@ Use **Parallel Scheduling** to reduce detection times for regional outages and r - **Backup Systems**: Every 15 minutes -### Resource Impact Considerations +### Resource impact considerations **Server Load Management:** - Higher frequency = more requests to your servers @@ -77,19 +77,19 @@ Use **Parallel Scheduling** to reduce detection times for regional outages and r - Balance detection speed with budget constraints - Review and adjust frequencies based on actual value -### Initial Configuration +### Initial configuration 1. **Start conservative** with 5-10 minute intervals 2. **Monitor high-impact services more frequently** 3. **Adjust based on actual failure patterns** 4. **Consider business hours and user activity** -### Ongoing Optimization +### Ongoing optimization - **Review frequency effectiveness** quarterly - **Adjust during high-risk periods** (deployments, traffic spikes) - **Balance detection speed with cost constraints** - **Use data-driven decisions** based on incident history -### Documentation and Communication +### Documentation and communication - **Document scheduling rationale** for different services - **Communicate frequency changes** to relevant teams - **Track scheduling effectiveness** over time diff --git a/constructs/agentic-check.mdx b/constructs/agentic-check.mdx index 26c6c8f5e..11d6d6cdf 100644 --- a/constructs/agentic-check.mdx +++ b/constructs/agentic-check.mdx @@ -1,5 +1,5 @@ --- -title: 'Agentic Check Construct' +title: 'Agentic Check construct' description: 'Review legacy Agentic Check constructs and migrate active checks before December 1, 2026.' sidebarTitle: 'Agentic Check' canonical: 'https://www.checklyhq.com/docs/constructs/agentic-check/' @@ -74,7 +74,7 @@ The Agentic Check configuration consists of Agentic-specific options and a subse | `agentRuntime` | `object` | No | `{ skills: [] }` | Extra runtime skills the agent is allowed to use during execution. | - + | Property | Type | Required | Default | Description | |----------|------|----------|---------|-------------| diff --git a/constructs/alert-escalation-policy.mdx b/constructs/alert-escalation-policy.mdx index 78cd85731..5f45a5ff1 100644 --- a/constructs/alert-escalation-policy.mdx +++ b/constructs/alert-escalation-policy.mdx @@ -1,7 +1,7 @@ --- -title: 'Alert Escalation Policy Construct' +title: 'Alert escalation policy construct' description: 'Learn how to configure alert escalation policies with the Checkly CLI.' -sidebarTitle: 'Alert Escalation Policy' +sidebarTitle: 'Alert escalation policy' canonical: 'https://www.checklyhq.com/docs/constructs/alert-escalation-policy/' --- @@ -58,7 +58,7 @@ Configure your alert escalation policies using the `AlertEscalationBuilder`, whi | `runBasedEscalation()` | Alert after N consecutive failed runs | `(failedRuns, reminders, parallelRunFailureThreshold)` | | `timeBasedEscalation()` | Alert after N minutes of continuous failures | `(minutesFailing, reminders, parallelRunFailureThreshold)` | -## Alert Escalation Builder Methods +## Alert escalation builder methods Creates an alert escalation policy that triggers after a specified number of consecutive failed runs. diff --git a/constructs/api-check.mdx b/constructs/api-check.mdx index 93211a761..55a2f75eb 100644 --- a/constructs/api-check.mdx +++ b/constructs/api-check.mdx @@ -90,7 +90,7 @@ The API check configuration consists of specific API check options and inherited | `tearDownScript` | `object` | ❌ | - | Script to run after the API check execution | - + | Property | Type | Required | Default | Description | |----------|------|----------|---------|-------------| @@ -116,7 +116,7 @@ The API check configuration consists of specific API check options and inherited -### `ApiCheck` Options +### `ApiCheck` options The HTTP request configuration that defines the API endpoint to monitor. This is the core component of any API check. @@ -441,7 +441,7 @@ You must provide either `entrypoint` or `content`, but not both. **Use cases**: Test data cleanup, resource cleanup, logging and reporting. -### `ApiCheck` Assertions +### `ApiCheck` assertions To define `assertions` for the `request` of an `ApiCheck` you should use the `AssertionBuilder`. The following sources are available for API check assertions: @@ -479,7 +479,7 @@ AssertionBuilder.headers('strict-transport-security', 'max-age=(\\d+)').greaterT { source: 'HEADERS', regex: 'max-age=(\d+)', property: 'strict-transport-security', comparison: 'GREATER_THAN', target: '10000' } ``` -### General Check Options +### General check options diff --git a/constructs/browser-check.mdx b/constructs/browser-check.mdx index 3851616d0..1245e512f 100644 --- a/constructs/browser-check.mdx +++ b/constructs/browser-check.mdx @@ -78,7 +78,7 @@ The Browser check configuration consists of specific Browser check options and i | `playwrightConfig` | `object` | ❌ | - | Playwright config for this check, with the same keys as `playwright.config.ts` (for example `use.viewport`) | - + | Property | Type | Required | Default | Description | |----------|------|----------|---------|-------------| @@ -195,7 +195,7 @@ new BrowserCheck("e2e-purchase", { **Use cases**: E2E testing, user journey validation, performance testing, visual regression testing. -### General Check Options +### General check options Friendly name for your Browser check that will be displayed in the Checkly dashboard and used in notifications. diff --git a/constructs/check-group-v2.mdx b/constructs/check-group-v2.mdx index 8cedd5afb..11183fda8 100644 --- a/constructs/check-group-v2.mdx +++ b/constructs/check-group-v2.mdx @@ -1,5 +1,5 @@ --- -title: 'CheckGroupV2 Construct' +title: 'CheckGroupV2 construct' description: 'Learn how to configure check groups with the Checkly CLI.' sidebarTitle: 'Check group V2' canonical: 'https://www.checklyhq.com/docs/constructs/check-group-v2/' @@ -11,7 +11,7 @@ Learn more about check groups in [the Groups overview](/platform/groups). Use `CheckGroupV2` to organize your checks into logical groups. This provides better organization, shared configuration, and group-level controls for your monitoring setup. -## `CheckGroupV2` Structure +## `CheckGroupV2` structure @@ -104,7 +104,7 @@ new ApiCheck("api-check-1", { If you want the group's alert settings to override check-level alert settings, you must set the [`alertEscalationPolicy`](/constructs/check-group-v2#param-alert-escalation-policy). Otherwise, the alert settings of individual checks will be used, even if `alertChannels` is defined in your group. -### Group Options +### Group options Friendly name for your check group that will be displayed in the Checkly dashboard and used for organization. @@ -274,7 +274,7 @@ When referencing existing groups with `fromId()`, note: If you need these features, you can either import the group using the [Checkly import feature](/cli/checkly-import) (e.g. `npx checkly import check-group:123`) or define a new group directly in your project. -## Shared Settings in Groups with Different Monitor Types +## Shared settings in groups with different monitor types With `CheckGroupV2` you can group uptime monitors (e.g. URL, TCP, DNS) and synthetic checks (e.g. API, Multistep, Playwright Check Suites). Depending on your plan type, some [group settings](/constructs/check-group-v2#configuration) (such as parallel runs or advanced retry strategies) may not be supported across both monitor types. @@ -286,7 +286,7 @@ See [Mixing Checks and Monitors in a Group](/platform/groups/#mixing-checks-and- ## Examples - + {/* typecheck-wrap: CheckGroupV2 */} ```ts const apiGroup = new CheckGroupV2("api-monitoring-group", { @@ -323,7 +323,7 @@ See [Mixing Checks and Monitors in a Group](/platform/groups/#mixing-checks-and- ``` - + {/* typecheck-wrap: CheckGroupV2 */} ```ts const servicesGroup = new CheckGroupV2("services-monitoring", { @@ -372,7 +372,7 @@ See [Mixing Checks and Monitors in a Group](/platform/groups/#mixing-checks-and- ``` - + {/* typecheck-wrap: CheckGroupV2 */} ```ts const regionalGroup = new CheckGroupV2("us-east-monitoring", { diff --git a/constructs/check-group.mdx b/constructs/check-group.mdx index e55250fbe..a2bf7d9a6 100644 --- a/constructs/check-group.mdx +++ b/constructs/check-group.mdx @@ -1,5 +1,5 @@ --- -title: 'CheckGroup Construct' +title: 'CheckGroup construct' description: 'Learn how to configure check groups with the Checkly CLI.' sidebarTitle: 'Check group (deprecated)' canonical: 'https://www.checklyhq.com/docs/constructs/check-group/' @@ -105,7 +105,7 @@ new ApiCheck("api-check-1", { | `browserChecks` | `object` | ❌ | - | Settings for Browser checks in the group | | `multiStepChecks` | `object` | ❌ | - | Settings for Multistep checks in the group | -### Group Options +### Group options Friendly name for your check group that will be displayed in the Checkly dashboard and used for organization. @@ -232,7 +232,7 @@ const group = new CheckGroup("api-multistep-group", { ## Examples - + {/* typecheck-wrap: CheckGroup */} ```ts const apiGroup = new CheckGroup("api-monitoring-group", { @@ -268,7 +268,7 @@ const group = new CheckGroup("api-multistep-group", { ``` - + {/* typecheck-wrap: CheckGroup */} ```ts const servicesGroup = new CheckGroup("services-monitoring", { @@ -316,7 +316,7 @@ const group = new CheckGroup("api-multistep-group", { ``` - + {/* typecheck-wrap: CheckGroup */} ```ts const regionalGroup = new CheckGroup("us-east-monitoring", { diff --git a/constructs/dashboard.mdx b/constructs/dashboard.mdx index d51a154fe..d1e25a03e 100644 --- a/constructs/dashboard.mdx +++ b/constructs/dashboard.mdx @@ -1,5 +1,5 @@ --- -title: 'Dashboard Construct' +title: 'Dashboard construct' description: 'Learn how to configure dashboards with the Checkly CLI.' sidebarTitle: 'Dashboard' canonical: 'https://www.checklyhq.com/docs/constructs/dashboard/' @@ -85,7 +85,7 @@ new Dashboard("advanced-dashboard", { | `useTagsAndOperator` | `boolean` | ❌ | `false` | Use AND instead of OR for tag filtering | | `width` | `string` | ❌ | `'FULL'` | Dashboard width: `'FULL'` \| `'960PX'` | -### Essential `Dashboard` Options +### Essential `Dashboard` options @@ -243,7 +243,7 @@ You must provide either `entrypoint` or `content`, but not both. ## Examples - + {/* typecheck-wrap: Dashboard */} ```ts new Dashboard("production-monitoring", { diff --git a/constructs/dns-monitor.mdx b/constructs/dns-monitor.mdx index a710cdcc0..324f4a88a 100644 --- a/constructs/dns-monitor.mdx +++ b/constructs/dns-monitor.mdx @@ -1,5 +1,5 @@ --- -title: 'DnsMonitor Construct' +title: 'DnsMonitor construct' description: 'Learn how to configure DNS monitors with the Checkly CLI.' sidebarTitle: 'DNS monitor' canonical: 'https://www.checklyhq.com/docs/constructs/dns-monitor/' @@ -92,14 +92,14 @@ A DNS monitor has its own DNS-specific settings, plus the standard monitor optio | `maxResponseTime` | `number` | ❌ | `1000` | Maximum response time in milliseconds before marking as failed (max 5000 by default) | - + -### `DnsMonitor` Options +### `DnsMonitor` options @@ -173,7 +173,7 @@ new DnsMonitor("fast-dns", { ``` -### `DnsMonitor` Assertions +### `DnsMonitor` assertions To define `assertions` for the `request` of an `DnsMonitor` you should use the `DnsAssertionBuilder`. The following sources are available for DNS monitor assertions: @@ -210,7 +210,7 @@ DnsAssertionBuilder.jsonAnswer('$.Answer.length').equals(4) Learn more in our docs on [Assertions](/detect/assertions). -### General Monitor Options +### General monitor options Friendly name for your DNS monitor that will be displayed in the Checkly dashboard and used in notifications. diff --git a/constructs/dynamic-monitor-creation.mdx b/constructs/dynamic-monitor-creation.mdx index f98436021..a7c0c6e4e 100644 --- a/constructs/dynamic-monitor-creation.mdx +++ b/constructs/dynamic-monitor-creation.mdx @@ -1,7 +1,7 @@ --- title: 'Dynamic monitor creation' description: "Create monitors dynamically with the Checkly CLI by looping over lists of targets in TypeScript or JavaScript, managing checks at scale without duplication." -sidebarTitle: 'Dynamic Monitor Creation' +sidebarTitle: 'Dynamic monitor creation' canonical: 'https://www.checklyhq.com/docs/constructs/dynamic-monitor-creation/' --- diff --git a/constructs/email-alert-channel.mdx b/constructs/email-alert-channel.mdx index 3a1d1ba02..9b8555ec5 100644 --- a/constructs/email-alert-channel.mdx +++ b/constructs/email-alert-channel.mdx @@ -1,5 +1,5 @@ --- -title: 'EmailAlertChannel Construct' +title: 'EmailAlertChannel construct' description: 'Learn how to configure email alert channels with the Checkly CLI.' sidebarTitle: 'Email' canonical: 'https://www.checklyhq.com/docs/constructs/email-alert-channel/' diff --git a/constructs/grpc-monitor.mdx b/constructs/grpc-monitor.mdx index a379e343a..4aaff824f 100644 --- a/constructs/grpc-monitor.mdx +++ b/constructs/grpc-monitor.mdx @@ -1,5 +1,5 @@ --- -title: 'GrpcMonitor Construct' +title: 'GrpcMonitor construct' description: 'Learn how to configure gRPC monitors with the Checkly CLI.' sidebarTitle: 'gRPC monitor' canonical: 'https://www.checklyhq.com/docs/constructs/grpc-monitor/' @@ -101,14 +101,14 @@ gRPC monitors have their own gRPC-specific settings, plus the standard monitor o | `maxResponseTime` | `number` | ❌ | `20000` | Response time in milliseconds at which the monitor is marked as failed (max 180,000) | - + -### `GrpcMonitor` Options +### `GrpcMonitor` options @@ -208,7 +208,7 @@ new GrpcMonitor('grpc-thresholds', { -### `GrpcMonitor` Assertions +### `GrpcMonitor` assertions Use `GrpcAssertionBuilder` to define assertions for the `request` of a `GrpcMonitor`. The following sources are available: @@ -263,7 +263,7 @@ GrpcAssertionBuilder.responseMetadata('content-type').contains('grpc') Learn more in our docs on [Assertions](/detect/assertions). -### General Monitor Options +### General monitor options Friendly name for your gRPC monitor displayed in the Checkly dashboard and used in notifications. diff --git a/constructs/heartbeat-monitor.mdx b/constructs/heartbeat-monitor.mdx index 54c424b9f..86947d183 100644 --- a/constructs/heartbeat-monitor.mdx +++ b/constructs/heartbeat-monitor.mdx @@ -79,7 +79,7 @@ The Heartbeat Monitoring configuration consists of specific heartbeat monitoring | `graceUnit` | `string` | ✅ | - | Grace time unit: `'seconds'` \| `'minutes'` \| `'hours'` \| `'days'` | - + | Property | Type | Required | Default | Description | |----------|------|----------|---------|-------------| @@ -93,7 +93,7 @@ The Heartbeat Monitoring configuration consists of specific heartbeat monitoring -### `HeartbeatMonitor` Options +### `HeartbeatMonitor` options The expected period between pings from your external service. This defines how often your job or service should check in. @@ -113,7 +113,7 @@ new HeartbeatMonitor('my-heartbeat', { **Examples:** - + {/* typecheck-wrap: HeartbeatMonitor */} ```ts @@ -128,7 +128,7 @@ new HeartbeatMonitor("backup-job", { ``` - + {/* typecheck-wrap: HeartbeatMonitor */} ```ts @@ -143,7 +143,7 @@ new HeartbeatMonitor("data-sync", { ``` - + {/* typecheck-wrap: HeartbeatMonitor */} ```ts @@ -200,7 +200,7 @@ new HeartbeatMonitor('my-heartbeat', { **Examples:** - + {/* typecheck-wrap: HeartbeatMonitor */} ```ts @@ -215,7 +215,7 @@ new HeartbeatMonitor("critical-task", { ``` - + {/* typecheck-wrap: HeartbeatMonitor */} ```ts @@ -230,7 +230,7 @@ new HeartbeatMonitor("standard-job", { ``` - + {/* typecheck-wrap: HeartbeatMonitor */} ```ts @@ -269,7 +269,7 @@ new HeartbeatMonitor('my-heartbeat', { **Available units**: `'seconds'`, `'minutes'`, `'hours'`, `'days'` -### General Monitor Options +### General monitor options Friendly name for your Heartbeat monitor that will be displayed in the Checkly dashboard and used in notifications. @@ -289,7 +289,7 @@ new HeartbeatMonitor('my-heartbeat', { ## Examples - + {/* typecheck-wrap: HeartbeatMonitor */} ```ts new HeartbeatMonitor("backup-job-heartbeat", { @@ -306,7 +306,7 @@ new HeartbeatMonitor('my-heartbeat', { ``` - + {/* typecheck-wrap: HeartbeatMonitor */} ```ts new HeartbeatMonitor("sync-job-heartbeat", { @@ -330,7 +330,7 @@ new HeartbeatMonitor('my-heartbeat', { ``` - + {/* typecheck-wrap: HeartbeatMonitor */} ```ts new HeartbeatMonitor('deployment-heartbeat', { @@ -350,7 +350,7 @@ new HeartbeatMonitor('my-heartbeat', { ``` - + {/* typecheck-wrap: HeartbeatMonitor */} ```ts new HeartbeatMonitor('log-processing-heartbeat', { @@ -382,7 +382,7 @@ new HeartbeatMonitor('my-heartbeat', { ``` - + {/* typecheck-wrap: HeartbeatMonitor */} ```ts new HeartbeatMonitor('frequent-task-heartbeat', { @@ -407,12 +407,12 @@ new HeartbeatMonitor('my-heartbeat', { -## Getting the heartbeat Ping URL +## Getting the heartbeat ping URL After deploying your Heartbeat monitor, you can obtain the ping URL in several ways: - + ```bash npx checkly deploy diff --git a/constructs/icmp-monitor.mdx b/constructs/icmp-monitor.mdx index d548eb8a8..b7367813f 100644 --- a/constructs/icmp-monitor.mdx +++ b/constructs/icmp-monitor.mdx @@ -1,5 +1,5 @@ --- -title: 'IcmpMonitor Construct' +title: 'IcmpMonitor construct' description: 'Learn how to configure ICMP monitors with the Checkly CLI.' sidebarTitle: 'ICMP monitor' canonical: 'https://www.checklyhq.com/docs/constructs/icmp-monitor/' @@ -80,14 +80,14 @@ ICMP monitors have their own ICMP-specific settings, plus the standard monitor o | `maxPacketLossThreshold` | `number` | ❌ | `20` | Packet loss percentage at which the monitor is marked as failed | - + -### `IcmpMonitor` Options +### `IcmpMonitor` options @@ -157,7 +157,7 @@ new IcmpMonitor("icmp-performance-tiers", { -### `IcmpMonitor` Assertions +### `IcmpMonitor` assertions Assertions for ICMP monitors can be defined using the `IcmpAssertionBuilder`. The following sources are available: @@ -184,7 +184,7 @@ IcmpAssertionBuilder.jsonResponse('$.packetsReceived').equals(10) Learn more in our docs on [Assertions](/detect/assertions). -### General Monitor Options +### General monitor options Friendly name for your ICMP monitor that will be displayed in the Checkly dashboard and used in notifications. diff --git a/constructs/incident-trigger.mdx b/constructs/incident-trigger.mdx index da98502dc..248c96cdb 100644 --- a/constructs/incident-trigger.mdx +++ b/constructs/incident-trigger.mdx @@ -1,7 +1,7 @@ --- -title: 'IncidentTrigger Configuration' +title: 'IncidentTrigger configuration' description: 'Learn how to configure status page incident automation with the Checkly CLI.' -sidebarTitle: 'Incident Trigger (deprecated)' +sidebarTitle: 'Incident trigger (deprecated)' canonical: 'https://www.checklyhq.com/docs/constructs/incident-trigger/' --- @@ -51,7 +51,7 @@ new PlaywrightCheck("playwright-check-suite", { ## Configuration - + | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| @@ -64,7 +64,7 @@ new PlaywrightCheck("playwright-check-suite", { -## `IncidentTrigger` Options +## `IncidentTrigger` options The status page service that this incident will be associated with. When a check or monitor fails, an incident is created for this service and connected status pages. diff --git a/constructs/incidentio-alert-channel.mdx b/constructs/incidentio-alert-channel.mdx index 7b9a474b9..cb6e328e2 100644 --- a/constructs/incidentio-alert-channel.mdx +++ b/constructs/incidentio-alert-channel.mdx @@ -1,5 +1,5 @@ --- -title: 'IncidentioAlertChannel Construct' +title: 'IncidentioAlertChannel construct' description: 'Learn how to configure Incident.io alert channels with the Checkly CLI.' sidebarTitle: 'Incident.io' canonical: 'https://www.checklyhq.com/docs/constructs/incidentio-alert-channel/' diff --git a/constructs/including-checks.mdx b/constructs/including-checks.mdx index 76a6bbcde..3efdc2fb3 100644 --- a/constructs/including-checks.mdx +++ b/constructs/including-checks.mdx @@ -1,7 +1,7 @@ --- -title: 'Create Checks Automatically from Files' +title: 'Create checks automatically from files' description: 'Learn how to automatically include checks in your project' -sidebarTitle: 'Check Discovery and Creation' +sidebarTitle: 'Check discovery and creation' canonical: 'https://www.checklyhq.com/docs/constructs/including-checks/' --- diff --git a/constructs/maintenance-window.mdx b/constructs/maintenance-window.mdx index 8cdc2f8af..3947ce82c 100644 --- a/constructs/maintenance-window.mdx +++ b/constructs/maintenance-window.mdx @@ -1,5 +1,5 @@ --- -title: 'MaintenanceWindow Construct' +title: 'MaintenanceWindow construct' description: 'Learn how to configure maintenance windows with the Checkly CLI.' sidebarTitle: 'Maintenance window' canonical: 'https://www.checklyhq.com/docs/constructs/maintenance-window/' @@ -56,7 +56,7 @@ new MaintenanceWindow("weekly-backup", { | `silenceAlertsTags` | `string[]` | ❌ | `[]` | Tags that filter which checks have their alerts silenced | | `silenceAllAlerts` | `boolean` | ❌ | `false` | Silence alerts for every check in the account | -### `MaintenanceWindow` Options +### `MaintenanceWindow` options A name for the maintenance window that will be displayed in the Checkly dashboard and used for identification. @@ -311,7 +311,7 @@ new MaintenanceWindow("quiet-period", { ## Examples - + {/* typecheck-wrap: MaintenanceWindow */} ```ts new MaintenanceWindow("database-maintenance", { @@ -326,7 +326,7 @@ new MaintenanceWindow("quiet-period", { ``` - + {/* typecheck-wrap: MaintenanceWindow */} ```ts new MaintenanceWindow("system-updates", { @@ -341,7 +341,7 @@ new MaintenanceWindow("quiet-period", { ``` - + {/* typecheck-wrap */} ```ts // For immediate one-time maintenance @@ -358,7 +358,7 @@ new MaintenanceWindow("quiet-period", { ``` - + {/* typecheck-wrap: MaintenanceWindow */} ```ts // API service maintenance @@ -388,7 +388,7 @@ new MaintenanceWindow("quiet-period", { -## Best Practices +## Best practices **Tag Matching**: Maintenance windows affect ALL checks that have ANY of the specified tags. Be specific with your tags to avoid affecting unintended checks. diff --git a/constructs/msteams-alert-channel.mdx b/constructs/msteams-alert-channel.mdx index f6256d461..41f928002 100644 --- a/constructs/msteams-alert-channel.mdx +++ b/constructs/msteams-alert-channel.mdx @@ -1,5 +1,5 @@ --- -title: 'MSTeamsAlertChannel Construct' +title: 'MSTeamsAlertChannel construct' description: 'Learn how to configure Microsoft Teams alert channels with the Checkly CLI.' sidebarTitle: 'Microsoft Teams' canonical: 'https://www.checklyhq.com/docs/constructs/msteams-alert-channel/' diff --git a/constructs/multistep-check.mdx b/constructs/multistep-check.mdx index 970225b0c..9dcef399a 100644 --- a/constructs/multistep-check.mdx +++ b/constructs/multistep-check.mdx @@ -75,7 +75,7 @@ new MultiStepCheck("complex-multistep-check", { | `code` | `object` | ✅ | - | The Playwright test code | - + | Property | Type | Required | Default | Description | |----------|------|----------|---------|-------------| @@ -262,7 +262,7 @@ test("SpaceX-API Dragon Capsules & Next Launch", async ({ request }) => { **Use cases**: Complex API journeys, end-to-end API workflows, business process validation. -### General Check Options +### General check options Friendly name for your Multistep check that will be displayed in the Checkly dashboard and used in notifications. @@ -332,7 +332,7 @@ new MultiStepCheck("global-check", { Examples: - + {/* typecheck-wrap: MultiStepCheck */} ```ts @@ -351,7 +351,7 @@ new MultiStepCheck("global-journey", { ``` - + {/* typecheck-wrap: MultiStepCheck */} ```ts diff --git a/constructs/opsgenie-alert-channel.mdx b/constructs/opsgenie-alert-channel.mdx index dd13f2b15..c76cd6c55 100644 --- a/constructs/opsgenie-alert-channel.mdx +++ b/constructs/opsgenie-alert-channel.mdx @@ -1,5 +1,5 @@ --- -title: 'OpsgenieAlertChannel Construct' +title: 'OpsgenieAlertChannel construct' description: 'Learn how to configure Opsgenie alert channels with the Checkly CLI.' sidebarTitle: 'Opsgenie' canonical: 'https://www.checklyhq.com/docs/constructs/opsgenie-alert-channel/' diff --git a/constructs/overview.mdx b/constructs/overview.mdx index 0137d5517..802d3bd28 100644 --- a/constructs/overview.mdx +++ b/constructs/overview.mdx @@ -1,5 +1,5 @@ --- -title: Using Checkly CLI Constructs +title: Using Checkly CLI constructs description: 'Build monitoring infrastructure using JavaScript/TypeScript and the Checkly CLI' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/constructs/overview/' @@ -56,7 +56,7 @@ new ApiCheck('api-health-check', { Test this API check with `npx checkly test` and transform it to production monitoring with `npx checkly deploy`. -## Project Structure +## Project structure - `checkly.config.ts` - Mandatory global project and CLI configuration. We recommend using TypeScript. - `src/__checks__/*` - TS/JS files defining your checks and other resources. @@ -78,18 +78,18 @@ Here is an example directory tree of what that would look like: The `checkly.config.ts` at the root of your project defines a range of defaults for all your checks. -## Project Configuration +## Project configuration As your project grows, you will want to override these defaults for specific checks or check groups. The recommended way to tackle this is using a mix of **global** and **local** configuration. -### Global Configuration +### Global configuration As mentioned, your global `checkly.config.ts` holds a set of defaults for your project, checks, and some CLI commands. Use `defineConfig` to configure your Checkly project. Find a full reference of all project properties in [the `Project` construct section](/constructs/project). -### Local Configuration +### Local configuration Override any of the `checks` global configuration settings at the individual check level. @@ -155,7 +155,7 @@ The project `logicalId` can be configured in the project's [global configuration When changing the logical ID of a project you will keep all resources on your Checkly account, unless you run [`npx checkly destroy`](/cli/checkly-destroy/) to remove the old project. -## Programming with Constructs +## Programming with constructs All resources you can create and manage using the Checkly CLI are derived from "constructs". These constructs are just [TypeScript classes](https://github.com/checkly/checkly-cli/tree/main/packages/cli/src/constructs). diff --git a/constructs/pagerduty-alert-channel.mdx b/constructs/pagerduty-alert-channel.mdx index 47150f422..05375c5f5 100644 --- a/constructs/pagerduty-alert-channel.mdx +++ b/constructs/pagerduty-alert-channel.mdx @@ -1,5 +1,5 @@ --- -title: 'PagerdutyAlertChannel Construct' +title: 'PagerdutyAlertChannel construct' description: 'Learn how to configure PagerDuty alert channels with the Checkly CLI.' sidebarTitle: 'PagerDuty' canonical: 'https://www.checklyhq.com/docs/constructs/pagerduty-alert-channel/' diff --git a/constructs/phone-call-alert-channel.mdx b/constructs/phone-call-alert-channel.mdx index cf6925430..9f0c68808 100644 --- a/constructs/phone-call-alert-channel.mdx +++ b/constructs/phone-call-alert-channel.mdx @@ -1,7 +1,7 @@ --- -title: 'PhoneCallAlertChannel Construct' +title: 'PhoneCallAlertChannel construct' description: 'Learn how to configure phone call alert channels with the Checkly CLI.' -sidebarTitle: 'Phone Call' +sidebarTitle: 'Phone call' canonical: 'https://www.checklyhq.com/docs/constructs/phone-call-alert-channel/' --- diff --git a/constructs/playwright-check.mdx b/constructs/playwright-check.mdx index 45d216b86..8587db109 100644 --- a/constructs/playwright-check.mdx +++ b/constructs/playwright-check.mdx @@ -74,7 +74,7 @@ The Playwright Check Suite configuration consists of specific Playwright Check S | `engine` | `Engine` | ❌ | Auto-detected, then Node.js 22 | JavaScript engine and version used to run the Playwright Check Suite | - + | Property | Type | Required | Default | Description | |----------|------|----------|---------|-------------| @@ -98,7 +98,7 @@ The Playwright Check Suite configuration consists of specific Playwright Check S -### Playwright Check Suite Options +### Playwright Check Suite options @@ -300,7 +300,7 @@ If no engine is set and the CLI cannot auto-detect one, Checkly uses the default -### General Check Options +### General check options Friendly name for your Playwright Check Suite that will be displayed in the Checkly dashboard and used in notifications. diff --git a/constructs/private-location.mdx b/constructs/private-location.mdx index 841d9a094..076e6a3fb 100644 --- a/constructs/private-location.mdx +++ b/constructs/private-location.mdx @@ -1,5 +1,5 @@ --- -title: 'PrivateLocation Construct' +title: 'PrivateLocation construct' description: 'Learn how to configure private locations with the Checkly CLI.' sidebarTitle: 'Private locations' canonical: 'https://www.checklyhq.com/docs/constructs/private-location/' @@ -100,7 +100,7 @@ new PrivateLocation("my-location", { **Examples:** - + {/* typecheck-wrap: PrivateLocation */} ```ts @@ -122,7 +122,7 @@ new PrivateLocation("datacenter-west", { ``` - + {/* typecheck-wrap: PrivateLocation */} ```ts @@ -176,12 +176,12 @@ new PrivateLocation('corporate-location', { }) ``` -## Referencing Existing Locations +## Referencing existing locations Reference private locations by using their construct reference or by slug names if they were created outside your CLI project: - + {/* typecheck-wrap: PrivateLocation */} ```ts @@ -202,7 +202,7 @@ new ApiCheck("existing-location-reference", { - + {/* typecheck-wrap: ApiCheck */} ```ts @@ -217,7 +217,7 @@ new ApiCheck("existing-location-check", { ``` - + {/* typecheck-wrap: PrivateLocation */} ```ts @@ -248,7 +248,7 @@ new ApiCheck("mixed-locations-check", { **Examples:** - + {/* typecheck-wrap: PrivateLocation */} ```ts @@ -260,7 +260,7 @@ new PrivateLocation("corp-proxy-location", { ``` - + {/* typecheck-wrap: PrivateLocation */} ```ts @@ -272,7 +272,7 @@ new PrivateLocation("secure-proxy-location", { ``` - + {/* typecheck-wrap: PrivateLocation */} ```ts @@ -327,7 +327,7 @@ When `proxyUrl` is configured, all HTTP calls from API checks running in this pr ``` - + {/* typecheck-wrap: PrivateLocation */} ```ts const eastDatacenter = new PrivateLocation("dc-east", { @@ -370,7 +370,7 @@ When `proxyUrl` is configured, all HTTP calls from API checks running in this pr ``` - + {/* typecheck-wrap: PrivateLocation */} ```ts const devEnvironment = new PrivateLocation("dev-env", { @@ -408,7 +408,7 @@ When `proxyUrl` is configured, all HTTP calls from API checks running in this pr ``` - + {/* typecheck-wrap: PrivateLocation */} ```ts const corporateLocation = new PrivateLocation("corporate-with-proxy", { diff --git a/constructs/project.mdx b/constructs/project.mdx index a8cd10a0c..7c6c5c8d1 100644 --- a/constructs/project.mdx +++ b/constructs/project.mdx @@ -1,5 +1,5 @@ --- -title: 'Project Construct' +title: 'Project construct' description: 'Learn how to configure projects with the Checkly CLI.' sidebarTitle: 'Project' canonical: 'https://www.checklyhq.com/docs/constructs/project/' @@ -77,7 +77,7 @@ export default defineConfig({ | `bundle` | `object` | ❌ | - | Dependency embedding and pruning for Playwright Check Suite code bundles. See [Internal Registries](/detect/synthetic-monitoring/playwright-checks/internal-registries), and [Speed up installs](/detect/synthetic-monitoring/playwright-checks/dependencies#speed-up-installs) for pruning to make installs faster | | `runner` | `object` | ❌ | - | Settings applied on Checkly runners for Playwright Check Suite installs: [registry routing](/detect/synthetic-monitoring/playwright-checks/internal-registries#route-runner-installs-to-other-registries) and the [dependency cache version](/detect/synthetic-monitoring/playwright-checks/dependencies#force-a-reinstall) | -### Core Project Options +### Core project options Friendly name for your project that will be displayed in the Checkly dashboard and used for identification. @@ -162,7 +162,7 @@ export default defineConfig({ **Use cases**: Local testing defaults, CI/CD configuration, development workflow. -### Check and Monitor Configuration +### Check and monitor configuration The `checks` property allows you to set global defaults for all checks and monitors in your project. Individual checks and groups can override these settings. @@ -215,7 +215,7 @@ export default defineConfig({ -### General Settings for All Check and Monitor Types +### General settings for all check and monitor types Define global defaults for all checks and monitors in this project. Individual checks and groups can override these settings. @@ -534,7 +534,7 @@ export default defineConfig({ -### Default Settings for Complex Check Types +### Default settings for complex check types @@ -636,7 +636,7 @@ export default defineConfig({ Checkly CLI version 10 and later no longer include the deprecated `groupName` option. Set `group` to the `CheckGroup` instead. - + | Property | Type | Required | Default | Description | |----------|------|----------|---------|-------------| @@ -663,7 +663,7 @@ export default defineConfig({ ## Examples - + {/* typecheck-wrap */} ```ts export default defineConfig({ @@ -681,7 +681,7 @@ export default defineConfig({ ``` - + ```ts import { defineConfig } from 'checkly' import { Frequency } from 'checkly/constructs' @@ -717,7 +717,7 @@ export default defineConfig({ ``` - + ```ts import { defineConfig } from 'checkly' import { Frequency } from 'checkly/constructs' diff --git a/constructs/retry-strategy.mdx b/constructs/retry-strategy.mdx index fdd522213..d21782ad3 100644 --- a/constructs/retry-strategy.mdx +++ b/constructs/retry-strategy.mdx @@ -1,7 +1,7 @@ --- -title: 'RetryStrategyBuilder Construct' +title: 'RetryStrategyBuilder construct' description: 'Learn how to configure retry strategies with the Checkly CLI.' -sidebarTitle: 'Retry Strategy' +sidebarTitle: 'Retry strategy' canonical: 'https://www.checklyhq.com/docs/constructs/retry-strategy/' --- @@ -74,7 +74,7 @@ A check, monitor or group that sets no `retryStrategy` uses the default for its | `PlaywrightCheck` | No retry strategy. Configure retries in your Playwright configuration instead. | | `CheckGroupV2` | No group retry strategy. Each check in the group uses its own. | -### Retry Strategy Methods +### Retry strategy methods Use the `RetryStrategyBuilder` methods to apply different retry strategies to your checks and monitors. @@ -153,7 +153,7 @@ new ApiCheck("stable-api", { ``` - + {/* typecheck-wrap: ApiCheck */} ```ts highlight={4-8} @@ -184,7 +184,7 @@ Time between retries with five seconds `baseBackoffSeconds` and three retries: ` **Usage:** - + {/* typecheck-wrap: ApiCheck */} ```ts highlight={4-8} @@ -202,7 +202,7 @@ new ApiCheck("gradual-backoff", { ``` - + {/* typecheck-wrap: ApiCheck */} ```ts highlight={4-8} @@ -233,7 +233,7 @@ Time between retries with five seconds `baseBackoffSeconds` and three retries: ` **Usage:** - + {/* typecheck-wrap: ApiCheck */} ```ts highlight={4-9} @@ -252,7 +252,7 @@ new ApiCheck("overloaded-api", { ``` - + {/* typecheck-wrap: ApiCheck */} ```ts highlight={4-9} @@ -276,7 +276,7 @@ new ApiCheck("rate-limited-api", { **Use cases**: Overloaded services, rate-limited APIs, aggressive backoff scenarios, circuit breaker patterns. -### Retry Strategy Options +### Retry strategy options Time to wait before the first retry attempt. Also used as the base value for calculating subsequent retry intervals in linear and exponential strategies. @@ -369,7 +369,7 @@ Currently supports `'NETWORK_ERROR'` for `ApiCheck` and `UrlMonitor` constructs ## Examples - + ```ts import { ApiCheck, RetryStrategyBuilder } from "checkly/constructs" @@ -384,7 +384,7 @@ Currently supports `'NETWORK_ERROR'` for `ApiCheck` and `UrlMonitor` constructs ``` - + ```ts import { ApiCheck, RetryStrategyBuilder } from "checkly/constructs" @@ -407,7 +407,7 @@ Currently supports `'NETWORK_ERROR'` for `ApiCheck` and `UrlMonitor` constructs ``` - + ```ts import { ApiCheck, RetryStrategyBuilder } from "checkly/constructs" @@ -430,7 +430,7 @@ Currently supports `'NETWORK_ERROR'` for `ApiCheck` and `UrlMonitor` constructs ``` - + ```ts import { ApiCheck, RetryStrategyBuilder } from "checkly/constructs" @@ -454,7 +454,7 @@ Currently supports `'NETWORK_ERROR'` for `ApiCheck` and `UrlMonitor` constructs ``` - + ```ts import { ApiCheck, @@ -489,7 +489,7 @@ Currently supports `'NETWORK_ERROR'` for `ApiCheck` and `UrlMonitor` constructs ``` - + ```ts checkly.config.ts import { defineConfig } from "checkly" import { Frequency, RetryStrategyBuilder } from "checkly/constructs" @@ -512,10 +512,10 @@ Currently supports `'NETWORK_ERROR'` for `ApiCheck` and `UrlMonitor` constructs -## Best Practices +## Best practices - + {/* typecheck-wrap */} ```ts // For stable APIs - minimal retries @@ -534,7 +534,7 @@ Currently supports `'NETWORK_ERROR'` for `ApiCheck` and `UrlMonitor` constructs ``` - + {/* typecheck-wrap */} ```ts // Critical endpoints - fail fast to alert quickly @@ -553,7 +553,7 @@ Currently supports `'NETWORK_ERROR'` for `ApiCheck` and `UrlMonitor` constructs ``` - + {/* typecheck-wrap */} ```ts // Browser checks - longer backoff due to complexity diff --git a/constructs/slack-alert-channel.mdx b/constructs/slack-alert-channel.mdx index 788480b70..f3e8d6741 100644 --- a/constructs/slack-alert-channel.mdx +++ b/constructs/slack-alert-channel.mdx @@ -1,7 +1,7 @@ --- -title: 'SlackAlertChannel Construct' +title: 'SlackAlertChannel construct' description: 'Learn how to configure Slack alert channels with the Checkly CLI.' -sidebarTitle: 'Slack Webhook' +sidebarTitle: 'Slack webhook' deprecated: true canonical: 'https://www.checklyhq.com/docs/constructs/slack-alert-channel/' --- diff --git a/constructs/slack-app-alert-channel.mdx b/constructs/slack-app-alert-channel.mdx index 9d535e689..a09c1ac19 100644 --- a/constructs/slack-app-alert-channel.mdx +++ b/constructs/slack-app-alert-channel.mdx @@ -1,5 +1,5 @@ --- -title: 'SlackAppAlertChannel Construct' +title: 'SlackAppAlertChannel construct' description: 'Learn how to configure Slack alert channels with the Checkly CLI.' sidebarTitle: 'Slack' tag: new diff --git a/constructs/sms-alert-channel.mdx b/constructs/sms-alert-channel.mdx index 66ddbfd8e..4f58dab23 100644 --- a/constructs/sms-alert-channel.mdx +++ b/constructs/sms-alert-channel.mdx @@ -1,5 +1,5 @@ --- -title: 'SmsAlertChannel Construct' +title: 'SmsAlertChannel construct' description: 'Learn how to configure SMS alert channels with the Checkly CLI.' sidebarTitle: 'SMS' canonical: 'https://www.checklyhq.com/docs/constructs/sms-alert-channel/' diff --git a/constructs/ssl-monitor.mdx b/constructs/ssl-monitor.mdx index d117e3996..ae07d8011 100644 --- a/constructs/ssl-monitor.mdx +++ b/constructs/ssl-monitor.mdx @@ -1,5 +1,5 @@ --- -title: 'SslMonitor Construct' +title: 'SslMonitor construct' description: 'Learn how to configure SSL monitors with the Checkly CLI.' sidebarTitle: 'SSL monitor' canonical: 'https://www.checklyhq.com/docs/constructs/ssl-monitor/' @@ -97,14 +97,14 @@ SSL monitors have SSL-specific settings and inherit the standard monitor options | `maxResponseTime` | `number` | ❌ | `10000` | Handshake time in milliseconds at which the monitor is marked failed | - + -### `SslMonitor` Options +### `SslMonitor` options @@ -175,7 +175,7 @@ new SslMonitor("my-ssl", { ``` -### `SslConfig` Options +### `SslConfig` options Raise a degraded alert when the certificate is within this many days of expiry. Range: 1–365. @@ -279,7 +279,7 @@ sslConfig: { Each rule's `severity` can be `'fail'` \| `'degrade'` \| `'ignore'`. -### `SslMonitor` Assertions +### `SslMonitor` assertions Define `assertions` using the `SslAssertionBuilder`. Five entry points map to the assertion sources — `certificate`/`connection` take a `property` (a field selector); `jsonResponse`/`textResponse` take a JSONPath/regex: @@ -343,7 +343,7 @@ SslAssertionBuilder.connection("cipherSuite").equals(CipherSuite.TLS_AES_128_GCM Learn more in our docs on [Assertions](/detect/assertions). -### General Monitor Options +### General monitor options Friendly name for your SSL monitor, displayed in the Checkly dashboard and used in notifications. @@ -401,7 +401,7 @@ new SslMonitor("my-ssl-monitor", { ## Examples - + ```ts import { Frequency, SslMonitor } from "checkly/constructs" @@ -419,7 +419,7 @@ new SslMonitor("my-ssl-monitor", { ``` - + ```ts import { Frequency, SslAssertionBuilder, SslMonitor, TlsVersion } from "checkly/constructs" @@ -447,7 +447,7 @@ new SslMonitor("my-ssl-monitor", { ``` - + ```ts import { Frequency, SslAssertionBuilder, SslMonitor } from "checkly/constructs" @@ -471,7 +471,7 @@ new SslMonitor("my-ssl-monitor", { ``` - + ```ts import { Frequency, SslAssertionBuilder, SslMonitor } from "checkly/constructs" @@ -494,7 +494,7 @@ new SslMonitor("my-ssl-monitor", { ``` - + ```ts import { Frequency, SslMonitor } from "checkly/constructs" diff --git a/constructs/status-page-service.mdx b/constructs/status-page-service.mdx index 5d5cac415..4e3c08886 100644 --- a/constructs/status-page-service.mdx +++ b/constructs/status-page-service.mdx @@ -1,5 +1,5 @@ --- -title: 'StatusPageService Construct' +title: 'StatusPageService construct' description: 'Learn how to configure status page services with the Checkly CLI.' sidebarTitle: 'Status page service (deprecated)' canonical: 'https://www.checklyhq.com/docs/constructs/status-page-service/' @@ -89,7 +89,7 @@ new StatusPage("acme-status", { -## `StatusPageService` Options +## `StatusPageService` options Display name for the service on the status page. This name appears in the status page cards and helps users identify which service component is being monitored. @@ -223,7 +223,7 @@ new StatusPage("simple-status", { -## Service Reusability +## Service reusability StatusPageService instances can be reused across multiple status pages: @@ -266,7 +266,7 @@ new StatusPage("internal-status", { }) ``` -## Integration with Checks and Monitors +## Integration with checks and monitors Status page services represent logical groupings of functionality. You'll typically have multiple checks monitoring different aspects of each service, but the service itself provides a high-level view for your status page visitors. Enable checks and monitors to trigger incidents by using the `triggerIncident` property. diff --git a/constructs/status-page-v3-automation-rule.mdx b/constructs/status-page-v3-automation-rule.mdx index d4ecf1cf3..1d4081f89 100644 --- a/constructs/status-page-v3-automation-rule.mdx +++ b/constructs/status-page-v3-automation-rule.mdx @@ -1,5 +1,5 @@ --- -title: 'StatusPageV3AutomationRule Construct' +title: 'StatusPageV3AutomationRule construct' description: 'Learn how to automate status page incidents with the Checkly CLI.' sidebarTitle: 'Status page automation rule' canonical: 'https://www.checklyhq.com/docs/constructs/status-page-v3-automation-rule/' @@ -37,7 +37,7 @@ new StatusPageV3AutomationRule("api-outage-rule", { ## Configuration -### `StatusPageV3AutomationRule` Options +### `StatusPageV3AutomationRule` options The page this rule belongs to. diff --git a/constructs/status-page-v3-component.mdx b/constructs/status-page-v3-component.mdx index b1653ec86..eab86ade4 100644 --- a/constructs/status-page-v3-component.mdx +++ b/constructs/status-page-v3-component.mdx @@ -1,5 +1,5 @@ --- -title: 'StatusPageV3Component Construct' +title: 'StatusPageV3Component construct' description: 'Learn how to configure status page components with the Checkly CLI.' sidebarTitle: 'Status page component' canonical: 'https://www.checklyhq.com/docs/constructs/status-page-v3-component/' @@ -33,7 +33,7 @@ new StatusPageV3Component("api-component", { ## Configuration -### `StatusPageV3Component` Options +### `StatusPageV3Component` options The page this component belongs to. A component belongs to exactly one page and cannot move to another one later. diff --git a/constructs/status-page-v3.mdx b/constructs/status-page-v3.mdx index 50c3825c6..299c99fb1 100644 --- a/constructs/status-page-v3.mdx +++ b/constructs/status-page-v3.mdx @@ -1,5 +1,5 @@ --- -title: 'StatusPageV3 Construct' +title: 'StatusPageV3 construct' description: 'Learn how to configure status pages with the Checkly CLI.' sidebarTitle: 'Status page' canonical: 'https://www.checklyhq.com/docs/constructs/status-page-v3/' @@ -93,7 +93,7 @@ new StatusPageV3AutomationRule("web-outage-rule", { ## Configuration -### `StatusPageV3` Options +### `StatusPageV3` options Name of the status page, shown in the header and browser title. diff --git a/constructs/status-page.mdx b/constructs/status-page.mdx index 64148f1d2..ea689c093 100644 --- a/constructs/status-page.mdx +++ b/constructs/status-page.mdx @@ -1,5 +1,5 @@ --- -title: 'StatusPage Construct' +title: 'StatusPage construct' description: 'Learn how to configure status pages with the Checkly CLI.' sidebarTitle: 'Status page (deprecated)' canonical: 'https://www.checklyhq.com/docs/constructs/status-page/' @@ -96,7 +96,7 @@ new StatusPage("acme-status", { -### `StatusPage` Options +### `StatusPage` options Name of the status page displayed in the header and browser title. diff --git a/constructs/tcp-monitor.mdx b/constructs/tcp-monitor.mdx index f75e4b9ba..6e25dd183 100644 --- a/constructs/tcp-monitor.mdx +++ b/constructs/tcp-monitor.mdx @@ -1,5 +1,5 @@ --- -title: 'TcpMonitor Construct' +title: 'TcpMonitor construct' description: 'Learn how to configure TCP monitors with the Checkly CLI.' sidebarTitle: 'TCP monitor' canonical: 'https://www.checklyhq.com/docs/constructs/tcp-monitor/' @@ -89,14 +89,14 @@ The TCP Monitoring configuration consists of specific TCP monitoring options and | `shouldFail` | `boolean` | ❌ | `false` | Treat connection failures (e.g. timeouts or refused ports) as passed. Successful connections still pass. Only failed assertions will cause the check to fail. | - + -### `TcpMonitor` Options +### `TcpMonitor` options TCP connection configuration that defines the hostname, port, and optional data to send. @@ -128,7 +128,7 @@ new TcpMonitor("tcp-monitor", { **Examples:** - + {/* typecheck-wrap: TcpMonitor */} ```ts @@ -144,7 +144,7 @@ new TcpMonitor("database-check", { ``` - + {/* typecheck-wrap: TcpMonitor */} ```ts @@ -163,7 +163,7 @@ new TcpMonitor("redis-ping", { ``` - + {/* typecheck-wrap: TcpMonitor */} ```ts @@ -264,7 +264,7 @@ new TcpMonitor("batch-service", { **Use cases**: Performance monitoring, SLA compliance, connection timeout management. -### `TcpMonitor` Assertions +### `TcpMonitor` assertions To define `assertions` for the `request` of an `TcpMonitor` you should use the `TcpAssertionBuilder`. The following sources are available for TCP monitor assertions: @@ -291,7 +291,7 @@ TcpAssertionBuilder.responseData().contains('ping') Learn more in our docs on [Assertions](/detect/assertions). -### General Monitor Options +### General monitor options Friendly name for your TCP monitor that will be displayed in the Checkly dashboard and used in notifications. @@ -322,7 +322,7 @@ new TcpMonitor("my-monitor", { Examples: - + {/* typecheck-wrap: TcpMonitor */} ```ts @@ -335,7 +335,7 @@ new TcpMonitor("critical-db", { ``` - + {/* typecheck-wrap: TcpMonitor */} ```ts @@ -348,7 +348,7 @@ new TcpMonitor("app-service", { ``` - + {/* typecheck-wrap: TcpMonitor */} ```ts @@ -381,7 +381,7 @@ new TcpMonitor('global-monitor', { Examples: - + {/* typecheck-wrap: TcpMonitor */} ```ts @@ -402,7 +402,7 @@ new TcpMonitor("global-db", { ``` - + {/* typecheck-wrap: TcpMonitor */} ```ts @@ -474,7 +474,7 @@ new TcpMonitor("maintenance-db", { ``` - + {/* typecheck-wrap: TcpMonitor */} ```ts new TcpMonitor("redis-check", { @@ -496,7 +496,7 @@ new TcpMonitor("maintenance-db", { ``` - + {/* typecheck-wrap: TcpMonitor */} ```ts new TcpMonitor("smtp-check", { @@ -518,7 +518,7 @@ new TcpMonitor("maintenance-db", { ``` - + {/* typecheck-wrap: TcpMonitor */} ```ts new TcpMonitor("ssh-check", { @@ -538,7 +538,7 @@ new TcpMonitor("maintenance-db", { ``` - + {/* typecheck-wrap: TcpMonitor */} ```ts new TcpMonitor("app-port-check", { diff --git a/constructs/telegram-alert-channel.mdx b/constructs/telegram-alert-channel.mdx index 704c294f2..b44c3fc3e 100644 --- a/constructs/telegram-alert-channel.mdx +++ b/constructs/telegram-alert-channel.mdx @@ -1,5 +1,5 @@ --- -title: 'TelegramAlertChannel Construct' +title: 'TelegramAlertChannel construct' description: 'Learn how to configure Telegram alert channels and forum topics with the Checkly CLI.' sidebarTitle: 'Telegram' canonical: 'https://www.checklyhq.com/docs/constructs/telegram-alert-channel/' diff --git a/constructs/traceroute-monitor.mdx b/constructs/traceroute-monitor.mdx index 162040325..638ab8dc1 100644 --- a/constructs/traceroute-monitor.mdx +++ b/constructs/traceroute-monitor.mdx @@ -1,5 +1,5 @@ --- -title: 'TracerouteMonitor Construct' +title: 'TracerouteMonitor construct' description: 'Learn how to configure Traceroute monitors with the Checkly CLI.' sidebarTitle: 'Traceroute monitor' canonical: 'https://www.checklyhq.com/docs/constructs/traceroute-monitor/' @@ -83,14 +83,14 @@ Traceroute monitors have their own probe-specific settings, plus the standard mo | `maxResponseTime` | `number` | ❌ | `20000` | Final-hop avg RTT in milliseconds at which the monitor is marked as failed | - + -### `TracerouteMonitor` Options +### `TracerouteMonitor` options @@ -163,7 +163,7 @@ new TracerouteMonitor("traceroute-latency-tiers", { ``` -### `TracerouteMonitor` Assertions +### `TracerouteMonitor` assertions Assertions for Traceroute monitors are defined using the `TracerouteAssertionBuilder`. The following sources are available: @@ -207,7 +207,7 @@ TracerouteAssertionBuilder.packetLoss().lessThan(10) Learn more in our docs on [Assertions](/detect/assertions). -### General Monitor Options +### General monitor options Friendly name for your Traceroute monitor that will be displayed in the Checkly dashboard and used in notifications. diff --git a/constructs/url-monitor.mdx b/constructs/url-monitor.mdx index f3bed7ca0..8241643bc 100644 --- a/constructs/url-monitor.mdx +++ b/constructs/url-monitor.mdx @@ -1,5 +1,5 @@ --- -title: 'UrlMonitor Construct' +title: 'UrlMonitor construct' description: 'Learn how to configure URL monitors with the Checkly CLI.' sidebarTitle: 'URL monitor' canonical: 'https://www.checklyhq.com/docs/constructs/url-monitor/' @@ -84,14 +84,14 @@ The URL Monitoring configuration consists of specific URL monitoring options and | `shouldFail` | `boolean` | ❌ | false | Treat HTTP error codes (4xx and 5xx) as passed. Please note that successful responses still pass. Only failed assertions will cause the check to fail. | - + -### `UrlMonitor` Options +### `UrlMonitor` options @@ -126,7 +126,7 @@ new UrlMonitor("url-monitor", { **Examples:** - + {/* typecheck-wrap: UrlMonitor */} ```ts @@ -143,7 +143,7 @@ new UrlMonitor('website-check', { ``` - + {/* typecheck-wrap: UrlMonitor */} ```ts @@ -159,7 +159,7 @@ new UrlMonitor("api-health", { ``` - + {/* typecheck-wrap: UrlMonitor */} ```ts @@ -245,7 +245,7 @@ new UrlMonitor("api-timeout", { **Use cases**: Performance monitoring, SLA compliance, user experience optimization. -### `UrlMonitor` Assertions +### `UrlMonitor` assertions To define `assertions` for the `request` of an `UrlMonitor` you should use the `UrlAssertionBuilder`. The following source is available for URL monitor assertions: @@ -269,7 +269,7 @@ UrlAssertionBuilder.statusCode().lessThan(300) Learn more in our docs on [Assertions](/detect/assertions). -### General Monitor Options +### General monitor options Friendly name for your URL monitor that will be displayed in the Checkly dashboard and used in notifications. @@ -302,7 +302,7 @@ new UrlMonitor("my-monitor", { **Examples:** - + {/* typecheck-wrap: UrlMonitor */} ```ts @@ -316,7 +316,7 @@ new UrlMonitor("critical-service", { ``` - + {/* typecheck-wrap: UrlMonitor */} ```ts @@ -330,7 +330,7 @@ new UrlMonitor("website-monitor", { ``` - + {/* typecheck-wrap: UrlMonitor */} ```ts @@ -365,7 +365,7 @@ new UrlMonitor("global-monitor", { **Examples:** - + {/* typecheck-wrap: UrlMonitor */} ```ts @@ -386,7 +386,7 @@ new UrlMonitor("global-website", { ``` - + {/* typecheck-wrap: UrlMonitor */} ```ts @@ -438,7 +438,7 @@ new UrlMonitor("maintenance-site", { ## Examples - + {/* typecheck-wrap: UrlMonitor */} ```ts new UrlMonitor("website-availability", { @@ -458,7 +458,7 @@ new UrlMonitor("maintenance-site", { ``` - + {/* typecheck-wrap: UrlMonitor */} ```ts new UrlMonitor("api-health-check", { @@ -479,7 +479,7 @@ new UrlMonitor("maintenance-site", { ``` - + {/* typecheck-wrap: UrlMonitor */} ```ts new UrlMonitor("cdn-performance", { @@ -498,7 +498,7 @@ new UrlMonitor("maintenance-site", { ``` - + {/* typecheck-wrap: UrlMonitor */} ```ts new UrlMonitor("redirect-chain", { @@ -518,7 +518,7 @@ new UrlMonitor("maintenance-site", { ``` - + {/* typecheck-wrap: UrlMonitor */} ```ts new UrlMonitor("ssl-certificate-check", { @@ -537,7 +537,7 @@ new UrlMonitor("maintenance-site", { }) ``` - + {/* typecheck-wrap: UrlMonitor */} ```ts new UrlMonitor("maintenance-page", { diff --git a/constructs/webhook-alert-channel.mdx b/constructs/webhook-alert-channel.mdx index 77c38024f..d717ff7f7 100644 --- a/constructs/webhook-alert-channel.mdx +++ b/constructs/webhook-alert-channel.mdx @@ -1,5 +1,5 @@ --- -title: 'WebhookAlertChannel Construct' +title: 'WebhookAlertChannel construct' description: 'Learn how to configure webhook alert channels with the Checkly CLI.' sidebarTitle: 'Webhook' canonical: 'https://www.checklyhq.com/docs/constructs/webhook-alert-channel/' diff --git a/detect/assertions.mdx b/detect/assertions.mdx index 8842495d1..75e83355a 100644 --- a/detect/assertions.mdx +++ b/detect/assertions.mdx @@ -1,5 +1,5 @@ --- -title: 'Defining Assertions' +title: 'Defining assertions' description: 'Add assertions to validate your check results' sidebarTitle: 'Assertions' canonical: 'https://www.checklyhq.com/docs/detect/assertions/' diff --git a/detect/overview.mdx b/detect/overview.mdx index 067c5987d..50024cb7c 100644 --- a/detect/overview.mdx +++ b/detect/overview.mdx @@ -8,11 +8,11 @@ canonical: 'https://www.checklyhq.com/docs/detect/overview/' **Checkly Detect** provides global reliability infrastructure to help test and monitor applications and services for exceptional user experiences. By combining automated testing and monitoring, Checkly helps you identify issues across the entire SDLC; and most importantly, **before they impact your users**. - + Monitor availability and response times across your website and infrastructure - + Proactively validate real user interactions with API, Browser, and Multistep checks @@ -22,40 +22,40 @@ Run automated Playwright tests to validate functionality and user workflows befo -## Key Benefits +## Key benefits - **Early, Proactive Issue Detection** — Identify problems before they impact users through proactive monitoring and testing across all application layers. - **Comprehensive, Global Coverage** — Monitor everything from basic uptime to complex user workflows with multiple monitoring types and global locations. - **Historical Performance Insights** — Track response times, availability percentages, and user experience metrics to optimize application performance. - **Automated Validation** — Reduce manual testing overhead with automated checks that run continuously and provide immediate feedback. -## How Checkly Works +## How Checkly works - + Start with the monitoring approach that best fits your immediate needs: - Create them inside the Checkly UI - Create them in your repository as [constructs](/constructs/overview) - + Once Checks are created, you configure where you want to run them, how often they should run, and how you want to be alerted when they fail. - + Run them as tests in your CI/CD pipeline. This ensures they are run in production like any other test. - `npx checkly test` Runs all of your local checks in your project - `npx checkly trigger` Runs all of your active checks in your account - + Once you are happy with your monitoring, you can deploy them to production. - `npx checkly deploy` Deploys all of your checks to production - Or just save your checks in the UI and they will start to run -## Reliability In Depth Strategy +## Reliability in depth strategy Implement testing and monitoring across multiple layers for a comprehensive view of your application's reliability, from infrastructure to user experience. With Checkly, monitor everything from homepage availability to the most complex user journeys in a single platform. @@ -63,20 +63,20 @@ Implement testing and monitoring across multiple layers for a comprehensive view - **Uptime Monitoring** — Monitor servers, databases, and network connectivity to ensure availability and responsiveness - **API Synthetic Monitoring** — Validate API endpoints and microservice communication - **Browser Synthetic Monitoring** — Validate user journeys and interactions in a real browser environment -## Getting Started +## Getting started Ready to start monitoring your applications? Choose the approach that best fits your current needs: - + Begin with automated testing for development workflows - + Set up basic availability monitoring for critical services - + Create comprehensive user experience validation diff --git a/detect/synthetic-monitoring/agentic-checks/configuration.mdx b/detect/synthetic-monitoring/agentic-checks/configuration.mdx index 0fdff69a1..3deb2a159 100644 --- a/detect/synthetic-monitoring/agentic-checks/configuration.mdx +++ b/detect/synthetic-monitoring/agentic-checks/configuration.mdx @@ -1,5 +1,5 @@ --- -title: 'Agentic Checks Configuration' +title: 'Agentic Checks configuration' description: 'Review the configuration of deprecated Agentic Checks before migrating them.' sidebarTitle: 'Configuration' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/agentic-checks/configuration/' diff --git a/detect/synthetic-monitoring/agentic-checks/overview.mdx b/detect/synthetic-monitoring/agentic-checks/overview.mdx index 536811ee6..57e86de5b 100644 --- a/detect/synthetic-monitoring/agentic-checks/overview.mdx +++ b/detect/synthetic-monitoring/agentic-checks/overview.mdx @@ -1,5 +1,5 @@ --- -title: 'Agentic Checks Overview' +title: 'Agentic Checks overview' description: 'Learn about deprecated Agentic Checks and migrate them before they stop running on December 1, 2026.' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/agentic-checks/overview/' @@ -107,7 +107,7 @@ Existing Agentic Checks can run until December 1, 2026. Deactivated checks retai Replace active checks before December 1, 2026. - + Review existing Agentic Checks managed with the Checkly CLI. diff --git a/detect/synthetic-monitoring/api-checks/api-structure.mdx b/detect/synthetic-monitoring/api-checks/api-structure.mdx index 99fac6f40..9975f0683 100644 --- a/detect/synthetic-monitoring/api-checks/api-structure.mdx +++ b/detect/synthetic-monitoring/api-checks/api-structure.mdx @@ -2,7 +2,7 @@ title: 'API check structure' description: 'Learn how to structure your API checks with the ApiCheck construct.' -sidebarTitle: MaC Structure +sidebarTitle: MaC structure canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/api-checks/api-structure/' --- @@ -32,9 +32,9 @@ new ApiCheck('user-api-health', { }) ``` -## Request Configuration +## Request configuration -### HTTP Methods +### HTTP methods Supported HTTP methods: - **GET**: Retrieve data from endpoints - **POST**: Create resources or submit data @@ -43,15 +43,15 @@ Supported HTTP methods: - **DELETE**: Remove resources - **HEAD**: Check resource existence without body -### Authentication Support +### Authentication support - **Bearer Token**: JWT and OAuth token authentication - **Basic Auth**: Username/password authentication - **API Keys**: Custom header or query parameter authentication - **Custom Headers**: Flexible authentication patterns -## Response Validation +## Response validation -### Status Code Assertions +### Status code assertions Validate HTTP response codes: ```typescript assertions: [ @@ -60,7 +60,7 @@ assertions: [ ] ``` -### Content Validation +### Content validation Validate response content and structure: ```typescript assertions: [ @@ -75,7 +75,7 @@ assertions: [ ] ``` -### Header Validation +### Header validation Check response headers: ```typescript assertions: [ @@ -85,7 +85,7 @@ assertions: [ ] ``` -## Advanced Features +## Advanced features ### Environment variables Use variables for dynamic content: @@ -98,7 +98,7 @@ const apiKey = process.env.API_KEY const userId = Math.floor(Math.random() * 1000) ``` -### Request Chaining +### Request chaining Use previous responses in subsequent requests: ```javascript // Setup script - create test user @@ -116,7 +116,7 @@ process.env.TEST_USER_ID = userData.id // URL: https://api.example.com/users/{{TEST_USER_ID}}/profile ``` -### GraphQL Support +### GraphQL support Monitor GraphQL APIs by sending the query and its variables as a JSON body: ```typescript new ApiCheck('graphql-get-user', { diff --git a/detect/synthetic-monitoring/api-checks/client-certificates.mdx b/detect/synthetic-monitoring/api-checks/client-certificates.mdx index 3d05f7ac2..b187a0de1 100644 --- a/detect/synthetic-monitoring/api-checks/client-certificates.mdx +++ b/detect/synthetic-monitoring/api-checks/client-certificates.mdx @@ -1,7 +1,7 @@ --- title: Client certificates description: "Authenticate API checks against APIs that require mutual TLS (mTLS) by adding client certificates, private keys, and a CA per domain on the Enterprise plan." -sidebarTitle: Client Certificates +sidebarTitle: Client certificates canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/api-checks/client-certificates/' --- diff --git a/detect/synthetic-monitoring/api-checks/configuration.mdx b/detect/synthetic-monitoring/api-checks/configuration.mdx index bfdfe30e9..9d17238d4 100644 --- a/detect/synthetic-monitoring/api-checks/configuration.mdx +++ b/detect/synthetic-monitoring/api-checks/configuration.mdx @@ -9,7 +9,7 @@ import GenericRuntimeVariablesTable from '/snippets/generic-runtime-variables-ta While configuring up your API check, you can run the request and its assertions using the **Run request** button. This will run the API check on production infrastructure and help you debug any issues. -## Basic Setup +## Basic setup Start by specifying the endpoint you want to track. @@ -247,7 +247,7 @@ The assertion evaluates the response body up to the 25MB limit above. Its *Actua display, and the stored response body remains subject to result-size limits. Checks without a Text body assertion keep the scrubbing behavior described in this section. -## Additional Settings +## Additional settings * **Name:** Give your check a clear name to identify it in dashboards and alerts * **Description:** Add context about what this check 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) diff --git a/detect/synthetic-monitoring/api-checks/openapi-spec.mdx b/detect/synthetic-monitoring/api-checks/openapi-spec.mdx index e927c2c6c..d08aec2ae 100644 --- a/detect/synthetic-monitoring/api-checks/openapi-spec.mdx +++ b/detect/synthetic-monitoring/api-checks/openapi-spec.mdx @@ -1,7 +1,7 @@ --- -title: 'Creating Checks from an OpenAPI Spec' +title: 'Creating checks from an OpenAPI spec' description: 'Step-by-step guide to creating your first API check in Checkly using the web UI and CLI.' -sidebarTitle: 'Importing OpenAPI Spec' +sidebarTitle: 'Importing OpenAPI spec' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/api-checks/openapi-spec/' --- @@ -25,9 +25,9 @@ Navigate to the Create API Check page and select the Import from Swagger / OpenA Add a valid URL to the Swagger / OpenAPI specification and click the Import Specfication button. -## Configuring Your Checks +## Configuring your checks -### Groups & Tagging +### Groups & tagging You can add your OpenAPI endpoints checks to a group to help you manage them. diff --git a/detect/synthetic-monitoring/api-checks/response-limits.mdx b/detect/synthetic-monitoring/api-checks/response-limits.mdx index 1cda4e31f..26937d4b7 100644 --- a/detect/synthetic-monitoring/api-checks/response-limits.mdx +++ b/detect/synthetic-monitoring/api-checks/response-limits.mdx @@ -1,5 +1,5 @@ --- -title: API Response time limits +title: API response time limits description: "Set degraded and failing response-time thresholds for API checks so slow-but-working APIs are flagged before they break, without hurting your success ratio." sidebarTitle: Response time limits canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/api-checks/response-limits/' diff --git a/detect/synthetic-monitoring/api-checks/setup-and-teardown.mdx b/detect/synthetic-monitoring/api-checks/setup-and-teardown.mdx index daaae9e90..654140040 100644 --- a/detect/synthetic-monitoring/api-checks/setup-and-teardown.mdx +++ b/detect/synthetic-monitoring/api-checks/setup-and-teardown.mdx @@ -1,7 +1,7 @@ --- -title: 'Setup and Teardown Scripts' +title: 'Setup and teardown scripts' description: 'Learn how to use setup and teardown scripts to prepare requests and process responses in API checks.' -sidebarTitle: Setup and Teardown +sidebarTitle: Setup and teardown canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/api-checks/setup-and-teardown/' --- diff --git a/detect/synthetic-monitoring/api-checks/troubleshooting.mdx b/detect/synthetic-monitoring/api-checks/troubleshooting.mdx index 7c10379a7..29f2c927e 100644 --- a/detect/synthetic-monitoring/api-checks/troubleshooting.mdx +++ b/detect/synthetic-monitoring/api-checks/troubleshooting.mdx @@ -19,7 +19,7 @@ Then, Checkly is closing the connection after the usual 30 seconds timeout, beca - The response headers will be empty. If Checkly doesn't get a connection, there is nothing to send back, e.g. the response headers. -## Authentication Problems +## Authentication problems **Issue: 401/403 status codes, authorization errors** **Solutions**: @@ -28,7 +28,7 @@ Then, Checkly is closing the connection after the usual 30 seconds timeout, beca 3. Validate authentication headers format 4. Test API manually with same credentials -## Timeout Issues +## Timeout issues **Issue: Requests timing out, slow responses** **Solutions**: @@ -37,7 +37,7 @@ Then, Checkly is closing the connection after the usual 30 seconds timeout, beca 3. Increase timeout thresholds if appropriate 4. Investigate API infrastructure capacity -## Assertion Failures +## Assertion failures **Issue: Unexpected response content or format** **Solutions**: diff --git a/detect/synthetic-monitoring/browser-checks/degraded.mdx b/detect/synthetic-monitoring/browser-checks/degraded.mdx index b5bb64f32..85c6a7a33 100644 --- a/detect/synthetic-monitoring/browser-checks/degraded.mdx +++ b/detect/synthetic-monitoring/browser-checks/degraded.mdx @@ -1,7 +1,7 @@ --- title: 'Degraded state' description: 'Degraded state with soft assertions' -sidebarTitle: 'Degraded State' +sidebarTitle: 'Degraded state' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/degraded/' --- @@ -17,7 +17,7 @@ To trigger a degraded state, checks use a helper library, `@checkly/playwright-h The helper library contains two methods, `markCheckAsDegraded` and `getAPIResponseTime`. -### Installing and Importing +### Installing and importing ```bash npm i @checkly/playwright-helpers @@ -35,7 +35,7 @@ const { getAPIResponseTime, markCheckAsDegraded } = require('@checkly/playwright -### Getting The Request Response Time +### Getting the request response time To get the request response time, call `getAPIResponseTime`. **Usage** @@ -45,7 +45,7 @@ if (getAPIResponseTime(response) > 100) { } ``` -### Marking A Check As Degraded +### Marking a check as degraded To mark a check as degraded, call `markCheckAsDegraded`. This can be used when: @@ -70,7 +70,7 @@ if (foo.length > 100) { **Arguments** - `response` [APIResponse](https://playwright.dev/docs/api/class-apiresponse) *(required)*. A response from a Playwright API request. -### Example of Marking A Check As Degraded +### Example of marking a check as degraded A check is marked as degraded when `markCheckAsDegraded` is called and there are no regular assertions triggered. diff --git a/detect/synthetic-monitoring/browser-checks/examples.mdx b/detect/synthetic-monitoring/browser-checks/examples.mdx index 6a762f0cb..02fbe0a02 100644 --- a/detect/synthetic-monitoring/browser-checks/examples.mdx +++ b/detect/synthetic-monitoring/browser-checks/examples.mdx @@ -9,9 +9,9 @@ These real-world use cases demonstrate how to implement comprehensive user journ The examples below leave out the `import { test, expect } from '@playwright/test'` line. Add it to the top of your script. -## E-commerce and Retail +## E-commerce and retail -### Product Discovery and Purchase Flow +### Product discovery and purchase flow Monitor the complete customer journey from browsing to purchase: ```typescript @@ -64,7 +64,7 @@ test('Complete e-commerce purchase workflow', async ({ page }) => { }) ``` -### Mobile Shopping Experience +### Mobile shopping experience Test responsive design and mobile-specific features: ```typescript @@ -100,7 +100,7 @@ test('Mobile shopping experience', async ({ page }) => { }) ``` -### Inventory and Availability Monitoring +### Inventory and availability monitoring Ensure product availability information is accurate: ```typescript @@ -135,9 +135,9 @@ test('Product availability and inventory updates', async ({ page }) => { }) ``` -## SaaS and Software Platforms +## SaaS and software platforms -### User Onboarding and Setup +### User onboarding and setup Monitor new user registration and initial setup flows: ```typescript @@ -188,7 +188,7 @@ test('SaaS user onboarding workflow', async ({ page }) => { }) ``` -### Feature Usage and Navigation +### Feature usage and navigation Test core application functionality and user workflows: ```typescript @@ -237,7 +237,7 @@ test('Core feature workflow - Project management', async ({ page }) => { }) ``` -### Subscription and Billing Workflows +### Subscription and billing workflows Monitor payment and subscription management: ```typescript @@ -277,9 +277,9 @@ test('Subscription upgrade workflow', async ({ page }) => { }) ``` -## Financial Services +## Financial services -### Online Banking Workflows +### Online banking workflows Monitor critical banking operations and security: ```typescript @@ -319,7 +319,7 @@ test('Online banking - Account management', async ({ page }) => { }) ``` -### Money Transfer and Payments +### Money transfer and payments Test fund transfer and payment processing: ```typescript @@ -370,7 +370,7 @@ test('Money transfer workflow', async ({ page }) => { }) ``` -### Investment Platform Monitoring +### Investment platform monitoring Test investment account access and trading functionality: ```typescript @@ -412,9 +412,9 @@ test('Investment platform workflow', async ({ page }) => { }) ``` -## Healthcare and Life Sciences +## Healthcare and life sciences -### Patient Portal Access +### Patient portal access Monitor patient information access and appointment scheduling: ```typescript @@ -463,7 +463,7 @@ test('Patient portal workflow', async ({ page }) => { }) ``` -### Telemedicine Platform +### Telemedicine platform Test video consultation and virtual care workflows: ```typescript @@ -510,9 +510,9 @@ test('Telemedicine consultation workflow', async ({ page }) => { }) ``` -## Education and E-Learning +## Education and E-learning -### Online Course Platform +### Online course platform Monitor student learning experience and course delivery: ```typescript @@ -571,9 +571,9 @@ test('Online learning platform workflow', async ({ page }) => { }) ``` -## Media and Entertainment +## Media and entertainment -### Video Streaming Platform +### Video streaming platform Test content discovery and playback functionality: ```typescript @@ -627,12 +627,12 @@ test('Video streaming platform workflow', async ({ page }) => { }) ``` -## Performance and Accessibility Monitoring +## Performance and accessibility monitoring -### Core Web Vitals Validation +### Core Web Vitals validation You don't need custom code to measure Core Web Vitals. Checkly collects Web Vitals automatically for every page your browser check visits. See [Performance & Web Vitals](/detect/synthetic-monitoring/browser-checks/performance-metrics). -### Accessibility Compliance Testing +### Accessibility compliance testing Run automated accessibility checks with [axe-core](https://github.com/dequelabs/axe-core). Checkly runtimes include `@axe-core/playwright`: ```typescript diff --git a/detect/synthetic-monitoring/browser-checks/mac-structure.mdx b/detect/synthetic-monitoring/browser-checks/mac-structure.mdx index 45a84c331..d2ffe578c 100644 --- a/detect/synthetic-monitoring/browser-checks/mac-structure.mdx +++ b/detect/synthetic-monitoring/browser-checks/mac-structure.mdx @@ -1,7 +1,7 @@ --- title: 'Browser check structure' description: 'Learn how to structure your Browser checks with Monitoring as Code.' -sidebarTitle: MaC Structure +sidebarTitle: MaC structure canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/mac-structure/' --- @@ -26,7 +26,7 @@ new BrowserCheck('browser-check-1', { }) ``` -## Test Script Structure +## Test script structure Checkly uses Playwright to power Browser checks. [Playwright](https://playwright.dev/docs/intro) is a robust, open-source framework for browser automation and end-to-end web application testing. It enables you to write atomic, reliable tests and easily control interactions within a web page. Browser checks execute automated test scripts in real browsers. diff --git a/detect/synthetic-monitoring/browser-checks/overview.mdx b/detect/synthetic-monitoring/browser-checks/overview.mdx index 1af354f7a..5a94db5e4 100644 --- a/detect/synthetic-monitoring/browser-checks/overview.mdx +++ b/detect/synthetic-monitoring/browser-checks/overview.mdx @@ -53,7 +53,7 @@ Checkly uses Playwright to power your Browser checks. [Playwright](https://playw 6. **Results Collection** - Records screenshots, videos, and detailed logs 7. **Alerts** - Triggers alerts if any of the assertions fail -## Check Structure +## Check structure @@ -63,7 +63,7 @@ Checkly uses Playwright to power your Browser checks. [Playwright](https://playw Create your Playwright test file in the Checkly IDE, then configure the check settings in the Checkly UI. - + Browser checks use Playwright's test framework with a familiar structure. It works by connecting constructs to handle the configuration of your Browser check, and then referencing the test file in your repository. @@ -134,28 +134,28 @@ Individual Browser check results contain: Learn more in our documentation on [Results](/concepts/results). -## Key Capabilities - +## Key capabilities + Execute scripts in real Chromium browsers to test complex user interactions, JavaScript functionality, and dynamic content. - + Write tests using Playwright's powerful API for cross-browser automation with built-in waiting, assertions, and debugging capabilities. - + Capture and compare screenshots to detect unintended visual changes in your application's UI. - + Monitor Core Web Vitals, page load times, and custom performance metrics to ensure optimal user experience. - + Test responsive designs and mobile-specific functionality by emulating various devices and screen sizes. - + Run checks from multiple worldwide locations to verify performance and availability across different regions. diff --git a/detect/synthetic-monitoring/browser-checks/performance-metrics.mdx b/detect/synthetic-monitoring/browser-checks/performance-metrics.mdx index 10ff64676..4c88d29d5 100644 --- a/detect/synthetic-monitoring/browser-checks/performance-metrics.mdx +++ b/detect/synthetic-monitoring/browser-checks/performance-metrics.mdx @@ -1,7 +1,7 @@ --- title: Performance & Web Vitals description: 'Web Vitals for Browser checks' -sidebarTitle: 'Performance Metrics' +sidebarTitle: 'Performance metrics' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/performance-metrics/' --- @@ -32,7 +32,7 @@ Running a Playwright Check Suite instead? See [Web Vitals for Playwright Check S -## Network Waterfalls +## Network waterfalls For each page you visit, we automatically collect the following: 1. Any `error`, `warning` or `info` level console messages. @@ -44,7 +44,7 @@ You can use this data to quickly find issues with the pages you visit. Use cases - Pinpoint missing images or other resources: they will show a `404` in the network tab. -## Web Performance Vitals +## Web performance vitals For each page your script visits, we automatically collect a set of five [Web Vitals](https://web.dev/learn-web-vitals/). Web Vitals are user focused quality signals for web pages that indicate a good, ok or poor user experience. @@ -93,18 +93,18 @@ Web Vitals are a part [Google Lighthouse](https://developers.google.com/web/tool Checkly automatically instruments your Playwright code to collect Web Vitals metrics. However, in some cases we will not be able to collect a good measurement. There are multiple reasons for this: -#### Route-Based Navigation +#### Route-based navigation A Single Page App like a React, Vue or Angular app only has one HTML page load event and then relies on route changes. The underlying [library we use for collecting Web Vitals](https://github.com/GoogleChrome/web-vitals) does not yet account for this. The folks over at Google are aware of this and [posted an FAQ](https://web.dev/vitals-spa-faq/). -#### Insufficient Measurement Time +#### Insufficient measurement time Cumulative Layout Shift (CLS) relies on layout events accumulating over time. If your script exits very fast, or triggers a redirect, there might not be enough time to actually "catch" this metric. -#### User Interaction Needed +#### User interaction needed Some metrics require a small amount of interaction to effectively "trigger". Clicking a button or other screen element in your Playwright script can help here. @@ -119,7 +119,7 @@ We are constantly tweaking and updating our Web Vitals collection code, so expec Checkly collects "lab" metrics for you. These are different from "field" metrics. - + **Controlled Environment** - Collected in synthetic environments - Generated by your Browser check scripts @@ -128,7 +128,7 @@ Checkly collects "lab" metrics for you. These are different from "field" metrics - Perfect for pre-deployment testing - + **Real User Monitoring (RUM)** - Based on real user traffic - Collected "in the wild" diff --git a/detect/synthetic-monitoring/browser-checks/playwright-support.mdx b/detect/synthetic-monitoring/browser-checks/playwright-support.mdx index 398adc77a..c80fe9a41 100644 --- a/detect/synthetic-monitoring/browser-checks/playwright-support.mdx +++ b/detect/synthetic-monitoring/browser-checks/playwright-support.mdx @@ -1,7 +1,7 @@ --- -title: Playwright Support in Checkly +title: Playwright support in Checkly description: "See which Playwright features Checkly's Browser checks support, from trace files and video recordings to auto-waiting, locators, and visual regression testing." -sidebarTitle: 'Playwright Support' +sidebarTitle: 'Playwright support' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/playwright-support/' --- @@ -152,7 +152,7 @@ Here's an example of a Playwright Test script that fails, and provides a video o When running tests from the editor page, video files are always available for download and preview, regardless of whether the check is passing or failing. For scheduled check runs videos are only preserved when the check failed. -## PageObject Model (POM) +## PageObject model (POM) If you are structuring your test codebase following the [PageObject pattern](https://martinfowler.com/bliki/PageObject.html), you can use the [Checkly CLI](/cli/overview) out of the box. Just make sure that: @@ -252,7 +252,7 @@ module.exports = config; -## Multi Test Checks +## Multi test checks One of the key benefits of using Playwright Test is that you can split your check into multiple independent test cases, and group them using the `test.describe` function. Your Checkly check will fail if **at least one** of the test cases fails. @@ -291,9 +291,9 @@ test.describe('two tests', () => { An executed Browser check that includes multiple Playwright test cases still counts as a single check run towards your pricing plan's defined limits. -## Interactions & Navigations +## Interactions & navigations -### Page Interactions +### Page interactions ```typescript // Navigation await page.goto('https://example.com') @@ -315,7 +315,7 @@ await page.hover('.tooltip-trigger') await page.setInputFiles('input[type="file"]', './document.pdf') ``` -### Element Selection Strategies +### Element selection strategies ```typescript // By test ID (recommended) await page.click('[data-testid="submit-button"]') @@ -333,9 +333,9 @@ await page.click('//button[@class="submit-btn"]') await page.click('role=button[name="Submit"]') ``` -## Assertions and Validation +## Assertions and validation -### Page Content Assertions +### Page content assertions ```typescript // Text content validation await expect(page.locator('.success-message')).toHaveText('Order confirmed') @@ -354,7 +354,7 @@ await expect(page.locator('input[name="email"]')).toHaveValue('user@example.com' await expect(page.locator('.status-badge')).toHaveClass('status-active') ``` -### Custom Validation Logic +### Custom validation logic ```typescript // Complex assertions with custom logic const orderTotal = await page.locator('[data-testid="order-total"]').textContent() @@ -369,9 +369,9 @@ expect(productTitles).toContain('Premium Plan') expect(productTitles).toHaveLength(3) ``` -## Advanced Features +## Advanced features -### Screenshots and Visual Testing +### Screenshots and visual testing Browser checks can take screenshots of the page and compare them to a baseline. This is useful for visual regression testing. @@ -386,7 +386,7 @@ await page.locator('.product-card').screenshot({ path: 'product.png' }) await expect(page).toHaveScreenshot('homepage.png') ``` -### Mobile Device Simulation +### Mobile device simulation ```typescript // Test responsive design test('Mobile checkout workflow', async ({ page }) => { @@ -400,7 +400,7 @@ test('Mobile checkout workflow', async ({ page }) => { }) ``` -### Multi-Tab and Context Handling +### Multi-tab and context handling ```typescript // Handle multiple tabs const [newPage] = await Promise.all([ diff --git a/detect/synthetic-monitoring/browser-checks/quickstart.mdx b/detect/synthetic-monitoring/browser-checks/quickstart.mdx index e0ec968aa..aca67c5c6 100644 --- a/detect/synthetic-monitoring/browser-checks/quickstart.mdx +++ b/detect/synthetic-monitoring/browser-checks/quickstart.mdx @@ -41,7 +41,7 @@ Browser checks are perfect for monitoring realistic user flows within your appli 2. **Choose from one of the Browser check templates** to start from a working example - + The following test script will check if the homepage is available, performing correctly, and [looks visually correct](/detect/synthetic-monitoring/browser-checks/visual-regressions). - + Configure your check settings by clicking the "Settings" button in the top right corner of the check editor - + - + Configure who gets notified when issues are detected: @@ -110,7 +110,7 @@ Configure who gets notified when issues are detected: - + Before activating your check: 1. **Click "Run check"** to run it once and verify it works @@ -119,7 +119,7 @@ Before activating your check: 4. **Click "Create"** to start continuous monitoring. New checks are activated by default. - + Once your check is active: @@ -141,7 +141,7 @@ Once your check is active: -## Next Steps +## Next steps Now that you have your first check running: diff --git a/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx b/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx index 6d33f46a5..5633ce749 100644 --- a/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx +++ b/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx @@ -1,13 +1,13 @@ --- -title: 'Trouble Shotting and Debugging' +title: 'Trouble shotting and debugging' description: 'Learn how to troubleshoot Browser checks.' sidebarTitle: Troubleshooting canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/troubleshooting/' --- -## Common Issues +## Common issues - + **Issue: Elements not found or interactions failing** **Solutions**: @@ -18,7 +18,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-c - + **Issue: Tests failing due to timing issues** **Solutions**: @@ -29,7 +29,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-c - + **Issue: Login failures or session timeouts** **Solutions**: @@ -40,7 +40,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-c - + **Issue: Tests timing out or running too slowly** **Solutions**: @@ -54,7 +54,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-c ## Error Handling and Debugging - + ```typescript // Wait for specific conditions await page.waitForSelector('[data-testid="loading-complete"]') @@ -72,7 +72,7 @@ await page.waitForSelector('.slow-element', { timeout: 30000 }) - + ```typescript // Graceful error handling try { diff --git a/detect/synthetic-monitoring/browser-checks/visual-regressions.mdx b/detect/synthetic-monitoring/browser-checks/visual-regressions.mdx index 6ce67a0f3..41c3aa26c 100644 --- a/detect/synthetic-monitoring/browser-checks/visual-regressions.mdx +++ b/detect/synthetic-monitoring/browser-checks/visual-regressions.mdx @@ -1,7 +1,7 @@ --- -title: Visual Monitoring with Checkly +title: Visual monitoring with Checkly description: 'Visual monitoring for more consistent UIs and complex assertions' -sidebarTitle: 'Visual Monitoring' +sidebarTitle: 'Visual monitoring' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-checks/visual-regressions/' --- @@ -279,16 +279,16 @@ Whenever your Playwright script encounters an error, we will automatically snap occurs. This is different than Visual Regression Monitoring Here is an example from real life! - + Your script clicks on a button using a selector `wait page.click(".my-button-class")`. - + For some reason, that button does not exist or is not clickable. - + Playwright waits for the button with the selector to appear. It does not and Playwright throws an error. - + Checkly automatically calls `page.screenshot()` a screenshot. The screenshot indicates that that specific button was missing. diff --git a/detect/synthetic-monitoring/multistep-checks/degraded-states.mdx b/detect/synthetic-monitoring/multistep-checks/degraded-states.mdx index 5c93399c9..b69f89f97 100644 --- a/detect/synthetic-monitoring/multistep-checks/degraded-states.mdx +++ b/detect/synthetic-monitoring/multistep-checks/degraded-states.mdx @@ -1,7 +1,7 @@ --- title: Degraded states in Multistep checks description: "Signal non-critical slowdowns in Multistep checks with the degraded state, using soft assertions and the @checkly/playwright-helpers markCheckAsDegraded helper." -sidebarTitle: Degraded States +sidebarTitle: Degraded states canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/multistep-checks/degraded-states/' --- @@ -18,7 +18,7 @@ To trigger a degraded state, checks use a helper library, `@checkly/playwright-h The helper library contains two methods, `markCheckAsDegraded` and `getAPIResponseTime`. -### Installing and Importing +### Installing and importing ```bash npm i @checkly/playwright-helpers @@ -36,7 +36,7 @@ const { getAPIResponseTime, markCheckAsDegraded } = require('@checkly/playwright -### Getting The Request Response Time +### Getting the request response time To get the request response time, call `getAPIResponseTime`. **Usage** @@ -49,7 +49,7 @@ if (getAPIResponseTime(response) > 100) { **Arguments** - `response` [APIResponse](https://playwright.dev/docs/api/class-apiresponse) *(required)*. A response from a Playwright API request. -### Marking A Check As Degraded +### Marking a check as degraded To mark a check as degraded, call `markCheckAsDegraded`. This can be used when: @@ -69,7 +69,7 @@ if (foo.length > 100) { **Arguments** - `reason` String *(optional)*. Logged when the method is called. Used to identify which method caused the degradation. -### Example of Marking A Check As Degraded +### Example of marking a check as degraded A check is marked as degraded when `markCheckAsDegraded` is called and there are no regular assertions triggered. diff --git a/detect/synthetic-monitoring/multistep-checks/examples.mdx b/detect/synthetic-monitoring/multistep-checks/examples.mdx index 8ee16fe9e..f0867ac3f 100644 --- a/detect/synthetic-monitoring/multistep-checks/examples.mdx +++ b/detect/synthetic-monitoring/multistep-checks/examples.mdx @@ -85,7 +85,7 @@ test("Verify Group API", async ({ request }) => { ``` -## Cleaning Up Test Data +## Cleaning up test data In this example we use `beforeAll` to verify that there's no old test data that will pollute the test, and `afterAll` to remove any data created by the test before it ends. @@ -154,7 +154,7 @@ test("Check Group", async ({ request }) => { ``` -## Verifying Binary Payloads +## Verifying binary payloads One way to ensure that e.g. CDN endpoints are serving images correctly is by verifying its binary. Here is an example of how to verify several images in a loop, checking each image against a unique binary. diff --git a/detect/synthetic-monitoring/multistep-checks/file-system.mdx b/detect/synthetic-monitoring/multistep-checks/file-system.mdx index 1b458021d..58f19adfd 100644 --- a/detect/synthetic-monitoring/multistep-checks/file-system.mdx +++ b/detect/synthetic-monitoring/multistep-checks/file-system.mdx @@ -1,7 +1,7 @@ --- -title: Uploading & Downloading Files To The File System +title: Uploading & downloading files to the file system description: "Upload and download binary files in Multistep checks with Playwright's request object, hosting files externally and validating them with HTTP requests." -sidebarTitle: File System +sidebarTitle: File system canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/multistep-checks/file-system/' --- diff --git a/detect/synthetic-monitoring/multistep-checks/multistep-structure.mdx b/detect/synthetic-monitoring/multistep-checks/multistep-structure.mdx index de1557359..2fe1fde9c 100644 --- a/detect/synthetic-monitoring/multistep-checks/multistep-structure.mdx +++ b/detect/synthetic-monitoring/multistep-checks/multistep-structure.mdx @@ -1,7 +1,7 @@ --- title: 'Multistep check structure' description: 'Learn how to structure your Multistep checks with Playwright.' -sidebarTitle: MaC Structure +sidebarTitle: MaC structure canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/multistep-checks/multistep-structure/' --- @@ -27,7 +27,7 @@ new MultiStepCheck('multistep-check-1', { ``` -## Test Script +## Test script Multistep checks use Playwright's `test.step()` function to organize sequential operations: @@ -62,7 +62,7 @@ test('create and delete a check group', async ({ request }) => { // 3 }) }) ``` -## Test Structure +## Test structure Let's look at the code above step-by-step, as it determines what our Multistep check will do. **1. Initial declarations:** Import the Playwright test framework. @@ -86,9 +86,9 @@ Always use `await` before `test.step`, otherwise the test will fail. If you want to build on the above example, you can add additional assertions, ensuring that the data returned is correct and contains a specific check, or add a `PUT` and `GET` test step to verify more of the `/check-groups` functionality. -## API Request Capabilities +## API request capabilities -### HTTP Methods Support +### HTTP methods support @@ -115,7 +115,7 @@ const response = await request.patch('/api/users/123', { const response = await request.delete('/api/users/123') ``` - + ```typescript const response = await request.get('/api/protected', { headers: { @@ -128,10 +128,10 @@ const response = await request.get('/api/protected', { -### Request Configuration +### Request configuration - + ```typescript const response = await request.get('/api/search', { params: { @@ -142,7 +142,7 @@ const response = await request.get('/api/search', { }) ``` - + ```typescript const file = await request.get('https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf') const response = await request.post('/api/upload', { @@ -157,7 +157,7 @@ const response = await request.post('/api/upload', { }) ``` - + ```typescript const response = await request.post('/api/data', { data: { @@ -171,9 +171,9 @@ const response = await request.post('/api/data', { -## Data Flow Between Steps +## Data flow between steps -### Variable Passing +### Variable passing ```typescript test('E-commerce purchase workflow', async ({ request }) => { let authToken, cartId, orderId @@ -243,7 +243,7 @@ test('E-commerce purchase workflow', async ({ request }) => { }) ``` -### Response Data Extraction +### Response data extraction ```typescript await test.step('Extract and validate response data', async () => { const response = await request.get('/api/complex-data') diff --git a/detect/synthetic-monitoring/multistep-checks/overview.mdx b/detect/synthetic-monitoring/multistep-checks/overview.mdx index 3024c6984..3d5d6683e 100644 --- a/detect/synthetic-monitoring/multistep-checks/overview.mdx +++ b/detect/synthetic-monitoring/multistep-checks/overview.mdx @@ -53,25 +53,25 @@ Multistep checks execute a series of API requests in sequence, with the ability Multistep checks are powered by Playwright's API testing mode, providing excellent debugging capabilities and detailed request/response logging. -## Key Capabilities +## Key capabilities - + Execute multiple API calls in a predefined order, ensuring each step completes successfully before proceeding to the next. - + Extract data from API responses and use it in subsequent requests, enabling realistic workflow testing with dynamic values. - + Handle multi-step authentication processes like OAuth flows, token refresh sequences, and session-based authentication chains. - + Verify that each step in your business process maintains proper state and data consistency throughout the entire workflow. - + Monitor response times and performance metrics for individual steps and the complete workflow to identify bottlenecks. @@ -79,7 +79,7 @@ Monitor response times and performance metrics for individual steps and the comp As with Browser checks, Checkly runs Multistep checks for a maximum of 240s. Scripts exceeding this will timeout. For more information on how to work with the timeout limits for Multistep and Browser checks, see [Timeouts](/detect/synthetic-monitoring/browser-checks/timeouts). -## Built-in Runtime Variables +## Built-in runtime variables The Multistep check [runtime](/platform/runtimes/overview) exposes a set of environment variables (e.g. `process.env.CHECK_NAME`) that indicate what check, check type etc. you are running. diff --git a/detect/synthetic-monitoring/multistep-checks/troubleshooting.mdx b/detect/synthetic-monitoring/multistep-checks/troubleshooting.mdx index bcdf1bf6a..88e15c2cd 100644 --- a/detect/synthetic-monitoring/multistep-checks/troubleshooting.mdx +++ b/detect/synthetic-monitoring/multistep-checks/troubleshooting.mdx @@ -8,7 +8,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/multistep Multistep checks are a powerful tool for monitoring complex API workflows. However, they can sometimes be tricky to troubleshoot. Here are some common issues and solutions: -## Authentication and Authorization +## Authentication and authorization **Issue: Authentication failures or token expiration** **Solutions**: @@ -17,7 +17,7 @@ Multistep checks are a powerful tool for monitoring complex API workflows. Howev 3. Check API permissions for all required endpoints 4. Use environment variables for sensitive credentials -## Data Flow Problems +## Data flow problems **Issue: Variables not passing correctly between steps** **Solutions**: @@ -26,7 +26,7 @@ Multistep checks are a powerful tool for monitoring complex API workflows. Howev 3. Check JSON parsing and data extraction logic 4. Validate API response formats match expectations -## Timing and Performance Issues +## Timing and performance issues **Issue: Workflows timing out or running slowly** **Solutions**: @@ -35,7 +35,7 @@ Multistep checks are a powerful tool for monitoring complex API workflows. Howev 3. Implement parallel processing where possible 4. Add monitoring for long-running operations -## Error Handling and Recovery +## Error handling and recovery **Issue: Workflows failing without proper cleanup** **Solutions**: diff --git a/detect/synthetic-monitoring/multistep-checks/websockets.mdx b/detect/synthetic-monitoring/multistep-checks/websockets.mdx index 00643930a..a6d7e472d 100644 --- a/detect/synthetic-monitoring/multistep-checks/websockets.mdx +++ b/detect/synthetic-monitoring/multistep-checks/websockets.mdx @@ -8,7 +8,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/multistep To create a WebSocket check in Checkly, you'll need to write a script that establishes a WebSocket connection, sends messages, and validates responses. -## Set Up the WebSocket Connection +## Set up the WebSocket connection First, we'll establish a connection to the WebSocket server. Replace `wss://your.websocketserver.com` with the URL of your WebSocket server. @@ -27,7 +27,7 @@ const ws = new WebSocket(url); ``` -## Handle WebSocket Events +## Handle WebSocket events Handle the key events like opening the connection, receiving messages, and encountering errors. @@ -64,7 +64,7 @@ ws.on('error', (error) => { ``` -## Sending and Receiving Messages +## Sending and receiving messages Implement the logic for sending messages and processing the received responses. @@ -92,7 +92,7 @@ function sendMessage(message) { -## Close the Connection +## Close the connection Ensure to properly close the WebSocket connection after your checks. diff --git a/detect/synthetic-monitoring/overview.mdx b/detect/synthetic-monitoring/overview.mdx index c6193d982..f801abf16 100644 --- a/detect/synthetic-monitoring/overview.mdx +++ b/detect/synthetic-monitoring/overview.mdx @@ -1,16 +1,16 @@ --- -title: 'Synthetic Monitoring Overview' +title: 'Synthetic monitoring overview' description: 'Comprehensive synthetic monitoring for detecting downtime and performance issues in APIs and Applications' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/overview/' --- -## What is Synthetic Monitoring? +## What is synthetic monitoring? Synthetic monitoring goes beyond simple uptime checks by proactively validating your applications by simulating real user interactions and API workflows. Checkly's Synthetic Monitoring ensures your critical systems work correctly from both technical and user experience perspectives. It validates complete business processes, user experiences, and system integrations before your users encounter issues. -## Types of Synthetic Monitoring Checks +## Types of synthetic monitoring checks Checkly provides four check types to comprehensively monitor your applications: @@ -40,7 +40,7 @@ Migrate your existing Playwright projects and tests to Checkly. -## What's Next? +## What's next? Ready to implement comprehensive synthetic monitoring? Choose your starting point based on your monitoring needs: diff --git a/detect/synthetic-monitoring/playwright-checks/add-to-group.mdx b/detect/synthetic-monitoring/playwright-checks/add-to-group.mdx index 6798618b8..8928952e5 100644 --- a/detect/synthetic-monitoring/playwright-checks/add-to-group.mdx +++ b/detect/synthetic-monitoring/playwright-checks/add-to-group.mdx @@ -1,7 +1,7 @@ --- -title: 'Adding Playwright Check Suites to Groups' +title: 'Adding Playwright Check Suites to groups' description: 'Organize your Playwright Check Suites with groups for better management and shared configuration.' -sidebarTitle: 'Add to Group' +sidebarTitle: 'Add to group' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/playwright-checks/add-to-group/' --- diff --git a/detect/synthetic-monitoring/playwright-checks/configuration.mdx b/detect/synthetic-monitoring/playwright-checks/configuration.mdx index 3a304a34a..04a910e7b 100644 --- a/detect/synthetic-monitoring/playwright-checks/configuration.mdx +++ b/detect/synthetic-monitoring/playwright-checks/configuration.mdx @@ -1,5 +1,5 @@ --- -title: 'Playwright Check Suites Configuration' +title: 'Playwright Check Suites configuration' description: 'Complete configuration reference for Playwright Check Suites including all available options and examples.' sidebarTitle: 'Configuration' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/playwright-checks/configuration/' diff --git a/detect/synthetic-monitoring/playwright-checks/dependencies.mdx b/detect/synthetic-monitoring/playwright-checks/dependencies.mdx index 642591649..c7c711c2e 100644 --- a/detect/synthetic-monitoring/playwright-checks/dependencies.mdx +++ b/detect/synthetic-monitoring/playwright-checks/dependencies.mdx @@ -108,7 +108,7 @@ registry=https://yourcompany.jfrog.io/artifactory/api/npm/npm-local/ //yourcompany.jfrog.io/artifactory/api/npm/npm-local/:_authToken=${ARTIFACTORY_TOKEN} ``` -#### Using GitHub Packages +#### Using GitHub packages ```txt //npm.pkg.github.com/:_authToken=${GITHUB_TOKEN} @@ -172,7 +172,7 @@ export default defineConfig({ Learn more about [customizing install commands](/detect/synthetic-monitoring/playwright-checks/configuration#customize-install-and-test-commands). -## Dependency Caching +## Dependency caching Checkly caches installed packages between check runs to speed up execution and reduce installation time. Dependencies are installed once and reused for subsequent runs until the files that define your dependencies change, such as your lock file and your `package.json` and `.npmrc` files, or until your `installCommand`, your working directory, or your [`engine`](/constructs/playwright-check#param-engine) change. Changes to [embedded or pruned packages and registry routing](/detect/synthetic-monitoring/playwright-checks/internal-registries) also invalidate the cache. @@ -219,7 +219,7 @@ For a one-off fresh install, pass `--refresh-cache` to [`checkly test`](/cli/che Checkly automatically retries transient failures during setup steps. Cache downloads retry up to 3 times with exponential backoff. If all attempts fail, the run falls back to a clean install. -### Dependency Cache behavior by location type +### Dependency cache behavior by location type **Public Locations**: Dependency caching is **Always ON**. @@ -268,7 +268,7 @@ Pruning works the same way in a single-package project as in a monorepo. Only re Checkly caches Playwright browsers so that runs don't download them every time. How caching works depends on which location your checks run. -### Browser caching on Public Locations +### Browser caching on public locations Checkly caches Playwright browsers across all public regions to reduce startup time. When a new Playwright version is available, runs download browsers until Checkly updates the shared cache. @@ -281,7 +281,7 @@ Browser caching requires private location agent v8.2.0 or later. -## Troubleshooting Dependency Installation +## Troubleshooting dependency installation ### Package not found diff --git a/detect/synthetic-monitoring/playwright-checks/internal-registries.mdx b/detect/synthetic-monitoring/playwright-checks/internal-registries.mdx index 1f64f6c9c..1bb194632 100644 --- a/detect/synthetic-monitoring/playwright-checks/internal-registries.mdx +++ b/detect/synthetic-monitoring/playwright-checks/internal-registries.mdx @@ -1,7 +1,7 @@ --- -title: 'Packages from Internal Registries in Playwright Check Suites' +title: 'Packages from internal registries in Playwright Check Suites' description: 'Install private packages from registries Checkly cannot reach, such as registries behind your firewall or VPN, by embedding them in the code bundle, pruning what the runner installs, or routing installs to other registries.' -sidebarTitle: 'Internal Registries' +sidebarTitle: 'Internal registries' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/playwright-checks/internal-registries/' --- diff --git a/detect/synthetic-monitoring/playwright-checks/overview.mdx b/detect/synthetic-monitoring/playwright-checks/overview.mdx index a4bf7b346..070dc4c63 100644 --- a/detect/synthetic-monitoring/playwright-checks/overview.mdx +++ b/detect/synthetic-monitoring/playwright-checks/overview.mdx @@ -39,7 +39,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/playwrigh - Detect issues in critical business processes - Verify functionality after deployments -## How Playwright Check Suites Work +## How Playwright Check Suites work @@ -58,7 +58,7 @@ Receive notifications when tests fail or performance degrades. -## Test Selection +## Test selection Control which tests run as monitors using: @@ -104,7 +104,7 @@ export default defineConfig({ Learn more about [test organization strategies](/detect/synthetic-monitoring/playwright-checks/test-organization) for selecting and grouping tests. -## Monitoring Configuration +## Monitoring configuration Customize how your checks run: @@ -113,18 +113,18 @@ Customize how your checks run: - **Alerting**: Set up notifications and escalation - **Dependencies**: Use private packages and custom registries (see [Dependencies](/detect/synthetic-monitoring/playwright-checks/dependencies)) -## Getting Started +## Getting started - + Deploy your first Playwright Check Suite - + Construct configuration options and examples - + Organize checks with groups diff --git a/detect/synthetic-monitoring/playwright-checks/quickstart.mdx b/detect/synthetic-monitoring/playwright-checks/quickstart.mdx index 89cc8074d..5c65c1115 100644 --- a/detect/synthetic-monitoring/playwright-checks/quickstart.mdx +++ b/detect/synthetic-monitoring/playwright-checks/quickstart.mdx @@ -56,7 +56,7 @@ npm install --save-dev checkly -## Step 2: Create Your checkly.config.ts +## Step 2: Create your checkly.config.ts Create a `checkly.config.ts` file in your project root. This file defines which tests become monitors and how they run. @@ -90,7 +90,7 @@ export default defineConfig({ }) ``` -## Step 3: Select Tests to Monitor +## Step 3: Select tests to monitor Each entry in the `playwrightChecks` array becomes a separate monitor. Use `pwProjects` or `pwTags` to control which tests each check suite runs. @@ -128,7 +128,7 @@ export default defineConfig({ Per-check `frequency` and `locations` override the global defaults set in Step 2. For strategies on grouping tests by urgency, environment, or feature area, see [Test organization](/detect/synthetic-monitoring/playwright-checks/test-organization). -## Step 4: Test Your Configuration +## Step 4: Test your configuration Before deploying, validate your monitoring setup locally: @@ -165,7 +165,7 @@ npx checkly test --env ENVIRONMENT=staging - `checkly pw-test` - Runs any Playwright tests defined in your `playwright.config.ts`, directly on Checkly's cloud infrastructure. See the [CLI reference](/cli/checkly-pw-test). -## Step 5: Deploy to Production Monitoring +## Step 5: Deploy to production monitoring Deploy your check suites to start continuous monitoring: @@ -184,24 +184,24 @@ Successfully deployed project "my-app-monitoring" to account "My Account". Your monitors run on the configured schedule. View results in your [Checkly dashboard](https://app.checklyhq.com/). -## Best Practices +## Best practices - **Start small** — Begin with 1-2 critical flows. Add more as you understand your monitoring needs. - **Keep suites fast** — Shorter suites mean faster alerts. See [How long should a check suite run?](/detect/synthetic-monitoring/playwright-checks/test-organization#how-long-should-an-ideal-playwright-check-suite-run) for guidance. - **Reuse authentication state** — Use [Playwright project dependencies and `storageState`](/detect/synthetic-monitoring/playwright-checks/test-organization#group-tests-to-reuse-authentication-states) to log in once and share the session across tests. -## Next Steps +## Next steps - + Advanced strategies for organizing test suites - + Set up notifications when checks fail - + Organize checks with groups diff --git a/detect/synthetic-monitoring/playwright-checks/test-organization.mdx b/detect/synthetic-monitoring/playwright-checks/test-organization.mdx index 67ef3b0e2..5cfd70c37 100644 --- a/detect/synthetic-monitoring/playwright-checks/test-organization.mdx +++ b/detect/synthetic-monitoring/playwright-checks/test-organization.mdx @@ -77,11 +77,11 @@ While it's possible to run **all** your Playwright tests as long as your suite r This approach leads to faster Mean Time to Detect (MTTD), overall transparency and more granular monitoring information. -## How to Organize your tests in Playwright Check Suites +## How to organize your tests in Playwright Check Suites Use the `pwProjects` and `pwTags` properties to group and organize your Playwright Check Suites. -### Group your Tests using Playwright Projects (recommended) +### Group your tests using Playwright projects (recommended) Select existing Playwright tests and run them in a Playwright Check Suite by relying on [Playwright projects](https://playwright.dev/docs/test-projects). @@ -139,7 +139,7 @@ Using `pwProjects` creates a custom `testCommand` that includes the exact same ` [Find more Playwright project examples below](#recommendations-and-examples). -### Group your Tests using Playwright tags +### Group your tests using Playwright tags Select existing Playwright tests and run them in a Playwright Check Suite by relying on [Playwright test annotations and tags](https://playwright.dev/docs/test-annotations#tag-tests). @@ -188,7 +188,7 @@ This approach improves the maintainability and separates the Playwright test con Using `pwTags` creates a custom `testCommand` that includes the exact same `npx playwright test --grep @tag` configuration for your check suite to run. -## Recommendations and Examples +## Recommendations and examples Synthetic monitoring with Playwright Check Suites is most effective when you organize your Playwright tests to match your monitoring needs. The best setup depends on your application and how quickly you want to receive alerts. diff --git a/detect/synthetic-monitoring/playwright-checks/timeouts.mdx b/detect/synthetic-monitoring/playwright-checks/timeouts.mdx index 3fb9d4b78..b45b16cbe 100644 --- a/detect/synthetic-monitoring/playwright-checks/timeouts.mdx +++ b/detect/synthetic-monitoring/playwright-checks/timeouts.mdx @@ -1,5 +1,5 @@ --- -title: 'Playwright Check Suite Timeouts' +title: 'Playwright Check Suite timeouts' description: 'Configure and troubleshoot timeouts in Playwright Check Suites.' sidebarTitle: 'Timeouts' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/playwright-checks/timeouts/' diff --git a/detect/synthetic-monitoring/playwright-monitoring-comparison.mdx b/detect/synthetic-monitoring/playwright-monitoring-comparison.mdx index 83414003a..4395b0ee6 100644 --- a/detect/synthetic-monitoring/playwright-monitoring-comparison.mdx +++ b/detect/synthetic-monitoring/playwright-monitoring-comparison.mdx @@ -1,7 +1,7 @@ --- -title: 'Playwright Monitoring Options' +title: 'Playwright monitoring options' description: 'Compare the features of the different Playwright-based checks' -sidebarTitle: 'Playwright Monitoring Options' +sidebarTitle: 'Playwright monitoring options' canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/playwright-monitoring-comparison/' --- diff --git a/detect/testing/creating-your-first-test.mdx b/detect/testing/creating-your-first-test.mdx index 3c4a7faf4..93b2cc45f 100644 --- a/detect/testing/creating-your-first-test.mdx +++ b/detect/testing/creating-your-first-test.mdx @@ -1,7 +1,7 @@ --- -title: 'Creating Your First Test' +title: 'Creating your first test' description: 'Get started with Checkly by creating and running your first Playwright test for application monitoring' -sidebarTitle: 'Creating Your First Test' +sidebarTitle: 'Creating your first test' canonical: 'https://www.checklyhq.com/docs/detect/testing/creating-your-first-test/' --- @@ -16,7 +16,7 @@ Checkly enables you to transform your existing Playwright tests into powerful sy -## Step 1: Initialize Your Project +## Step 1: Initialize your project In your project folder, set up Checkly using the CLI: @@ -32,7 +32,7 @@ This command will: You'll first be asked whether your AI agent should set up Checkly. Answer yes to install the Checkly skill for your AI coding agent, or no to set up the project yourself and add the demo checks. -## Step 2: Project Structure +## Step 2: Project structure After initialization, your project will have the following structure: @@ -48,7 +48,7 @@ my-checkly-project/ └── README.md ``` -## Step 3: Configure Your Project +## Step 3: Configure your project Open `checkly.config.ts` to configure your monitoring setup: @@ -81,7 +81,7 @@ export default defineConfig({ }) ``` -## Step 4: Write Your First Test +## Step 4: Write your first test Create a new Playwright test file in the `__checks__` directory: @@ -109,7 +109,7 @@ test('Homepage loads successfully', async ({ page }) => { ``` -## Step 5: Test Your Checks +## Step 5: Test your checks Before deploying, run your checks on Checkly to make sure they pass: @@ -130,7 +130,7 @@ npx checkly test --env ENVIRONMENT_URL="https://staging.example.com" - Generate screenshots, videos, and traces - Provide detailed output and debugging information -## Step 6: Deploy Your Checks +## Step 6: Deploy your checks Deploy your checks so Checkly runs them on a schedule: @@ -138,7 +138,7 @@ Deploy your checks so Checkly runs them on a schedule: npx checkly deploy ``` -## Step 7: View Results +## Step 7: View results After deployment, you can: - View check results in the [Checkly dashboard](https://app.checklyhq.com) @@ -146,7 +146,7 @@ After deployment, you can: - Access detailed traces and screenshots - Monitor performance trends over time -## Advanced Check Configuration +## Advanced check configuration For more control over your Browser checks: @@ -169,7 +169,7 @@ new BrowserCheck('advanced-check', { }) ``` -## Best Practices +## Best practices 1. **Start Simple**: Begin with basic page load tests before adding complex interactions 2. **Use Page Object Model**: Organize your tests with reusable page objects @@ -182,7 +182,7 @@ new BrowserCheck('advanced-check', { ## Troubleshooting -### Common Issues +### Common issues **Check fails locally but works in browser:** - Verify selectors are stable @@ -205,7 +205,7 @@ test.use({ storageState: 'auth.json' }) - Join the [Checkly community](https://www.checklyhq.com/slack) - Review example projects on [GitHub](https://github.com/checkly) -## Next Steps +## Next steps Once you have your first test running: diff --git a/detect/testing/overview.mdx b/detect/testing/overview.mdx index c923313fc..7a244b8e0 100644 --- a/detect/testing/overview.mdx +++ b/detect/testing/overview.mdx @@ -26,23 +26,23 @@ Checkly combines testing and monitoring into one workflow. With Checkly, you can - Plan recurring test execution on a schedule - Run tests from [Checkly's global locations](/concepts/locations) -## Test Types +## Test types Create a single test and use it for both pre-production validation and production monitoring: - + Simple HTTP requests to verify your API endpoints are responding correctly. Create an [API test](/detect/synthetic-monitoring/api-checks/overview) - + Advanced tests that chain multiple API requests in sequence, without a browser. Create a [Multi-step test](/detect/synthetic-monitoring/multistep-checks/overview) - + Full browser automation to test complex user interactions and workflows. Create a [Browser test](/detect/synthetic-monitoring/browser-checks/overview) diff --git a/detect/testing/playwright-reporter-changelog.mdx b/detect/testing/playwright-reporter-changelog.mdx index 979cd8458..a1b97b829 100644 --- a/detect/testing/playwright-reporter-changelog.mdx +++ b/detect/testing/playwright-reporter-changelog.mdx @@ -1,6 +1,6 @@ --- -title: Playwright Reporter Changelog -sidebarTitle: Reporter Changelog +title: Playwright reporter changelog +sidebarTitle: Reporter changelog description: Release history for the Checkly Playwright Reporter rss: true canonical: 'https://www.checklyhq.com/docs/detect/testing/playwright-reporter-changelog/' diff --git a/detect/testing/playwright-reporter.mdx b/detect/testing/playwright-reporter.mdx index c8d1d4ae1..d3c34dddc 100644 --- a/detect/testing/playwright-reporter.mdx +++ b/detect/testing/playwright-reporter.mdx @@ -1,7 +1,7 @@ --- -title: 'Playwright Reporter' +title: 'Playwright reporter' description: 'Learn how to use the Checkly Playwright Reporter.' -sidebarTitle: 'Using the Playwright Reporter' +sidebarTitle: 'Using the Playwright reporter' canonical: 'https://www.checklyhq.com/docs/detect/testing/playwright-reporter/' --- @@ -21,7 +21,7 @@ Before using the Playwright reporter, ensure you have: - A Checkly account ([sign up](https://app.checklyhq.com/signup)) -## Install the Playwright Reporter +## Install the Playwright reporter Install [the Playwright reporter package](https://www.npmjs.com/package/@checkly/playwright-reporter) via npm. @@ -29,9 +29,9 @@ Install [the Playwright reporter package](https://www.npmjs.com/package/@checkly npm install --save-dev @checkly/playwright-reporter ``` -## Quick Start +## Quick start -### 1. Create an API key and get your Account ID +### 1. Create an API key and get your account ID Authenticate the reporter with your Checkly Account ID and an API Key: @@ -100,7 +100,7 @@ chromium 3 3 0 0 0 100.00% ## Configuration -### Reporter Options +### Reporter options ```ts playwright.config.ts import { defineConfig } from '@playwright/test'; @@ -172,11 +172,11 @@ export default defineConfig({ **Security Note**: Always use environment variables for credentials. Never commit API keys to version control. -## Secret Scrubbing +## Secret scrubbing The reporter automatically removes sensitive values from reports, trace files, and logs before upload. Scrubbing is enabled by default. -### What Gets Scrubbed +### What gets scrubbed | Category | What is redacted | Default behavior | |----------|-----------------|------------------| @@ -226,7 +226,7 @@ export default defineConfig({ | `sensitiveHeaders` | `string[] \| false` | Built-in list | Redact sensitive HTTP headers; pass an array for a custom list, or `false` to disable | | `replacement` | `string` | `'*********'` | Replacement text for scrubbed values | -### Disabling Scrubbing +### Disabling scrubbing Disable all scrubbing: @@ -250,7 +250,7 @@ createChecklyReporter({ Secret scrubbing applies to the JSON report, trace files, and reporter log entries. Values are replaced before upload and never appear in Checkly. -## What Gets Uploaded +## What gets uploaded - Test results and status (passed/failed/flaky) - Execution duration and timing @@ -284,13 +284,13 @@ View your results at [app.checklyhq.com/test-sessions](https://app.checklyhq.com ## Features -### Real-time Test Progress +### Real-time test progress Shows test results as they run with status icons and error details. Similar to Playwright's `list` reporter with Checkly integration. Set `showProgress: false` when using another reporter for terminal output. -### Summary Table +### Summary table Displays a summary table with per-project breakdown of test results. Set `showSummaryTable: false` to disable. @@ -301,7 +301,7 @@ firefox 10 10 0 0 0 100.00% webkit 10 8 2 0 0 80.00% ``` -### Multi-Provider Git Detection +### Multi-provider Git detection Automatically detects git information (branch, commit, author) from: @@ -309,11 +309,11 @@ Automatically detects git information (branch, commit, author) from: - Jenkins, Azure DevOps, Bitbucket Pipelines - Local git repository (when running locally) -### Test Step Source Code +### Test step source code Includes source code context in test step reports. View the exact line of code that executed with surrounding context for easier debugging. -## Dry Run Mode +## Dry run mode Skip uploading to Checkly while still generating local files: @@ -339,7 +339,7 @@ createChecklyReporter({ Dry runs will create a `checkly-report.zip` in your output directory for local inspection. -## CI/CD Integration +## CI/CD integration @@ -419,7 +419,7 @@ jobs: -## Multiple Reporters +## Multiple reporters Combine with other Playwright reporters: diff --git a/detect/uptime-monitoring/dns-monitors/configuration.mdx b/detect/uptime-monitoring/dns-monitors/configuration.mdx index f03dc5317..5d9dbd002 100644 --- a/detect/uptime-monitoring/dns-monitors/configuration.mdx +++ b/detect/uptime-monitoring/dns-monitors/configuration.mdx @@ -9,7 +9,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/dns-monitors To configure a DNS monitor using code, learn more about the [DNS monitor construct](/constructs/dns-monitor). */} -### Basic Setup +### Basic setup Specify the domain and record type you want to check: @@ -51,7 +51,7 @@ The raw and JSON responses are shown on the results page of a DNS monitor run an Learn more about JSON path assertions: [JSON responses with JSON path](/detect/assertions/#json-responses-with-json-path). -### JSON Response Schemas +### JSON response schemas The DNS response is parsed into a structured JSON format. All responses share a common structure: @@ -81,7 +81,7 @@ The DNS response is parsed into a structured JSON format. All responses share a - `AD` - Authenticated data flag - `CD` - Checking disabled flag - + ```json { "Answer": [ @@ -116,7 +116,7 @@ Common assertions: - `$.Answer[0].TTL` - Validate TTL value - + ```json { "Answer": [ @@ -142,7 +142,7 @@ Common assertions: - `$.Answer[0].TTL` - Validate TTL value - + ```json { "Answer": [ @@ -167,7 +167,7 @@ Common assertions: - `$.Answer[0].data` - Verify canonical name target - + ```json { "Answer": [ @@ -198,7 +198,7 @@ Common assertions: - `$.Answer[0].data` - Check MX priority and mail server (format: "priority hostname") - + ```json { "Answer": [ @@ -224,7 +224,7 @@ Common assertions: - Text response contains `v=spf1` - Check for SPF record - + ```json { "Answer": [ @@ -255,7 +255,7 @@ Common assertions: - `$.Answer[0].data` - Check specific nameserver - + ```json { "Answer": [ @@ -283,7 +283,7 @@ Common assertions: - Text response contains expected serial number - + HTTPS records carry [SvcParams](https://www.rfc-editor.org/rfc/rfc9460) — the parameters a browser uses to connect over HTTP/3 on its first request (`alpn`, `ipv4hint`/`ipv6hint`, `ech`, …). The whole record is rendered into the `data` @@ -327,7 +327,7 @@ scopes the match to the advertised protocols. **Record type support**: DNS monitors currently support A, AAAA, CNAME, MX, NS, SOA, TXT, and HTTPS record types. Additional record types (SRV, CAA, PTR, etc.) may be added in future updates. -### Response Time Limits +### Response time limits Define performance thresholds for degraded or failed states: @@ -345,7 +345,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours): DNS monitor frequency selection interface -### Scheduling & Locations +### Scheduling & locations DNS monitor scheduling strategy and location selection interface @@ -355,7 +355,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours): * **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling) * **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from -### Additional Settings +### 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) @@ -363,7 +363,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours): * **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries) * **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 +## Common use cases **Scenario**: Your CDN provides multiple IP addresses for redundancy. You need to ensure all IPs are reachable. diff --git a/detect/uptime-monitoring/dns-monitors/overview.mdx b/detect/uptime-monitoring/dns-monitors/overview.mdx index 486de393b..5bad7b9b6 100644 --- a/detect/uptime-monitoring/dns-monitors/overview.mdx +++ b/detect/uptime-monitoring/dns-monitors/overview.mdx @@ -96,7 +96,7 @@ Select a specific check run to inspect its results: * **Response payload:** Displays the raw DNS response and the [parsed JSON output](/detect/uptime-monitoring/dns-monitors/configuration#json-response-schemas) for assertions and debugging -## Troubleshooting Common Issues +## Troubleshooting common issues **Symptom**: DNS updated but users still reach old infrastructure diff --git a/detect/uptime-monitoring/grpc-monitors/configuration.mdx b/detect/uptime-monitoring/grpc-monitors/configuration.mdx index 9cc405b8f..8e1d74a54 100644 --- a/detect/uptime-monitoring/grpc-monitors/configuration.mdx +++ b/detect/uptime-monitoring/grpc-monitors/configuration.mdx @@ -9,7 +9,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/grpc-monitor To configure a gRPC monitor using code, learn more about the [gRPC monitor construct](/constructs/grpc-monitor). -### Basic Setup +### Basic setup Configure your gRPC monitor by specifying the target service and monitoring mode: @@ -19,11 +19,11 @@ Configure your gRPC monitor by specifying the target service and monitoring mode * **TLS**: Whether to use TLS encryption for the connection (default: enabled). Disable for plaintext connections. * **Skip SSL verification**: Skip TLS certificate validation. Useful for servers with self-signed certificates in non-production environments. -### Monitoring Mode +### Monitoring mode Choose between two monitoring modes: -#### BEHAVIOR Mode (default) +#### BEHAVIOR mode (default) Invokes a unary gRPC method and asserts on the response. Requires: @@ -34,7 +34,7 @@ Invokes a unary gRPC method and asserts on the response. Requires: * **Request message**: Optional JSON-encoded payload sent as the gRPC request body * **Metadata**: Optional key/value pairs sent as gRPC request headers (e.g. `authorization: Bearer {{MY_TOKEN}}`) -#### HEALTH Mode +#### HEALTH mode Calls `grpc.health.v1.Health/Check` using the standard gRPC health-check protocol. Useful for monitoring overall server health without invoking a specific application method. @@ -57,7 +57,7 @@ You can create assertions based on: For more details, see our documentation on [Assertions](/detect/assertions). -### Response Time Limits +### Response time limits Set performance thresholds for your gRPC service: @@ -70,12 +70,12 @@ The maximum allowed threshold is 180,000 ms (3 minutes), matching the maximum ca Set how often the monitor runs (every 10 seconds to 24 hours). -### Scheduling & Locations +### Scheduling & locations * **Strategy**: Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling) * **Locations**: Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from -### Additional Settings +### 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) diff --git a/detect/uptime-monitoring/heartbeat-monitors/configuration.mdx b/detect/uptime-monitoring/heartbeat-monitors/configuration.mdx index 215326b55..74c1b1a8a 100644 --- a/detect/uptime-monitoring/heartbeat-monitors/configuration.mdx +++ b/detect/uptime-monitoring/heartbeat-monitors/configuration.mdx @@ -1,11 +1,11 @@ --- -title: Heartbeat Configuration +title: Heartbeat configuration description: Ensure your critical automated processes are running as expected. sidebarTitle: Configuration canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/heartbeat-monitors/configuration/' --- -### Additional Settings +### 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) diff --git a/detect/uptime-monitoring/heartbeat-monitors/examples.mdx b/detect/uptime-monitoring/heartbeat-monitors/examples.mdx index 4fae5ca44..1a3c0e472 100644 --- a/detect/uptime-monitoring/heartbeat-monitors/examples.mdx +++ b/detect/uptime-monitoring/heartbeat-monitors/examples.mdx @@ -1,5 +1,5 @@ --- -title: 'Heartbeat Examples' +title: 'Heartbeat examples' description: 'Implementation examples for sending heartbeat pings to monitor your scheduled jobs.' sidebarTitle: Examples canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/heartbeat-monitors/examples/' @@ -17,9 +17,9 @@ Before diving into specific examples, remember these key principles: Checkly records that a ping arrived, plus its `User-Agent` and `Origin` or `Referer` header. A request body is ignored, so any job metadata sent in the examples below isn't stored in Checkly. -## Shell Scripts and Command Line +## Shell scripts and command line -### Basic cURL Examples +### Basic cURL examples The most common way to ping Heartbeat monitors from shell scripts: @@ -61,7 +61,7 @@ fi ``` -### wget Alternative +### wget alternative If cURL isn't available, use wget instead: @@ -90,7 +90,7 @@ wget -T 5 -t 3 -q -O /dev/null \ echo "Backup completed successfully!" ``` -## Platform-Specific Integrations +## Platform-specific integrations ### Heroku Scheduler @@ -101,7 +101,7 @@ Monitor Heroku scheduled tasks: run_task.sh && curl -m 5 --retry 3 https://ping.checklyhq.com/your-heartbeat-id ``` -### Render Cron Jobs +### Render cron jobs For Render cron job services: @@ -118,7 +118,7 @@ if [ $? -eq 0 ]; then fi ``` -### Railway Cron Jobs +### Railway cron jobs Similar pattern for Railway scheduled deployments: @@ -128,9 +128,9 @@ npm run data-sync && \ curl -m 5 --retry 3 https://ping.checklyhq.com/your-heartbeat-id ``` -## Kubernetes Cron Jobs +## Kubernetes cron jobs -### Basic CronJob with Heartbeat +### Basic CronJob with heartbeat ```yaml apiVersion: batch/v1 @@ -173,7 +173,7 @@ spec: restartPolicy: OnFailure ``` -### Advanced CronJob with Sidecar +### Advanced CronJob with sidecar For more complex scenarios, use a sidecar pattern: @@ -226,7 +226,7 @@ spec: ## Node.js and JavaScript -### Built-in HTTPS Module +### Built-in HTTPS module ```typescript TypeScript @@ -387,7 +387,7 @@ async function pingHeartbeat(source) { ``` -### Fetch API (Modern Browsers/Node.js 18+) +### Fetch API (modern browsers/Node.js 18+) ```javascript async function pingHeartbeat(url, source = null) { @@ -427,7 +427,7 @@ async function pingHeartbeat(url, source = null) { } ``` -## Vercel Cron Jobs +## Vercel cron jobs Monitor your Vercel cron jobs across different routing patterns: @@ -552,9 +552,9 @@ export async function GET({ request }) { ``` -## Python Examples +## Python examples -### Using Requests Library +### Using requests library ```python Basic Example @@ -703,7 +703,7 @@ def backup_database(): ``` -### Django Management Commands +### Django management commands ```python # management/commands/send_newsletter.py @@ -740,7 +740,7 @@ class Command(BaseCommand): raise ``` -## PowerShell Examples +## PowerShell examples For Windows environments and Azure functions: @@ -838,9 +838,9 @@ try { ``` -## Advanced Patterns +## Advanced patterns -### Conditional Heartbeats +### Conditional heartbeats Sometimes you only want to ping under certain conditions: @@ -862,7 +862,7 @@ def conditional_heartbeat_example(): print(f"Skipped heartbeat - only processed {results['processed_count']} items") ``` -### Multi-Step Job Monitoring +### Multi-step job monitoring For complex jobs with multiple phases: @@ -914,10 +914,10 @@ echo "All steps completed successfully" ## Troubleshooting -### Common Issues +### Common issues - + **Problem**: Pings fail due to network timeouts or slow connections. **Solution**: Always configure timeouts and retries: @@ -930,7 +930,7 @@ curl --connect-timeout 10 -m 30 --retry 3 https://ping.checklyhq.com/your-id ``` - + **Problem**: Pings are ignored due to blocked user agents. **Blocked user agents**: Twitterbot, Slackbot, Googlebot, Discordbot, Facebot, TelegramBot, WhatsApp, LinkedInBot @@ -941,7 +941,7 @@ curl -A "MyApp/1.0" https://ping.checklyhq.com/your-id ``` - + **Problem**: Using unsupported HTTP methods. **Supported**: GET, POST @@ -958,7 +958,7 @@ requests.put(heartbeat_url) ``` - + **Problem**: Pings sent even when job fails. **Solution**: Structure your code correctly: @@ -982,7 +982,7 @@ finally: -### Testing Your Implementation +### Testing your implementation Before deploying, test your heartbeat integration: diff --git a/detect/uptime-monitoring/heartbeat-monitors/overview.mdx b/detect/uptime-monitoring/heartbeat-monitors/overview.mdx index e4609549c..d5e45371e 100644 --- a/detect/uptime-monitoring/heartbeat-monitors/overview.mdx +++ b/detect/uptime-monitoring/heartbeat-monitors/overview.mdx @@ -49,7 +49,7 @@ The heartbeat monitoring process is straightforward. Once created, your Heartbea 3. **Add the ping** - Include a simple HTTP request in your task's success path 4. **Monitor results** - Checkly tracks pings and alerts you if a ping is missed or delayed -## Grace Period +## Grace period The **grace period** provides extra time before alerting. @@ -60,7 +60,7 @@ Choose grace periods based on: - Acceptable delay before you need to know about failures - Time needed for any retries or recovery processes -## Timer Behavior +## Timer behavior The heartbeat timer works predictably: @@ -115,7 +115,7 @@ The state indicates when your scheduled job pinged the Heartbeat monitor, relati The source shows where your ping originated, determined by the `origin` and `referer` request headers. -## Best Practices +## Best practices **Always include timeout and retry options:** ```bash diff --git a/detect/uptime-monitoring/heartbeat-monitors/quickstart.mdx b/detect/uptime-monitoring/heartbeat-monitors/quickstart.mdx index 5de0cf0a6..c8bfec793 100644 --- a/detect/uptime-monitoring/heartbeat-monitors/quickstart.mdx +++ b/detect/uptime-monitoring/heartbeat-monitors/quickstart.mdx @@ -33,17 +33,17 @@ Before creating your Heartbeat monitor, make sure you have: -## Step 1: Basic Configuration +## Step 1: Basic configuration Start by giving your monitor a descriptive name and relevant tags and description. Choose something descriptive that clearly identifies what the monitor is tracking, like "Nightly Database Backup" or "Weekly Reports Job". Use tags to group related monitors and make them easier to find and manage. -## Step 2: Timing Configuration +## Step 2: Timing configuration The timing configuration is the heart of your Heartbeat monitor. You need to specify when you expect pings and how much flexibility to allow. -### Period Setting +### Period setting The **period** defines how often your task should ping Checkly: @@ -53,7 +53,7 @@ The **period** defines how often your task should ping Checkly: ![Configure period and grace settings for your Heartbeat monitor](/images/heartbeat-monitors/getting-started-period-and-grace.png) -### Grace Period +### Grace period The **grace period** provides extra time before alerting, compensating for natural variance in job execution times: @@ -63,7 +63,7 @@ The **grace period** provides extra time before alerting, compensating for natur - **Hourly sync job** with 5-minute grace → Alert if ping is more than 5 minutes late - + Grace periods compensate for natural variance in job execution times. For example: - **Daily backup at 2 AM** with 30-minute grace → Alert if no ping by 2:30 AM @@ -76,7 +76,7 @@ Choose grace periods based on: - Time needed for any retries or recovery processes - + The heartbeat timer works predictably: - **First ping starts the timer** - When you send the first ping, monitoring begins @@ -89,7 +89,7 @@ This means if your job is supposed to run every 6 hours but runs late at hour 7, ![Understanding how grace periods and timing work in heartbeat monitoring](/images/heartbeat-monitors/heartbeats-grace.jpg) - + **Consider Your Job Variance** - How much does your job's runtime vary? @@ -104,7 +104,7 @@ This means if your job is supposed to run every 6 hours but runs late at hour 7, -## Step 3: Alert Configuration +## Step 3: Alert configuration Connect your Heartbeat monitor to [alert channels](/communicate/alerts/overview) to be notified when pings are missing. @@ -123,7 +123,7 @@ Connect your Heartbeat monitor to [alert channels](/communicate/alerts/overview) - **Medium priority**: Slack + Email - **High priority**: PagerDuty + Slack + Email -### Alert Timing +### Alert timing Configure when alerts should fire: @@ -133,16 +133,16 @@ Configure when alerts should fire: All alert channels subscribed to the monitor are notified at the same time. -## Step 4: Ping URL and Implementation +## Step 4: Ping URL and implementation Once created, your Heartbeat monitor provides a unique ping URL. Your tasks should make an HTTP `GET` or `POST` request to this URL when they complete successfully. -## Step 5: Testing Your Setup +## Step 5: Testing your setup Before deploying to production, test your Heartbeat monitor: -### Manual Testing +### Manual testing You can manually send pings through the Checkly interface to: @@ -159,10 +159,10 @@ You can also send manual pings directly from your monitors list using the quick ![Quick ping option in the heartbeat monitors list view](/images/heartbeat-monitors/heartbeat-ping-quick-menu.png) -## Common Configuration Patterns +## Common configuration patterns - + ```typescript import { HeartbeatMonitor } from 'checkly/constructs' @@ -178,7 +178,7 @@ new HeartbeatMonitor('daily-backup-monitor', { ``` - + ```typescript import { HeartbeatMonitor } from 'checkly/constructs' @@ -194,7 +194,7 @@ new HeartbeatMonitor('weekly-report-monitor', { ``` - + ```typescript import { HeartbeatMonitor } from 'checkly/constructs' @@ -212,7 +212,7 @@ new HeartbeatMonitor('hourly-sync-monitor', { -## Best Practices for Pings +## Best practices for pings **Always include timeout and retry options:** ```bash diff --git a/detect/uptime-monitoring/icmp-monitors/configuration.mdx b/detect/uptime-monitoring/icmp-monitors/configuration.mdx index 514b42034..d4fd21fa2 100644 --- a/detect/uptime-monitoring/icmp-monitors/configuration.mdx +++ b/detect/uptime-monitoring/icmp-monitors/configuration.mdx @@ -5,7 +5,7 @@ sidebarTitle: 'Configuration' canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/icmp-monitors/configuration/' --- -### Basic Setup +### Basic setup Configure your ICMP monitor by specifying the target host: @@ -17,7 +17,7 @@ Configure your ICMP monitor by specifying the target host: * **IP family:** Choose between IPv4 (default) or IPv6 * **Pings per run:** Number of ICMP Echo Request packets to send per check run (1-50, default: 10) -### Packet Loss Limits +### Packet loss limits Define packet loss thresholds to determine when an ICMP monitor should be considered degraded or failed: @@ -46,7 +46,7 @@ You can create assertions based on: Learn more about JSON path assertions: [JSON responses with JSON path](/detect/assertions/#json-responses-with-json-path). -### JSON Response Schema +### JSON response schema The ICMP response is parsed into a structured JSON format. All responses share a common structure: @@ -89,7 +89,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours): ICMP monitor frequency selection interface -### Scheduling & Locations +### Scheduling & locations ICMP monitor scheduling strategy and location selection interface @@ -99,7 +99,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours): * **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling) * **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from -### Additional Settings +### 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) diff --git a/detect/uptime-monitoring/icmp-monitors/overview.mdx b/detect/uptime-monitoring/icmp-monitors/overview.mdx index eaf2869ea..d0596ad70 100644 --- a/detect/uptime-monitoring/icmp-monitors/overview.mdx +++ b/detect/uptime-monitoring/icmp-monitors/overview.mdx @@ -82,7 +82,7 @@ The monitor's overview page aggregates historical run data, allowing you to anal Learn more in our documentation on [Results](/concepts/results). -## Troubleshooting Common Issues +## Troubleshooting common issues Container runtimes drop `NET_RAW` by default. ICMP monitors need raw sockets, so the Checkly Agent needs this capability explicitly granted. diff --git a/detect/uptime-monitoring/overview.mdx b/detect/uptime-monitoring/overview.mdx index d55bb1d90..1dcbf2bd3 100644 --- a/detect/uptime-monitoring/overview.mdx +++ b/detect/uptime-monitoring/overview.mdx @@ -1,5 +1,5 @@ --- -title: 'Uptime Monitoring' +title: 'Uptime monitoring' description: 'Monitor your application uptime and availability with Checkly' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/overview/' @@ -19,7 +19,7 @@ Uptime monitoring is essential for ensuring your applications are always availab alt="Uptime monitor overview" /> -## Types of Uptime Monitors +## Types of uptime monitors Choose the Uptime Monitor that best fits your monitoring needs: @@ -53,7 +53,7 @@ Choose the Uptime Monitor that best fits your monitoring needs: -## Benefits of Uptime Monitoring +## Benefits of uptime monitoring Uptime monitoring continuously checks if your applications and services are accessible and responding correctly. Typical use cases include: - Ensuring your marketing site returns a 200 OK diff --git a/detect/uptime-monitoring/ssl-monitors/configuration.mdx b/detect/uptime-monitoring/ssl-monitors/configuration.mdx index 490e54495..48fa1f15c 100644 --- a/detect/uptime-monitoring/ssl-monitors/configuration.mdx +++ b/detect/uptime-monitoring/ssl-monitors/configuration.mdx @@ -9,7 +9,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/ssl-monitors To configure an SSL monitor using code, learn more about the [SSL monitor construct](/constructs/ssl-monitor). -### Basic Setup +### Basic setup Configure your SSL monitor by specifying the target host: @@ -17,7 +17,7 @@ Configure your SSL monitor by specifying the target host: * **Port:** The TCP port to connect to. Defaults to `443`. * **IP family:** Choose between IPv4 (default) or IPv6. -### SSL Configuration +### SSL configuration Fine-grained control over the TLS handshake behavior: @@ -29,7 +29,7 @@ Fine-grained control over the TLS handshake behavior: * **Skip chain validation:** When enabled, Checkly does not verify the certificate chain against trusted roots. The certificate is still inspected for expiry and the security baseline. Use this when monitoring internal or self-signed certificates. -### Client Certificate / mTLS +### Client certificate / mTLS SSL monitors can present a client certificate during the TLS handshake to verify mTLS-protected endpoints: @@ -40,7 +40,7 @@ Omit `clientCertificateMode` to connect without a client certificate (the defaul Client certificates are stored at the account level under **Settings → Client Certificates**. -### Security Baseline +### Security baseline The security baseline is a configurable rule set that evaluates the negotiated TLS session against best-practice requirements. It runs on each successful handshake and certificate verification, and produces a **verdict** (`pass` / `warn` / `fail`) and a **grade** (`A-`, `B`, or `F`). It is skipped when an earlier step fails (e.g. hostname mismatch or chain untrusted). @@ -126,7 +126,7 @@ Certificate validity, minimum TLS version and minimum key size are also enforced For more details, see our documentation on [Assertions](/detect/assertions). -### Response Time Limits +### Response time limits Set performance thresholds based on the TLS handshake duration: @@ -137,12 +137,12 @@ Set performance thresholds based on the TLS handshake duration: Set how often the monitor runs. SSL monitors run at most **once per minute** (every 1 minute to 24 hours) — sub-minute frequencies aren't available, since certificate state changes slowly. -### Scheduling & Locations +### Scheduling & locations * **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). * **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from. -### Additional Settings +### 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). diff --git a/detect/uptime-monitoring/ssl-monitors/overview.mdx b/detect/uptime-monitoring/ssl-monitors/overview.mdx index e6e410714..817cf1480 100644 --- a/detect/uptime-monitoring/ssl-monitors/overview.mdx +++ b/detect/uptime-monitoring/ssl-monitors/overview.mdx @@ -48,7 +48,7 @@ Select a specific check run to inspect its results: Learn more in our documentation on [Results](/concepts/results). -## The Security Baseline +## The security baseline The security baseline is a built-in rule set that evaluates each successful handshake and certificate verification against current best practices without requiring explicit assertions. Rules cover: @@ -74,7 +74,7 @@ The aggregate **grade** is computed from the worst rule outcome: You can override the default severity for each rule or disable the baseline entirely in the [SSL Config](/detect/uptime-monitoring/ssl-monitors/configuration#security-baseline). -## Troubleshooting Common Issues +## Troubleshooting common issues This can happen when a server hosts multiple certificates and the default certificate served to Checkly does not cover the monitored hostname. The runner reports this as failure category `hostname`. Use the **SNI server name** (`serverName`) option in the SSL config to explicitly request the certificate for your hostname. diff --git a/detect/uptime-monitoring/tcp-monitors/configuration.mdx b/detect/uptime-monitoring/tcp-monitors/configuration.mdx index 5925e19e4..f8962a510 100644 --- a/detect/uptime-monitoring/tcp-monitors/configuration.mdx +++ b/detect/uptime-monitoring/tcp-monitors/configuration.mdx @@ -9,7 +9,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/tcp-monitors To configure a TCP monitor using code, learn more about the [TCP monitor construct](/constructs/tcp-monitor). -### Basic Setup +### Basic setup Configure your TCP monitor by specifying the target service: @@ -35,7 +35,7 @@ Use assertions to validate TCP connection timing and response data returned by t For more details, see our documentation on [Assertions](/detect/assertions). -### Response Time Limits +### Response time limits Set performance thresholds to ensure your application meets speed requirements: @@ -56,7 +56,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours). Sub-minute freque TCP monitor frequency selection interface -### Scheduling & Locations +### Scheduling & locations TCP monitor scheduling strategy and location selection interface @@ -65,7 +65,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours). Sub-minute freque * **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling) * **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from -### Additional Settings +### 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) diff --git a/detect/uptime-monitoring/tcp-monitors/quickstart.mdx b/detect/uptime-monitoring/tcp-monitors/quickstart.mdx index 1d4700c61..32dd22a78 100644 --- a/detect/uptime-monitoring/tcp-monitors/quickstart.mdx +++ b/detect/uptime-monitoring/tcp-monitors/quickstart.mdx @@ -13,7 +13,7 @@ This guide walks you through creating your first TCP monitor to check the availa TCP monitors verify the availability of non-HTTP services by establishing a connection to a specific host and port. -## Basic Setup +## Basic setup Configure your TCP monitor by specifying the target service: @@ -35,7 +35,7 @@ Add assertions on the response time or response data of your TCP request: TCP monitor assertions table with response time and response data sources -## Response Validation +## Response validation Validate the service response for more precise monitoring: @@ -54,7 +54,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours): TCP monitor frequency selection interface -## Scheduling & Locations +## Scheduling & locations TCP monitor scheduling strategy and location selection interface @@ -63,7 +63,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours): * **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling#scheduling-strategies) * **Locations:** Select [public](/concepts/locations) or [private](/platform/private-locations/overview) locations to run the monitor from -## Additional Settings +## 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) diff --git a/detect/uptime-monitoring/traceroute-monitors/configuration.mdx b/detect/uptime-monitoring/traceroute-monitors/configuration.mdx index 7830d9244..aea7af116 100644 --- a/detect/uptime-monitoring/traceroute-monitors/configuration.mdx +++ b/detect/uptime-monitoring/traceroute-monitors/configuration.mdx @@ -9,7 +9,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/traceroute-m To configure a Traceroute monitor using code, learn more about the [Traceroute monitor construct](/constructs/traceroute-monitor). -### Basic Setup +### Basic setup Configure your Traceroute monitor by specifying the target host and probe parameters: @@ -34,7 +34,7 @@ You can create assertions based on: For more details, see [Assertions](/detect/assertions). -### Response Time Limits +### Response time limits Set performance thresholds based on final-hop latency: @@ -45,7 +45,7 @@ Set performance thresholds based on final-hop latency: Response-time thresholds apply to the **final-hop average RTT**, not the total check execution time. If the destination is not reached, the monitor is marked as failed regardless of these thresholds. -### JSON Response Schema +### JSON response schema The Traceroute response is available as structured JSON. These are the key fields (a few internal bookkeeping fields are omitted here, and fields marked as omitted are absent from the JSON rather than empty): @@ -98,12 +98,12 @@ The Traceroute response is available as structured JSON. These are the key field Set how often the monitor runs. Traceroute monitors run at most **once every 30 seconds** (every 30 seconds to 24 hours) — the two sub-30-second frequencies aren't available. -### Scheduling & Locations +### Scheduling & locations * **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling) * **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from -### Additional Settings +### 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) diff --git a/detect/uptime-monitoring/traceroute-monitors/overview.mdx b/detect/uptime-monitoring/traceroute-monitors/overview.mdx index 11b2ae5d0..3b0e369a6 100644 --- a/detect/uptime-monitoring/traceroute-monitors/overview.mdx +++ b/detect/uptime-monitoring/traceroute-monitors/overview.mdx @@ -60,7 +60,7 @@ Select a specific check run to inspect its results: Learn more in our documentation on [Results](/concepts/results). -## Troubleshooting Common Issues +## Troubleshooting common issues **Symptom**: `destinationReached` is `false`, yet the website or API responds normally. diff --git a/detect/uptime-monitoring/url-monitors/configuration.mdx b/detect/uptime-monitoring/url-monitors/configuration.mdx index 230da618b..ecc6a31cf 100644 --- a/detect/uptime-monitoring/url-monitors/configuration.mdx +++ b/detect/uptime-monitoring/url-monitors/configuration.mdx @@ -5,7 +5,7 @@ sidebarTitle: 'Configuration' canonical: 'https://www.checklyhq.com/docs/detect/uptime-monitoring/url-monitors/configuration/' --- -### Basic Setup +### Basic setup Monitor public URLs by specifying the endpoint you want to track. @@ -30,7 +30,7 @@ Use assertions to validate the status code of your URL request. When one or more For more details, see our documentation on [Assertions](/detect/assertions). -### Response Time Limits +### Response time limits Set performance thresholds to ensure your application meets speed requirements: @@ -52,7 +52,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours). Sub-minute freque URL monitor frequency selection interface showing available check intervals -### Scheduling Strategy +### Scheduling strategy Choose when and how your checks run across multiple locations: @@ -92,7 +92,7 @@ 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 | -### Alert Settings +### Alert settings Configure notifications for your team: @@ -100,7 +100,7 @@ Configure notifications for your team: URL monitor alert settings interface showing notification configuration options -#### Notification Scope +#### Notification scope Choose how alerts are configured for this monitor: @@ -109,7 +109,7 @@ Choose how alerts are configured for this monitor: | **Use global account notification settings** | Inherit notification preferences from Global Notification Settings | | **Use specific notification settings** | Configure alert behavior exclusively for this check | -#### Escalation Rules +#### Escalation rules Control when alerts are triggered: @@ -142,7 +142,7 @@ Define where notifications are sent when checks fail or recover. Additional chan **Global Alert Settings**: By default, monitors inherit your account's notification preferences. Select "Use specific notification settings" to customize alerts for individual monitors. -### Additional Settings +### 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) diff --git a/detect/uptime-monitoring/url-monitors/overview.mdx b/detect/uptime-monitoring/url-monitors/overview.mdx index 70491a21a..949a0849b 100644 --- a/detect/uptime-monitoring/url-monitors/overview.mdx +++ b/detect/uptime-monitoring/url-monitors/overview.mdx @@ -43,7 +43,7 @@ URL monitors send HTTP requests to specified URLs and validate availability and Enter the URL you want to monitor. - + Configure the response times and status codes you want to check for. @@ -80,27 +80,27 @@ Each result includes: Learn more in our documentation on [Results](/concepts/results). -## Best Practices +## Best practices - + - **Critical services**: Every 1-2 minutes - **Important services**: Every 5 minutes - **Standard services**: Every 10-15 minutes - **Background services**: Every 30 minutes to 1 hour - + - Choose 2-3 locations covering your user base - Include at least one location near your infrastructure - Consider regulatory requirements for data residency - + - Always check status codes - Set appropriate response time thresholds - Test assertions thoroughly before deployment - + For monitoring as code workflows, use the URL monitor construct to version control your monitoring configuration and deploy alongside your application code. [Learn about URL monitor construct →](/constructs/url-monitor) diff --git a/detect/uptime-monitoring/url-monitors/quickstart.mdx b/detect/uptime-monitoring/url-monitors/quickstart.mdx index 6abd5fb53..feca783d3 100644 --- a/detect/uptime-monitoring/url-monitors/quickstart.mdx +++ b/detect/uptime-monitoring/url-monitors/quickstart.mdx @@ -13,7 +13,7 @@ This guide walks you through creating your first URL monitor to check the availa Each URL monitor is defined by its request configuration, which includes the target URL and how its availability and performance should be validated. -## Basic Setup +## Basic setup Configure your URL monitor by specifying the endpoint and request method: @@ -25,7 +25,7 @@ Configure your URL monitor by specifying the endpoint and request method: * **URL:** The HTTP(S) URL to monitor (e.g. `https://api.example.com`) * **IP family:** Defaults to IPv4 -## Response Validation +## Response validation ### Assertions Validate the returned response status code: @@ -34,7 +34,7 @@ Validate the returned response status code: URL monitor assertions interface showing status code configuration -### Response Performance +### Response performance Define performance thresholds for degraded or failed states: @@ -50,7 +50,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours). -## Scheduling & Locations +## Scheduling & locations URL monitor scheduling strategy interface showing round robin vs fixed schedule options @@ -59,7 +59,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours). * **Scheduling:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling) * **Locations:** Select [public](/concepts/locations) or [private](/platform/private-locations/overview) locations to run the monitor from -## Additional Settings +## 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) diff --git a/guides/agent-driven-repair.mdx b/guides/agent-driven-repair.mdx index 62f8e054c..f7778e8a2 100644 --- a/guides/agent-driven-repair.mdx +++ b/guides/agent-driven-repair.mdx @@ -1,6 +1,6 @@ --- title: Send failed checks to a coding agent -sidebarTitle: Agent-Driven Repair +sidebarTitle: Agent-driven repair description: Start a Claude Code routine from a Checkly webhook alert channel when a check fails. The agent follows a runbook skill, investigates with the Checkly CLI, and opens a pull request for you to review. canonical: 'https://www.checklyhq.com/docs/guides/agent-driven-repair/' --- diff --git a/guides/agentic-workflows.mdx b/guides/agentic-workflows.mdx index a1d6eece9..f96869035 100644 --- a/guides/agentic-workflows.mdx +++ b/guides/agentic-workflows.mdx @@ -1,6 +1,6 @@ --- -title: Control and Configure your Monitoring Infrastructure with AI -sidebarTitle: Controlling Monitoring with Agents +title: Control and configure your monitoring infrastructure with AI +sidebarTitle: Controlling monitoring with agents description: >- Thanks to Checkly's Monitoring as Code approach, LLMs and AI agents can set up, configure and control your entire monitoring setup. canonical: 'https://www.checklyhq.com/docs/guides/agentic-workflows/' diff --git a/guides/alerting.mdx b/guides/alerting.mdx index fe6c18c2c..cbfc38e5b 100644 --- a/guides/alerting.mdx +++ b/guides/alerting.mdx @@ -1,6 +1,6 @@ --- title: Alerting that doesn't wake you up for nothing -sidebarTitle: Alert without the Noise +sidebarTitle: Alert without the noise description: Send failures to the right people, retry blips in place, escalate on consecutive runs, let regions vote, and mute planned deploys, all defined in code with the Checkly CLI. canonical: 'https://www.checklyhq.com/docs/guides/alerting/' --- diff --git a/guides/api-monitoring.mdx b/guides/api-monitoring.mdx index 186df1ea9..6d8ab9c53 100644 --- a/guides/api-monitoring.mdx +++ b/guides/api-monitoring.mdx @@ -1,6 +1,6 @@ --- title: Monitor your API end to end -sidebarTitle: API Monitoring +sidebarTitle: API monitoring description: Turn every endpoint into an API check that asserts on status, headers, and body, tells slow from down, authenticates in a setup script, and cleans up in a teardown. canonical: 'https://www.checklyhq.com/docs/guides/api-monitoring/' --- diff --git a/guides/claude-code-monitoring.mdx b/guides/claude-code-monitoring.mdx index 42b43388c..e0acd7825 100644 --- a/guides/claude-code-monitoring.mdx +++ b/guides/claude-code-monitoring.mdx @@ -1,5 +1,5 @@ --- -title: In-Depth Monitoring With Checkly and Claude Code +title: In-depth monitoring with Checkly and Claude Code sidebarTitle: Using Checkly and Claude Code description: By integrating AI into your development workflow, you can generate valid Checkly constructs—including URL monitors and Playwright-based Browser checks—with minimal effort. @@ -41,7 +41,7 @@ claude mcp add playwright npx @playwright/mcp@latest ``` This will let us ask Claude Code to do things like crawling a particular website and interacting with pages. -## Give Claude Code Some Context +## Give Claude Code some context Everything we write into the CLI interface is part of a 'prompt,' and by default, Claude Code will add a bit of information to what we submit as 'context' on that prompt. Ideally, our requests written into Claude Code would include context about our specific project: its structure, language, and even its purpose. Because of the `npx checkly init` command we ran above, our folder already has a boilerplate version of a Checkly project. We can't feed in all of these files as context, but we can add a summary of our whole project as context by opening Claude Code and running [the slash command](https://docs.anthropic.com/en/docs/claude-code/slash-commands): ```{title="Prompt:"} @@ -92,11 +92,11 @@ While we're writing this simplest of monitors, it's worth testing the limits of Based on the search results, 17 seconds is NOT a valid frequency value for Checkly monitors. The closest valid option was selected: 20 seconds. ``` -## Create Playwright Synthetics Checks With Claude Code +## Create Playwright synthetics checks with Claude Code With our context set up, and a browser available via the Playwright MCP, we can create more complex Playwright scripts for browser monitoring of our site. With specific instructions and clear prompting, you can get consistent performance of Claude Code writing our Browser checks. -### 1. Start With a single test +### 1. Start with a single test First you'll want to write a single check that does straightforward browsing and checking for page elements. With some context engineering, you can instruct Claude to navigate a page while recording the taken actions to generate a Playwright test. Read more about this approach and [extensive prompt guidelines on our blog](https://www.checklyhq.com/blog/generate-end-to-end-tests-with-ai-and-playwright/). @@ -212,7 +212,7 @@ new BrowserCheck('book-detail-visibility-check-v1', { Alternatively, you can deploy a Playwright check without a `.check.ts` configuration file, and the file name will be used as the logical ID. -### 2. Add our new Check to Claude's Context +### 2. Add our new check to Claude's context With this check created, let's add the following lines to your updated `CLAUDE.md` file: @@ -305,7 +305,7 @@ This would change every locator in the check, which may or may not be what you w ``` Once Claude Code added a single `.first()` to the checks written above, everything was passing. If you're having trouble reading the generated tests, take a look at [Checkly's Playwright documentation](https://www.checklyhq.com/learn/playwright/). -### 4. Going Further: Edit Multiple Checks and Configurations +### 4. Going further: Edit multiple checks and configurations Updating checks is another use case that may be useful for larger projects. Try prompting Claude Code with something like: @@ -322,7 +322,7 @@ The url.check.ts and api.check.ts files don't have individual frequency settings Once we're done creating new checks, we can test them with `npx checkly test` like we did above. Then it's time to run them all. -## Deploy With the Checkly CLI +## Deploy with the Checkly CLI In our example, we want to deploy a couple of checks at once, so it's worth checking whether the project is properly set up before deployment. Many problems would have been revealed while running `test`, but if, for example, some checks were unintentionally removed from our project, we'll need to use `deploy` to detect that. Run the `deploy` command with the `-p` preview flag: @@ -383,7 +383,7 @@ AI-assisted coding tools like Claude Code can significantly accelerate the creat While AI can handle much of the boilerplate work, human oversight remains essential for ensuring best practices, refining assertions, and maintaining high-quality monitoring scripts. By combining AI efficiency with developer expertise, teams can achieve comprehensive monitoring coverage in minutes rather than days. -### Further Reading +### Further reading Throughout this tutorial, we added a few lines to the CLAUDE.md context file. In all, those additions were (rewritten for clarity): diff --git a/guides/global-monitoring.mdx b/guides/global-monitoring.mdx index 80eebd8f3..86cc1a4c2 100644 --- a/guides/global-monitoring.mdx +++ b/guides/global-monitoring.mdx @@ -1,6 +1,6 @@ --- title: Why monitoring from around the globe is critical for modern organizations -sidebarTitle: Monitoring around the Globe +sidebarTitle: Monitoring around the globe description: A monitor next to your servers sees your servers. Your users see DNS, CDN edges, transit routes, and regions. Run the same checks from where they are, in parallel, and let the regions vote before you get paged. canonical: 'https://www.checklyhq.com/docs/guides/global-monitoring/' --- diff --git a/guides/keyword-monitoring.mdx b/guides/keyword-monitoring.mdx index c9ac8ec73..d5ea1f049 100644 --- a/guides/keyword-monitoring.mdx +++ b/guides/keyword-monitoring.mdx @@ -1,6 +1,6 @@ --- title: Monitor the content your customers need to see -sidebarTitle: Monitoring Changes in Content +sidebarTitle: Monitoring changes in content description: Assert that your best seller, offer banner, and call to action are on the page, in the right place, exactly once, and that error copy never is, with one Playwright test that runs every five minutes. canonical: 'https://www.checklyhq.com/docs/guides/keyword-monitoring/' --- diff --git a/guides/monitoring-an-openapi-spec.mdx b/guides/monitoring-an-openapi-spec.mdx index ea3ab3fad..824b866e2 100644 --- a/guides/monitoring-an-openapi-spec.mdx +++ b/guides/monitoring-an-openapi-spec.mdx @@ -1,6 +1,6 @@ --- -title: How to Create an API Monitor using an OpenAPI (Swagger) Spec -sidebarTitle: Monitoring an OpenAPI Spec +title: How to create an API monitor using an OpenAPI (Swagger) spec +sidebarTitle: Monitoring an OpenAPI spec description: OpenAPI and Swagger help users design and document APIs in a way that is readable from both humans and machines. As a consequence, they can also be used to generate the code that will run the specified API - both on the provider and consumer side. Can we leverage this same principle to simplify API monitoring? After a brief first look at OpenAPI and Swagger, this article will show how we can quickly use them to monitor a new or existing API. tags: API Monitoring canonical: 'https://www.checklyhq.com/docs/guides/monitoring-an-openapi-spec/' @@ -234,7 +234,7 @@ As we look to increase our endpoint coverage across our APIs, we might want to e 2. Defining our [API checks as code](/guides/structuring-a-checkly-project) to scale our setup. 3. Integrating our API monitoring with [E2E monitoring](/learn/monitoring/end-to-end-monitoring/) for our websites. -## Read More +## Read more
diff --git a/guides/monitoring-ecommerce-apps-using-playwright.mdx b/guides/monitoring-ecommerce-apps-using-playwright.mdx index fe6459f9f..668fc1d69 100644 --- a/guides/monitoring-ecommerce-apps-using-playwright.mdx +++ b/guides/monitoring-ecommerce-apps-using-playwright.mdx @@ -1,6 +1,6 @@ --- title: Monitor a checkout flow -sidebarTitle: Monitoring a Checkout Flow +sidebarTitle: Monitoring a checkout flow description: Cover browse, search, add to cart, and checkout on a shop with a Playwright Check Suite that asserts the order confirmation, uses safe test data, and runs against a per-environment base URL. canonical: 'https://www.checklyhq.com/docs/guides/monitoring-ecommerce-apps-using-playwright/' --- diff --git a/guides/monitoring-ecommerce-apps-using-terraform.mdx b/guides/monitoring-ecommerce-apps-using-terraform.mdx index 88e57a863..edb3d7efa 100644 --- a/guides/monitoring-ecommerce-apps-using-terraform.mdx +++ b/guides/monitoring-ecommerce-apps-using-terraform.mdx @@ -1,6 +1,6 @@ --- title: Monitor a shop with Terraform -sidebarTitle: Monitoring a Shop with Terraform +sidebarTitle: Monitoring a shop with Terraform description: Declare a shop's whole monitoring stack in Terraform with the Checkly provider, from the alert channel and check group to Browser checks loaded from spec files and an API check with body assertions. canonical: 'https://www.checklyhq.com/docs/guides/monitoring-ecommerce-apps-using-terraform/' --- diff --git a/guides/monitoring-the-stripe-api.mdx b/guides/monitoring-the-stripe-api.mdx index 7bfdac8b7..596853012 100644 --- a/guides/monitoring-the-stripe-api.mdx +++ b/guides/monitoring-the-stripe-api.mdx @@ -1,5 +1,5 @@ --- -title: How to monitor the Stripe customer API with Checkly | API Monitoring Examples +title: How to monitor the Stripe customer API with Checkly | API monitoring examples displayTitle: How to monitor the Stripe customer API with Checkly sidebarTitle: Monitoring a Stripe API description: Application Programming Interfaces (APIs) are used throughout software to define interactions between different software applications. In this article we focus on web APIs specifically, taking a look at how they fit in the Jamstack architecture and how we can set up API monitoring in order to make sure they don't break and respond fast. @@ -364,7 +364,7 @@ As we increase our monitoring coverage across our APIs, we can also increase the 2. [Defining our API checks as code](/guides/structuring-a-checkly-project) to scale our setup while lowering maintenance needs. 3. Combining our API checks with [E2E monitoring](/learn/monitoring/end-to-end-monitoring/) for any website or web app service whose API we might be monitoring. -## Read More +## Read more
@@ -375,7 +375,7 @@ As we increase our monitoring coverage across our APIs, we can also increase the Learn end-to-end monitoring with Playwright to test key website flows. - + OpenAPI and Swagger help users design and document APIs in a way that is readable from both humans and machines.
diff --git a/guides/playwright-testing-to-monitoring.mdx b/guides/playwright-testing-to-monitoring.mdx index d0f89d478..2a6245f63 100644 --- a/guides/playwright-testing-to-monitoring.mdx +++ b/guides/playwright-testing-to-monitoring.mdx @@ -1,6 +1,6 @@ --- title: Turn your Playwright tests into monitors -sidebarTitle: Turning Tests into Monitors +sidebarTitle: Turning tests into monitors description: Run the Playwright tests you already have as scheduled production monitors with a Playwright Check Suite, without rewriting them. canonical: 'https://www.checklyhq.com/docs/guides/playwright-testing-to-monitoring/' --- diff --git a/guides/reading-traces.mdx b/guides/reading-traces.mdx index 8d9fc0070..856be29dc 100644 --- a/guides/reading-traces.mdx +++ b/guides/reading-traces.mdx @@ -1,6 +1,6 @@ --- title: Debug a failed check -sidebarTitle: Debug a Failed Check +sidebarTitle: Debug a failed check description: Go from a failing Playwright check to its root cause with the Checkly CLI, the Playwright trace in your terminal, and Rocky AI, then confirm the fix with a test run before you deploy. canonical: 'https://www.checklyhq.com/docs/guides/reading-traces/' --- diff --git a/guides/sdlc-monitoring.mdx b/guides/sdlc-monitoring.mdx index b0ea28656..46fe1c75c 100644 --- a/guides/sdlc-monitoring.mdx +++ b/guides/sdlc-monitoring.mdx @@ -1,6 +1,6 @@ --- title: Run checks on every deploy -sidebarTitle: Monitoring Every Release +sidebarTitle: Monitoring every release description: Test pull request previews before merging, trigger deployed checks after production deployments, and record the commit, branch, and environment. canonical: 'https://www.checklyhq.com/docs/guides/sdlc-monitoring/' --- diff --git a/guides/setup-scripts-for-apis.mdx b/guides/setup-scripts-for-apis.mdx index ea828da19..b0baf5d10 100644 --- a/guides/setup-scripts-for-apis.mdx +++ b/guides/setup-scripts-for-apis.mdx @@ -1,8 +1,8 @@ --- -title: How to Use Setup and Teardown Scripts for Better API Monitoring +title: How to use setup and teardown scripts for better API monitoring description: Setup and teardown scripts are fundamental tools to tailor API checks to your target endpoints. This guide presents real-world examples to help you master these tools. tags: API Monitoring -sidebarTitle: Setup and Teardown Scripts +sidebarTitle: Setup and teardown scripts canonical: 'https://www.checklyhq.com/docs/guides/setup-scripts-for-apis/' --- @@ -240,7 +240,7 @@ if (response.statusCode >= 200 && response.statusCode < 300) { ## Read more
- + Full reference for setup and teardown scripts, including built-in variables and technical details. diff --git a/guides/structuring-a-checkly-project.mdx b/guides/structuring-a-checkly-project.mdx index 736f968ba..b5f79be69 100644 --- a/guides/structuring-a-checkly-project.mdx +++ b/guides/structuring-a-checkly-project.mdx @@ -1,6 +1,6 @@ --- title: Structure a Checkly project for a real codebase -sidebarTitle: Structuring a Project +sidebarTitle: Structuring a project description: Organize checks by service with groups, keep shared settings in one config, and deploy monitoring from CI on every merge to main. canonical: 'https://www.checklyhq.com/docs/guides/structuring-a-checkly-project/' --- diff --git a/guides/uptime-monitoring.mdx b/guides/uptime-monitoring.mdx index 3afaab2a0..73a3aeeb4 100644 --- a/guides/uptime-monitoring.mdx +++ b/guides/uptime-monitoring.mdx @@ -1,6 +1,6 @@ --- title: Cover every endpoint with uptime monitors -sidebarTitle: Growing Monitoring Coverage +sidebarTitle: Growing monitoring coverage description: Turn a list of public pages into URL monitors, tell slow from down, and watch the certificate every one of them depends on, all from a few lines of code. canonical: 'https://www.checklyhq.com/docs/guides/uptime-monitoring/' --- diff --git a/index.mdx b/index.mdx index 1067e00b9..01ad87633 100644 --- a/index.mdx +++ b/index.mdx @@ -1,5 +1,5 @@ --- -title: 'Checkly Documentation' +title: 'Checkly documentation' sidebarTitle: 'Home' description: 'The active monitoring layer for engineers and agents. Detect, communicate, and resolve failures with checks defined as code.' mode: "frame" @@ -11,7 +11,7 @@ import { CopyPromptButton } from '/snippets/copy-prompt-button.jsx'; > **For AI agents:** Start with [llms.txt](https://www.checklyhq.com/docs/llms.txt) for the full documentation index. Append `.md` to any docs URL to get its Markdown. To set Checkly up in a project, follow the [Quickstart](https://www.checklyhq.com/docs/quickstart.md). -# Checkly Documentation +# Checkly documentation Checkly is the active monitoring layer for engineers & agents. Detect downtime with Playwright-powered monitors defined in TypeScript running from global or internal locations. Communicate outages with custom alerts and status pages. Resolve errors with traces and AI root cause analysis for new failures. diff --git a/integrations/alerts/discord.mdx b/integrations/alerts/discord.mdx index be5267153..53507963f 100644 --- a/integrations/alerts/discord.mdx +++ b/integrations/alerts/discord.mdx @@ -1,5 +1,5 @@ --- -title: 'Send Alerts to Discord' +title: 'Send alerts to Discord' description: 'Configure Discord integration to receive real-time alerts from Checkly monitors' sidebarTitle: 'Discord' canonical: 'https://www.checklyhq.com/docs/integrations/alerts/discord/' @@ -34,9 +34,9 @@ deliver failure, degradation, and recovery messages to any project in your Disco Congratulations! You have successfully integrated Checkly with Discord! -## Advanced Discord Configuration +## Advanced Discord configuration -### Custom Discord Alerts +### Custom Discord alerts For more control over Discord alert formatting, you can create custom webhook payloads using Discord's embed format: @@ -74,7 +74,7 @@ For more control over Discord alert formatting, you can create custom webhook pa } ``` -### Discord Alert Colors +### Discord alert colors Use different colors to distinguish alert types: @@ -82,7 +82,7 @@ Use different colors to distinguish alert types: - **Orange (16776960)**: Degraded performance alerts - **Green (3066993)**: Recovery notifications -### Discord Best Practices +### Discord best practices - Use separate channels for different environments (production, staging, development) - Configure appropriate notification settings to avoid alert fatigue diff --git a/integrations/alerts/email.mdx b/integrations/alerts/email.mdx index 015e68ab0..c03a91559 100644 --- a/integrations/alerts/email.mdx +++ b/integrations/alerts/email.mdx @@ -1,5 +1,5 @@ --- -title: 'Email Notifications' +title: 'Email notifications' description: 'Configure email alerts for individuals or distribution lists' sidebarTitle: 'Email' canonical: 'https://www.checklyhq.com/docs/integrations/alerts/email/' @@ -24,7 +24,7 @@ Email notifications provide a reliable and widely-supported way to receive alert /> -## Basic Email Configuration +## Basic email configuration To receive alerts, you'll need to add one or more valid email addresses, choose what states you want to receive alerts for, and then also add subscriptions to checks. diff --git a/integrations/alerts/gitlab_alerts.mdx b/integrations/alerts/gitlab_alerts.mdx index 31408c0f0..372f77eb7 100644 --- a/integrations/alerts/gitlab_alerts.mdx +++ b/integrations/alerts/gitlab_alerts.mdx @@ -1,7 +1,7 @@ --- -title: "Integrating GitLab Alerts" +title: "Integrating GitLab alerts" description: "Configure GitLab Alerts integration to receive failure, degradation, and recovery messages from Checkly" -sidebarTitle: "GitLab Alerts" +sidebarTitle: "GitLab alerts" canonical: 'https://www.checklyhq.com/docs/integrations/alerts/gitlab_alerts/' --- diff --git a/integrations/alerts/msteams.mdx b/integrations/alerts/msteams.mdx index af85c8a03..30d5716e8 100644 --- a/integrations/alerts/msteams.mdx +++ b/integrations/alerts/msteams.mdx @@ -1,5 +1,5 @@ --- -title: 'Send Alerts to Microsoft Teams' +title: 'Send alerts to Microsoft Teams' description: 'Configure Microsoft Teams integration to receive failure, degradation, and recovery messages from Checkly' sidebarTitle: 'Microsoft Teams' canonical: 'https://www.checklyhq.com/docs/integrations/alerts/msteams/' diff --git a/integrations/alerts/phone-calls.mdx b/integrations/alerts/phone-calls.mdx index 28d8381b4..926a6f45e 100644 --- a/integrations/alerts/phone-calls.mdx +++ b/integrations/alerts/phone-calls.mdx @@ -1,7 +1,7 @@ --- -title: 'Phone Calls' +title: 'Phone calls' description: 'Configure phone call notifications for critical alerts and emergency escalation' -sidebarTitle: 'Phone Calls' +sidebarTitle: 'Phone calls' canonical: 'https://www.checklyhq.com/docs/integrations/alerts/phone-calls/' --- diff --git a/integrations/alerts/slack.mdx b/integrations/alerts/slack.mdx index 5c9ddff0d..70f07bccc 100644 --- a/integrations/alerts/slack.mdx +++ b/integrations/alerts/slack.mdx @@ -18,7 +18,7 @@ You can add any **#public-channel-name** or **@username** for Direct Messages. E If you're using a free Slack workspace, be aware of [message limits](https://slack.com/help/articles/115002422943-Usage-limits-for-free-workspaces). Exceeding these limits may prevent new alerts from being delivered. -## Example Failed Slack Alert +## Example failed Slack alert For each check and / or monitor, the Slack alert message contains key information, a possible root cause analysis and key actions like rerunning the check. @@ -28,7 +28,7 @@ For each check and / or monitor, the Slack alert message contains key informatio The root cause analysis uses AI to analyze your logs, traces, test source code, error information and other artefacts available to Checkly. Be aware that AI can make mistakes so outputs should be verified independently. -## Example Recovered Slack Alert +## Example recovered Slack alert From the recovered Slack message, you can see the timestamp as well as a link to the check itself. @@ -70,6 +70,6 @@ Checkly requests these Slack permissions for the Checkly Slack app to work withi | `links:read` | Read links for allow-listed domains like [app.checklyhq.com](http://app.checklyhq.com) to provide rich context | | `links:write` | Writes rich context for allow-listed domains like [app.checklyhq.com](http://app.checklyhq.com) | -## Privacy Policy +## Privacy policy For information about how Checkly collects, uses, and protects your data, see our [Privacy Policy](https://checklyhq.com/privacy). \ No newline at end of file diff --git a/integrations/alerts/sms.mdx b/integrations/alerts/sms.mdx index 5eaf16e2c..9fb0e8588 100644 --- a/integrations/alerts/sms.mdx +++ b/integrations/alerts/sms.mdx @@ -1,5 +1,5 @@ --- -title: 'SMS Alerts' +title: 'SMS alerts' description: 'Configure SMS text message notifications for critical alerts and emergency escalation' sidebarTitle: 'SMS' canonical: 'https://www.checklyhq.com/docs/integrations/alerts/sms/' diff --git a/integrations/alerts/telegram.mdx b/integrations/alerts/telegram.mdx index ab7d7cc06..d93582238 100644 --- a/integrations/alerts/telegram.mdx +++ b/integrations/alerts/telegram.mdx @@ -1,5 +1,5 @@ --- -title: 'Send Alerts via Telegram' +title: 'Send alerts via Telegram' description: 'Learn how to send Checkly alerts to Telegram direct chats, groups, and forum topics' sidebarTitle: 'Telegram' canonical: 'https://www.checklyhq.com/docs/integrations/alerts/telegram/' @@ -16,7 +16,7 @@ deliver failure, degradation, and recovery messages to direct chats, groups, and -## Telegram Bot +## Telegram bot 1. Create a **Telegram Bot** using the [@BotFather](https://t.me/botfather). Detailed instructions can be found [here](https://core.telegram.org/bots), however you can simply message the Telegram user `@BotFather` and send them the command message `/newbot`. Then follow the instructions the bot replies with. @@ -32,13 +32,13 @@ deliver failure, degradation, and recovery messages to direct chats, groups, and For direct messages, you can retrieve your user Chat ID with an ID bot. For groups and forum topics, query the Telegram API to retrieve the target group's Chat ID and optional Message Thread ID. -#### ID Bot +#### ID bot You can retrieve your own Telegram Chat ID by starting a chat with another bot. This Telegram bot user can be found at `@get_id_bot`. 1. Send the `@get_id_bot` bot the `/my_id` command. Copy the ID from its reply. -#### API Query +#### API query Use the bot API to retrieve a Chat ID for any target chat. For a forum group, the same response includes the Message Thread ID, which Telegram also calls the topic ID. @@ -71,7 +71,7 @@ Use the bot API to retrieve a Chat ID for any target chat. For a forum group, th The `getUpdates` method does not work while your bot has an outgoing webhook configured. In that case, retrieve these fields from the update sent to your webhook. -## Checkly Integration +## Checkly integration With the **HTTP API Token**, **Chat ID**, and optional **Message Thread ID** in hand, you can create a Telegram alert channel in Checkly. @@ -94,16 +94,16 @@ Congratulations! You have successfully integrated Checkly with Telegram! Telegram also accepts messages via an HTTP `GET` request. Therefore, you can use the API Token and Chat ID to create a custom Telegram alert channel with a [webhook alert channel](/integrations/alerts/webhooks). The webhook should use the `GET` method and target `https://api.telegram.org/bot/sendMessage?chat_id=&text=Your%20Alert%20Title`. To target a forum topic, add `&message_thread_id=` before the `text` parameter. See Telegram's [`sendMessage` documentation](https://core.telegram.org/bots/api#sendmessage) for more information. -## Telegram Best Practices +## Telegram best practices -### Group vs Direct Messages +### Group vs direct messages - **Direct Messages**: Use your personal chat ID for personal notifications - **Group Chats**: Add the bot to group chats and use the group's Chat ID for team notifications - **Forum Topics**: Use the group's Chat ID together with the topic's Message Thread ID - **Channels**: Bots can post to channels if added as administrators -### Message Formatting +### Message formatting Checkly sends Telegram messages with HTML formatting (`parse_mode=HTML`), so use HTML tags such as ``, `` and `` in your payload. Markdown syntax is shown as plain text. @@ -119,7 +119,7 @@ Error: {{CHECK_ERROR_MESSAGE}} View Details ``` -### Security Considerations +### Security considerations - **Bot Token Security**: Keep your bot tokens secure and never share them publicly - **Chat ID Privacy**: Chat IDs can be sensitive information, especially for private groups diff --git a/integrations/alerts/webhooks.mdx b/integrations/alerts/webhooks.mdx index 58fb28e9b..1f240e652 100644 --- a/integrations/alerts/webhooks.mdx +++ b/integrations/alerts/webhooks.mdx @@ -1,5 +1,5 @@ --- -title: "Webhook Integrations" +title: "Webhook integrations" description: "Create custom webhook integrations to send Checkly alerts to any API endpoint" sidebarTitle: "Webhooks" canonical: 'https://www.checklyhq.com/docs/integrations/alerts/webhooks/' @@ -19,7 +19,7 @@ Webhooks allow you to POST custom payloads to any endpoint in your own infrastru - Create a **custom payload body** using any environment variables and specific instance variables per event. Note: that means that if you are attaching the webhook to a Group, you will be able to access Group-level variables, too. - **Debug and test the webhook** in the editor by sending test messages. -## Using Variables +## Using variables The example above shows a webhook configured to create a Jira ticket on each event. Notice the following: @@ -90,7 +90,7 @@ When [automatic Rocky AI analysis](/resolve/ai-root-cause-analysis/overview#auto } ``` -### Handlebars Helpers +### Handlebars helpers Webhook templates support [Handlebars built-in helpers](https://handlebarsjs.com/guide/builtin-helpers.html), such as `if`, `unless`, and `each`, as well as these Checkly helpers: @@ -170,7 +170,7 @@ Two clear benefits here: - You only need to create one webhook to inform a 3rd party system. - You can translate Checkly terms to your 3rd party tool's term for the same concept, i.e. the "up status" of a check. -## Webhook Secrets +## Webhook secrets You can validate each webhook we deliver to your endpoint(s). Using the optional webhook secret, you can: @@ -263,13 +263,13 @@ def webhook(request): -## Webhook Retries +## Webhook retries Checkly will retry your webhook up to **5 times** if the request fails, for example with an HTTP response higher than 399 (such as a 404 or 503), a network error, or no response within 5 seconds. Retries back off exponentially: 10, 20, 40, 80 and 160 seconds, about 5 minutes in total. This means that for checks on a 1 minute schedule, there is a potential overlap between a failure alert and recovery alert. For this reason every webhook we send has a timestamp in the `x-checkly-timestamp` header. You can use this timestamp on the receiving end to ignore any webhooks that come in "late". -## Webhook Examples +## Webhook examples The following examples give an idea how to integrate Checkly with 3rd party alerting and issue tracking systems. diff --git a/integrations/ci-cd/gitlab/overview.mdx b/integrations/ci-cd/gitlab/overview.mdx index 574896539..73706f956 100644 --- a/integrations/ci-cd/gitlab/overview.mdx +++ b/integrations/ci-cd/gitlab/overview.mdx @@ -5,7 +5,7 @@ sidebarTitle: GitLab canonical: 'https://www.checklyhq.com/docs/integrations/ci-cd/gitlab/overview/' --- -## A Basic GitLab Pipeline Example +## A basic GitLab pipeline example Create a new `.gitlab-ci.yml` file in your repo, or add the steps and stages from the example below to your existing file. This pipeline is "branch aware" and treats the `main` branch as the production branch. This means checks are only deployed diff --git a/integrations/ci-cd/jenkins/overview.mdx b/integrations/ci-cd/jenkins/overview.mdx index db52f6c58..88edeb9fc 100644 --- a/integrations/ci-cd/jenkins/overview.mdx +++ b/integrations/ci-cd/jenkins/overview.mdx @@ -20,7 +20,7 @@ You can also set these data items specifically by using environment variables. -## A Basic pipeline example +## A basic pipeline example Create a new Jenkinsfile in your repo, or add the steps and stages from the example below to your existing file. This pipeline is "branch aware" and treats the `main` branch as the production branch. This means checks are only deployed @@ -45,7 +45,7 @@ Store them as "secret text" and assign and ID to the credential. ![Jenkins Nodejs config](/images/docs/images/cicd/cicd_jenkins_credentials.png) -## Configuring the Jenkins Pipeline +## Configuring the Jenkins pipeline Add the `Jenkinsfile` to your repo that defines the basic stages and steps. Make sure to set up your SCM settings correctly so Jenkins can fetch your git repo and look for the `Jenkinsfile` in the root of your project. diff --git a/integrations/ci-cd/overview.mdx b/integrations/ci-cd/overview.mdx index a3760bb1f..ae3c98e11 100644 --- a/integrations/ci-cd/overview.mdx +++ b/integrations/ci-cd/overview.mdx @@ -17,18 +17,18 @@ Regardless of the provider or platform you use, integrating Checkly into your CI With this approach, you can validate your application and infrastructure before deploying to production, staging or any other environments. Simultaneously , you can life cycle (create/update/delete) your checks from your code base as part of your CI/CD workflow. -## CI/CD Integration with the Checkly CLI +## CI/CD integration with the Checkly CLI The preferred and most flexible way to integrate Checkly with your CI/CD is through the [Checkly CLI](/cli/overview). -## CI/CD Integration using vendor webhooks +## CI/CD integration using vendor webhooks - [Vercel](/integrations/ci-cd/vercel/overview) - [GitHub deployment hooks](/integrations/ci-cd/github/deployments) -## CI/CD Basics +## CI/CD basics We've optimized the [Checkly CLI](/cli/overview) to work in any CI/CD workflow. Here are the basics you need to know that will come in handy when adapting the examples we give you to your own, specific setup. diff --git a/integrations/ci-cd/vercel/deployment-protection.mdx b/integrations/ci-cd/vercel/deployment-protection.mdx index 4c613fd49..0b5132168 100644 --- a/integrations/ci-cd/vercel/deployment-protection.mdx +++ b/integrations/ci-cd/vercel/deployment-protection.mdx @@ -1,7 +1,7 @@ --- title: Vercel Deployment Protection description: "Let Checkly's Browser checks reach protected Vercel preview and production deployments by passing a Protection Bypass for Automation secret in your tests." -sidebarTitle: Deployment Protection +sidebarTitle: Deployment protection canonical: 'https://www.checklyhq.com/docs/integrations/ci-cd/vercel/deployment-protection/' --- @@ -13,7 +13,7 @@ so we can validate your preview branches before they reach production and contin Vercel has a few different ways to authenticate your deployments. Each work a bit different. We will go over each of them below. -## Bypass for Automation +## Bypass for automation You can fully bypass any deployment protection using Vercel's [Protection Bypass for Automation feature](https://vercel.com/docs/security/deployment-protection/methods-to-bypass-deployment-protection/protection-bypass-automation). With this feature, you can provide a secret in an HTTP header or query parameter to bypass any deployment protection. @@ -51,14 +51,14 @@ For an API check you can do something similar request.headers['x-vercel-protection-bypass'] = process.env.VERCEL_BYPASS_TOKEN ``` -## Vercel Authentication +## Vercel authentication Vercel has a few different ways to authenticate your deployments. Each work a bit different and require a different approach to make them work with Checkly. > Vercel enables **Standard Protection** by default on all new deployments. -### Standard Protection +### Standard protection [Standard Protection](https://vercel.com/docs/concepts/deployments/deployment-protection#vercel-authentication) works by prompting the user to log in to Vercel with their normal Vercel user before they can access the deployment. @@ -119,7 +119,7 @@ You will have to supply your GitHub username and password as environment variabl the code example) to your Checkly account or as part of the [Browser check's environment variables](/platform/variables). -### Only Preview Deployments +### Only preview deployments [Only Preview Deployments](https://vercel.com/docs/concepts/deployments/deployment-protection#vercel-authentication) is the same as Standard Protection, but only applies to Preview deployments. This means that we need to tweak the above code @@ -183,7 +183,7 @@ explore bypassing 2FA using the `otpauth` library. [Check our blog post for more -## Password Protection +## Password protection Vercel's [Password Protection](https://vercel.com/docs/concepts/deployments/deployment-protection#password-protection) is a paid addon that allows you to set a dedicated password for your deployments and specifically bypass protection for E2E tests / automation. You can accomplish this using the resources referenced in the docs for [Browser checks](/detect/synthetic-monitoring/browser-checks/examples#username--password-login) diff --git a/integrations/ci-cd/vercel/managing-plan.mdx b/integrations/ci-cd/vercel/managing-plan.mdx index f61131301..45f84d517 100644 --- a/integrations/ci-cd/vercel/managing-plan.mdx +++ b/integrations/ci-cd/vercel/managing-plan.mdx @@ -1,7 +1,7 @@ --- -title: Managing Users and Plans with Vercel +title: Managing users and plans with Vercel description: "Manage Checkly users, plans, and billing through Vercel's native integration, adding team members and adjusting your plan from the Vercel dashboard." -sidebarTitle: Managing Users and Plans +sidebarTitle: Managing users and plans canonical: 'https://www.checklyhq.com/docs/integrations/ci-cd/vercel/managing-plan/' --- diff --git a/integrations/ci-cd/vercel/overview.mdx b/integrations/ci-cd/vercel/overview.mdx index 0919523c1..78acbcd3a 100644 --- a/integrations/ci-cd/vercel/overview.mdx +++ b/integrations/ci-cd/vercel/overview.mdx @@ -17,7 +17,7 @@ Checkly offers two integrations for Vercel users: Using Vercel deployment protection? Read [this section](/integrations/ci-cd/vercel/deployment-protection) on how to make this work with Checkly. -## Installing the Marketplace Integration +## Installing the Marketplace integration To install Checkly's managed Vercel integration, navigate to the [integration's marketplace listing](https://vercel.com/integrations/checkly) and click `Install`. @@ -54,7 +54,7 @@ Once the project and the check/group have been linked, you are able to specify w Should you wish to unlink the Vercel project, simply click `Unlink this project`. -### Targeting Preview deployments with `ENVIRONMENT_URL` and `ENVIRONMENT_NAME` +### Targeting preview deployments with `ENVIRONMENT_URL` and `ENVIRONMENT_NAME` On each deployment triggered by Vercel, we inject the Checkly runtime with two variables: @@ -177,7 +177,7 @@ So, what does this mean for the blocking heuristics? It means that we will mark For more info on the **Virtual Experience Score** [check the documentation on the Vercel site](https://vercel.com/docs/concepts/analytics/web-vitals#virtual-experience-score). -### Skipping Performance checks +### Skipping performance checks In some cases, Checkly will completely skip performance checks. You will see the "skipped" status in your Vercel deployment overview. Checkly skips performance checks when the domain of the visited URL in the script does not match the domain of the **deployment URL**. In 9 out of 10 cases this should be the URL for your Preview and Production deployments. diff --git a/integrations/iac/pulumi/best-practices.mdx b/integrations/iac/pulumi/best-practices.mdx index f654ea2e5..3c94f2b53 100644 --- a/integrations/iac/pulumi/best-practices.mdx +++ b/integrations/iac/pulumi/best-practices.mdx @@ -1,7 +1,7 @@ --- -title: 'Pulumi Best Practices' +title: 'Pulumi best practices' description: 'Best practices for managing monitoring as code with the Checkly Pulumi provider' -sidebarTitle: 'Best Practices' +sidebarTitle: 'Best practices' canonical: 'https://www.checklyhq.com/docs/integrations/iac/pulumi/best-practices/' --- @@ -12,12 +12,12 @@ This guide covers best practices for effectively managing your Checkly monitorin The code samples on this page only show the properties that matter for each practice. A `checkly.Check` also needs `type`, `activated` and `frequency` (and a `request` for API checks), and a `checkly.CheckGroup` needs `activated` and `concurrency`. See the [Pulumi examples](/integrations/iac/pulumi/examples) for complete resources. -## Resource Management +## Resource management -### Naming Conventions +### Naming conventions - + **Consistent Naming** - Use descriptive, lowercase names with hyphens - Include environment prefixes (dev, staging, prod) @@ -25,7 +25,7 @@ The code samples on this page only show the properties that matter for each prac - Avoid generic names like "check1" or "test" - + **Organized Tagging** - Use consistent tag patterns across resources - Include environment, team, and purpose tags @@ -55,7 +55,7 @@ new checkly.Check('check1', { name: 'Test' }) new checkly.Check('my_check', { name: 'My Check' }) ``` -### Resource Organization +### Resource organization Organize your Pulumi code into logical modules and use check groups to maintain clear relationships between related resources. @@ -82,9 +82,9 @@ apiChecks.forEach(check => { }) ``` -## Security Best Practices +## Security best practices -### Secret Management +### Secret management Never commit API keys, passwords, or other sensitive information directly in your Pulumi code or version control. @@ -119,10 +119,10 @@ const apiKey = config.requireSecret('apiKey') const accountId = config.require('accountId') ``` -### Access Control +### Access control - + **Secure API Keys** - Use dedicated API keys for Pulumi - Rotate keys regularly @@ -130,7 +130,7 @@ const accountId = config.require('accountId') - Monitor key usage - + **Team Permissions** - Use Pulumi organizations for team collaboration - Implement role-based access control @@ -139,9 +139,9 @@ const accountId = config.require('accountId') -## Environment Management +## Environment management -### Stack Strategy +### Stack strategy Use separate Pulumi stacks for different environments to maintain isolation and enable environment-specific configurations. @@ -180,7 +180,7 @@ const envConfig = { const currentConfig = envConfig[environment] ``` -### Configuration Management +### Configuration management Use Pulumi's configuration system to manage environment-specific settings and avoid hardcoding values. @@ -198,12 +198,12 @@ pulumi config set apiUrl https://staging-api.example.com --stack staging pulumi config set apiUrl https://api.example.com --stack prod ``` -## Monitoring Strategy +## Monitoring strategy -### Check Frequency Optimization +### Check frequency optimization - + **High Frequency** - 1-5 minute intervals for critical APIs - Multiple locations for redundancy @@ -211,7 +211,7 @@ pulumi config set apiUrl https://api.example.com --stack prod - Comprehensive assertions - + **Lower Frequency** - 10-30 minute intervals for non-critical services - Single location monitoring @@ -220,7 +220,7 @@ pulumi config set apiUrl https://api.example.com --stack prod -### Location Strategy +### Location strategy ```javascript // Critical service - multiple locations @@ -238,7 +238,7 @@ new checkly.Check('admin-dashboard', { }) ``` -### Assertion Best Practices +### Assertion best practices **Comprehensive API checks:** ```javascript @@ -278,9 +278,9 @@ new checkly.Check('comprehensive-api-check', { }) ``` -## Code Organization +## Code organization -### Modular Structure +### Modular structure Organize your Pulumi code into logical modules to improve maintainability and reusability. @@ -325,7 +325,7 @@ function createApiChecks(environment) { module.exports = { createApiChecks } ``` -### Reusable Functions +### Reusable functions ```javascript // utils/helpers.js @@ -356,9 +356,9 @@ function createStandardApiCheck(name, url, options = {}) { module.exports = { createStandardApiCheck } ``` -## CI/CD Integration +## CI/CD integration -### Automated Deployments +### Automated deployments @@ -410,9 +410,9 @@ jobs: CHECKLY_API_KEY: ${{ secrets.CHECKLY_API_KEY }} ``` -## Testing and Validation +## Testing and validation -### Preview Changes +### Preview changes Always use `pulumi preview` before deploying to understand what changes will be made to your infrastructure. @@ -426,24 +426,24 @@ pulumi preview --stack prod pulumi preview --stack prod --show-replacement-steps ``` -### Validation Strategies +### Validation strategies - + - Validate environment variables are set - Check API key permissions - Verify account ID format - Test connectivity to Checkly API - + - Verify check configurations - Test alert channel connectivity - Validate check group assignments - Confirm location availability - + - Monitor initial check runs - Verify alert channel notifications - Check resource relationships @@ -451,9 +451,9 @@ pulumi preview --stack prod --show-replacement-steps -## Performance Considerations +## Performance considerations -### Resource Limits +### Resource limits Be mindful of Checkly's resource limits and pricing when creating large numbers of checks or high-frequency monitoring. @@ -488,9 +488,9 @@ endpoints.forEach(endpoint => { }) ``` -## Maintenance and Updates +## Maintenance and updates -### Regular Reviews +### Regular reviews Schedule regular reviews of your monitoring infrastructure to ensure it remains effective and up-to-date. @@ -517,25 +517,25 @@ Maintain comprehensive documentation of your monitoring infrastructure, includin - Troubleshooting guides - Change management procedures -## Common Pitfalls to Avoid +## Common pitfalls to avoid - + **Problem**: Manual changes in Checkly UI create drift with Pulumi state **Solution**: Always manage resources through Pulumi or document manual changes - + **Problem**: Committing secrets to version control **Solution**: Use environment variables and Pulumi's secret management - + **Problem**: Too many checks or too frequent monitoring **Solution**: Focus on critical paths and optimize check frequencies - + **Problem**: Unclear or inconsistent resource names **Solution**: Establish and follow naming conventions diff --git a/integrations/iac/pulumi/ci-cd.mdx b/integrations/iac/pulumi/ci-cd.mdx index 8ae9e4b1f..e951cf679 100644 --- a/integrations/iac/pulumi/ci-cd.mdx +++ b/integrations/iac/pulumi/ci-cd.mdx @@ -1,7 +1,7 @@ --- -title: 'CI/CD Integration' +title: 'CI/CD integration' description: 'Integrate Pulumi with CI/CD pipelines for automated monitoring infrastructure deployments' -sidebarTitle: 'CI/CD Integration' +sidebarTitle: 'CI/CD integration' canonical: 'https://www.checklyhq.com/docs/integrations/iac/pulumi/ci-cd/' --- @@ -15,7 +15,7 @@ CI/CD integration enables you to automatically deploy monitoring changes when co - + **Continuous Deployment** - Deploy monitoring changes automatically - Reduce manual configuration errors @@ -23,7 +23,7 @@ CI/CD integration enables you to automatically deploy monitoring changes when co - Enable rapid iteration - + **Multi-Environment Support** - Separate stacks for each environment - Environment-specific configurations @@ -31,7 +31,7 @@ CI/CD integration enables you to automatically deploy monitoring changes when co - Consistent monitoring across environments - + **Secure Deployments** - Secure secret management - Role-based access control @@ -39,7 +39,7 @@ CI/CD integration enables you to automatically deploy monitoring changes when co - Compliance with security policies - + **Team Workflows** - Code review for monitoring changes - Pull request-based deployments @@ -50,10 +50,10 @@ CI/CD integration enables you to automatically deploy monitoring changes when co ## GitHub Actions -### Basic Workflow +### Basic workflow - + ```yaml .github/workflows/deploy.yml name: Deploy Monitoring Infrastructure @@ -125,7 +125,7 @@ jobs: -### Multi-Environment Workflow +### Multi-environment workflow ```yaml .github/workflows/multi-env.yml name: Deploy Monitoring Infrastructure @@ -165,7 +165,7 @@ jobs: PULUMI_ACCESS_TOKEN: ${{ secrets.PULUMI_ACCESS_TOKEN }} ``` -### Advanced Workflow with Testing +### Advanced workflow with testing ```yaml .github/workflows/pipeline.yml name: Monitoring Infrastructure Pipeline @@ -284,7 +284,7 @@ jobs: ## GitLab CI/CD -### Basic Pipeline +### Basic pipeline ```yaml .gitlab-ci.yml stages: @@ -710,9 +710,9 @@ workflows: only: main ``` -## Security Best Practices +## Security best practices -### Secret Management +### Secret management @@ -723,7 +723,7 @@ workflows: - Use least-privilege access - + **Role-Based Access** - Limit deployment permissions - Use separate accounts for different environments @@ -732,10 +732,10 @@ workflows: -### Security Checklist +### Security checklist - + - [ ] Store secrets in CI/CD platform's secret management - [ ] Use environment-specific secrets - [ ] Rotate API keys regularly @@ -743,7 +743,7 @@ workflows: - [ ] Never log or expose secrets - + - [ ] Implement approval gates for production - [ ] Use separate accounts for environments - [ ] Limit who can trigger deployments @@ -751,7 +751,7 @@ workflows: - [ ] Use branch protection rules - + - [ ] Validate code before deployment - [ ] Use trusted base images - [ ] Scan for vulnerabilities @@ -762,10 +762,10 @@ workflows: ## Troubleshooting -### Common Issues +### Common issues - + **Problem**: Pulumi or Checkly authentication fails **Solutions**: - Verify API keys are correctly set in secrets @@ -774,7 +774,7 @@ workflows: - Test authentication locally first - + **Problem**: Pipeline lacks permissions to deploy **Solutions**: - Check CI/CD platform permissions @@ -783,7 +783,7 @@ workflows: - Review branch protection rules - + **Problem**: Resources already exist or conflict **Solutions**: - Use `pulumi refresh` to sync state diff --git a/integrations/iac/pulumi/examples.mdx b/integrations/iac/pulumi/examples.mdx index a61443119..1b96add58 100644 --- a/integrations/iac/pulumi/examples.mdx +++ b/integrations/iac/pulumi/examples.mdx @@ -1,5 +1,5 @@ --- -title: 'Pulumi Examples' +title: 'Pulumi examples' description: 'Comprehensive examples for different check types and configurations using the Checkly Pulumi provider' sidebarTitle: 'Examples' canonical: 'https://www.checklyhq.com/docs/integrations/iac/pulumi/examples/' @@ -10,7 +10,7 @@ This page provides comprehensive examples of how to use the Checkly Pulumi provi ## Basic API checks -### Simple GET Request +### Simple GET request @@ -67,7 +67,7 @@ new checkly.Check('simple-get-api', { -### POST Request with JSON Body +### POST request with JSON body @@ -152,7 +152,7 @@ new checkly.Check('post-api-check', { ## Browser checks -### Basic Page Load Check +### Basic page load check @@ -213,7 +213,7 @@ new checkly.Check('basic-browser-check', { -### Login Flow Check +### Login flow check @@ -294,7 +294,7 @@ new checkly.Check('login-flow-check', { ## Check groups -### Organizing Related Checks +### Organizing related checks @@ -581,9 +581,9 @@ new checkly.Check('critical-api', { -## Advanced Configurations +## Advanced configurations -### Environment-Specific Configurations +### Environment-specific configurations @@ -690,10 +690,10 @@ new checkly.Check('environment-aware-check', { -## Best Practices +## Best practices - + **Consistent Naming** - Use descriptive names for resources - Include environment prefixes @@ -701,7 +701,7 @@ new checkly.Check('environment-aware-check', { - Use consistent tagging strategies - + **Logical Grouping** - Group related checks together - Use check groups for organization @@ -717,7 +717,7 @@ new checkly.Check('environment-aware-check', { - Implement least-privilege access - + **Effective Monitoring** - Define clear success criteria - Use appropriate check frequencies diff --git a/integrations/iac/pulumi/overview.mdx b/integrations/iac/pulumi/overview.mdx index 3d769e1e3..010697d00 100644 --- a/integrations/iac/pulumi/overview.mdx +++ b/integrations/iac/pulumi/overview.mdx @@ -1,7 +1,7 @@ --- -title: 'The Checkly Pulumi Provider' +title: 'The Checkly Pulumi provider' description: 'Learn about the Checkly Pulumi Provider' -sidebarTitle: 'Pulumi Provider' +sidebarTitle: 'Pulumi provider' canonical: 'https://www.checklyhq.com/docs/integrations/iac/pulumi/overview/' --- @@ -133,7 +133,7 @@ $ pulumi config set checkly:apiKey cu_xxx --secret $ pulumi config set checkly:accountId xxx ``` -### Install the Checkly Pulumi Provider +### Install the Checkly Pulumi provider Install the Checkly Pulumi provider (`@checkly/pulumi`) with `yarn` or `npm` to integrate it in your new project. diff --git a/integrations/iac/pulumi/setup.mdx b/integrations/iac/pulumi/setup.mdx index fcda425d0..ecdf97a51 100644 --- a/integrations/iac/pulumi/setup.mdx +++ b/integrations/iac/pulumi/setup.mdx @@ -1,7 +1,7 @@ --- -title: 'Pulumi Setup Guide' +title: 'Pulumi setup guide' description: 'Detailed setup instructions for Pulumi CLI and Checkly integration' -sidebarTitle: 'Setup Guide' +sidebarTitle: 'Setup guide' canonical: 'https://www.checklyhq.com/docs/integrations/iac/pulumi/setup/' --- @@ -20,7 +20,7 @@ Before starting, ensure you have: ## Step 1: Install Pulumi CLI - + Select your preferred installation method based on your operating system and package manager @@ -28,12 +28,12 @@ Select your preferred installation method based on your operating system and pac Run the appropriate installation command for your system - + Confirm Pulumi CLI is working correctly -### Installation Options +### Installation options ```bash install-pulumi-brew @@ -45,7 +45,7 @@ curl -fsSL https://get.pulumi.com | sh ``` -### Verify Installation +### Verify installation ```bash verify-installation pulumi version @@ -56,15 +56,15 @@ You should see output similar to: v3.100.0 ``` -## Step 2: Pulumi Account Setup +## Step 2: Pulumi account setup -### Create Account +### Create account 1. Visit [app.pulumi.com/signup](https://app.pulumi.com/signup) 2. Sign up with your preferred method (GitHub, GitLab, etc.) 3. Complete the account verification process -### Generate Access Token +### Generate access token 1. Navigate to [app.pulumi.com/account/tokens](https://app.pulumi.com/account/tokens) 2. Click "Create token" @@ -89,15 +89,15 @@ Verify your login: pulumi whoami ``` -## Step 3: Checkly API Configuration +## Step 3: Checkly API configuration -### Get Your Account ID +### Get your account ID 1. Log into [app.checklyhq.com](https://app.checklyhq.com) 2. Navigate to **Settings** → **Account** → **General** 3. Copy your **Account ID** -### Create API Key +### Create API key 1. Go to **Settings** → **User** → **API Keys** 2. Click "Create API Key" @@ -108,15 +108,15 @@ pulumi whoami API keys act with the [role and permissions](/admin/creating-api-key) of the user who created them. Keep them secure and never commit them to version control. -## Step 4: Project Setup +## Step 4: Project setup -### Create Project Directory +### Create project directory ```bash create-project mkdir my-checkly-monitoring && cd my-checkly-monitoring ``` -### Initialize Pulumi Project +### Initialize Pulumi project ```bash init-pulumi-project pulumi new javascript @@ -127,7 +127,7 @@ Follow the prompts: - **Project description**: `Checkly monitoring infrastructure as code` - **Stack name**: `dev` (or your preferred environment name) -### Install Checkly Provider +### Install Checkly provider ```bash install-checkly-npm @@ -139,7 +139,7 @@ yarn add @checkly/pulumi ``` -## Step 5: Configure Authentication +## Step 5: Configure authentication ### Option 1: Environment variables (recommended for development) @@ -156,7 +156,7 @@ Reload your shell or source the profile: source ~/.bashrc # or ~/.zshrc ``` -### Option 2: Pulumi Configuration (Recommended for Teams) +### Option 2: Pulumi configuration (recommended for teams) ```bash setup-pulumi-config pulumi config set checkly:apiKey your_api_key --secret @@ -167,7 +167,7 @@ pulumi config set checkly:accountId your_account_id Using Pulumi configuration is better for team environments as it stores settings with your stack and can be shared across team members. -### Verify Configuration +### Verify configuration Test that your credentials are accessible: @@ -182,7 +182,7 @@ Or check Pulumi config: pulumi config ``` -## Step 6: Create Your First Check +## Step 6: Create your first check ### Update index.js @@ -214,9 +214,9 @@ new checkly.Check('hello-world-api', { }) ``` -## Step 7: Deploy Your Infrastructure +## Step 7: Deploy your infrastructure -### Preview Changes +### Preview changes ```bash preview-changes pulumi preview @@ -236,25 +236,25 @@ When prompted, type `yes` to confirm the deployment. Congratulations! You've successfully set up Pulumi with Checkly and deployed your first monitoring check. -## Step 8: Verify Deployment +## Step 8: Verify deployment 1. Visit your [Checkly dashboard](https://app.checklyhq.com) 2. Navigate to **Checks** 3. You should see your new "Hello World API" check 4. The check should be running and showing as "Passing" -## Next Steps +## Next steps Explore more complex examples and configurations - + Learn best practices for managing monitoring as code - + Set up automated deployments in your CI/CD pipeline @@ -265,10 +265,10 @@ Common issues and solutions ## Troubleshooting -### Common Issues +### Common issues - + If you see authentication errors, verify: - Your Checkly API key is correct and active - Your account ID is correct @@ -276,14 +276,14 @@ If you see authentication errors, verify: - You're logged into Pulumi (`pulumi whoami`) - + If the Checkly provider isn't found: - Ensure you've installed `@checkly/pulumi` - Check your `package.json` for the dependency - Run `npm install` or `yarn install` - + If you get permission errors: - Verify your API key has the necessary permissions - Check that your account ID is correct diff --git a/integrations/iac/terraform/checks-groups.mdx b/integrations/iac/terraform/checks-groups.mdx index f86a79f28..eb3b7889f 100644 --- a/integrations/iac/terraform/checks-groups.mdx +++ b/integrations/iac/terraform/checks-groups.mdx @@ -1,6 +1,6 @@ --- title: 'Checks and groups for Terraform' -sidebarTitle: 'Checks & Groups' +sidebarTitle: 'Checks & groups' description: 'Create and manage Browser checks, API checks, Heartbeat monitors, and check groups using Terraform' canonical: 'https://www.checklyhq.com/docs/integrations/iac/terraform/checks-groups/' --- diff --git a/integrations/iac/terraform/ci-cd.mdx b/integrations/iac/terraform/ci-cd.mdx index 013726919..2375b39bd 100644 --- a/integrations/iac/terraform/ci-cd.mdx +++ b/integrations/iac/terraform/ci-cd.mdx @@ -1,6 +1,6 @@ --- title: 'CI/CD pipelines for Terraform' -sidebarTitle: 'CI/CD Pipelines' +sidebarTitle: 'CI/CD pipelines' description: 'Integrate Terraform with CI/CD tools for automated monitoring setup deployment' canonical: 'https://www.checklyhq.com/docs/integrations/iac/terraform/ci-cd/' --- diff --git a/integrations/iac/terraform/command-line-triggers.mdx b/integrations/iac/terraform/command-line-triggers.mdx index 639f1fe29..5fbc41eac 100644 --- a/integrations/iac/terraform/command-line-triggers.mdx +++ b/integrations/iac/terraform/command-line-triggers.mdx @@ -1,6 +1,6 @@ --- title: 'Command line triggers for Terraform' -sidebarTitle: 'Command line Triggers' +sidebarTitle: 'Command line triggers' description: 'Set up command line triggers to run checks from CI/CD pipelines or programmatically' canonical: 'https://www.checklyhq.com/docs/integrations/iac/terraform/command-line-triggers/' --- diff --git a/integrations/iac/terraform/dashboards.mdx b/integrations/iac/terraform/dashboards.mdx index 1b035b67f..4cd060176 100644 --- a/integrations/iac/terraform/dashboards.mdx +++ b/integrations/iac/terraform/dashboards.mdx @@ -29,7 +29,7 @@ resource "checkly_dashboard" "dashboard-main" { You can see all the configuration options for checks, as well as more examples, on the official Terraform registry [documentation page](https://registry.terraform.io/providers/checkly/checkly/latest/docs/resources/dashboard). -### Private Dashboards +### Private dashboards > Available as of `v1.6.6` diff --git a/integrations/iac/terraform/parameterized-resources.mdx b/integrations/iac/terraform/parameterized-resources.mdx index a8ef2cf22..48a3f9bfa 100644 --- a/integrations/iac/terraform/parameterized-resources.mdx +++ b/integrations/iac/terraform/parameterized-resources.mdx @@ -1,6 +1,6 @@ --- title: 'Parameterized resources in Terraform' -sidebarTitle: 'Parameterized Resources' +sidebarTitle: 'Parameterized resources' description: 'Use Terraform meta-arguments to create multiple resources from parameterized configurations' canonical: 'https://www.checklyhq.com/docs/integrations/iac/terraform/parameterized-resources/' --- diff --git a/integrations/iac/terraform/testing-scripts-locally.mdx b/integrations/iac/terraform/testing-scripts-locally.mdx index 932921d61..28445defe 100644 --- a/integrations/iac/terraform/testing-scripts-locally.mdx +++ b/integrations/iac/terraform/testing-scripts-locally.mdx @@ -1,6 +1,6 @@ --- title: 'Testing Terraform scripts locally' -sidebarTitle: 'Testing Scripts Locally' +sidebarTitle: 'Testing scripts locally' description: 'Run Playwright Test scripts locally for faster development and debugging of Browser checks' canonical: 'https://www.checklyhq.com/docs/integrations/iac/terraform/testing-scripts-locally/' --- diff --git a/integrations/incident-management/firehydrant.mdx b/integrations/incident-management/firehydrant.mdx index 0f8d9d1ac..18dd1aa48 100644 --- a/integrations/incident-management/firehydrant.mdx +++ b/integrations/incident-management/firehydrant.mdx @@ -1,5 +1,5 @@ --- -title: 'Send Alerts to FireHydrant' +title: 'Send alerts to FireHydrant' description: 'Integrate with FireHydrant to create and resolve incidents from Checkly alerts' sidebarTitle: 'FireHydrant' canonical: 'https://www.checklyhq.com/docs/integrations/incident-management/firehydrant/' diff --git a/integrations/incident-management/ilert.mdx b/integrations/incident-management/ilert.mdx index 7283370bb..9f3c25e5d 100644 --- a/integrations/incident-management/ilert.mdx +++ b/integrations/incident-management/ilert.mdx @@ -1,5 +1,5 @@ --- -title: 'Send Alerts to ilert' +title: 'Send alerts to ilert' description: 'Configure ilert integration to monitor incidents from Checkly alerts' sidebarTitle: 'ilert' canonical: 'https://www.checklyhq.com/docs/integrations/incident-management/ilert/' diff --git a/integrations/incident-management/incidentio.mdx b/integrations/incident-management/incidentio.mdx index c506e6601..a1993170c 100644 --- a/integrations/incident-management/incidentio.mdx +++ b/integrations/incident-management/incidentio.mdx @@ -1,5 +1,5 @@ --- -title: 'Send Alerts to Incident.io' +title: 'Send alerts to Incident.io' description: 'Configure Incident.io integration to create and resolve incidents from Checkly alerts' sidebarTitle: 'Incident.io' canonical: 'https://www.checklyhq.com/docs/integrations/incident-management/incidentio/' diff --git a/integrations/incident-management/opsgenie.mdx b/integrations/incident-management/opsgenie.mdx index fc809e360..bf39151d8 100644 --- a/integrations/incident-management/opsgenie.mdx +++ b/integrations/incident-management/opsgenie.mdx @@ -1,5 +1,5 @@ --- -title: 'Send Alerts to Opsgenie' +title: 'Send alerts to Opsgenie' description: 'Learn how to integrate Checkly with Opsgenie and deliver failure, degradation, and recovery events to any Opsgenie team' sidebarTitle: 'Opsgenie' canonical: 'https://www.checklyhq.com/docs/integrations/incident-management/opsgenie/' diff --git a/integrations/incident-management/pagerduty.mdx b/integrations/incident-management/pagerduty.mdx index a820f1b43..b509790bb 100644 --- a/integrations/incident-management/pagerduty.mdx +++ b/integrations/incident-management/pagerduty.mdx @@ -1,5 +1,5 @@ --- -title: 'Send Alerts to PagerDuty' +title: 'Send alerts to PagerDuty' description: 'Learn how Checkly integrates seamlessly with PagerDuty, delivering real-time failure and recovery alerts to your PagerDuty account' sidebarTitle: 'PagerDuty' canonical: 'https://www.checklyhq.com/docs/integrations/incident-management/pagerduty/' @@ -43,7 +43,7 @@ to hit **Create PagerDuty channel**. 5. Checkly will trigger an incident in PagerDuty when checks fail and also mark them as resolved when the checks are passing again. ![set up checkly pagerduty integration step 5](/images/docs/images/integrations/pagerduty_step5.png) -## PagerDuty Best Practices +## PagerDuty best practices - **Service Organization**: Create separate PagerDuty services for different applications or teams - **Escalation Policies**: Set up appropriate escalation chains based on check criticality diff --git a/integrations/incident-management/rootly.mdx b/integrations/incident-management/rootly.mdx index 518beb1ff..d4882fda7 100644 --- a/integrations/incident-management/rootly.mdx +++ b/integrations/incident-management/rootly.mdx @@ -1,5 +1,5 @@ --- -title: 'Send Alerts via Rootly' +title: 'Send alerts via Rootly' description: 'Configure Rootly integration to receive real-time alerts from Checkly monitors' sidebarTitle: 'Rootly' canonical: 'https://www.checklyhq.com/docs/integrations/incident-management/rootly/' diff --git a/integrations/incident-management/spike.mdx b/integrations/incident-management/spike.mdx index b620ac69d..473717260 100644 --- a/integrations/incident-management/spike.mdx +++ b/integrations/incident-management/spike.mdx @@ -1,5 +1,5 @@ --- -title: 'Send Alerts via Spike' +title: 'Send alerts via Spike' description: 'Configure Spike integration to receive real-time alerts from Checkly monitors' sidebarTitle: 'Spike' canonical: 'https://www.checklyhq.com/docs/integrations/incident-management/spike/' diff --git a/integrations/incident-management/splunk-on-call.mdx b/integrations/incident-management/splunk-on-call.mdx index 9d34003ce..d48ca9531 100644 --- a/integrations/incident-management/splunk-on-call.mdx +++ b/integrations/incident-management/splunk-on-call.mdx @@ -1,5 +1,5 @@ --- -title: 'Send Alerts via Splunk On-Call' +title: 'Send alerts via Splunk On-Call' description: 'Configure Splunk On-Call integration to receive real-time alerts from Checkly monitors' sidebarTitle: 'Splunk On-Call' canonical: 'https://www.checklyhq.com/docs/integrations/incident-management/splunk-on-call/' diff --git a/integrations/observability/coralogix.mdx b/integrations/observability/coralogix.mdx index 4b8c1c995..fb3970490 100644 --- a/integrations/observability/coralogix.mdx +++ b/integrations/observability/coralogix.mdx @@ -1,5 +1,5 @@ --- -title: 'Export Metrics & Data via Coralogix' +title: 'Export metrics & data via Coralogix' description: 'Deep integration with Coralogix for OpenTelemetry tracing, RUM monitoring, and alert notifications' sidebarTitle: 'Coralogix' canonical: 'https://www.checklyhq.com/docs/integrations/observability/coralogix/' @@ -101,7 +101,7 @@ After enabling the RUM integration, Checkly will start sending RUM data to Coral > Note that you do not need to install the RUM SDK in your application, Checkly will automatically inject the necessary > JavaScript snippet into your Browser checks. However, if you have installed the SDK we will use the existing installation and not inject the snippet. -## Alert channel → Coralogix Logs integration +## Alert channel → Coralogix logs integration You can set up Coralogix as an alert channel destination, so Coralogix receives any alert notifications you have set up as logs. Note that you can use this integration separately from the other two integrations mentioned above. diff --git a/integrations/observability/prometheus-v2.mdx b/integrations/observability/prometheus-v2.mdx index 74f05c34f..240867517 100644 --- a/integrations/observability/prometheus-v2.mdx +++ b/integrations/observability/prometheus-v2.mdx @@ -1,5 +1,5 @@ --- -title: 'Exporting Metrics & Data via Prometheus V2' +title: 'Exporting metrics & data via Prometheus V2' description: 'Export Checkly monitoring data to Prometheus for advanced metrics analysis and Grafana dashboards' sidebarTitle: 'Prometheus V2' canonical: 'https://www.checklyhq.com/docs/integrations/observability/prometheus-v2/' @@ -51,7 +51,7 @@ If you run multiple Prometheus instances, each instance scrapes independently. A Keep `enable_compression` set to `true` to reduce response size and make scrapes faster. Prometheus supports this setting in version 2.49 and later. If your account has many checks, use a longer `scrape_timeout`, such as 30 seconds, to give Prometheus enough time to scrape all metrics. -## Check Metrics +## Check metrics The Prometheus exporter exposes several metrics you can use to monitor the status of your checks, as well as to inspect detailed information such as [Web Vitals](/detect/synthetic-monitoring/browser-checks/performance-metrics). @@ -128,7 +128,7 @@ 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 +### 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. @@ -151,7 +151,7 @@ Here is an example for how to set this in your `prometheus.yml` config: locationLabelEnabled: ['true'] ``` -### Check Retry Attempts +### Check retry attempts By default, [retry attempts](/communicate/alerts/retries/) are not included in the reported metrics. For example, if a check is failing on the initial attempt and passing on the retry, `checkly_check_result_total` and other metrics will only report the final passing check result. @@ -176,7 +176,7 @@ Here is an example for how to configure `includeRetryAttempts` in your `promethe includeRetryAttempts: ['true'] ``` -### PromQL Examples +### PromQL examples This section contains a few PromQL queries that you can use to start working with the Prometheus data. @@ -205,7 +205,7 @@ The different histogram metrics can all be used to compute averages. For example sum by(type) (rate(checkly_browser_check_web_vitals_seconds_sum{name="Check Name"}[30m])) / sum by(type) (rate(checkly_browser_check_web_vitals_seconds_count{name="Check Name"}[30m])) ``` -## Heartbeat Metrics +## Heartbeat metrics [Heartbeat monitors](/detect/uptime-monitoring/heartbeat-monitors/overview) are passive checks that wait for your scheduled jobs and automated processes to send a ping. The Prometheus exporter includes heartbeat checks in the standard `checkly_check_status` and `checkly_check_result_total` metrics, plus two heartbeat-specific gauges designed for [dead man's switch](https://en.wikipedia.org/wiki/Dead_man%27s_switch) alerting. @@ -222,7 +222,7 @@ Heartbeat checks contribute to `checkly_check_result_total` using a 1-hour count | `failing` | `FAILING` — no ping received before the grace period expired | | `degraded` | Always `0` — Heartbeat monitors do not have a degraded state | -### Dead Man's Switch PromQL Examples +### Dead man's switch PromQL examples #### Alert when a heartbeat ping is overdue diff --git a/integrations/observability/prometheus.mdx b/integrations/observability/prometheus.mdx index 3fe94b4d9..257845abb 100644 --- a/integrations/observability/prometheus.mdx +++ b/integrations/observability/prometheus.mdx @@ -1,5 +1,5 @@ --- -title: 'Send Alerts via Prometheus' +title: 'Send alerts via Prometheus' description: 'Configure Prometheus integration to receive real-time alerts from Checkly monitors' sidebarTitle: 'Prometheus' canonical: 'https://www.checklyhq.com/docs/integrations/observability/prometheus/' diff --git a/learn/incidents/anatomy-of-a-status-page.mdx b/learn/incidents/anatomy-of-a-status-page.mdx index bd2105cfe..e145e5629 100644 --- a/learn/incidents/anatomy-of-a-status-page.mdx +++ b/learn/incidents/anatomy-of-a-status-page.mdx @@ -1,5 +1,5 @@ --- -title: Anatomy of a status page | Checkly Guide +title: Anatomy of a status page | Checkly guide displayTitle: Anatomy of a status page sidebarTitle: Anatomy of a status page description: Discover what makes a status page users trust - automated monitoring, clear visuals, service groupings, and more. @@ -19,26 +19,26 @@ When I first started in the tech industry, a new idea was on the scene for your A status page helps users know if your applications or services are working. Here’s what users expect from a good status page: -### 1. Clear Status Updates +### 1. Clear status updates - Show if services are **up, down, or having issues**. - Use simple labels (like "Operational," "Degraded," or "Outage"). -### 2. Externally Hosted +### 2. Externally hosted - The page should be on a separate system (not your main website). This way, users can check it even if your site is down. -### 3. Subscribe Function +### 3. Subscribe function - Let users **subscribe** to updates via email, SMS, or RSS. - Notify them when status changes. -### 4. Easy for Everyone to Use +### 4. Easy for everyone to use - **Regular users** should understand it easily. - **Application owners** should be able to manually mark a service as down if needed. -### 5. Multiple Sections +### 5. Multiple sections - Support different **audiences** (e.g., one page for customers, another for internal teams). - Let users **subscribe only to the pages they care about**. diff --git a/learn/incidents/automation-incident-response.mdx b/learn/incidents/automation-incident-response.mdx index 368ac023e..48911d02b 100644 --- a/learn/incidents/automation-incident-response.mdx +++ b/learn/incidents/automation-incident-response.mdx @@ -1,7 +1,7 @@ --- -title: Incident Response Automation - From Alerts to Action +title: Incident response automation - From alerts to action displayTitle: Automation in incident response -sidebarTitle: Playbooks & Automation +sidebarTitle: Playbooks & automation description: Discover how to layer semi‑automated workflows, automated scripts, and safety checks into your playbooks for faster recovery. date: 2025-02-15 author: Nocnica Mellifera @@ -15,7 +15,7 @@ canonical: 'https://www.checklyhq.com/docs/learn/incidents/automation-incident-r While human judgment remains essential, automation can significantly reduce response times, minimize human error, and streamline workflows. This guide explores how developers can integrate automation into incident playbooks effectively, balancing speed with safety. Often SaaS offerings will promise to ‘handle outages fully automatically’ but that’s generally not the reality. Why can’t we automate incident response, and what levels of automation make sense for your team? -### **1. Automation Spectrum in Incident Response** +### **1. Automation spectrum in incident response** Automation in incident playbooks exists on a spectrum: @@ -29,7 +29,7 @@ Most organizations lean toward **semi-automation** due to risk tolerance, but th - **Failure domain isolation** (Can automation safely fix this without cascading failures?) - **Regulatory/compliance requirements** (Some industries require human approval for changes.) -## **2. Key Automation Use Cases in Playbooks** +## **2. Key automation use cases in playbooks** **A. Alert Enrichment & Context Gathering** @@ -72,7 +72,7 @@ Example (ChatOps): - **Route to the right team** based on symptoms (e.g., SRE vs. Data Engineering) - **Follow availability and escalation rules** this is the kind of thing that is closely associated with PagerDuty: notifying the person who’s currently on-call, and escalating as needed if that person doesn’t respond -## **3. Tools & Integration Patterns** +## **3. Tools & integration patterns** | **Tool** | **Use Case** | **Example Integration** | | --- | --- | --- | @@ -82,7 +82,7 @@ Example (ChatOps): | **Ansible/Chef** | Safe, idempotent remediation | Rollback to last known good config | | **Serverless (AWS Lambda)** | Lightweight automation hooks | Auto-mitigate S3 bucket throttling | -## **4. Security & Guardrails** +## **4. Security & guardrails** Automation introduces risks—**fail-safes are critical**: @@ -101,7 +101,7 @@ fi ``` -## **5. Cultural & Organizational Factors** +## **5. Cultural & organizational factors** - **Start small**: Automate only the most repetitive, low-risk tasks. - **Trust through transparency**: Engineers should see what automation is doing (e.g., ChatOps command logging). @@ -112,7 +112,7 @@ A quote from one engineer talking about how automation can get rolled back after > "At one company, we automated DNS failover—until it once failed over unnecessarily. Now it pings the on-call first." > -### The final word on Automation in playbooks +### The final word on automation in playbooks Automation in incident playbooks isn’t about replacing humans—it’s about **augmenting response efforts** while minimizing toil. By focusing on **enrichment, safe remediation, and guardrails**, developers can build systems that accelerate recovery without sacrificing reliability. diff --git a/learn/incidents/detection-best-practices.mdx b/learn/incidents/detection-best-practices.mdx index f9d9ffc55..d161e64a8 100644 --- a/learn/incidents/detection-best-practices.mdx +++ b/learn/incidents/detection-best-practices.mdx @@ -1,7 +1,7 @@ --- -title: Best Practices for Detecting Downtime | Incident Response +title: Best practices for detecting downtime | Incident response displayTitle: Best Practices for Detecting Downtime - A Guide for Developers -sidebarTitle: Detecting Downtime +sidebarTitle: Detecting downtime description: Discover how to implement multi‑layered monitoring, smart alerts, third‑party checks, failure drills & global probes to catch outages fast and reduce revenue loss date: 2025-02-15 author: Nocnica Mellifera @@ -16,7 +16,7 @@ canonical: 'https://www.checklyhq.com/docs/learn/incidents/detection-best-practi Downtime can be costly—leading to lost revenue, frustrated users, and damage to your brand’s reputation. As a developer, ensuring high availability and quickly detecting outages is critical. -## **1. Implement Multi-Layered Monitoring** +## **1. Implement multi-layered monitoring** Relying on a single monitoring method can lead to blind spots. Instead, use a combination of: @@ -24,7 +24,7 @@ Relying on a single monitoring method can lead to blind spots. Instead, use a co - **Application Monitoring**: Gather traces internal from your application, and look for errors or long timespans that indicate trouble. Send logs to a single locality to help you investigate problems after one is detected. - **Infrastructure Monitoring**: Use tools like Prometheus, Grafana, or Nagios to keep an eye on the underlying health of your system. -## **2. Set Up Intelligent Alerting** +## **2. Set up intelligent alerting** Avoid "alert fatigue" by ensuring alerts are meaningful and actionable: @@ -32,7 +32,7 @@ Avoid "alert fatigue" by ensuring alerts are meaningful and actionable: - **Prioritize Alerts**: Distinguish between *critical* (full outage) and *warning* (degraded performance). Any time your on-call team gets an alert that doesn’t require action, this should be counted as a false alarm and call for improvements to your alert thresholds. - **Avoid Static Thresholds**: When a service that usually responds in 4.98 seconds starts responding after 5.1 seconds, it’s a negative trend that might call for some investigation. But it certainly does *not* call for a midnight alert to the on-call team. As just one example, Playwright’s assertions about page elements use an [auto-waiting](https://www.checklyhq.com/blog/playwright-auto-waiting/) system that is more flexible than static time thresholds. -## **3. Monitor Third-Party Dependencies** +## **3. Monitor third-party dependencies** Your application may depend on APIs, CDNs, or cloud providers—any of which can fail. @@ -40,7 +40,7 @@ Your application may depend on APIs, CDNs, or cloud providers—any of which can - **Implement Fallbacks**: Gracefully degrade functionality if a dependency fails. For core dependencies this might go as far as switching to a backup payment provider if your primary service fails. -## **4. Test Failure Scenarios** +## **4. Test failure scenarios** Proactively simulate outages to ensure your monitoring works: @@ -50,7 +50,7 @@ Proactively simulate outages to ensure your monitoring works: --- -## **5. Ensure Global Visibility** +## **5. Ensure global visibility** Downtime may only affect certain regions due to DNS, CDN, or cloud provider issues. @@ -59,7 +59,7 @@ Downtime may only affect certain regions due to DNS, CDN, or cloud provider issu --- -## **6. Automate Incident Response** +## **6. Automate incident response** When downtime occurs, speed is crucial. diff --git a/learn/incidents/dora-metrics.mdx b/learn/incidents/dora-metrics.mdx index 02c3c75ea..a8fa4b7fa 100644 --- a/learn/incidents/dora-metrics.mdx +++ b/learn/incidents/dora-metrics.mdx @@ -1,7 +1,7 @@ --- -title: How to Use DORA Metrics the Right Way | Checkly +title: How to use DORA metrics the right way | Checkly displayTitle: How to Use DORA Metrics the Right Way -sidebarTitle: DORA Metrics for Performance Evaluation +sidebarTitle: DORA metrics for performance evaluation description: Learn to track and interpret DORA’s four metrics—deployments, lead time, failure rate, and restore time—to improve your software delivery. date: 2025-03-13 author: Nocnica Mellifera @@ -26,7 +26,7 @@ DORA metrics measurements are inherently subjective to your team and **not a goo There’s an interesting variety in DORA metrics. Some are unequivocal in their interpretation (it’s always better to have a lower ‘time to restore service’), while others have no meaning outside context (I could write a script that makes small grammar edits and deploys them, massively boosting ‘deployment frequency’ with no benefit). Some are easy to measure like deployment frequency, others like change failure rate require some thought about *what* is being measured before we even ask why it matters. Here’s all four metrics in detail. -### Deployment Frequency +### Deployment frequency Deployment frequency measures how often a team successfully releases code to production. @@ -44,7 +44,7 @@ Deployment frequency is also an object lesson in why **DORA metrics don't transl Factors like underlying code structure and QA practices can cause large differences between teams, so it's best to establish baselines for your team based on past performance. -### Lead Time for Changes +### Lead time for changes Lead time for changes measures how long it takes for code to go from being written to running in production. To calculate it, find the time between when a commit is made and when it’s deployed. Use the middle value (median) of these times over a set period. @@ -54,7 +54,7 @@ To measure lead time, start tracking when a pull request (PR) is created or merg In general, shorter lead times are better. For example, top teams (elite performers) deploy changes in less than a day, while slower teams might take weeks or even months. Faster lead times mean your team can respond quickly to needs and keep improving. -### Time to Restore Services +### Time to restore services Time to restore services measures how long it takes to fix a service after it fails. The clock stops when the issue is resolved, and the related bug or incident report is closed. @@ -72,7 +72,7 @@ To calculate the metric, add up the time spent on all incidents and divide by th Faster recovery times are better. Top teams (elite performers) fix issues in less than an hour, while slower teams might take days or even weeks. -### Change Failure Rate +### Change failure rate Change failure rate measures how often deployments cause problems. It’s the percentage of deployments that fail out of the total number of deployments. diff --git a/learn/incidents/incident-assessment-severity.mdx b/learn/incidents/incident-assessment-severity.mdx index f26f330f7..804ea39b9 100644 --- a/learn/incidents/incident-assessment-severity.mdx +++ b/learn/incidents/incident-assessment-severity.mdx @@ -1,7 +1,7 @@ --- -title: Incident Assessment & Severity | Checkly Guide +title: Incident assessment & severity | Checkly guide displayTitle: Incident Assessment & Severity Guide for Engineering Teams (+ Cheat Sheet) -sidebarTitle: Incident Assessment & Severity Guide +sidebarTitle: Incident assessment & severity guide description: Not every alert is an incident—and not every incident is equally urgent. How to classify incidents and determine their severity? date: 2025-05-23 author: Sara Miteva @@ -13,7 +13,7 @@ learn_incidents: canonical: 'https://www.checklyhq.com/docs/learn/incidents/incident-assessment-severity/' --- -## **Incident Assessment & Severity** +## **Incident assessment & severity** Not every alert is an incident—and not every incident is equally urgent. @@ -28,7 +28,7 @@ The goal of incident assessment is to **evaluate the scope and impact** of a pro Let’s break down what effective assessment looks like and how to build your own severity classification system. -### **What Is Incident Assessment?** +### **What is incident assessment?** Incident assessment is the process of determining whether an observed issue qualifies as an incident—and if so, how serious it is. @@ -41,7 +41,7 @@ To assess an incident, you typically ask: The outcome of this process is a **severity level** that maps to your internal response playbook: who gets paged, how quickly you communicate, and how visible the incident becomes across the company. -### **Why Severity Levels Matter** +### **Why severity levels matter** Clear severity definitions help your team: @@ -52,7 +52,7 @@ Clear severity definitions help your team: They also create psychological safety. When engineers know exactly what qualifies as a SEV1, they don’t waste time debating—they act. -## Severity Levels: Example Framework +## Severity levels: Example framework Here’s a simple, 3-tier severity model you can adopt or adapt: @@ -62,7 +62,7 @@ Here’s a simple, 3-tier severity model you can adopt or adapt: | **SEV2** | High / Partial Outage | 10% of users can’t log in, degraded performance, partial failure | Escalate to on-call immediately. Frequent updates. Prioritized fix. | | **SEV3** | Moderate / Minor Bug | Broken styling, slow dashboard load, minor UX issue | Fix during business hours. Log the issue. May not require updates. | -### A Score-Based System for Classifying Severity +### A score-based system for classifying severity You can use a weighted scoring system that evaluates incidents across five dimensions. This adds structure and reduces subjective decisions: @@ -93,30 +93,30 @@ Let’s say our business is a review site with an ecommerce store. Users on Micr → **Score: 12 → SEV1** -## Downloadable Incident Severity Cheat Sheet +## Downloadable incident severity cheat sheet If you want to adopt or adapt this process, you can make a copy of our own [incident severity cheat sheet](https://docs.google.com/spreadsheets/d/18L2r8u5h8ylRWNbfMZv0Ff-amJ-ySk5ZU1FLxW2G4uY/edit?usp=sharing). -## Creating Your Own Severity Rules +## Creating your own severity rules Every organization operates differently, and what counts as a critical incident for one team may be a routine alert for another. Here’s how to build a severity scoring system that reflects your team’s priorities, customer expectations, and business context. -### **1. Pick Dimensions That Matter to You** +### **1. Pick dimensions that matter to you** Start by identifying the dimensions of impact that are most relevant to your systems and stakeholders. Common ones include **user impact**, **feature impact**, **business risk**, **urgency**, and **workaround availability**—but you might also include **compliance violations**, **customer tier affected**, or **data integrity** if those are key concerns. The goal is to capture the real-world consequences of an incident in a way that reflects your product and risk model. -### **2. Agree on What “High”, “Medium”, and “Low” Mean** +### **2. Agree on what “High”, “Medium”, and “Low” mean** Without clear definitions, severity scoring quickly becomes subjective. What one engineer sees as a “minor issue” might be considered “urgent” by someone in customer success. To avoid this, document clear criteria for each level of impact. For example, define “High User Impact” as “more than 25% of users affected” or “SEV1 Business Impact” as “any outage that causes revenue loss or legal risk.” These definitions become your north star for consistent triage. -### **3. Add Automation Where Possible** +### **3. Add automation where possible** Manual severity scoring can slow things down and introduce inconsistencies, especially during high-pressure incidents. Automate as much of the process as you can. A shared Google Sheet or Notion template can help teams select impact levels via dropdowns, with scores and severity levels calculated automatically. For more mature teams, connect this logic directly into your alerting pipeline or incident management tool so severity is auto-assigned on alert creation. -### **4. Train Your Incident Responders** +### **4. Train your incident responders** Severity models only work if everyone is aligned on how to use them. Run training sessions or tabletop exercises with your incident response team. Use past incidents to “test” the model—how would they score it now, and does the outcome feel right in hindsight? Over time, this helps calibrate judgment, improves consistency across teams, and creates shared understanding between engineering, support, and leadership. -## Final Words +## Final words Clear severity rules turn gut-feel decisions into structured, confident responses. With a shared scoring model, your team can triage faster, communicate better, and stay focused when it matters most. diff --git a/learn/incidents/incident-communication.mdx b/learn/incidents/incident-communication.mdx index 86c82a75a..9c0bec134 100644 --- a/learn/incidents/incident-communication.mdx +++ b/learn/incidents/incident-communication.mdx @@ -1,7 +1,7 @@ --- -title: Best Practices for Communicating During Outages and Incidents +title: Best practices for communicating during outages and incidents displayTitle: Incident Communication - Best Practices -sidebarTitle: Incident Communication +sidebarTitle: Incident communication description: Lack of communication, or wrong communication, can often be the part of incident response that comes in for the most criticism. While it’s critical to define playbooks for communication, this article will talk in general about the best practices for communicating with users during an incident. date: 2025-02-15 author: Nocnica Mellifera @@ -73,7 +73,7 @@ Further, entrusting communications to a customer facing team member means that: - The support or sales engineer tasked with communication is likely to understand what exactly this outage means for most users, as users average behavior is more clear to someone who works with users directly. - Customer-facing engineers are often the best people to identify expected behavior for the product, proving enormously helpful during the diagnosis stage. -## Conclusions: Communication Remains a Human Speciality +## Conclusions: Communication remains a human speciality Effective communication during an incident is just as critical as the technical response itself. While engineers naturally prioritize diagnosing and resolving issues, keeping users informed—accurately and promptly—can significantly mitigate frustration and prevent churn. This article has outlined key best practices for incident communication, emphasizing the importance of timing, automation, delegation, and trust in the on-call team’s judgment. diff --git a/learn/incidents/incident-management-challenges.mdx b/learn/incidents/incident-management-challenges.mdx index 80d1a2293..0d8e20943 100644 --- a/learn/incidents/incident-management-challenges.mdx +++ b/learn/incidents/incident-management-challenges.mdx @@ -1,7 +1,7 @@ --- -title: Incident Management Challenges | Checkly Guide +title: Incident management challenges | Checkly guide displayTitle: Incident Management Challenges -sidebarTitle: Incident Management Challenges +sidebarTitle: Incident management challenges description: Find out what are the most common incident challenges and how to address them. date: 2025-05-23 author: Sara Miteva @@ -25,7 +25,7 @@ Let’s break down the real-world challenges teams face when managing incidents ![Incident Management Challenges](learn/images/Incident Management Challenges (1).png) -## Early Detection Is Still Hard +## Early detection is still hard Despite proactive monitoring tools, teams often struggle to detect incidents early enough. The challenge? @@ -37,7 +37,7 @@ Instead, it’s a single failing endpoint. A slightly elevated latency. A login In the end, early detection isn’t just about tooling. It’s about tuning, ownership, and continuously improving your signal-to-noise ratio. -## **2. Defining What Is an Incident** +## **2. Defining what is an incident** *An **incident** is any unplanned disruption or degradation of a service that affects users or business operations and requires a response.* @@ -57,13 +57,13 @@ Here’s an example of how you could classify incidents by severity: The challenge is not just defining these, but aligning everyone—engineering, support, and leadership—on what they mean in practice. -## 3. Coordination and Escalation Can Get Messy +## 3. Coordination and escalation can get messy When things go wrong, teams scramble. But without a clearly defined incident commander or roles like communication lead or scribe, progress stalls. People either duplicate efforts or wait for someone else to lead. Escalation must be automatic. Everyone should know: when this happens, who gets paged, and who owns the response. -## 4. Postmortems Get Ignored or Misused +## 4. Postmortems get ignored or misused The post-incident review often turns into a blame game or a checkbox exercise. But a good postmortem is blameless, structured, and actionable. @@ -75,7 +75,7 @@ Ask: Without real reflection, you’re doomed to repeat the same fire drills. -## 5. Fear Slows Down Response +## 5. Fear slows down response One of the most dangerous challenges in incident management isn’t technical—it’s emotional. @@ -93,7 +93,7 @@ If people are afraid of being called out, they'll wait. And in incident response Your culture determines whether your team moves fast—or freezes. Choose transparency over silence. Choose learning over blame. -## Chaos is the Enemy, Structure is the Fix +## Chaos is the enemy, structure is the fix Incident management is a high-stakes, high-pressure process. But when you build in structure—detection, communication, escalation, resolution, reflection—you replace chaos with clarity. diff --git a/learn/incidents/modern-root-cause-analysis.mdx b/learn/incidents/modern-root-cause-analysis.mdx index ece6f0cf9..f59130ef8 100644 --- a/learn/incidents/modern-root-cause-analysis.mdx +++ b/learn/incidents/modern-root-cause-analysis.mdx @@ -1,7 +1,7 @@ --- -title: Modern Root Cause Analysis | Checkly Guide +title: Modern root cause analysis | Checkly guide displayTitle: Modern Root Cause Analysis -sidebarTitle: Modern Root Cause Analysis +sidebarTitle: Modern root cause analysis description: Discover how unified metrics, logs, traces, and synthetic tests help you pinpoint failures faster, reduce downtime, and more. date: 2025-04-06 author: Nocnica Mellifera @@ -36,7 +36,7 @@ Going from high level dashboards to logs is still common for operations engineer As cloud architectures expand into greater complexity, broadening our search for a root cause, we need modern techniques enabled by tools like OpenTelemetry, Jaeger, and Checkly to tackle the problems of modern RCA. -### Key Improvements in Modern RCA: +### Key improvements in modern RCA: 1. **Automated Correlation** – With distributed tracing and [context propagation](https://www.checklyhq.com/learn/opentelemetry/context-propagation/), we shouldn’t be trying to line up time codes to correlate observability data from multiple services 2. **Context-Aware Alerts** – Alerts prioritize issues impacting business metrics (like checkout errors vs. low-severity logs). Sophisticated routing and status updates on tools like Rootly mean only the right team members get woken up during incidents. @@ -51,7 +51,7 @@ A payment service fails intermittently. Traditional RCA might check logs in isol - **Logs** highlight a third-party API throttling connections. - **Dashboards** correlate this with a recent deployment, suggesting a rollback. -### Tools for Effective RCA: +### Tools for effective RCA: - **OpenTelemetry** (unified data collection for the back end) - **Prometheus/Grafana** (metrics visualization) diff --git a/learn/incidents/mttr-challenges.mdx b/learn/incidents/mttr-challenges.mdx index 85f6fc662..3e5f7da40 100644 --- a/learn/incidents/mttr-challenges.mdx +++ b/learn/incidents/mttr-challenges.mdx @@ -1,7 +1,7 @@ --- -title: MTTR Challenges & Solutions | Checkly +title: MTTR challenges & solutions | Checkly displayTitle: Best Practices for Reduced Mean Time To Repair -sidebarTitle: Reducing Time to Repair +sidebarTitle: Reducing time to repair description: Find out why MTTR targets fail—from weak observability and slow detection to cloud‑native complexity—and apply practical tactics to meet your SLAs. date: 2025-02-15 author: Nocnica Mellifera @@ -15,7 +15,7 @@ canonical: 'https://www.checklyhq.com/docs/learn/incidents/mttr-challenges/' Missing MTTR and the concomitant SLA targets is a common occurrence among large tech teams. We all start each quarter with a goal of always resolving issues quickly and delivering high uptime for our users. So why do we fail on these goals? This article is a list of the common causes of missed MTTR: -### 1. **Observability Tools Are Falling Short** +### 1. **Observability tools are falling short** Often the longest period of an incident response is the time spent between knowing you have a problem and understanding what’s causing the problem. This is almost definitional, since once you know the nature of the problem it’s generally possible to fix or at least remediate it pretty quickly, for example with a rollback. But what makes this time to understanding the problem so long? @@ -25,7 +25,7 @@ Imagine you’re trying to solve an outage that’s only affecting some users an When tools are cumbersome and fail to provide actionable insights, engineers spend more time diagnosing problems, which increases MTTR. -### 2. **Time to Detect (TTD) Is Overlooked** +### 2. **Time to detect (TTD) is overlooked** Another factor contributing to high MTTR is the time it takes to detect an issue in the first place. Reducing the mean time to detect ([MTTD](/learn/incidents/reduce-mttd)) is crucial for improving MTTR, as delays in detection can lead to prolonged outages. An entire guide on time to detection is available on our Learn site, but in short the most common failures are: @@ -36,7 +36,7 @@ An entire guide on time to detection is available on our Learn site, but in shor Again these concerns and more are in a separate page on [optimizing time to detection](/learn/incidents/reduce-mttd). -### 3. **The Complexity of Cloud-Native Environments** +### 3. **The complexity of cloud-native environments** Many organizations are adopting cloud-native architectures, such as containers and microservices, to improve efficiency and scalability. However, this shift has introduced greater complexity, higher data volumes, and increased pressure on engineering teams. Cloud-native architectures have made it harder to discover and troubleshoot incidents. This complexity can significantly delay the time it takes to detect and resolve issues. @@ -47,15 +47,15 @@ If you’re unsure if this is true in your own organization, ask this question o I believe that most engineers would honestly answer: “no,” and that this was different before cloud native architecture. -## How Can Companies Improve MTTR? +## How can companies improve MTTR? To address these challenges, organizations need to focus on optimizing each stage of the incident response process: -### 1. **Reduce Time to Detect (TTD)** +### 1. **Reduce time to detect (TTD)** Improving detection times requires robust monitoring and alerting systems that can quickly identify issues. This involves setting low scrape intervals for data collection and ensuring that observability tools can ingest and generate alerts rapidly. Faster detection allows teams to begin remediation efforts sooner, which can significantly reduce MTTR. This is covered in more detail in our page on [optimizing detection time](/learn/incidents/reduce-mttd). -### 2. **Streamline Time to Remediate** +### 2. **Streamline time to remediate** Once an issue is detected, the next step is to stop the customer pain by implementing a temporary fix. This can be achieved by: @@ -65,7 +65,7 @@ Once an issue is detected, the next step is to stop the customer pain by impleme With these tools an on-call team can get the system working for users quickly, followed by a longer period of root cause analysis and postmortem. -### 3. **Time to Remediate over Time to Repair** +### 3. **Time to remediate over time to repair** In our guide on defining MTTR we discussed how the time to remediate (how long it takes to patch the problem such that users are not experiencing an error) versus time to repair (how long it takes to fix the underlying problem). In a simple if outdated example: resetting a server with a memory leak remediates an out-of-memory error, finding and fixing the memory leak repairs the problem. diff --git a/learn/incidents/on-call-schedule.mdx b/learn/incidents/on-call-schedule.mdx index c4b546004..9c47976d0 100644 --- a/learn/incidents/on-call-schedule.mdx +++ b/learn/incidents/on-call-schedule.mdx @@ -1,7 +1,7 @@ --- -title: How to Set an On‑Call Schedule | Checkly Incident Response +title: How to set an on‑call schedule | Checkly incident response displayTitle: How to Set an On-Call Schedule -sidebarTitle: On-Call Schedules - How to +sidebarTitle: On-call schedules - How to description: Learn to design effective on‑call rotations—shift models, clear response rules, scheduling tools, mock drills, and fairness to prevent burnout. date: 2025-03-15 author: Nocnica Mellifera @@ -15,13 +15,13 @@ canonical: 'https://www.checklyhq.com/docs/learn/incidents/on-call-schedule/' Once an incident is detected, it’s time to classify the incident and coordinate with your team. To all that, you’ll need an on-call schedule. This guide covers the necessary components for a successful on-call schedule. -## Why Have an On-Call Schedule? +## Why have an on-call schedule? Things break. People need help. No matter how well-designed, a software system that is constantly getting new features and scaling to meet demand will experience outages and other incidents. Putatively, an on-call schedule is there to make sure someone is always ready to fix problems, but really they tend to be adopted for another reason: burning out your best. After the first inchoate stage of a software team, there will remain a tendency to bring all technical questions, at any hour of the day, to just 1 or 2 experts. These are often people who are both knowledgeable and possessed of a tendency to look at their phone during dinner. These very effective engineers will quickly get burnt out if they’re the only ones who can actually fix things during a crisis. As such, an on-call schedule can help focus minds as to who can cover during incidents, and who needs more training to get to that level. -## Steps to Set Up Your Schedule +## Steps to set up your schedule First, decide who needs to be on call. Pick people who know how to handle problems and can respond quickly. Make sure everyone gets a turn so no one feels overworked. @@ -33,14 +33,14 @@ After that, use tools to make it easier. A scheduling app like PagerDuty or Opsg Finally, test the schedule before real problems happen. Send a practice alert to make sure it works. Ask the team for feedback and adjust if needed. A good on-call schedule keeps things running smoothly and helps everyone feel prepared. -### 1. Choose Who Is On Call +### 1. Choose who is on call The first and arguably most important step of an on-call schedule is deciding who is eligible to help field reports of emerging issues. The number of available on-call engineers will affect every decision you make afterward. - Pick team members who know how to handle emergencies. - Make sure everyone gets a fair turn. -### 2. Decide the Rotation +### 2. Decide the rotation Next, choose how long each shift will last. Some teams switch every day, while others cover a full week. Think about what works best for your team and how often emergencies happen. @@ -52,7 +52,7 @@ The third model, **daylight hours**, spreads coverage across time zones so no on It’s important to note that your team members will not all feel the same way about these rotations. If possible, let engineers choose a model that makes sense for them, and doesn’t simplistically assign a ‘fair’ system for how easy it is to administer. Remember that a small team can often get by with something like: ‘on-call rotates every day, if you need your day off you’re responsible for finding someone to switch with you.’ -### 3. Set Clear Rules +### 3. Set clear rules Try to answer questions about on-call expectations early in the process, not during a post-mortem for an incident that went unread for 8 hours. @@ -63,7 +63,7 @@ Try to answer questions about on-call expectations early in the process, not dur Answer these questions now, as a team, or face case-by-case problems and embarrassment later! -### 4. Use Tools to Help +### 4. Use tools to help Unless your team is tiny, you’ll need a few tools to help coordinate on call rotations. @@ -73,14 +73,14 @@ Unless your team is tiny, you’ll need a few tools to help coordinate on call r A lot more could be written about how observability tools help during incidents, but those are considered in another guide, read on for more! -### 5. Make It Fair +### 5. Make it fair Tech workers are happy to put up with a lot of ambiguity, complexity, and unpredictability in their jobs, but no one likes working in a situation that feels unfair. - Avoid burnout. Don’t put the same person on call too often. - If you’re relying on one person to cover most of the on-call time, it’s time to take staff development seriously, and pair your on-call expert with someone who needs to gain those skills. - Rotate holidays and weekends. - The more geographically diverse your team, the less likely you are to run into schedule conflicts. -### 6. Test It +### 6. Test it As your team adjusts to a schedule and process, stage mock incidents to test out the process. @@ -89,15 +89,15 @@ As your team adjusts to a schedule and process, stage mock incidents to test out Again if you’re having frequent incidents this may not be necessary, but if every incident isn’t following process, it’s time to practice a dry run! -### 7. Keep Improving +### 7. Keep improving - **Ask the team for feedback** - It’s critical to perform post-mortems, even after successfully handled incidents, ask ‘what could have gone better’ about the on-call process. - **Continuously update your process** - Ideally your team and your market will be growing throughout each year, so the process that worked last year probably won’t keep working this year. -## Be Kind +## Be kind Being on call can be stressful. Support your team. Say thanks. Help when needed. -### You Have One Team +### You have one team On-call is one of the reasons that people list for leaving teams. Don’t destroy your team while trying to handle incidents, listen to your team members and find a solution that works for you. Spend your energy lifting each other up. A good on-call schedule keeps things running—and people happy. \ No newline at end of file diff --git a/learn/incidents/overview.mdx b/learn/incidents/overview.mdx index 8aaddec1a..45e1448f6 100644 --- a/learn/incidents/overview.mdx +++ b/learn/incidents/overview.mdx @@ -1,5 +1,5 @@ --- -title: Incident Response - Improve Recovery & Avoid Downtime +title: Incident response - Improve recovery & avoid downtime displayTitle: Learn the fundamentals of Incident Response description: Master incident response with real-world insights. Learn how to reduce downtime, regain user trust, and build a resilient incident management workflow. date: 2025-04-07 @@ -15,11 +15,11 @@ We’ve all been there, the 3AM phone call, the bleary-eye scanning of a Slack c In the last decade as the whole world has grown to accept software-as-a-service, the standards for uptime and responsiveness to issues have increased steadily. While day-long maintenance windows and hours-long outages were par for the course in 2015, now even an outage of a few minutes can affect business health. Further, expectations about uptime have gone from ‘best practices’ to ‘binding agreements with financial costs for failures,’ with enterprise clients demanding service level agreements (SLAs) with penalty schedules if uptime goals aren’t met. -## Getting Started +## Getting started Incident Response in the software industry refers to a time-critical response to some kind of availability incident. @@ -32,14 +32,14 @@ Further, expectations about uptime have gone from ‘best practices’ to ‘bin -## Detect and Resolve Incidents Faster With Playwright +## Detect and resolve incidents faster with Playwright -## On the Checkly Blog +## On the Checkly blog Learn seven best practices to fight alert fatigue. @@ -51,7 +51,7 @@ Further, expectations about uptime have gone from ‘best practices’ to ‘bin Strategies to configure your alerts for team success. Five best practices to help you deploy your software more securely and reliably. diff --git a/learn/incidents/playbooks.mdx b/learn/incidents/playbooks.mdx index f50909aa4..e9b018596 100644 --- a/learn/incidents/playbooks.mdx +++ b/learn/incidents/playbooks.mdx @@ -1,7 +1,7 @@ --- -title: Incident Response Playbooks - Culture & Compliance | Checkly +title: Incident response playbooks - Culture & compliance | Checkly displayTitle: Incident Response Playbooks -sidebarTitle: Incident Response Playbooks +sidebarTitle: Incident response playbooks description: Master playbooks by setting clear standards, empowering team autonomy, and refining processes when steps are skipped. date: 2025-04-07 author: Nocnica Mellifera @@ -15,7 +15,7 @@ canonical: 'https://www.checklyhq.com/docs/learn/incidents/playbooks/' Incident management is a critical aspect of maintaining system reliability. When engineers are woken up late at night, getting on an incident chat, and trying to fix things while communicating with the team, a huge source of safety and stability is a playbook that describes what to do when. This article serves as a guide for application developers on how to get started writing playbooks for incident response. -## Team Culture in Incident Response Playbooks +## Team culture in incident response playbooks The term ‘playbook’ sometimes implies a sort of mechanical process that tells engineers exactly what to do, a bit like a robot following lines of code. But of course the term is taken from sport, where a playbook lists individual plays that allow for human participants and implicit randomness. Team culture is a clear part of incident response, and you need to consider how real people will interpret plans when faced with real failures and stressful situations. Two early questions are how much standardization of playbooks should happen between teams, and how to handle cases where people don’t follow the process. @@ -35,7 +35,7 @@ One senior ops engineer talks about the balance between team standardization and That general truism should apply to your organization: if a team’s individual process for incidents isn’t working, it’ll show up in the number of incidents assigned to the team. -### What to Do When Someone Doesn’t Follow the Process +### What to do when someone doesn’t follow the process People often skip steps when the process feels slow or hard. If this happens, it means something is wrong—maybe the process is confusing, scary, or takes too long. Others might not ask for help because they had a bad experience before or feel rushed. diff --git a/learn/incidents/postmortems.mdx b/learn/incidents/postmortems.mdx index a99171661..431fc6ce0 100644 --- a/learn/incidents/postmortems.mdx +++ b/learn/incidents/postmortems.mdx @@ -1,7 +1,7 @@ --- -title: Postmortems That Drive Real Improvements (+ Template) | Checkly Guide +title: Postmortems that drive real improvements (+ template) | Checkly guide displayTitle: Postmortems That Drive Real Improvement (+ Template) -sidebarTitle: Postmortems That Drive Real Improvement (+ Template) +sidebarTitle: Postmortems that drive real improvement (+ template) description: Postmortems aren’t just documentation exercises. Check out how to properly do one + get a downloadable template. date: 2025-05-23 author: Sara Miteva @@ -20,7 +20,7 @@ Postmortems aren’t just documentation exercises. Done well, they’re powerful In this article, we’ll walk through how to run postmortems that actually make your systems and teams stronger—not just your incident timeline longer. -## Why Postmortems Matter +## Why postmortems matter Incidents are inevitable. What separates high-performing teams is not how rarely they fail—but **how well they learn from failure**. @@ -33,7 +33,7 @@ A strong postmortem: Too often, though, postmortems are rushed, overly technical, or just ignored. The result? No follow-through, no learning, no improvement. -### The Firefighter Trap +### The firefighter trap We recently interviewed a senior tech lead who told us about an antipattern called ‘The Firefighter Trap:’ @@ -46,11 +46,11 @@ We recently interviewed a senior tech lead who told us about an antipattern call It’s great to take a victory lap after an incident is resolved. But you must work to ensure that this problem is handled automatically in the future. Post-mortems, then are a critical step in incident response: Without them you’re likely to find yourself stuck in a loop of responding to incidents without solving their causes. -## What a Great Postmortem Looks Like +## What a great postmortem looks like Here’s the anatomy of a postmortem that actually drives improvement, based on the framework shared in the webinar: -### 1. **Create a Safe, Blameless Space** +### 1. **Create a safe, blameless space** Psychological safety is the foundation. No one should feel like they’re on trial. Focus on systems, not individuals. Use phrases like: @@ -60,7 +60,7 @@ Psychological safety is the foundation. No one should feel like they’re on tri If people fear blame, they’ll delay declaring incidents or avoid contributing to future postmortems. Safety enables transparency. -### 2. **Write a Clear, Honest Timeline** +### 2. **Write a clear, honest timeline** Document the incident as it unfolded: @@ -71,7 +71,7 @@ Document the incident as it unfolded: Include timestamps, links to check results or traces, and any relevant logs. This isn’t just about storytelling—it’s about understanding time to detect, time to resolve, and where delays happened. -### 3. **Analyze What Went Wrong—and Why** +### 3. **Analyze what went wrong—and why** Was there a monitoring gap? A failed alert? A communication bottleneck? A missing runbook? @@ -90,7 +90,7 @@ Go beyond symptoms and look at root causes—technical and procedural. - *Can we monitor this third-party service proactively, e.g., [with an API monitor](https://www.checklyhq.com/learn/monitoring/api-monitoring/)?* -### 4. **Capture What Went Well** +### 4. **Capture what went well** It’s easy to focus on failures, but recognizing **what worked** reinforces good behavior and boosts team morale. @@ -98,7 +98,7 @@ Did the alert fire correctly? Did someone step up as incident commander? Was cus Call it out. Celebrate wins—even in chaos. -### 5. **Define Next Steps With Owners** +### 5. **Define next steps with owners** Turn findings into action: @@ -111,14 +111,14 @@ Each action item should have an **owner** and a **due date**. Otherwise, nothing 💡 *We did a whole webinar on incidents and post-mortems, which you can watch on-demand [here](https://www.checklyhq.com/webinars/incident-management-101-detection-to-communication/).* -## Steal Our Postmortem Template +## Steal our postmortem template If you want a ready-to-use postmortem template you can steal and/or adapt, use ours: - [Copy the Notion template](https://www.notion.so/Checkly-s-Incident-Postmortem-Template-for-Engineering-Teams-1ecec050b06e805e80b7d714d2a22fb3?pvs=21) - [Download a Google Doc](https://docs.google.com/document/d/1qdLpwkn-qrF5kJk_Y-EFWHmMTiH6jmlRpQ6YFzOlZCU/edit?tab=t.0) -## Postmortems Are Not Just for SEV1s +## Postmortems are not just for SEV1s Every SEV1 should have a postmortem. But consider doing them for SEV2s too—especially if: @@ -128,7 +128,7 @@ Every SEV1 should have a postmortem. But consider doing them for SEV2s too—esp Small incidents are often the warning signs for bigger ones. Don’t miss the learning moment. -## Final Thoughts +## Final thoughts Postmortems aren't just a checkbox at the end of an incident—they're a lever for building resilience, clarity, and trust. diff --git a/learn/incidents/reduce-mttd.mdx b/learn/incidents/reduce-mttd.mdx index 1748ad5bd..9ad7bf759 100644 --- a/learn/incidents/reduce-mttd.mdx +++ b/learn/incidents/reduce-mttd.mdx @@ -1,7 +1,7 @@ --- -title: Reduce Mean Time to Detection MTTD - Best Practices Guide +title: Reduce mean time to detection MTTD - Best practices guide displayTitle: How to Detect Problems Faster -sidebarTitle: MTTD Best Practices +sidebarTitle: MTTD best practices description: Avoid user‑reported outages with synthetic checks, anomaly detection, smart alerting, and rich failure traces for rapid detection. date: 2025-02-15 author: Nocnica Mellifera @@ -38,7 +38,7 @@ How do you stop relying on user reports of problems? In general there are three With its power to find outages before your users do, the rest of this article will focus on the right way to user synthetic monitoring to find outages proactively. -## Check Frequently +## Check frequently Automated tools like [Checkly](https://www.checklyhq.com/) can make sure that every outage is detected quickly and accurately, but if you set the interval between checks too long, you’ll still be relying on users to report some outages. If no checks of your service are running for more than 15 minutes, it’s highly likely that some outages will be discovered by your users before a synthetic monitor can alert you. For more aggressive SLA’s, you may want to [set your check cadence](https://www.checklyhq.com/blog/check-frequency/) to run every minute from at least one location. @@ -90,6 +90,6 @@ A final point, once again related in part to alert fatigue, is making sure that *A Checkly trace showing a full debug session for a failed check.* -## Conclusions: Detect Faster to Fix Faster +## Conclusions: Detect faster to fix faster In this article I’ve argued that detection is a critical step in your time to repair, and thereby critical for meeting your SLA. Detection isn’t just about closer monitoring or a faster rate of monitoring. By engineering notifications and alerts to be informative, timely, and targtetted you can improve time to detection without any increased infrastructure cost, and reduced stress for your on-call team! \ No newline at end of file diff --git a/learn/incidents/root-cause-with-traces.mdx b/learn/incidents/root-cause-with-traces.mdx index b94328cf8..09969133e 100644 --- a/learn/incidents/root-cause-with-traces.mdx +++ b/learn/incidents/root-cause-with-traces.mdx @@ -1,7 +1,7 @@ --- -title: Root Cause with Traces - Faster RCA | Checkly +title: Root cause with traces - Faster RCA | Checkly displayTitle: Tracing for Root Cause Analysis -sidebarTitle: Tracing for Root Cause Analysis +sidebarTitle: Tracing for root cause analysis description: Combine distributed tracing with synthetic checks to pinpoint failures across microservices, preserve request context, and reduce MTTR. date: 2025-04-06 author: Nocnica Mellifera @@ -15,7 +15,7 @@ canonical: 'https://www.checklyhq.com/docs/learn/incidents/root-cause-with-trace Modern applications built with microservices and distributed architectures make root cause analysis (RCA) increasingly complex. When failures occur across dozens of interconnected services, traditional debugging methods fall short. This guide explains how combining distributed tracing with synthetic monitoring creates a powerful approach for faster incident resolution through vastly improved time to understand the root cause of failure. -## The Challenge of Modern Root Cause Analysis +## The challenge of modern root cause analysis One senior operations engineer I spoke to after a webinar mentioned his frustration with root cause analysis in his team: @@ -36,9 +36,9 @@ All of these types of failures could have happened at a SaaS company ten years a While we can use tools like synthetic monitoring to know that something isn’t working correctly, it’s become increasingly difficult to remediate failures, much less find the root cause. -## The Solution: Tracing + Synthetic Checks +## The solution: Tracing + synthetic checks -### Distributed Tracing +### Distributed tracing Traces provide a complete map of requests as they flow through your system: @@ -55,7 +55,7 @@ Example trace showing a failed payment process: ``` -### Synthetic Monitoring +### Synthetic monitoring Proactively test critical user journeys with: @@ -69,15 +69,15 @@ When combined, these approaches: 2. **Preserve context** across frontend and backend 3. **Accelerate RCA** with complete request histories -## Implementation Guide +## Implementation guide -### 1. Instrument Your Stack +### 1. Instrument your stack - Use synthetic checks for key user flows. - Add OpenTelemetry for tracing. - Correlate trace IDs with check results. -### 2. Build Your Observability Stack +### 2. Build your observability stack | Tool Type | Example Tools | Purpose | | --- | --- | --- | @@ -85,7 +85,7 @@ When combined, these approaches: | Synthetic | Checkly, Synthetics | Test user journeys proactively | | Alerting | Rootly, Opsgenie | Route incidents effectively | -### 3. Analyze Incidents +### 3. Analyze incidents When failures occur: @@ -96,7 +96,7 @@ When failures occur: - How long it took to fail - What dependencies were involved -## Real-World Example: E-Commerce Checkout Failure +## Real-world example: E-commerce checkout failure **Scenario**: Customers report payment failures during peak hours @@ -117,7 +117,7 @@ When failures occur: **Result**: MTTR reduced from 47 minutes to 8 minutes -## Key Benefits +## Key benefits 1. **Faster Detection** - Catch issues before users do @@ -129,7 +129,7 @@ When failures occur: - Identify weak points in architecture - Build resilience based on real failure patterns -## Getting Started +## Getting started 1. **Start small**: Instrument one critical user journey 2. **Correlate data**: Connect synthetic checks to traces diff --git a/learn/incidents/slo-sla-sli.mdx b/learn/incidents/slo-sla-sli.mdx index b8e778dab..10358e514 100644 --- a/learn/incidents/slo-sla-sli.mdx +++ b/learn/incidents/slo-sla-sli.mdx @@ -1,5 +1,5 @@ --- -title: SLA vs SLO vs SLI - What’s the Difference? Comparison with examples +title: SLA vs SLO vs SLI - What’s the difference? Comparison with examples displayTitle: SLA vs SLO vs SLI - What’s the Difference? sidebarTitle: SLA vs SLO vs SLI description: Avoid user‑reported outages with synthetic checks, anomaly detection, smart alerting, and rich failure traces for rapid detection. @@ -24,11 +24,11 @@ SLOs, or Service Level Objectives, are the specific goals that service providers | **Who Builds It?** | A collaborative effort involving service providers and customers, often led by technical teams. | A collaborative effort involving technical teams to set measurable goals within the SLA framework. | Developed by technical teams to measure and monitor specific aspects of service performance. | | **What Happens if It's Breached?** | Breaching SLA terms may lead to penalties, legal consequences, and reputation damage to the provider. | Breaching SLOs signifies a failure to meet performance goals, triggering corrective actions and potential reevaluation. | SLI breaches indicate deviations in specific performance metrics, requiring investigation and improvement. | -## What is an SLA (Service Level Agreement) +## What is an SLA (service level agreement) At its core, a [Service Level Agreement (SLA)](https://www.techtarget.com/news/service-level-agreement-SLA/847216/) defines the expectations between service providers and customers. Overcoming challenges such as technical intricacies, customer preferences, language clarity, and detailed documentation is key to optimizing SLA effectiveness. By embracing best practices, SLAs become dynamic tools fostering transparency, accountability, and customer satisfaction. -### SLA Challenges +### SLA challenges Hitting your SLAs can bring many challenges that demand a nuanced and strategic approach. Understanding and addressing these challenges is important for the success and effectiveness of SLAs: @@ -39,7 +39,7 @@ Hitting your SLAs can bring many challenges that demand a nuanced and strategic - **Monitoring Mechanisms:** Implementing robust mechanisms for [monitoring service level agreements](https://www.checklyhq.com/blog/how-to-monitor-all-the-nines-of-your-service-level-agreements/) is crucial. Regular assessments and timely feedback loops help identify and address deviations, ensuring service levels meet agreed-upon standards consistently. - **Commitment to Continuous Improvement:** SLAs are not static documents. They are living agreements that demand a commitment to continuous improvement. A proactive approach to refining processes and adapting to changing circumstances is necessary for sustained success. -### SLA Best Practices +### SLA best practices To overcome these challenges and ensure the effectiveness of SLAs, certain best practices should be observed: @@ -48,7 +48,7 @@ To overcome these challenges and ensure the effectiveness of SLAs, certain best - **Keep SLAs Simple and Use Clear Language:** Maintaining simplicity in SLAs is a best practice that cannot be overstated. Clear and straightforward language enhances understanding and reduces the risk of misinterpretation. - **Document Everything:** Comprehensive documentation is crucial for successful SLAs. Documenting all aspects of the agreement ensures transparency. It also provides a reference point for dispute resolution and aids in continuous improvement. -### Who Needs an SLA? +### Who needs an SLA? Understanding who benefits from SLAs is essential for businesses looking to establish effective service standards. In essence, SLAs are beneficial for: @@ -56,7 +56,7 @@ Understanding who benefits from SLAs is essential for businesses looking to esta - **Customers:** They have a transparent understanding of the services they can expect. - **Businesses:** SLAs contribute to accountability, transparency, and customer satisfaction, ultimately impacting the bottom line positively. -### SLA Examples +### SLA examples To illustrate the practical application and importance of effective SLA management, let's explore some real-world examples across various industries: @@ -66,15 +66,15 @@ To illustrate the practical application and importance of effective SLA manageme | IT Support | An agreement detailing response times for IT support requests, resolution times based on the severity of issues, and the modes of support available (e.g., phone, email, chat). | | Telecommunications | SLA for a telecom company can include network availability targets, call quality standards, and maintenance window notifications. | -## What is an SLO (Service Level Objective) +## What is an SLO (service level objective) [Service Level Objectives (SLOs)](https://www.gartner.com/en/information-technology/glossary/slo-service-level-objective) are critical to managing and maintaining reliable and efficient systems. An SLO is a set of quantitative measures that define the level of service a system must deliver. This helps teams align their performance goals with user expectations. SLOs play a pivotal role in ensuring that services meet user needs while allowing organizations to manage their resources effectively. -### SLO Challenges +### SLO challenges Implementing SLOs comes with a set of challenges. Teams often face difficulties in defining precise and meaningful objectives and striking the right balance between aggressiveness and achievability. The challenge lies in creating objectives that align with user expectations while being realistic regarding system capabilities. Additionally, unforeseen contingencies can impact the achievement of SLOs, requiring continuous adaptation and improvement. -### SLO Best Practices +### SLO best practices To overcome challenges associated with SLOs, it is essential to follow best practices that streamline the process and enhance the effectiveness of these objectives: @@ -83,11 +83,11 @@ To overcome challenges associated with SLOs, it is essential to follow best prac - **Create SLOs for Internal Systems:** While SLOs are often associated with customer-facing services, internal systems also benefit from performance metrics. Implementing SLOs for internal services ensures that the entire infrastructure operates at optimal levels. This contributes to overall organizational efficiency. - **Don’t Create More Than Necessary SLOs:** Creating an excessive number of SLOs can be counterproductive. Focus on the most critical aspects of your services and establish a manageable set of objectives. This enables teams to prioritize effectively and dedicate resources where they are most needed. -### Who Needs an SLO? +### Who needs an SLO? The adoption of SLOs is not limited to specific roles or teams. Anyone involved in delivering, managing, or maintaining services can benefit from implementing SLOs. Development teams, operations teams, and leadership play crucial roles in defining and achieving SLOs. SLOs serve as a unifying metric that aligns the efforts of various teams toward a common goal—ensuring a high-quality user experience. -### SLO Examples +### SLO examples To demonstrate how Service Level Objectives (SLOs) set the stage for measuring and achieving service quality, here are examples from various industries. @@ -97,25 +97,25 @@ To demonstrate how Service Level Objectives (SLOs) set the stage for measuring a | Online Banking | For an online banking service, an SLO can specify a transaction success rate of 99.5%, ensuring reliability and trust in digital transactions. | | Cloud Storage | A cloud storage service can have an SLO that guarantees data retrieval times of less than 300 milliseconds for 99% of requests, providing quick access to stored information. | -## What is an SLI (Service Level Indicator) +## What is an SLI (service level indicator) [Service Level Indicators (SLIs)](https://www.techtarget.com/searchcustomerexperience/definition/service-level-indicator) are fundamental components of service level management. They provide measurable metrics to evaluate the performance of a system. SLIs are specific, quantifiable measurements that give insights into various aspects of a service. This enables teams to assess the service’s reliability and effectiveness. -### SLI Challenges +### SLI challenges Implementing SLIs comes with its share of challenges. Defining metrics that accurately represent the user experience can be complex. Teams often struggle with selecting the right indicators that align with user expectations and business goals. Additionally, ensuring that SLIs remain relevant and meaningful over time requires continuous attention and adaptation. -### SLI Best Practices +### SLI best practices Overcoming challenges associated with SLIs involves following best practices that enhance their accuracy and relevance. - **Create Precise and Measurable SLIs:** SLIs should be crafted with precision, reflecting the specific aspects of a service that matter most to users. Measurable metrics allow for objective evaluation and facilitate data-driven decision-making. Avoid vague or overly broad indicators to ensure the effectiveness of SLIs. - **Keep SLIs Simple:** Simplicity is key when designing SLIs. Clear and straightforward indicators are easier to understand and communicate across teams. Avoid unnecessary complexity that can lead to confusion and misinterpretation of performance metrics. -### Who Needs an SLI? +### Who needs an SLI? The importance of SLIs extends to various roles within an organization. Anyone involved in the development, deployment, or maintenance of services can benefit from incorporating SLIs into their processes. Development teams use SLIs to monitor the impact of code changes. Operations teams leverage SLIs to ensure system reliability. Leadership relies on SLIs to make informed decisions about resource allocation and strategy. -### SLI Examples +### SLI examples To refine our understanding of service measurement further, let's examine some Service Level Indicators (SLIs) that quantify the performance of services. @@ -125,45 +125,45 @@ To refine our understanding of service measurement further, let's examine some S | API Response | In API services, an SLI could be the average response time for API calls, with a target of responding within 500 milliseconds for 95% of the requests. | | Customer Support Response | For a customer support team, an SLI can track the average response time to customer inquiries, with a goal of responding to 90% of inquiries within 1 hour. | -## Why are SLAs, SLOs, and SLIs Important? +## Why are SLAs, SLOs, and SLIs important? Service Level Agreements (SLAs), Service Level Objectives (SLOs), and Service Level Indicators (SLIs) are integral components of effective service management. Each of them serves a unique purpose in ensuring the delivery of high-quality services. Understanding their importance is paramount for organizations striving to meet user expectations and maintain operational excellence. -### Ensuring Accountability with SLAs +### Ensuring accountability with SLAs SLAs set the foundation for accountability and transparency. These agreements define the expected level of service a customer can anticipate. It also outlines measurable metrics such as response times, uptime, and resolution periods. By clearly defining these expectations, SLAs foster trust between service providers and customers. When complied with, SLAs help organizations demonstrate their commitment to delivering reliable and timely services. -### Aligning Objectives with SLOs +### Aligning objectives with SLOs SLOs bridge the gap between user expectations and system capabilities. These objectives establish quantifiable performance goals. This allows teams to align their efforts with user needs. SLOs serve as a roadmap for maintaining service quality. They help organizations strike a balance between ambitious targets and achievable benchmarks. Establishing SLOs encourages continuous improvement, adaptability, and a proactive approach to managing service levels. -### Gaining Insights Through SLIs +### Gaining insights through SLIs SLIs provide a granular view of service performance. These indicators offer specific, measurable metrics that serve as the building blocks for SLOs. SLIs enable teams to monitor various aspects of service. These range from latency and error rates to user interactions. By regularly evaluating SLIs, organizations gain valuable insights into the real-time health of their services. This process empowers them to make informed decisions, identify areas for improvement, and respond promptly to emerging issues. -### The Collective Impact +### The collective impact When integrated, SLAs, SLOs, and SLIs form a comprehensive framework for service excellence. SLAs provide a contractual foundation, SLOs establish performance objectives, and SLIs offer tangible metrics to measure success. This triad ensures a holistic approach to service management, aligning customer expectations with organizational capabilities. -## Practical Example: Implementing SLIs, SLOs, and SLAs for APIs +## Practical example: Implementing SLIs, SLOs, and SLAs for APIs In the context of managing a customer-facing, business-critical API, it's essential to establish clear standards and expectations to ensure high-quality service. Here, we dive into an example that outlines SLIs, SLOs, and SLAs, using a practical scenario. -### SLI: Service Level Indicator +### SLI: Service level indicator The SLI acts as a measure of the performance and reliability of the API. In this case, the SLI is defined by the API's ability to respond successfully with HTTP status codes ranging from 200 to 499, coupled with a response time of under one second. This metric is crucial because it quantifies the operational performance of the API from a technical standpoint, focusing on availability and speed. -### SLO: Service Level Objective +### SLO: Service level objective Building on the SLI, the SLO sets a target for the level of service the API aims to deliver. For our API, the objective is that the SLI conditions (response codes within 200-499 and response times below one second) are met for the 99th percentile of all requests. This means that out of 100 requests, at least 99 should satisfy these criteria. The SLO is a commitment to maintaining a high standard of service, ensuring that nearly all requests are handled efficiently and effectively. -### SLA: Service Level Agreement +### SLA: Service level agreement The SLA transforms the SLO into a formal agreement with the customer. It guarantees that the service will achieve the SLO targets for a specified period, in this case, a quarter. The SLA also outlines the compensation customers will receive if the service fails to meet these expectations. This compensation could take various forms, such as financial credits, discounts, or other remedies. The SLA is a crucial part of customer contracts, providing a legal framework that ensures accountability and offers reassurance to customers about the reliability of the service. By setting these SLIs, SLOs, and SLAs, the company not only commits to delivering a high-quality API service but also provides transparency and trust to its customers. This framework helps manage expectations, foster customer satisfaction, and drive continuous improvement in service performance. -## **How Checkly Can Help You Hit Your SLAs** +## **How Checkly can help you hit your SLAs** [Checkly](https://www.checklyhq.com/) focuses on Synthetic Monitoring to track how well websites, applications, and APIs work. Its goal is to help [meet Service Level Agreements (SLAs)](https://www.checklyhq.com/blog/how-to-monitor-all-the-nines-of-your-service-level-agreements/) with customers with its features such as API checks, Browser checks, heartbeat monitoring, etc. @@ -202,7 +202,7 @@ Checkly’s Browser checks can help you achieve your SLAs through: *To find out more about Checkly’s Browser checks & how to get started, check out [this article](/detect/synthetic-monitoring/browser-checks/overview).* -### **Checkly Best Practices** +### **Checkly best practices** If you’re using Checkly, here are some best practices that will help you make sure you’re doing everything you can to adhere to your SLAs. @@ -214,7 +214,7 @@ If you’re using Checkly, here are some best practices that will help you make ![a checkly dashboard](/images/learn/images/sla-03.png) -### **Integrating Into Your Existing Workflow** +### **Integrating into your existing workflow** Checkly enables you to monitor your SLAs by allowing you to monitor services closely and check how they perform worldwide in over 20 locations. You get instant alerts when there's any issue, helping you react quickly to fix it. The platform keeps an eye on services all the time and adjusts to new needs or changes. diff --git a/learn/incidents/what-is-incident-response.mdx b/learn/incidents/what-is-incident-response.mdx index 765dcd01a..38d37fee3 100644 --- a/learn/incidents/what-is-incident-response.mdx +++ b/learn/incidents/what-is-incident-response.mdx @@ -1,7 +1,7 @@ --- -title: What is Incident Response? Fundamentals and best practices +title: What is incident response? Fundamentals and best practices displayTitle: What is Incident Response? -sidebarTitle: What is Incident Response? +sidebarTitle: What is incident response? description: Learn the key types and stages of incident response—outages, performance issues, security events, user‑reported problems—and keep your services resilient. date: 2025-02-15 author: Nocnica Mellifera @@ -14,7 +14,7 @@ canonical: 'https://www.checklyhq.com/docs/learn/incidents/what-is-incident-resp --- "Incident Response" in the software industry refers to a time-critical response to some kind of availability incident. The terms are a bit vague since, although many incidents are also outages, not every incident is an outage of a service where it's unavailable to users. Whenever we need to gather one or more engineers to work outside of their scheduled work hours to handle a problem with our service, it's an incident. This intro page lists common incident categories, and the stages of incident response. -### Types of Incidents +### Types of incidents Understanding the different types of incidents is key to managing them well. Here are the main types: @@ -25,7 +25,7 @@ Understanding the different types of incidents is key to managing them well. Her By knowing these types, teams can handle each one in the best way. This helps keep services running smoothly and keeps customers happy. -### Stages of Incident Response +### Stages of incident response The incident response process helps teams handle problems quickly and effectively. As noted in the list, some stages may not happen in this order; for example the incident may be closed and reviewed with a root cause resolution not being deployed until later. Here are the key stages: @@ -42,7 +42,7 @@ The incident response process helps teams handle problems quickly and effectivel By following these stages, teams can handle incidents efficiently, reduce downtime, and keep services running smoothly. -## Best Practices of incident response +## Best practices of incident response Each of the stages of incident response has associated best practices: diff --git a/learn/kubernetes/centralized-logging.mdx b/learn/kubernetes/centralized-logging.mdx index 8f3f01440..3df2314f7 100644 --- a/learn/kubernetes/centralized-logging.mdx +++ b/learn/kubernetes/centralized-logging.mdx @@ -1,7 +1,7 @@ --- title: Centralized logging in Kubernetes with OpenTelemetry - guide with examples displayTitle: Centralized logging in Kubernetes with OpenTelemetry -sidebarTitle: Centralized Logging +sidebarTitle: Centralized logging description: Monitoring logs effectively in a Kubernetes environment requires tools that centralize and streamline log management. date: 2024-11-08 author: Nocnica Mellifera @@ -13,19 +13,19 @@ canonical: 'https://www.checklyhq.com/docs/learn/kubernetes/centralized-logging/ --- Monitoring logs effectively in a Kubernetes environment requires tools that centralize and streamline log management. With OpenTelemetry, Kubernetes administrators can collect, process, and export logs from applications and infrastructure, ensuring consistent data and reducing the need for multiple, disparate logging solutions. Here’s an overview of how OpenTelemetry supports centralized logging in Kubernetes and the practical benefits it offers. -### Why Centralized Logging Matters in Kubernetes +### Why centralized logging matters in Kubernetes Logs provide critical insights into application performance, errors, and security events. In a Kubernetes setup, workloads are distributed across many nodes, making it essential to have a centralized logging solution to collect logs in one place. Centralized logging enables teams to efficiently manage logs from across the entire Kubernetes cluster and prevents loss of logs during pod restarts or node replacements. The OpenTelemetry project, initially created to address distributed tracing, has expanded to include metrics and now, comprehensive logging support. With its recent logging capabilities, OpenTelemetry provides a unified framework for collecting and correlating logs alongside traces and metrics, ensuring consistency and reliability. -### Key Components of OpenTelemetry for Centralized Logging +### Key components of OpenTelemetry for centralized logging 1. **OpenTelemetry Collector**: The [OpenTelemetry Collector](/learn/opentelemetry/what-is-the-otel-collector/) is at the heart of centralized logging with OpenTelemetry. It’s a standalone agent that can be deployed on Kubernetes nodes, Windows, or Linux hosts, and it’s capable of collecting logs from multiple sources. In Kubernetes, the collector can capture logs, system metrics (such as CPU and memory usage), and metrics from third-party applications. 2. **Instrumentation Libraries**: OpenTelemetry includes libraries and SDKs for popular programming languages, which can add logging capabilities directly to application code. By using OpenTelemetry’s appenders, developers can export logs in OpenTelemetry’s native format, simplifying log management and reducing the overhead typically required for parsing and reshaping logs. 3. **Data Model and Semantic Conventions**: OpenTelemetry introduces a standardized data model and semantic conventions, ensuring that logs have consistent metadata and structure across the entire system. This is critical for efficient querying and analysis, as it eliminates the need for complex parsing and filtering. -### Benefits of Using OpenTelemetry for Centralized Logging +### Benefits of using OpenTelemetry for centralized logging OpenTelemetry’s approach to centralized logging addresses some common challenges in log management: @@ -33,7 +33,7 @@ OpenTelemetry’s approach to centralized logging addresses some common challeng - **Performance Optimization**: By processing logs directly in OpenTelemetry’s format, the collector minimizes CPU and memory usage associated with parsing and reshaping logs. Logs from OpenTelemetry-enabled applications can be sent directly to the collector without intermediary processing steps, saving resources. - **Correlation Across Data Types**: OpenTelemetry simplifies correlating logs, traces, and metrics. This correlation provides a holistic view of application performance, helping teams diagnose and resolve issues quickly. For instance, logs from a failed request can be directly linked to corresponding trace data, helping teams identify the root cause faster. -### How the OpenTelemetry Collector Works in Kubernetes +### How the OpenTelemetry Collector works in Kubernetes The OpenTelemetry Collector can be deployed as a DaemonSet in a Kubernetes cluster, running as an agent on each node. This setup allows the collector to: @@ -43,7 +43,7 @@ The OpenTelemetry Collector can be deployed as a DaemonSet in a Kubernetes clust The collector includes built-in parsers and transformation capabilities to handle logs in various formats, such as JSON or text. This flexibility is especially useful in Kubernetes environments where logs from different applications and services may not share a standard format. For more detail on deployment options for the collector, [see our guide to collector architecture](/learn/opentelemetry/what-is-the-otel-collector/). -### Implementing Centralized Logging with OpenTelemetry in Kubernetes +### Implementing centralized logging with OpenTelemetry in Kubernetes Here’s how to set up centralized logging in Kubernetes with OpenTelemetry: @@ -52,7 +52,7 @@ Here’s how to set up centralized logging in Kubernetes with OpenTelemetry: 3. **Define Transformations and Exports**: Use OpenTelemetry’s processing capabilities to normalize logs, add metadata, and apply semantic conventions. After processing, configure the collector to export logs to a centralized logging backend or a cloud-based logging service. 4. **Correlate Logs with Traces and Metrics**: The collector can correlate logs, traces, and metrics by applying consistent metadata and sampling rules. For instance, if you’re sampling traces at a certain rate, the collector can apply the same sampling rate to logs, ensuring that traces and logs remain aligned. -### Advantages of OpenTelemetry Logging in Kubernetes +### Advantages of OpenTelemetry logging in Kubernetes By adopting [OpenTelemetry for centralized logging](https://www.checklyhq.com/learn/opentelemetry/logs/), Kubernetes administrators gain several benefits: diff --git a/learn/kubernetes/events.mdx b/learn/kubernetes/events.mdx index 3cb0ff67e..a99be625f 100644 --- a/learn/kubernetes/events.mdx +++ b/learn/kubernetes/events.mdx @@ -1,5 +1,5 @@ --- -title: Kubernetes Events - A Native Resource for State Insight +title: Kubernetes events - A native resource for state insight displayTitle: Kubernetes Events sidebarTitle: Events description: In Kubernetes, **Events** are a native resource, providing insight into actions and state changes of objects in the cluster. Events are platform-generated messages accessible through the Kubernetes API, often used by operators and users to understand what has happened to various Kubernetes objects. @@ -20,7 +20,7 @@ Events serve as valuable resources for monitoring and debugging, allowing users --- -## Event Mechanics +## Event mechanics Kubernetes Events can be accessed by querying the Kubernetes API. Each Event describes an action related to a Kubernetes object, such as a Pod, Deployment, or Node. These Events are often labeled with the following attributes: - **Type**: Indicates whether the Event is `Normal` (standard actions) or `Warning` (indicating potential issues). @@ -31,7 +31,7 @@ Kubernetes Events can be accessed by querying the Kubernetes API. Each Event des --- -### Example: Viewing Events for a Pod +### Example: Viewing events for a pod To see Events associated with a specific Pod, use the `kubectl describe` command. Here’s an example output for a Pod named `webapp-5d8dbbd4bb-2lqfs`: @@ -52,7 +52,7 @@ Warning BackOff 40s kubelet, ip-10-0-1-233 Back-off restartin In this output, each Event shows a timestamp and message about actions related to the Pod, from scheduling to a restart back-off warning. -### Example: Viewing Events for a Namespace +### Example: Viewing events for a namespace To retrieve Events for all resources in a namespace, you can use the `kubectl get events` command: @@ -71,11 +71,11 @@ LAST SEEN TYPE REASON OBJECT MESSAGE This output shows Events from the namespace, covering various resources, such as Pods, ReplicaSets, and Deployments, with some Events indicating a container restart issue for further investigation. --- -## Monitoring and Alerting with Events +## Monitoring and alerting with events Events provide real-time insights, allowing operators to monitor Kubernetes activity. Although not commonly used for direct automation, some approaches leverage Events for alerting and monitoring: -### Event Exporters +### Event exporters An **Event exporter** can expose Events as metrics to external monitoring systems. For example, Prometheus can scrape metrics derived from Events, enabling alerting based on conditions like frequent container restarts or persistent failures in Pod scheduling. diff --git a/learn/kubernetes/klog.mdx b/learn/kubernetes/klog.mdx index c45e7f24d..345fa956e 100644 --- a/learn/kubernetes/klog.mdx +++ b/learn/kubernetes/klog.mdx @@ -1,5 +1,5 @@ --- -title: Introducing klog - The Kubernetes Logging Library +title: Introducing klog - The Kubernetes logging library displayTitle: klog for structured logging sidebarTitle: klog description: Meet klog, the Kubernetes-specific logging library designed to provide structured and reliable logging across Kubernetes components. In this post, we’ll dive into klog’s purpose, key features, and how it’s transforming logging in Kubernetes. @@ -20,7 +20,7 @@ klog is the logging library used within Kubernetes to manage logs across its var Starting with Kubernetes v1.19, klog adopted structured logging to make log entries easier to parse, search, and analyze. This change enables administrators to move away from unstructured plain text logs, which often require custom parsing and lead to inconsistencies across components. Structured logs also allow for better integration with logging tools like Elasticsearch, Fluent Bit, and Grafana, making it easier to monitor, alert, and troubleshoot. -### Why klog Matters for Kubernetes Logging +### Why klog matters for Kubernetes logging In Kubernetes, logs are generated by numerous components, each responsible for specific functions. For example: @@ -30,7 +30,7 @@ In Kubernetes, logs are generated by numerous components, each responsible for s Managing these logs without a consistent format can quickly become overwhelming. klog solves this issue by providing a structured approach to logging, allowing log aggregation and analysis tools to work more effectively. By adopting structured logging, Kubernetes improves observability, making logs easier to query and analyze. -### Key Features of klog +### Key features of klog 1. **Structured Logging with Key-Value Pairs**: klog enables structured logging by supporting key-value pairs, allowing log entries to be machine-readable and easily parsable. This structure simplifies log queries, as logs with consistent fields can be filtered and aggregated efficiently. @@ -41,17 +41,17 @@ klog provides new methods (`InfoS` and `ErrorS`) for logging informational and e 4. **Seamless Integration with Kubernetes Components**: klog is embedded in the core of Kubernetes, meaning it’s natively supported by key system components. This allows for out-of-the-box structured logging across all critical areas of a Kubernetes cluster. -### klog vs. Glog: Why the Shift? +### klog vs. Glog: Why the shift? Kubernetes previously relied on `glog`, but as the system grew, the limitations of `glog` became apparent. Glog’s lack of structured logging meant that logs were generated as plain text, making them hard to parse and analyze. With structured logging increasingly becoming the standard in observability, Kubernetes needed a library that could support a consistent format across components. klog, with its JSON support and key-value pair structure, was developed to meet these needs. Structured logging also allows Kubernetes to integrate more easily with third-party monitoring tools, as JSON logs are more compatible with Elasticsearch, Grafana, Prometheus, and other tools that rely on consistent data formatting. -### Key klog Methods: `InfoS` and `ErrorS` +### Key klog methods: `InfoS` and `ErrorS` To facilitate structured logging, klog introduced the `InfoS` and `ErrorS` methods. These methods replace traditional logging functions by enforcing a structured, key-value format. -### 1. **InfoS**: Log Informational Messages +### 1. **InfoS**: Log informational messages The `InfoS` method captures general information in a structured format. This method requires a message followed by key-value pairs, where each key represents a field, and the associated value provides context. @@ -62,7 +62,7 @@ klog.InfoS("Pod status updated", "pod", "kube-dns", "status", "ready") This example logs an informational message, specifying the pod name (`kube-dns`) and its current status (`ready`). -### 2. **ErrorS**: Log Error Messages +### 2. **ErrorS**: Log error messages The `ErrorS` method is used for error logging. It requires an error as the first parameter, followed by a descriptive message and key-value pairs that provide context for the error. @@ -73,7 +73,7 @@ klog.ErrorS(err, "Failed to update pod status", "pod", "kube-dns") In this example, `ErrorS` logs an error with a detailed message and relevant pod information. This structure makes it easier to track down issues within specific pods or components. -### Example: JSON Output with klog +### Example: JSON output with klog klog’s structured approach outputs logs in JSON format, making it easier to parse and analyze. Here’s what a typical JSON log entry might look like when generated by klog: @@ -91,27 +91,27 @@ klog’s structured approach outputs logs in JSON format, making it easier to pa Each log entry contains key-value pairs for essential information like timestamp, log level, message, pod name, and status, making it easy for log management tools to filter and analyze the data. -### Benefits of Structured Logging with klog +### Benefits of structured logging with klog 1. **Improved Observability**: Structured logging makes it easier to monitor Kubernetes environments by providing consistent, easily searchable logs. 2. **Efficient Log Analysis**: By outputting logs in JSON, klog supports efficient parsing and querying, which is essential when working with large volumes of data. 3. **Enhanced Integration**: JSON logs integrate seamlessly with observability tools, allowing Kubernetes administrators to visualize and analyze logs more effectively. 4. **Reduced Parsing Complexity**: Structured logs eliminate the need for custom parsing, as log fields are consistent across entries, enabling more straightforward log processing. -### Best Practices for Using klog in Kubernetes +### Best practices for using klog in Kubernetes 1. **Use Key-Value Pairs Consistently**: Define standard fields for commonly logged events to keep logs consistent across components. For instance, use `"pod"`, `"namespace"`, and `"status"` consistently in pod-related logs. 2. **Set Log Levels Appropriately**: Use log levels (`InfoS` for informational logs and `ErrorS` for errors) to differentiate critical information from general updates. This ensures that logs are meaningful and that critical events are easy to identify. 3. **Monitor Log Performance**: Structured logging can add overhead, so monitor klog’s impact on performance, particularly in high-traffic clusters. 4. **Integrate with Log Management Tools**: klog is compatible with log management systems that support JSON, so integrate it with tools like Fluent Bit, Prometheus, and Grafana to visualize and analyze logs effectively. -### Implementing klog in Your Kubernetes Environment +### Implementing klog in your Kubernetes environment To enable structured logging with klog, Kubernetes administrators can configure components to use `InfoS` and `ErrorS` methods and output JSON-formatted logs. This setup standardizes logs, improving the efficiency of log aggregation and analysis pipelines. For a fully integrated solution, combine klog with logging agents like Fluent Bit or Fluentd. These agents can collect logs from across the Kubernetes cluster, parse them, and forward them to centralized storage or monitoring systems. -### Future of klog and Structured Logging in Kubernetes +### Future of klog and structured logging in Kubernetes The move toward structured logging reflects a larger industry trend towards improving observability across distributed systems. With features like contextual logging and enhanced compatibility with monitoring tools, klog will continue to improve the reliability and manageability of Kubernetes logging. diff --git a/learn/kubernetes/logging-best-practices.mdx b/learn/kubernetes/logging-best-practices.mdx index eebd92d4d..fd3b87878 100644 --- a/learn/kubernetes/logging-best-practices.mdx +++ b/learn/kubernetes/logging-best-practices.mdx @@ -1,7 +1,7 @@ --- -title: Logging in Kubernetes - Best Practices +title: Logging in Kubernetes - Best practices displayTitle: Logging in Kubernetes - Best Practices -sidebarTitle: Best Practices +sidebarTitle: Best practices description: Monitoring logs effectively in a Kubernetes environment requires tools that centralize and streamline log management. date: 2024-11-08 author: Nocnica Mellifera @@ -13,17 +13,17 @@ canonical: 'https://www.checklyhq.com/docs/learn/kubernetes/logging-best-practic --- Logging in Kubernetes can be a challenge, especially when dealing with data across a distributed, containerized system. To keep your logs efficient and actionable, it's essential to understand logging best practices, from handling diverse formats to managing back pressure effectively. Here are the best practices for Kubernetes logging, focused on tools, performance, and scalability. -### 1. Define Your Logging Goals +### 1. Define your logging goals The main goal of logging isn’t just to collect data—it’s to analyze it and gain insights into your system's health and performance. Collecting excess logs can create noise, so start by defining clear goals. Consider which data is essential for troubleshooting, compliance, and performance monitoring, and focus on collecting only that information. This targeted approach helps reduce unnecessary log volume and keeps analysis efficient. -### 2. Centralize and Standardize Logging +### 2. Centralize and standardize logging Kubernetes applications can produce logs in various formats and locations. Some applications write to standard output, while others log to specific files. In addition, different applications, such as NGINX, syslog, or even Windows services, may log in entirely different formats. Use a centralized logging system to consolidate all logs into a single view. A common tool for this purpose is **Fluent Bit**, which is lightweight, supports various inputs and outputs, and has a plugin system that allows it to integrate with numerous backends. Fluent Bit’s flexibility makes it a solid choice for aggregating logs from multiple sources and delivering them in a standardized format, such as JSON. -### 3. Structure Your Logs +### 3. Structure your logs Unstructured logs (raw text logs) can be difficult to parse and analyze, especially at scale. Structuring logs, ideally in a key-value format, makes it easier to query and process them. Consider using structured logging formats like JSON to provide clear, consistent fields (e.g., timestamp, log level, message). Fluent Bit can handle log parsing and transformation to convert unstructured logs into a structured format. @@ -41,11 +41,11 @@ For example, rather than storing a plain log message, structure it to include re ``` -### 4. Enrich Logs with Contextual Information +### 4. Enrich logs with contextual information In distributed systems, it’s often hard to pinpoint where an issue occurred based on logs alone. Enrich your logs with additional metadata, such as the Kubernetes namespace, pod name, and container ID. This metadata provides valuable context that makes debugging easier. Fluent Bit can automatically add Kubernetes metadata to logs, providing instant visibility into which parts of the system are generating specific logs. -### 5. Filter and Reduce Log Volume +### 5. Filter and reduce log volume Logging everything can quickly lead to storage and performance issues, especially with high log volumes. It’s essential to filter out non-critical logs, such as verbose debug logs, to reduce unnecessary data. Implement filters to retain only the logs you need, based on severity (e.g., only errors and warnings in production environments). @@ -59,7 +59,7 @@ In Fluent Bit, you can apply filters to drop debug-level logs in production. For ``` -### 6. Handle Sensitive Data Securely +### 6. Handle sensitive data securely Logs can sometimes contain sensitive information, such as user IDs or payment data. To prevent exposing sensitive data, redact or mask it in logs. Fluent Bit supports redaction and can modify logs to obscure sensitive data before it’s stored or transmitted. @@ -73,13 +73,13 @@ Example: Use the `modify` filter's `Set` rule to overwrite a sensitive field, su ``` -### 7. Use Logs-to-Metrics Conversion +### 7. Use logs-to-metrics conversion Some logs contain high-frequency, repetitive events that might be more useful as metrics rather than logs. Converting these logs into metrics can improve performance and reduce storage needs. For instance, tracking the number of failed authentication attempts is often more efficient as a metric. Fluent Bit can convert log entries to metrics, which can then be visualized and analyzed in tools like Prometheus. This approach reduces storage costs and enhances visibility for events that are better tracked over time. -### 8. Manage Back Pressure and Buffering +### 8. Manage back pressure and buffering In high-throughput environments, the risk of back pressure increases, especially when logs are sent to remote endpoints with limited processing capacity. Fluent Bit provides buffering options, including in-memory and file-based buffers, to handle spikes in log traffic. Using a file-based buffer is generally more reliable for production, as it prevents data loss if in-memory buffers are exhausted. @@ -103,13 +103,13 @@ Configure Fluent Bit with file-based buffering for resilience: ``` -### 9. Monitor Log Pipeline Health +### 9. Monitor log pipeline health Once your logging infrastructure is in place, monitor its health to ensure consistent performance. Metrics like input and output rates, dropped logs, and processing latency can reveal bottlenecks and prevent data loss. You can use Prometheus to monitor Fluent Bit’s internal metrics and set up alerts for issues like increased log drop rates or high memory usage. Regular monitoring helps you catch problems early and ensures that your logging pipeline remains effective. -### 10. Plan for Scale +### 10. Plan for scale Kubernetes clusters grow over time, so it’s essential to design your logging solution to scale with your application. Ensure your log storage backend can handle increased volumes, and consider using Fluent Bit’s load-balancing capabilities if you have multiple log destinations. diff --git a/learn/kubernetes/monitoring-challenges.mdx b/learn/kubernetes/monitoring-challenges.mdx index e032944bf..c0e02b063 100644 --- a/learn/kubernetes/monitoring-challenges.mdx +++ b/learn/kubernetes/monitoring-challenges.mdx @@ -1,5 +1,5 @@ --- -title: Learn How to Observe and Monitor your Kubernetes Environment with Open Source Tools +title: Learn how to observe and monitor your Kubernetes environment with open source tools displayTitle: The Challenge of Monitoring Production Kubernetes - Insights and Tools sidebarTitle: Monitoring Kubernetes description: Managing Kubernetes in production is no small feat, especially when it comes to monitoring and observability. @@ -13,39 +13,39 @@ canonical: 'https://www.checklyhq.com/docs/learn/kubernetes/monitoring-challenge --- Managing Kubernetes in production is no small feat, especially when it comes to monitoring and observability. As modern applications grow in complexity, traditional methods of monitoring, limited to CPU and memory usage, often fall short. In this article, we explore the unique challenges of monitoring Kubernetes environments and the open-source tools that can improve visibility and control. -### The Layers of Complexity in Kubernetes +### The layers of complexity in Kubernetes Starting with Kubernetes can be straightforward—deploying a service, setting up replicas, and configuring basic settings. But as deployment scales, the complexity grows significantly. Organizations must manage stateful services, custom resource definitions (CRDs), networking, and more, which are essential to production-grade Kubernetes. Even experienced administrators can find these layers challenging, especially as each layer adds new demands and potential points of failure. To aid with this complexity, the Cloud Native Computing Foundation (CNCF) offers a trail map of projects suited to various aspects of Kubernetes management, from containerization to continuous integration, service discovery, and, importantly, observability. -### The Core of Observability: Logs, Metrics, and Traces +### The core of observability: Logs, metrics, and traces Observability in Kubernetes focuses on three pillars: logs, metrics, and traces. Each plays a distinct role in providing a clear picture of an application’s health and performance. -### 1. Centralized Logging +### 1. Centralized logging In dynamic, cloud-native environments, centralized logging is essential. Logs help trace what happened in each instance, and they provide necessary details for compliance, especially in regulated industries like finance, which often require logs to be retained for years. With centralized logging, administrators avoid the pitfalls of ephemeral logging. For example, if Kubernetes nodes are updated or workloads shift, logs can disappear. Tools like Loki, an open-source log aggregation tool, enable centralized logging by collecting logs across services and making them accessible in tools like Grafana. This setup ensures that logs are available from a central point, reducing the need to search individual nodes or pods. -### 2. Metrics Collection +### 2. Metrics collection Metrics provide a big-picture view of resource consumption and application health over time. Unlike logs, which capture individual events, metrics are aggregated and are ideal for spotting trends, such as CPU or memory usage spikes, that indicate resource needs or scaling requirements. Prometheus is a widely used tool in Kubernetes environments for metrics collection. Combined with Grafana, which provides visualization, administrators can access real-time dashboards that show cluster CPU usage, memory utilization, and other metrics. These insights are invaluable in optimizing resources and setting up auto-scaling rules to adjust to application demand. -### 3. Distributed Tracing +### 3. Distributed tracing With microservices architectures, distributed tracing is crucial. It tracks the journey of requests across services, helping identify bottlenecks and pinpointing where failures occur. This is particularly helpful in production, where diagnosing issues quickly is critical to maintaining uptime. Jaeger, a distributed tracing tool, integrates with OpenTelemetry to capture trace data across microservices, making it possible to follow a request’s entire journey and spot where time is spent or where errors occur. This visibility is essential for optimizing performance and understanding how services interact. -### OpenTelemetry: A Standardized Approach +### OpenTelemetry: A standardized approach OpenTelemetry is a vendor-neutral standard that simplifies observability by consolidating data from multiple sources. It offers a single framework for instrumenting code, collecting, and exporting logs, metrics, and traces, reducing the need to install multiple agents or integrate separate SDKs. OpenTelemetry allows switching backends without major reconfiguration, avoiding vendor lock-in. -### Challenges in Kubernetes Observability +### Challenges in Kubernetes observability Monitoring Kubernetes comes with its own set of challenges: @@ -53,7 +53,7 @@ Monitoring Kubernetes comes with its own set of challenges: - **Vendor Lock-In**: Proprietary monitoring tools can lead to lock-in. Open-source and standards-based tools like OpenTelemetry and Grafana help avoid this. - **High Setup Overheads**: While the ecosystem offers many observability tools, setting them up and maintaining them can be complex. -### Tools to Consider +### Tools to consider Here are a few recommended tools for Kubernetes observability: diff --git a/learn/kubernetes/node-problem-detector.mdx b/learn/kubernetes/node-problem-detector.mdx index d96efa2f0..575ae4480 100644 --- a/learn/kubernetes/node-problem-detector.mdx +++ b/learn/kubernetes/node-problem-detector.mdx @@ -14,23 +14,23 @@ canonical: 'https://www.checklyhq.com/docs/learn/kubernetes/node-problem-detecto The **Node Problem Detector (NPD)** is a Kubernetes tool for monitoring the health of nodes. Designed to identify and report a range of node issues, NPD aims to maintain cluster stability by detecting faulty nodes and reporting them to the Kubernetes API server, so that other components can keep workloads off potentially unstable environments. NPD's purpose is to make sure workloads only run on healthy nodes, minimizing disruptions from faulty node behavior. -### How Node Problem Detector Works +### How Node Problem Detector works Node Problem Detector operates by running as a DaemonSet on each node in the Kubernetes cluster. It monitors system logs and checks for specific conditions or failures that could compromise the node's stability. Once NPD detects an issue, it reports it to the API server as a node condition or an event. NPD does not cordon the node itself. A separate remedy system, such as the [Descheduler](https://github.com/kubernetes-sigs/descheduler), Cluster API's MachineHealthCheck or your cloud provider's node auto-repair, can act on these conditions and mark the node as "unschedulable" so the scheduler excludes it. -### Remediation and Challenges +### Remediation and challenges While NPD does identify and isolate nodes with issues, automatically remediating these problems can be more challenging. Some of the common issues, like a read-only root filesystem, may point to deeper hardware faults or configurations that may need manual intervention. NPD's role is limited to problem detection; it doesn’t solve the underlying issues, which often require hardware fixes or support from system constructors, especially in physical environments. In virtualized environments, such as on cloud-managed Kubernetes clusters, nodes flagged by NPD can often be drained and replaced. This is common in platforms like Azure Kubernetes Service (AKS), where a failing node can be terminated, and a new one created by the autoscaler. However, simply replacing nodes might not address the underlying cause, especially if it stems from node misconfiguration or application-related issues. -### Use Cases and Limitations +### Use cases and limitations NPD's effectiveness shines in physical clusters where hardware inconsistencies can cause unexpected issues. Having NPD exclude problematic nodes prevents further complications and can be a stopgap until the hardware can be inspected or replaced. In virtual environments, NPD's role can sometimes be limited, as issues tend to arise more from configuration or workload setup, both of which should ideally be resolved in staging before hitting production. In summary, Node Problem Detector acts as a health monitoring and early-warning system, isolating problematic nodes to protect workload stability. It’s especially valuable in detecting issues in physical nodes where hardware problems may be more common. However, for automated remediation in virtual clusters, the approach is usually to replace the node entirely, although this doesn’t address root causes directly. -## How to Enable the Node Problem Detector +## How to enable the Node Problem Detector To enable **Node Problem Detector (NPD)** on your Kubernetes cluster, follow these steps to deploy and configure it as a DaemonSet. This deployment will ensure that NPD runs on each node, actively monitoring for issues and reporting them as node conditions and events. @@ -44,7 +44,7 @@ kubectl apply -f https://k8s.io/examples/debug/node-problem-detector.yaml This command downloads and applies a predefined DaemonSet configuration for NPD, ensuring it runs on each node in your cluster. The configuration file contains necessary setup for resource limits, logging, and permissions needed by NPD to function properly. -### 2. Verify the Deployment +### 2. Verify the deployment After deploying the DaemonSet, confirm that NPD is running on each node: @@ -54,7 +54,7 @@ kubectl get daemonset -n kube-system node-problem-detector This command checks the status of the NPD DaemonSet in the `kube-system` namespace, where it’s typically deployed. Look for the `DESIRED`, `CURRENT`, and `AVAILABLE` fields to confirm that the DaemonSet is running on all nodes as expected. -### 3. Check Node Problem Detector Logs +### 3. Check Node Problem Detector logs To see what issues NPD is detecting, check its logs. This can be useful for troubleshooting or confirming that NPD is actively monitoring node health: @@ -64,7 +64,7 @@ kubectl logs -l k8s-app=node-problem-detector -n kube-system This command fetches logs from all pods in the NPD DaemonSet, allowing you to review any node issues that NPD has detected. -### 4. Configure Node Problem Detector (Optional) +### 4. Configure Node Problem Detector (optional) The default configuration may not cover all specific needs of your cluster. For example, you can customize what types of problems NPD detects by modifying the configuration file or using custom plugins. To edit NPD’s configuration, download the DaemonSet YAML file, make necessary changes, and reapply it: @@ -74,7 +74,7 @@ kubectl apply -f /path/to/your-modified-node-problem-detector.yaml Refer to the official [Node Problem Detector documentation](https://github.com/kubernetes/node-problem-detector) for available configuration options and plugins. Customizing NPD lets you tailor detection parameters to your environment, making it more effective in identifying relevant node issues. -### 5. Confirm NPD’s Functionality +### 5. Confirm NPD’s functionality To ensure NPD is operating correctly, simulate a node condition or trigger an event that it should detect. Verify that the node shows the new condition (for example with `kubectl describe node`) or that an appropriate event is logged when NPD reports the condition. diff --git a/learn/kubernetes/operators-metrics.mdx b/learn/kubernetes/operators-metrics.mdx index 35a865b6f..0073c81ba 100644 --- a/learn/kubernetes/operators-metrics.mdx +++ b/learn/kubernetes/operators-metrics.mdx @@ -1,5 +1,5 @@ --- -title: Introduction to Kubernetes Operators - scraping metrics with Prometheus +title: Introduction to Kubernetes operators - scraping metrics with Prometheus displayTitle: sidebarTitle: Operators description: Operators in Kubernetes enable custom automation by encapsulating specific operational knowledge within Kubernetes itself. They function as custom controllers that manage complex applications and provide features like automated deployment, scaling, and management. @@ -20,7 +20,7 @@ With operators, you can manage resources beyond the built-in types like Pods and Kubebuilder is a development framework for building Kubernetes operators using the Go programming language. It provides project scaffolding, resource definitions, and controller logic to simplify operator creation. In short, Kubebuilder allows developers to create CRDs (Custom Resource Definitions) and controllers, which watch Kubernetes resources and act upon changes. -#### Setting Up a Project with Kubebuilder +#### Setting up a project with Kubebuilder The typical process starts by setting up a basic project structure using the `kubebuilder init` command. This scaffolds the folders and files necessary for an operator project. The following commands initialize a project and create a custom API for a simple application: @@ -31,7 +31,7 @@ kubebuilder create api --group app --version v1 --kind WebApp This creates a project structure that includes an API definition for `WebApp`, a custom resource that will deploy and manage a Kubernetes Deployment and Service. -#### Adding Metrics to the Operator +#### Adding metrics to the operator For observability, we can integrate Prometheus metrics into the operator. In Kubernetes, Prometheus can scrape data from custom endpoints to provide insights into application behavior. By using the `prometheus.NewCounter` method from the Prometheus Go client, we set up counters to track resource actions, such as the creation and deletion of `WebApp` instances. @@ -59,7 +59,7 @@ func init() { Each time the reconciliation loop (the main loop of the controller) handles a creation or update event, the counter increments. -#### Deploying Prometheus to Scrape Metrics +#### Deploying Prometheus to scrape metrics You must configure Prometheus to scrape the operator’s metrics endpoint. Recent Kubebuilder scaffolds serve metrics over HTTPS on port `8443` and require authentication. The example below assumes plain HTTP on port `8080`, which you get by starting the manager with `--metrics-bind-address=:8080 --metrics-secure=false`. To achieve this, add a scrape configuration to the Prometheus setup, pointing to the operator service endpoint: @@ -74,7 +74,7 @@ scrape_configs: With Prometheus deployed, the operator exposes metrics under the `/metrics` path, which Prometheus regularly scrapes to collect data. -#### Running the Operator and Observing Metrics +#### Running the operator and observing metrics After deploying the operator to a Kubernetes cluster (e.g., a local KIND cluster), we can create custom `WebApp` resources that initiate deployments. By applying YAML files with the custom `WebApp` definitions, developers can observe metrics that Prometheus scrapes and view them in a dashboard like Grafana. diff --git a/learn/kubernetes/overview.mdx b/learn/kubernetes/overview.mdx index 6c3afbb28..1f4a70524 100644 --- a/learn/kubernetes/overview.mdx +++ b/learn/kubernetes/overview.mdx @@ -1,5 +1,5 @@ --- -title: Learn How to Observe and Monitor your Kubernetes +title: Learn how to observe and monitor your Kubernetes displayTitle: Monitoring Kubernetes sidebarTitle: Overview description: Learn OpenTelemetry with Checkly. Add monitoring to every piece of your stack with the open standards and open-source tools. @@ -12,7 +12,7 @@ canonical: 'https://www.checklyhq.com/docs/learn/kubernetes/overview/' Learn about monitoring Kubernetes. -## Getting Started +## Getting started -## Diving Deeper +## Diving deeper diff --git a/learn/monitoring/frontend-monitoring.mdx b/learn/monitoring/frontend-monitoring.mdx index 55b5bd247..a629f2000 100644 --- a/learn/monitoring/frontend-monitoring.mdx +++ b/learn/monitoring/frontend-monitoring.mdx @@ -1,7 +1,7 @@ --- -title: Frontend Monitoring - Benefits, Challenges, and Top Tools +title: Frontend monitoring - Benefits, challenges, and top tools displayTitle: Frontend Monitoring - a beginner's guide -sidebarTitle: Frontend Monitoring +sidebarTitle: Frontend monitoring description: Discover the benefits, challenges, and top tools for frontend monitoring. Learn how to track performance, detect issues, and optimize user experience. date: 2024-12-15 author: Nocnica Mellifera @@ -26,14 +26,14 @@ Frontend monitoring ensures seamless user experiences by observing and analyzing In this article, we’ll cover the basics of frontend monitoring, explore its various types, key metrics, benefits, and challenges, and review some top tools to help you manage and optimize your applications effectively. -## What is Frontend Monitoring? +## What is frontend monitoring? Frontend monitoring involves tracking and analyzing the performance, reliability, and user experience of web applications from the user’s perspective. Frontend monitoring can either occur by observing users real interactions on the frontend (real user monitoring) or by sending an automated system to interact with your frontend (synthetic user monitoring). It helps teams identify issues like slow page load times, JavaScript errors, or failed API calls that can negatively impact user satisfaction. -## Types of Frontend Monitoring +## Types of frontend monitoring **Proactive Monitoring** @@ -81,13 +81,13 @@ APM is a general term, usually referring to a combined solution that includes bo --- -## How Frontend Monitoring Works +## How frontend monitoring works Frontend monitoring tools capture data through a combination of synthetic tests, browser instrumentation, and real user interactions. These tools generate insights by analyzing performance metrics, logging errors, and tracking user behavior. --- -## Key Components of Frontend Application Monitoring +## Key components of frontend application monitoring - **Performance Metrics**: Monitor loading speeds, [rendering times, and resource usage](https://www.checklyhq.com/learn/playwright/performance/#performance-with-headless-tools). - **Error Detection**: Identify JavaScript errors, API failures, and crashes. Crash reporting can be a complex problem but it’s great if it’s possible to report some details from user browser crashes. @@ -95,7 +95,7 @@ Frontend monitoring tools capture data through a combination of synthetic tests, --- -## Key Metrics in Frontend Monitoring +## Key metrics in frontend monitoring The key metrics for frontend monitoring—*performance*, *user interactions*, *errors*, and *availability*—are crucial for understanding and optimizing the user experience. **Performance** metrics, including page load time and Core Web Vitals (e.g., Largest Contentful Paint, Interaction to Next Paint), measure how fast and smoothly content is delivered to users. **User interactions** capture events like clicks, form submissions, and navigations to gauge how users engage with the application. **Errors** track JavaScript exceptions, resource failures, and API issues, helping teams identify and resolve defects impacting functionality. **Availability** monitors uptime and service reachability to ensure the application is consistently accessible. Together, these metrics provide a comprehensive view of application health, enabling teams to improve performance, address issues proactively, and enhance the overall user experience. @@ -110,7 +110,7 @@ Key metrics in detail: --- -## Common Use Cases of Frontend Monitoring +## Common use cases of frontend monitoring - **Monitoring Page Load Times**: [Ensure optimal page rendering speed](/detect/synthetic-monitoring/browser-checks/performance-metrics#total-blocking-time). - **Tracking Third-Party Services**: No amount of pre-deploy testing with stubs of third party services can find all the possible interaction problems with those services. Frontend monitoring can detect issues caused by external libraries or APIs. @@ -119,7 +119,7 @@ Key metrics in detail: --- -## Benefits of Frontend Monitoring +## Benefits of frontend monitoring **Proactive Issue Detection** @@ -139,7 +139,7 @@ By identifying specific areas that require attention, monitoring data enables te --- -## Challenges of Frontend Monitoring +## Challenges of frontend monitoring **Managing Tool Sprawl and Integration Issues** @@ -176,7 +176,7 @@ Frontend monitoring alone cannot provide a complete view of an application’s h --- -## How to Choose the Right Frontend Monitoring Tool +## How to choose the right frontend monitoring tool Consider features like synthetic monitoring, RUM, session replay, language compatibility, and security. Evaluate pricing, ease of use, and whether an agent or agentless setup fits your needs. @@ -184,7 +184,7 @@ Consider features like synthetic monitoring, RUM, session replay, language compa Frontend monitoring has historically lagged behind backend systems in sophistication and integration. With OpenTelemetry (OTel), frontend monitoring can now achieve deeper insights into user experiences. However, it also brings unique challenges that require careful consideration. -## Challenges in Using OpenTelemetry for Frontend Monitoring** +## Challenges in using OpenTelemetry for frontend monitoring** **1. Initial Complexity of Setup** @@ -215,7 +215,7 @@ Traditional frontend monitoring tools often report *what* is happening (e.g., a OpenTelemetry opens a new frontier for frontend observability, but it’s not a plug-and-play solution. Teams must balance instrumentation depth with performance and focus on collecting the data that best illuminates user experiences. By addressing these challenges head-on, developers can achieve a robust, connected view of their systems and elevate the standard of frontend monitoring. -## Developing a Frontend Monitoring Strategy: A Step-by-Step Guide +## Developing a frontend monitoring strategy: A step-by-step guide 1. **Identify Key Metrics**: Focus on what matters most to your application. 2. **Select Tools**: Choose tools that integrate with your tech stack. @@ -224,7 +224,7 @@ OpenTelemetry opens a new frontier for frontend observability, but it’s not a --- -## How Can Checkly Help with Frontend Monitoring? +## How can Checkly help with frontend monitoring? Checkly performs synthetic monitoring with the power of Playwright for robust testing of key workflows. By simulating real-world scenarios, it ensures applications remain functional and performant under varying conditions. diff --git a/learn/monitoring/https-for-app-developers.mdx b/learn/monitoring/https-for-app-developers.mdx index edf59ef78..da32458b4 100644 --- a/learn/monitoring/https-for-app-developers.mdx +++ b/learn/monitoring/https-for-app-developers.mdx @@ -1,5 +1,5 @@ --- -title: HTTPS Fundamentals - Beginner's Guide for App Developers +title: HTTPS fundamentals - Beginner's guide for app developers displayTitle: Intro to HTTPS sidebarTitle: Intro to HTTPS description: Let’s break down what HTTPS is, why it matters, and how to use it in your apps. @@ -25,7 +25,7 @@ HTTPS stands for **HyperText Transfer Protocol Secure**. It’s the secure versi --- -### Why Use HTTPS? +### Why use HTTPS? 1. **Protects Data**: HTTPS encrypts data like passwords, credit card numbers, and messages. HTTPS is crucial on insecure networks (like public Wi-Fi) to prevent data tampering or theft. I 2. **Builds Trust**: Users see a padlock icon in their browser when your app uses HTTPS. This tells them your app is safe. @@ -34,7 +34,7 @@ HTTPS stands for **HyperText Transfer Protocol Secure**. It’s the secure versi --- -### How HTTPS Works +### How HTTPS works HTTPS uses two main tools to secure data: @@ -49,7 +49,7 @@ To enhance security, developers should use HTTP Strict Transport Security (HSTS) --- -### How to Add HTTPS to Your App +### How to add HTTPS to your app 1. **Get an SSL/TLS Certificate**: - You can buy one from a Certificate Authority (CA) or get a free one from services like Let’s Encrypt. @@ -64,7 +64,7 @@ To enhance security, developers should use HTTP Strict Transport Security (HSTS) --- -### Common Mistakes to Avoid +### Common mistakes to avoid - **Mixed Content**: Don’t mix HTTP and HTTPS. For example, if your app uses HTTPS but loads images over HTTP, it can break the security. - **Expired Certificates**: Always renew your certificates on time. diff --git a/learn/monitoring/intro-to-sdlc.mdx b/learn/monitoring/intro-to-sdlc.mdx index 085506fff..0c2d5559a 100644 --- a/learn/monitoring/intro-to-sdlc.mdx +++ b/learn/monitoring/intro-to-sdlc.mdx @@ -1,5 +1,5 @@ --- -title: Understanding the Software Development Life Cycle (SDLC) for Engineers +title: Understanding the software development life cycle (SDLC) for engineers displayTitle: Understanding the Software Development Life Cycle (SDLC) sidebarTitle: Understanding the SDLC description: With fast-paced standards for development and operations; where Agile, DevOps, and continuous delivery dominate—understanding SDLC remains crucial. @@ -46,7 +46,7 @@ The SDLC typically consists of several key phases: *The traditional testing pyramid, inspired by Martin Fowler’s version* -## **The Changing Landscape of Testing in the SDLC** +## **The changing landscape of testing in the SDLC** The traditional **Testing Pyramid** (favoring many unit tests over fewer UI tests) as a support of the SDLC is being questioned. Challenges include: diff --git a/learn/monitoring/metrics-every-team-needs.mdx b/learn/monitoring/metrics-every-team-needs.mdx index 9720ba794..472808e25 100644 --- a/learn/monitoring/metrics-every-team-needs.mdx +++ b/learn/monitoring/metrics-every-team-needs.mdx @@ -1,7 +1,7 @@ --- -title: Observability Basics - Metrics that every team needs +title: Observability basics - Metrics that every team needs displayTitle: Metrics Every Team Needs -sidebarTitle: Metrics Every Team Needs +sidebarTitle: Metrics every team needs description: This article will help define the metrics that every team needs to get tracking of their system’s performance date: 2025-04-15 author: Nocnica Mellifera @@ -57,7 +57,7 @@ Of the metrics in this article, response time can be the most difficult to measu Finally, when viewing response times **it’s critical not to just use simple averages to capture performance**. Special statistical slices like ‘percent of responses over threshold’ (how often did a user get an unacceptably slow response) and ‘95th percentile response times’ (including all but the very slowest responses, which are often outliers caused by special requests that are predictably quite slow) is critical to get an accurate picture of performance over time. -## Infrastructure Metrics +## Infrastructure metrics You should always be able to see a small group of metrics that shows the health of your infrastructure. This article doesn’t give a single answer for these infrastructure metrics due to evolution of how we host applications, and what things stress us out now. In the old days of bare metal servers, infrastructure health was usually covered by looking at available memory and CPU usage. But if a team using mainly serverless computation on a public cloud, those numbers would be both meaningless and ephemeral, and of bigger concern is a metric showing how much is being spent to handle all customer requests. Some possible examples of key infrastructure metrics: @@ -71,7 +71,7 @@ These metrics are still critical for any operations or on-call team, and are esp The best practices for infrastructure management could fill a whole book, but at the very highest level the most critical skill for monitoring infrastructure is to **perform deep, blameless postmortems any time you have an outage that was user-reported**. Outages reported by users are failures that your current observability tools can’t detect. By asking ‘what did we miss’ you’ll begin to identify what needs to be measured better, and surfaced better for your engineers, from your infrastructure. -## Error Rate +## Error rate Error rate is a critical APM metric that quantifies the frequency of failed requests or transactions within an application, expressed as a percentage of total requests. It captures HTTP errors (e.g., 4xx client errors, 5xx server errors), timeouts, exceptions, and can cover business logic failures (e.g., payment declines, API call failures). This metric is often segmented by endpoint, service, or dependency to pinpoint failure hotspots. A high or rising error rate may indicate code defects, infrastructure instability (e.g., database overload), or third-party service degradation. Engineering teams use error rate alongside logs and distributed tracing to diagnose root causes. In SLOs (Service Level Objectives), error rate thresholds (e.g., <0.1%) help enforce reliability targets. Proactive monitoring and alerting on error rate spikes enable faster [incident response](https://www.checklyhq.com/learn/incidents/what-is-incident-response/), reducing MTTR (Mean Time to Repair) and minimizing user impact. @@ -107,7 +107,7 @@ This kind of response, with a `200 OK` status and an error in the body, may not For all of these four key metrics, I can think of examples where only one of them will be ‘off’ during a certain type of failure. Therefore all four are the table stakes to monitoring a production application. -## **Conclusions: The Sturdy Table of Your Application** +## **Conclusions: The sturdy table of your application** Effective observability begins with tracking **four foundational metrics**: **Throughput**, **Response Time**, **Infrastructure Health**, and **Error Rate**. Each of these metrics provides a unique lens into system performance, and missing any one of them can leave critical blind spots in your monitoring strategy. @@ -116,7 +116,7 @@ Effective observability begins with tracking **four foundational metrics**: **Th - **Infrastructure Metrics** ensure the underlying systems are healthy and cost-efficient. - **Error Rate** exposes *how often* things are failing—even when failures are silent. -### **Key Takeaways** +### **Key takeaways** 1. **No Single Metric Tells the Whole Story** 2. **Define Metrics Clearly and Consistently** @@ -133,7 +133,7 @@ Effective observability begins with tracking **four foundational metrics**: **Th - Even "soft" errors (like payment declines) should be tracked if they impact UX. - Beware of **false-success responses** (HTTP 200s with error messages). -### **Final Thought: Start Small, Then Expand** +### **Final thought: Start small, then expand** While advanced observability (heatmaps, business intelligence, etc.) is valuable, these four metrics form the minimum viable dashboard every team should monitor. Once they’re stable, you can layer on deeper insights—but without them, you’re flying blind. diff --git a/learn/monitoring/monitoring-as-code.mdx b/learn/monitoring/monitoring-as-code.mdx index ffa414854..fe3205866 100644 --- a/learn/monitoring/monitoring-as-code.mdx +++ b/learn/monitoring/monitoring-as-code.mdx @@ -1,5 +1,5 @@ --- -title: Monitoring as Code - A Practical Guide from Checkly +title: Monitoring as Code - A practical guide from Checkly displayTitle: What is monitoring as code? description: >- Learn how to implement monitoring as code with Checkly's guide. Bring transparency, scalability, and efficiency to your cloud infrastructure management. @@ -23,7 +23,7 @@ Monitoring as Code (MaC) addresses these pain points by automating and integrati Let’s explore MaC, its benefits, and how you can use it to level up your monitoring. -## What Is Monitoring as Code? +## What is Monitoring as Code? Monitoring as Code involves defining monitoring configurations and operations as code, enabling automated setups, real-time observability across DevOps lifecycles, and seamless integration with development workflows. @@ -49,7 +49,7 @@ Operations teams have traditionally owned monitoring tools within organizations Traditional synthetic monitoring tools work at the surface level of an application, unable to give detailed explanations of the root cause of the alert. -### Growing Costs +### Growing costs Whenever we discuss the ideal setup for synthetic monitoring, experienced DevOps and SRE engineers will respond: "Sure, that would be great, if we had the budget for it." While it would be nice to simulate a complex user behavior every 30 seconds from 5 different geographic regions, the cost of most synthetic tools makes that cost-prohibitive. @@ -57,7 +57,7 @@ Whenever we discuss the ideal setup for synthetic monitoring, experienced DevOps Here are the most important benefits of adopting Monitoring as Code: -### **Codified & Programmable** +### **Codified & programmable** Monitoring as Code transforms your monitoring setup into code that is stored, managed, and versioned alongside your application code. This approach brings significant advantages over traditional monitoring tools: @@ -69,7 +69,7 @@ With MaC, your monitoring evolves alongside your codebase, enabling precision, f ![VS Code showing the checkly.config and a define API monitor.](/images/guides/images/guides-mac-teaser.jpg "VS Code showing the checkly.config and a define API monitor.") -### **Reusability Enforces Consistency** +### **Reusability enforces consistency** Reusability in Monitoring as Code (MaC) goes beyond efficiency—it ensures consistent, reliable, and scalable monitoring across environments and teams. By reusing existing assets like Playwright tests and API definitions, MaC streamlines setup and eliminates redundancy. @@ -80,7 +80,7 @@ Reusability in Monitoring as Code (MaC) goes beyond efficiency—it ensures cons By reusing existing assets and creating modular configurations, MaC ensures monitoring is efficient, consistent, and adaptable to changing needs. -### **Increased Collaboration** +### **Increased collaboration** MaC breaks down silos by embedding monitoring into the development lifecycle, fostering collaboration across teams: @@ -90,31 +90,31 @@ MaC breaks down silos by embedding monitoring into the development lifecycle, fo By embedding collaboration into the monitoring process, MaC drives alignment, reduces friction, and creates a culture of shared accountability. -## Monitoring as Code Use Cases +## Monitoring as Code use cases -### **Continuous Monitoring Throughout the SDLC** +### **Continuous monitoring throughout the SDLC** To maintain high-quality deployments, monitoring should span every stage of the Software Development Life Cycle (SDLC)—from local development to staging and production. Monitoring as Code (MaC) integrates directly into CI/CD pipelines, enabling automatic and consistent observability across environments. This ensures that issues are detected and addressed before they reach production, significantly reducing downtime and errors. For instance, commercetools, a leader in headless commerce, [adopted MaC](https://www.checklyhq.com/case-study/commercetools/) to implement continuous monitoring throughout their SDLC. By codifying their monitoring setup, they ensured every stage of their pipeline was equipped with accurate, automated checks. This approach caught issues early in development, reduced production incidents, and provided end-to-end visibility into their systems without adding extra operational overhead. -### **Automating Monitoring for Rapidly Changing Systems** +### **Automating monitoring for rapidly changing systems** Monitoring APIs and UIs in fast-paced environments is a complex challenge, especially when new endpoints are constantly being added or updated. Traditional approaches often involve manually setting up and maintaining checks, which is time-consuming and prone to errors. As systems scale, gaps in monitoring coverage or misconfigured alerts can lead to missed issues and delayed responses, impacting the reliability of your services. Monitoring as Code solves this by automating the creation and deployment of monitoring configurations, ensuring every API is consistently and comprehensively monitored from staging to production. By integrating monitoring into your development pipelines, you can keep up with rapid changes without sacrificing reliability. For example, TrueLayer, a leading open banking platform, [adopted Monitoring as Code to address these challenges](https://www.checklyhq.com/case-study/truelayer/). By codifying their API monitoring configurations and automating their setup with Checkly, they reduced manual effort by 60%. This allowed their team to scale monitoring as they introduced new endpoints, ensuring complete coverage and faster issue detection, all while focusing more on innovation rather than operational tasks. -### **Enhancing Monitoring Ownership Across Teams** +### **Enhancing monitoring ownership across teams** In large organizations, monitoring is often centralized under SRE teams, creating bottlenecks and slowing down response times. This approach limits the ability of engineering teams to adapt and manage monitoring for their own services. Monitoring as Code (MaC) decentralizes this process, empowering teams to define and control their monitoring setups directly within their workflows. This fosters greater accountability and enables faster detection and resolution of issues. [LinkedIn leveraged MaC](https://www.checklyhq.com/case-study/modernizing-linkedins-monitoring-infrastructure/) to transition from an SRE-managed model to one where engineering teams took full ownership of their monitoring. Using Checkly, they streamlined the process, allowing teams to tailor monitoring configurations to their specific needs. This shift reduced time to detection, improved system reliability, and gave teams the autonomy to innovate without relying on a central authority. -## What Can You Monitor Using Monitoring as Code? +## What can you monitor using Monitoring as Code? Monitoring as Code (MaC) enables you to test key aspects of your application and infrastructure with precision and automation. Here are some of the areas where it excels: -### Application Uptime +### Application uptime Application uptime reflects how reliably your application is available to users, and even a few minutes of downtime can lead to user frustration, loss of revenue, and damage to your reputation. @@ -122,7 +122,7 @@ MaC allows you to define uptime checks programmatically, ensuring these checks a MaC also simplifies scaling uptime monitoring across multiple regions. By deploying checks from different geographic locations, you can ensure your application is accessible worldwide and identify regional connectivity issues. Additionally, codified monitoring enables you to keep pace with application changes—new services and endpoints are automatically incorporated into your monitoring setup, reducing the risk of missed coverage. -### **UI Functionality** +### **UI functionality** MaC allows you to simulate and test user interactions with your web application. For example, you can create Browser checks to validate critical workflows like logging in, completing a checkout, or performing a search. @@ -148,7 +148,7 @@ test('Login to Checkly', async ({ page }) => { // 2 ``` -### **API Health** +### **API health** APIs power modern applications, and MaC ensures their availability, performance, and correctness. You can automate checks to validate response status codes, measure latency, and verify payloads. @@ -199,7 +199,7 @@ new ApiCheck('update-inventory-item', { ``` -### Application Performance +### Application performance Slow app load times or high latency can drive users away and impact revenue. Monitoring as Code provides a streamlined way to track performance metrics like page load times, API response times, and latency, ensuring your application consistently meets expectations. @@ -209,7 +209,7 @@ MaC also excels at monitoring deployments by running performance checks automati MaC makes it easy to monitor performance across regions, simulating user experiences in different locations. This helps identify latency caused by network issues, server configurations, or CDNs, ensuring fast, consistent performance worldwide. By codifying performance monitoring, MaC standardizes and automates the process, allowing your team to maintain a responsive, reliable web app at scale. -### **Scheduled Jobs or Cron Jobs** +### **Scheduled jobs or cron jobs** 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. @@ -217,7 +217,7 @@ A Heartbeat monitor verifies that a job reports back within the expected timefra This proactive approach ensures your critical automation workflows are reliable and resilient. -### **Infrastructure Reliability** +### **Infrastructure reliability** MaC also tests the health and reliability of your infrastructure. This includes uptime monitoring for servers, latency checks for databases, and validating metrics like CPU or memory usage. @@ -227,7 +227,7 @@ By codifying these checks, you create an automated system that detects potential Monitoring as Code (MaC) with Checkly empowers you to streamline, automate, and scale your monitoring strategy by leveraging advanced tools and integrations. With native Playwright support, Terraform and Pulumi integrations, and seamless CI/CD pipeline compatibility, Checkly simplifies complex monitoring setups and enables dynamic, code-driven observability. -### **CI/CD Pipeline Integration** +### **CI/CD pipeline integration** Checkly’s compatibility with CI/CD pipelines ensures monitoring is embedded into your development workflow. You can configure performance, uptime, and functional checks to run automatically during deployments, catching issues early and maintaining system reliability. This tight integration helps teams: @@ -235,13 +235,13 @@ Checkly’s compatibility with CI/CD pipelines ensures monitoring is embedded in - Monitor deployments in real-time to detect regressions or failures. - Streamline troubleshooting by aligning monitoring data with code changes. -### Native Playwright Support +### Native Playwright support With native Playwright support, Checkly enables you to directly use existing Playwright scripts as Browser checks. This integration allows you to monitor complex user workflows—such as logins, form submissions, or multi-step transactions—without needing to rewrite tests. Your monitoring aligns with your application logic, offering precise, actionable insights into the user experience. -### **Alert Management via Code** +### **Alert management via code** A strong alerting strategy ensures critical issues are addressed promptly while minimizing noise for your team. With Checkly, you can configure alerting integrations like [PagerDuty](/integrations/incident-management/pagerduty) or [Opsgenie](/integrations/incident-management/opsgenie) directly in your codebase. This approach allows you to: @@ -258,7 +258,7 @@ A strong alerting strategy ensures critical issues are addressed promptly while - Share consistent, reliable dashboards across teams or environments. - Communicate app and API availability to your customers. -### **Performance Benchmarking** +### **Performance benchmarking** Performance benchmarking helps you understand your application’s limits and track improvements over time. MaC allows you to automate performance tests and benchmark configurations, ensuring consistent measurement across deployments. You can: @@ -268,7 +268,7 @@ Performance benchmarking helps you understand your application’s limits and tr Codified benchmarks keep your team aligned and make it easier to identify potential bottlenecks before they impact users. -### **Incident Postmortems and Continuous Improvement** +### **Incident postmortems and continuous improvement** Postmortems are crucial for learning from incidents, and MaC ensures these lessons are integrated directly into your monitoring setup. After identifying root causes, you can: @@ -278,7 +278,7 @@ Postmortems are crucial for learning from incidents, and MaC ensures these lesso This approach turns every incident into an opportunity for growth, building resilience into your application with each iteration. -### **Regional or Multi-Environment Testing** +### **Regional or multi-environment testing** Modern applications often run across multiple regions or environments, and ensuring consistent performance everywhere is a major challenge. MaC allows you to: @@ -288,7 +288,7 @@ Modern applications often run across multiple regions or environments, and ensur This granular, automated approach ensures your application delivers a seamless experience to users regardless of their location or environment. -### **Infrastructure as Code (IaC) Support** +### **Infrastructure as Code (IaC) support** Checkly integrates seamlessly with popular IaC tools like Terraform and Pulumi. This means you can define monitoring configurations alongside your infrastructure code, ensuring monitoring setups are automatically deployed with your infrastructure updates. These integrations enable: @@ -296,7 +296,7 @@ Checkly integrates seamlessly with popular IaC tools like Terraform and Pulumi. - Simplified updates to monitors as your infrastructure evolves. - Centralized version control, ensuring your monitoring is always aligned with your application and infrastructure. -## Best Practices for Monitoring as Code +## Best practices for Monitoring as Code Implementing monitoring as code effectively requires following best practices to ensure reliability, scalability, and maintainability. diff --git a/learn/monitoring/overview.mdx b/learn/monitoring/overview.mdx index ca1489215..8bdf66fd1 100644 --- a/learn/monitoring/overview.mdx +++ b/learn/monitoring/overview.mdx @@ -1,5 +1,5 @@ --- -title: Monitoring Resources - Tools, Metrics & Best Practices +title: Monitoring resources - Tools, metrics & best practices sidebarTitle: Monitoring description: Browse essential monitoring resources from Checkly. Learn key metrics, performance tools, and best practices to optimize your systems and user experience. date: 2024-10-17 @@ -10,7 +10,7 @@ canonical: 'https://www.checklyhq.com/docs/learn/monitoring/overview/' --- Monitoring your production services is a key part of a good user experience. Traditional stopgaps like 'pingers' or simply waiting for user reported issues are insufficient. These guides are an introduction to the basic concepts of monitoring. -## Getting Started +## Getting started How does software get made? Breaking down the basic phases of software development. @@ -32,36 +32,36 @@ Monitoring your production services is a key part of a good user experience. Tra Learn all about web application monitoring, performance and reliability and discover top tools. Discover the benefits and top tools for frontend monitoring. Track performance and optimize user experience. -## On the Checkly Blog +## On the Checkly blog Learn seven best practices to fight alert fatigue. Traditional monitoring has become insufficient for managing complex systems. Five best practices to help you deploy your software more securely and reliably. diff --git a/learn/monitoring/real-user-monitoring.mdx b/learn/monitoring/real-user-monitoring.mdx index 577ce0a04..f51e3ece4 100644 --- a/learn/monitoring/real-user-monitoring.mdx +++ b/learn/monitoring/real-user-monitoring.mdx @@ -1,7 +1,7 @@ --- -title: Real User Monitoring (RUM) - Benefits, Challenges, and Alternatives +title: Real user monitoring (RUM) - Benefits, challenges, and alternatives displayTitle: Real User Monitoring (RUM) - A Practical Guide -sidebarTitle: Real User Monitoring +sidebarTitle: Real user monitoring description: Discover the benefits, challenges, and top tools for frontend monitoring. Learn how to track performance, detect issues, and optimize user experience. date: 2024-12-15 author: Nocnica Mellifera @@ -14,11 +14,11 @@ weight: 50 canonical: 'https://www.checklyhq.com/docs/learn/monitoring/real-user-monitoring/' --- -## **Why Real User Monitoring Matters** +## **Why real user monitoring matters** Real User Monitoring (RUM) gives you actual performance data from real people using your website or app. Unlike synthetic tests (which simulate users), RUM shows you exactly what your customers experience—the promise is that if even one of your users encounters an error, you’ll know about it. -### **Key Benefits:** +### **Key benefits:** - **Pinpoint Performance Issues** – Discover which pages load slowly or behave poorly on specific devices (e.g., mobile vs. desktop). - **Reduce User Frustration** – Catch errors before they drive users away. @@ -30,9 +30,9 @@ Real User Monitoring (RUM) gives you actual performance data from real people us If checkout pages take 8 seconds to load on mobile, but only 2 seconds on desktop, RUM helps you find and fix the bottleneck. RUM monitoring shows exactly which users are encountering slow load times, and you can look at historical trends to see if a recent change may have been the cause. -## **How RUM Works: From Data to Insights** +## **How RUM works: From data to insights** -### **1. Data Collection (The "What")** +### **1. Data collection (the "What")** A lightweight JavaScript snippet (or mobile SDK) tracks: @@ -43,12 +43,12 @@ A lightweight JavaScript snippet (or mobile SDK) tracks: All of this data is collected, generally as a trace with annotations for events and errors, for tramsission by the lightweight RUM code. -### **2. Data Transmission (The "How")** +### **2. Data transmission (the "How")** - Data is sent to a monitoring backend - **Sampling** (optional) reduces cost by sending only a % of sessions. -### **3. Analysis & Action (The "Why")** +### **3. Analysis & action (the "Why")** - **Dashboards** show performance trends (e.g., "Mobile users in Europe are 40% slower"). - **Alerts** notify you when error rates spike. @@ -60,13 +60,13 @@ Start with core metrics (load time, error rate), then expand to track business g --- -## **Sampling & Storage: Balancing Cost and Detail** +## **Sampling & storage: Balancing cost and detail** -### **The Data Fire Hose Problem** +### **The data fire hose problem** RUM generates **massive** amounts of data. If you track every click, scroll, and page load for millions of users, costs can spiral. Storing RUM data isn’t just expensive for your storage solutions, it also means incredibly slow queries for trying to see historical performance. -### **Solution: Tiered Storage (Like a "Data Lake")** +### **Solution: Tiered storage (like a "Data Lake")** 1. **Raw Bucket** – Store *everything* (for rare deep dives). - Example: Keep 100% of data for 7 days, then archive. diff --git a/learn/monitoring/synthetic-monitoring.mdx b/learn/monitoring/synthetic-monitoring.mdx index fbd227b25..a46c7e95f 100644 --- a/learn/monitoring/synthetic-monitoring.mdx +++ b/learn/monitoring/synthetic-monitoring.mdx @@ -1,7 +1,7 @@ --- -title: Synthetic Monitoring - Concepts, Benefits & Challenges +title: Synthetic monitoring - Concepts, benefits & challenges displayTitle: What is Synthetic Monitoring? -sidebarTitle: Synthetic Monitoring +sidebarTitle: Synthetic monitoring description: Explore the what and why of synthetic monitoring. date: 2025-04-15 author: Nocnica Mellifera @@ -18,7 +18,7 @@ Synthetic monitoring enables software teams to better understand the performance Just as automated testing is essential for high-velocity development teams, enabling them to catch bugs and defects by simulating real user flows in testing and preview environments, synthetic monitoring enables teams to continuously monitor for optimal user experiences. Some synthetic monitoring tools, like Checkly, allow engineers to reuse entire end-to-end tests as production monitors. This enables true continuous quality to be practiced by organizations. -## How does Synthetic Monitoring work? +## How does synthetic monitoring work? At its core, synthetic monitoring is about simulating user interactions with an application to preemptively identify issues before they impact real users. Synthetic monitoring gives developers and operations engineers the confidence that they are one step ahead, ensuring that potential problems are identified and resolved swiftly. In practice, synthetic monitoring works a lot like automated testing in production. Teams constantly run “tests” against a production environment from global locations. Using a Monitoring as Code workflow, its easy to even reuse real end-to-end tests as monitors, simply by deploying them to infrastructure such as Checkly. @@ -27,7 +27,7 @@ Synthetic monitors can measure uptime, transactions, status response performance This enables continuous confidence when making rapid changes to mission-critical services and applications by allowing you to notice issues before your customers do. -## Benefits of Synthetic Monitoring +## Benefits of synthetic monitoring Synthetic monitoring plays a pivotal role in understanding an application's behavior under various scenarios. It allows teams to test how their application performs in different geographical locations, under various network conditions, and during peak load times. This insight is critical for applications that cater to a global audience, where performance can vary significantly based on a user's location and the time of day. Here are some other benefits of synthetic monitoring: ### Proactive error detection @@ -49,7 +49,7 @@ Many things can cause performance degradation, but synthetic monitoring will unv ### Controlled environments Monitors are run from controlled environments with consistent browser properties and network connections to make root-cause analysis efficient and accurate. -## Synthetic monitoring vs Real User Monitoring (RUM) +## Synthetic monitoring vs real user monitoring (RUM) Real user monitoring, also called RUM or passive monitoring, is another way to analyze and monitor your application. RUM monitoring offers insights into user interactions, performance statistics, and your users' devices and locations in a way that differs greatly from synthetic monitoring. Unlike synthetic monitoring tools, RUM monitoring tools don't simulate user interactions, but rather record real user interactions. There's nothing for you to script or define. With RUM, an embedded JavaScript snippet records and reports the behavior of actual users back to you so that you can monitor and analyze your applications' performance and health. Your users are the data source! This sounds great, but there are a few challenges with RUM. @@ -66,50 +66,50 @@ Unlike synthetic monitoring tools, RUM monitoring tools don't simulate user inte A comparison of RUM vs. Synthetics -## Types of Synthetic Monitoring +## Types of synthetic monitoring 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: -### Uptime or Availability Monitoring +### Uptime or availability monitoring 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. -### Transaction Monitoring +### Transaction monitoring Transaction Monitoring takes a step further. To know that every part is really working as expected, Transaction Monitoring means simulating complex user transactions or workflows to verify that critical processes, like checkout or login, are working as intended. Scripts are designed to mimic the path a user would take through the application. This can be as simple as logging in or as complex as completing a multi-step transaction. The goal is to identify performance issues or bugs that might not be evident in other forms of testing. For example, this will reveal whether third-party services have failed, resulting in degraded performance on our own site. -### Performance Monitoring +### Performance monitoring Web Performance Monitoring is all about speed and efficiency. It evaluates how quickly and smoothly your web application loads and operates from the user's perspective. This is a more analog measurement than the Availability or Transaction Monitoring, as exact loading times will vary and won't give simple "up or down" feedback. Web Performance Monitoring can identify technical debt, as small changes to your experience can add up to degraded (or improved!) performance for your end users. -### Keyword Monitoring +### Keyword monitoring Keyword monitoring entails monitoring for content that is expected to appear in an API response or within a UI. [Keyword monitoring](/guides/monitoring-ecommerce-apps-using-playwright) can be extremely helpful for commerce sites or other content-driven websites like news publishers and blogs. -## Synthetic Monitoring Best Practices +## Synthetic monitoring best practices Implementing synthetic monitoring effectively ensures you maximize its value in identifying and resolving performance issues. Here are key best practices to follow: -### 1. Define Key User Journeys +### 1. Define key user journeys Before you implement synthetic monitoring, identify the most critical user interactions, such as login flows, checkout processes, or API endpoints that drive your business. These are the flows you want to be setting synthetic monitors for. Simulating these core pathways ensures that issues affecting customer satisfaction are detected early. -### 2. Test From Multiple Locations +### 2. Test from multiple locations Set up monitors across geographically distributed data centers to simulate user access from various regions. This practice helps uncover location-specific latency or connectivity issues and ensures a consistent experience for global users. -### 3. Use Realistic Scenarios +### 3. Use realistic scenarios Craft test scripts that mimic real user behaviors, including complex interactions like multi-step forms or dynamic content loading. Ensure these scripts reflect typical device types, browsers, and network conditions to emulate authentic experiences. -### 4. Monitor Continuously and Strategically +### 4. Monitor continuously and strategically Schedule monitoring at frequent intervals to capture real-time performance data. Combine this with strategic off-peak monitoring to identify time-sensitive bottlenecks, such as overnight updates or backups affecting availability. -### 5. Set Up Meaningful Alerts +### 5. Set up meaningful alerts Configure alerts to balance urgency and relevance. Alerts should only trigger for significant issues, avoiding noise from false positives or minor deviations, to ensure your team focuses on critical problems. -### 6. Regularly Update Scripts +### 6. Regularly update scripts Keep monitoring scripts updated to align with application changes. Regular maintenance prevents outdated tests from providing inaccurate results or missing new vulnerabilities. -### 7. Integrate Synthetic Monitoring with Your CI/CD Pipeline +### 7. Integrate synthetic monitoring with your CI/CD pipeline Incorporate synthetic monitoring checks into your deployment workflows to catch issues before they reach production. Automated tests can act as gatekeepers for performance and functionality. By following these best practices, you can leverage synthetic monitoring to proactively enhance performance and deliver seamless user experiences. -## Synthetic Monitoring Use Cases +## Synthetic monitoring use cases Here are key use cases where synthetic monitoring shines: * Website Performance Monitoring: Simulate user interactions to measure load times, responsiveness, and overall performance of web pages. @@ -128,13 +128,13 @@ Here are key use cases where synthetic monitoring shines: These use cases make synthetic monitoring essential for delivering reliable and high-performing applications. -## Common Synthetic Monitoring tools +## Common synthetic monitoring tools To do synthetic monitoring right, you'll either need to run a service totally independently of your existing tech stack or use a SaaS tool. A system to monitor your production services shouldn't go down when your own system does! You'll also need a tool to store past performance data and present it within a dashboard. ### Playwright - The leader in browser automation Backed by Microsoft, Playwright quickly became one of the leaders in synthetic and [end-to-end testing](/learn/monitoring/end-to-end-monitoring). Its ability to control headless browsers while providing a stellar developer experience convinced the developers, quality assurance, and DevOps communities. And we at Checkly believe it's the best tool for synthetic monitoring. -### Checkly - The best platform for running Synthetic Tests +### Checkly - The best platform for running synthetic tests While multiple Observability vendors offer limited site pings as part of a larger toolset, Checkly offers the best experience for users focused on synthetics testing. While other teams use Playwright only for the occasional end-to-end checks, Checkly lets you run these detailed checks with complex scripted behavior at any cadence you need to maintain your SLA. And Checkly can cost less than [half of what our competitors charge](https://www.checklyhq.com/blog/how-to-spend-ten-grand-12-bucks-at-a-time/). Checkly offers rich options for scheduling tests on a cadence, including [scheduling checks from multiple regions](https://www.checklyhq.com/blog/parallel-scheduling/), and offers the most complete answer to ‘how is our service performing for all our users? @@ -148,7 +148,7 @@ Synthetic monitoring and Monitoring as Code anticipate and resolve issues before Because you have to remember you can only fix issues you know about. -## Frequently Asked questions about Synthetic Monitoring +## Frequently asked questions about synthetic monitoring ### What is the difference between observability and synthetic monitoring? diff --git a/learn/monitoring/tcp-and-ssl.mdx b/learn/monitoring/tcp-and-ssl.mdx index fe3a8b51d..c868991fc 100644 --- a/learn/monitoring/tcp-and-ssl.mdx +++ b/learn/monitoring/tcp-and-ssl.mdx @@ -36,7 +36,7 @@ One senior developer shared a story of why it's important to understand the netw As an application developer, you need to know how TCP and SSL/TLS work together to establish secure connections, authenticate parties, and ensure data integrity. This article will explain the relationship between TCP and SSL/TLS, focusing on authentication and how it impacts your application. -## How TCP and SSL/TLS Work Together +## How TCP and SSL/TLS work together TCP provides the underlying communication channel for SSL/TLS. Here’s how they work together: @@ -47,11 +47,11 @@ TCP provides the underlying communication channel for SSL/TLS. Here’s how they The SSL/TLS handshake is critical for authentication, ensuring that the client is communicating with the intended server and not an imposter. -## SSL/TLS Authentication +## SSL/TLS authentication Authentication in SSL/TLS ensures that the parties involved in the communication are who they claim to be. This is typically done using digital certificates and public-key cryptography. -### Server Authentication +### Server authentication In most cases, SSL/TLS is used to authenticate the server to the client. Here’s how it works: @@ -64,7 +64,7 @@ In most cases, SSL/TLS is used to authenticate the server to the client. Here’ This process ensures that the client is communicating with the legitimate server and not a man-in-the-middle attacker. -### Client Authentication (Optional) +### Client authentication (optional) In some cases, the server may also require the client to authenticate itself. This is less common but is used in scenarios where mutual trust is required (e.g., enterprise applications, APIs). Here’s how it works: @@ -76,7 +76,7 @@ Client authentication adds an extra layer of security but requires managing clie --- -## SSL/TLS Handshake in Detail +## SSL/TLS handshake in detail The SSL/TLS handshake is a multi-step process that establishes a secure connection. Here’s a simplified overview: @@ -96,7 +96,7 @@ Once the handshake is complete, the secure connection is established, and encryp --- -## What Application Developers Need to Know +## What application developers need to know Certificate Management - Server Certificates: Ensure your server has a valid certificate signed by a trusted CA. Self-signed certificates are not trusted by default and may cause errors in clients. @@ -118,7 +118,7 @@ Once the handshake is complete, the secure connection is established, and encryp --- -## Common Issues and Troubleshooting +## Common issues and troubleshooting Certificate Expiry - Certificates have a limited validity period. If a certificate expires, the SSL/TLS handshake will fail. Monitor certificate expiration dates and renew them before they expire. @@ -137,7 +137,7 @@ Once the handshake is complete, the secure connection is established, and encryp --- -## Best Practices for SSL/TLS Authentication +## Best practices for SSL/TLS authentication * Use Strong Certificates: - Use certificates with a key length of at least 2048 bits (RSA) or 256 bits (ECDSA). diff --git a/learn/monitoring/transaction-monitoring.mdx b/learn/monitoring/transaction-monitoring.mdx index 61d87202a..f9971c53a 100644 --- a/learn/monitoring/transaction-monitoring.mdx +++ b/learn/monitoring/transaction-monitoring.mdx @@ -1,7 +1,7 @@ --- -title: Transaction Monitoring - Components, Benefits & Challenges +title: Transaction monitoring - Components, benefits & challenges displayTitle: What is Transaction Monitoring? -sidebarTitle: Transaction Monitoring +sidebarTitle: Transaction monitoring description: Explore transaction monitoring for application developers and SREs. date: 2024-12-15 author: Nocnica Mellifera @@ -22,11 +22,11 @@ Unlike traditional monitoring of a site or service, which relies on observing re --- -## Synthetic Monitoring vs. Synthetic Transaction Monitoring +## Synthetic monitoring vs. Synthetic transaction monitoring First some language confusion: ‘Synthetic Monitoring’ isn’t a particularly widely used term, what’s with the addition of ‘transaction?’ [Synthetic monitoring](https://www.checklyhq.com/blog/what-is-synthetic-monitoring/) broadly refers to any monitoring that uses automated tests to emulate users, sometimes a simple as a page load. Synthetic transaction monitoring is a subset focused on multi-step workflows or transactions, such as filling out forms, completing e-commerce purchases, or using APIs. While synthetic monitoring may involve simple checks like testing website uptime, synthetic transaction monitoring goes deeper into the user experience by validating the performance and functionality of complex processes. -## How Does Synthetic Transaction Monitoring Work? +## How does synthetic transaction monitoring work? Synthetic transaction monitoring involves several key steps: @@ -37,7 +37,7 @@ Synthetic transaction monitoring involves several key steps: 5. **Analysis and Reporting**: Results are analyzed to identify anomalies, trends, or potential bottlenecks. 6. **Alerting**: If thresholds are breached, alerts notify relevant teams for investigation and resolution. For almost all monitoring, alerts should wait on at least one retry, so as not to cause alert fatigue. -## Why Synthetic Transaction Monitoring Matters +## Why synthetic transaction monitoring matters Synthetic transaction monitoring offers several advantages, especially over real user monitoring. @@ -48,7 +48,7 @@ Synthetic transaction monitoring offers several advantages, especially over real However, challenges include maintaining up-to-date scripts as applications evolve and ensuring synthetic tests accurately reflect real-world usage. -## Components of Synthetic Transaction Monitoring +## Components of synthetic transaction monitoring Effective synthetic transaction monitoring relies on several core components: @@ -76,7 +76,7 @@ An alerting system notifies teams when performance thresholds are breached. Aler Synthetic transaction monitoring tools often integrate with observability platforms, incident management systems, and CI/CD pipelines, enabling streamlined workflows and comprehensive insights. At Checkly, the results of synthetics checks can integrate with your OpenTelemetry data via [Checkly Traces](/resolve/traces/how-it-works). -## Synthetic Transaction Monitoring Use Cases with Examples +## Synthetic transaction monitoring use cases with examples 1. **E-Commerce Checkout Process** A retailer uses synthetic transaction monitoring to simulate a user adding items to a cart, entering payment details, and completing a purchase. This ensures the checkout process remains functional, even as the underlying datastores and visual polish on the e-commrce experience change. @@ -93,7 +93,7 @@ A video streaming service tests its platform from multiple regions to ensure vid Synthetic transaction monitoring is an essential tool for organizations aiming to ensure optimal performance and reliability of their digital services. By proactively addressing issues and gaining insights into user workflows, businesses can deliver superior experiences to their customers. -## Benefits of Synthetic Transaction Monitoring +## Benefits of synthetic transaction monitoring **Early Detection of Issues** @@ -121,7 +121,7 @@ While it’s nice to imagine our service or website as self-contained, albeit wi Synthetic transaction monitoring can aid in compliance with service-level agreements (SLAs) by consistently measuring uptime and performance against defined benchmarks. This ensures businesses meet contractual obligations and regulatory requirements. You can also use synthetic transaction monitoring to make sure you’re compliant with accessibility requirements, [in Playwright you can use the Axe testing engine to automatically check your pages for accessibility issues](https://www.checklyhq.com/blog/integrating-accessibility-checks-in-playwright-tes/). -## Challenges of Synthetic Transaction Monitoring +## Challenges of synthetic transaction monitoring **Need for Validation** @@ -142,7 +142,7 @@ Integrating synthetic monitoring tools with existing systems can pose challenges By understanding these benefits and challenges, organizations can better implement synthetic transaction monitoring as part of a balanced observability strategy. -## Best Practices for Synthetic Transaction Monitoring +## Best practices for synthetic transaction monitoring **Defining Clear Objectives** @@ -176,7 +176,7 @@ Integrate synthetic monitoring with broader observability platforms to enhance t Synthetic monitoring is a powerful tool for validating Service Level Agreements (SLAs). By continuously testing key metrics, you can provide objective evidence of SLA adherence to stakeholders. -## Synthetic Transaction Monitoring Tools +## Synthetic transaction monitoring tools Numerous tools are available to implement synthetic transaction monitoring effectively. Solutions like Catchpoint and Dynatrace offer advanced features such as global test locations, detailed reporting, and integration with other observability tools. Open-source options, such as those leveraging CNCF projects, can provide flexibility and customization for Kubernetes-based environments. @@ -184,7 +184,7 @@ Numerous tools are available to implement synthetic transaction monitoring effec [Checkly](https://www.checklyhq.com/product/synthetic-monitoring/) is a purpose-built platform for synthetic monitoring that simplifies the creation and management of test scripts. With features like a developer-friendly CLI, seamless integration with CI/CD pipelines, and out-of-the-box support for the multi-language Playwright automation framework. Checkly enables teams to monitor critical user journeys effectively. Its dashboards and alerting systems ensure you’re always aware of issues before they impact customers. -## How Checkly Can Help with Synthetic Transaction Monitoring +## How Checkly can help with synthetic transaction monitoring Checkly provides a robust set of tools to implement synthetic monitoring seamlessly. Its scripting capabilities allow you to craft realistic user scenarios while its cloud-based infrastructure ensures consistent monitoring from multiple geographies. Integration with observability platforms and APIs enables you to incorporate Checkly into your existing workflows, making it an efficient choice for synthetic monitoring needs. diff --git a/learn/monitoring/web-application-monitoring.mdx b/learn/monitoring/web-application-monitoring.mdx index 53948fe55..05c347cdc 100644 --- a/learn/monitoring/web-application-monitoring.mdx +++ b/learn/monitoring/web-application-monitoring.mdx @@ -1,7 +1,7 @@ --- -title: Web Application Monitoring - Types, Benefits & Top 10 Tools +title: Web application monitoring - Types, benefits & top 10 tools displayTitle: What is Web Application Monitoring? -sidebarTitle: Web Application Monitoring +sidebarTitle: Web application monitoring description: Explore web application monitoring to boost performance and reliability with real user insights, performance tracking, and top tools. date: 2024-12-15 author: Nocnica Mellifera @@ -22,11 +22,11 @@ Web application monitoring refers to the practice of observing, tracking, and ma Web application monitoring is a highly generalized term, and distinctions between, for example, ‘metrics’ and ‘monitoring;’ and ‘error tracking’ versus ‘performance monitoring’ are often distinctions without a difference. The question we’re trying to answer with Web Application Monitoring is: “how well is our application performing for users?” Observations that don’t relate to this question, for example the popularity of a single post on our social media site, or how well our live-generated site follows brand standards, are outside the scope of web application monitoring. -## How Web Application Monitoring Works +## How web application monitoring works Monitoring tools collect data from your web application, servers, and user interactions. They process this data to generate insights about application health, performance, and user behavior. Alerts, dashboards, and reports provide actionable insights for resolving issues and optimizing performance. -## Types of Web Application Monitoring +## Types of web application monitoring Monitoring a web application requires understanding various dimensions of performance, usability, and security. Each type of monitoring addresses specific aspects of the application to ensure seamless operation. Let’s explore these types in greater detail. @@ -89,14 +89,14 @@ Server and infrastructure monitoring tracks the health of the hardware, virtual --- -## Key Metrics to Monitor +## Key metrics to monitor - Response Time: Time taken by the application to respond to requests. - Error Rate: Frequency of errors in the application. - Throughput: Number of requests processed over a time frame. - Uptime and Availability: Percentage of time the application is operational. -## Benefits of Web Application Monitoring +## Benefits of web application monitoring * Instant Downtime Alerts @@ -106,7 +106,7 @@ By monitoring your web application directly, you have a better chance of knowing Often, poor performance doesn’t happen all at once. For every user who gets in touch complaining of slow response times, dozens or hundreds will have simply abandoned your service, and written off the quality of your site. Without web application monitoring, you’ll use users for some time before you’re even aware of a problem. -## Limitations of Web Application Monitoring +## Limitations of web application monitoring * Dynamic Content @@ -116,7 +116,7 @@ Monitoring tools may struggle with rapidly changing, personalized content. A rob As mentioned in the introduction, Web Application Monitoring has a specific use: finding how well a service performs for users. Once the use case expands into security monitoring or business analytics, mission creep can kill your efficiency. -## Best Practices for Monitoring Web Applications +## Best practices for monitoring web applications Effective monitoring is essential to maintaining the performance, availability, and security of web applications. However, monitoring is more than just collecting data; it’s a strategic process of learning and acting based on insights. By following these best practices, organizations can ensure their monitoring efforts are both meaningful and actionable. @@ -219,7 +219,7 @@ Periodic audits ensure that your monitoring strategy remains effective and that Effective monitoring isn’t just about data collection—it’s about using data to improve your application and achieve your organization’s goals. By integrating these best practices into your strategy, you ensure that monitoring becomes a driver of growth, user satisfaction, and operational excellence. -## Top 9 Web Application Monitoring Tools +## Top 9 web application monitoring tools * 1. Datadog @@ -291,7 +291,7 @@ Instana promises AI-driven insights and automatic monitoring for dynamic applica Personal Experience: During an initiative to modernize a legacy application, Instana was pitched to us as the “next-generation AI observability solution.” While it delivered on automated dependency mapping, the AI insights often felt like little more than a repackaging of existing metrics with an added buzzword. It was helpful for identifying sudden resource spikes, but I often found myself relying on other tools for detailed root-cause analysis. The promises of “AI-driven” observability didn’t live up to the hype. -## Open Source Monitoring: a key part of web application monitoring +## Open source monitoring: a key part of web application monitoring Open source monitoring plays a pivotal role in modern cloud-native web application monitoring by leveraging community-driven tools to provide robust, scalable, and accessible monitoring solutions. These tools empower organizations to manage the complexity of distributed systems without being locked into proprietary solutions. @@ -323,7 +323,7 @@ Cloud-native applications, by design, introduce new complexities: Open source monitoring is not just a viable alternative to proprietary solutions—it is the backbone of modern observability. With tools like Prometheus, Loki, Jaeger, and eBPF, organizations can effectively monitor cloud-native applications, dynamically adjust to changing workloads, and achieve operational excellence. By embracing these technologies, teams can focus on delivering exceptional user experiences while keeping operational costs in check. -## How Can Checkly Help with Web Application Monitoring +## How can Checkly help with web application monitoring [Checkly](https://www.checklyhq.com/) offers an integrated platform for synthetic monitoring and API testing, ensuring applications are functional and performant. For simulating user requests to perform synthetic monitoring, Checkly harnesses the power of the open source automation tool Playwright. With [Checkly and Playwright](/detect/synthetic-monitoring/browser-checks/playwright-support), there’s no user behavior that you can’t test, and no critical path you can’t monitor continually. diff --git a/learn/monitoring/what-is-tcp.mdx b/learn/monitoring/what-is-tcp.mdx index 77387a7c7..81e55ef8c 100644 --- a/learn/monitoring/what-is-tcp.mdx +++ b/learn/monitoring/what-is-tcp.mdx @@ -20,7 +20,7 @@ As an application developer, you might think that Transmission Control Protocol TCP stands for Transmission Control Protocol. It is one of the main protocols used in the Internet Protocol (IP) suite. TCP is responsible for ensuring that data sent from one device to another arrives correctly and in the right order. TCP connections underlie the application-layer connections like HTTP connections that we're more familiar with as app developers. It is a connection-oriented protocol, which means it establishes a connection between the sender and receiver before data is sent. -## Why Should Application Developers Care About TCP? +## Why should application developers care about TCP? Even though TCP operates at a lower level than your application code, it directly impacts how your application performs. Here are a few reasons why you should care about TCP: @@ -30,9 +30,9 @@ Even though TCP operates at a lower level than your application code, it directl Understanding these aspects can help you optimize your application's performance and troubleshoot issues more effectively. -## How TCP Works +## How TCP works -### TCP Connection Establishment +### TCP connection establishment Before data can be sent, a TCP connection must be established between the sender (client) and the receiver (server). This process is known as the **three-way handshake**: @@ -44,19 +44,19 @@ Before data can be sent, a TCP connection must be established between the sender Once the three-way handshake is complete, the connection is established, and data can be transmitted. -### Data Transmission +### Data transmission After the connection is established, data is sent in segments. Each segment contains a sequence number that helps the receiver reassemble the data in the correct order. The receiver sends an acknowledgment (ACK) for each segment received. If the sender does not receive an ACK within a certain time, it will retransmit the segment. -### Flow Control +### Flow control TCP uses a mechanism called **flow control** to ensure that the sender does not overwhelm the receiver with too much data. The receiver advertises a window size, which indicates how much data it can accept. The sender adjusts the amount of data it sends based on this window size. -### Congestion Control +### Congestion control TCP also implements **congestion control** to prevent network congestion. If the network is congested, TCP will reduce the rate at which it sends data. This is done using algorithms like **Slow Start**, **Congestion Avoidance**, and **Fast Retransmit**. -### Connection Termination +### Connection termination When the data transfer is complete, the TCP connection is terminated using a four-step process: @@ -67,9 +67,9 @@ When the data transfer is complete, the TCP connection is terminated using a fou After this process, the connection is closed. -## Key TCP Concepts for Application Developers +## Key TCP concepts for application developers -### Ports and Sockets +### Ports and sockets In TCP, communication is identified by a pair of **sockets**. A socket is a combination of an IP address and a port number. The IP address identifies the device, and the port number identifies the specific application or service on that device. @@ -79,7 +79,7 @@ As an application developer, you need to be aware of the ports your application TCP uses buffers to store data before it is sent or after it is received. As a developer, you can control the size of these buffers, which can impact performance. Larger buffers can improve throughput but may increase latenc. -### Keep-Alive +### Keep-alive TCP connections can be kept alive even when no data is being transmitted. This is useful for applications that need to maintain a connection for a long time. However, keep-alive packets can consume network resources, so you should use them judiciously. @@ -87,11 +87,11 @@ TCP connections can be kept alive even when no data is being transmitted. This i TCP uses timeouts to detect when a connection is no longer active. If no data is received within a certain time, the connection may be closed. As a developer, you can configure these timeouts to suit your application's needs. -### Error Handling +### Error handling TCP handles most errors automatically, but you should still be aware of potential issues. For example, if a connection is lost, TCP will attempt to retransmit data, but if the connection cannot be reestablished, your application may need to handle the error. -## TCP and Application Performance +## TCP and application performance ### Latency @@ -105,63 +105,63 @@ Throughput is the amount of data that can be transmitted in a given time. TCP's TCP connections consume resources on both the client and server. If your application needs to handle many simultaneous connections, you should consider how TCP's connection management affects scalability. Techniques like connection pooling and load balancing can help. -## Common TCP Issues and How to Troubleshoot Them +## Common TCP issues and how to troubleshoot them -### Packet Loss +### Packet loss Packet loss can occur due to network congestion or hardware issues. TCP will retransmit lost packets, but frequent packet loss can degrade performance. Use tools like `ping` or `traceroute` to diagnose network issues. -### Slow Performance +### Slow performance Slow performance can be caused by many factors, including high latency, low throughput, or network congestion. Use tools like `netstat` or `tcpdump` to analyze TCP connections and identify bottlenecks. -## Best Practices for Application Developers +## Best practices for application developers -### Use Persistent Connections +### Use persistent connections Persistent connections reduce the overhead of establishing and tearing down TCP connections. This can improve performance, especially for applications that make many small requests. -### Optimize Buffer Sizes +### Optimize buffer sizes Adjusting the size of TCP buffers can improve performance. Larger buffers can increase throughput, while smaller buffers can reduce latency. Experiment with different buffer sizes to find the optimal configuration for your application. -### Monitor TCP Metrics +### Monitor TCP metrics Monitoring TCP metrics like latency, throughput, and packet loss can help you identify performance issues. Use monitoring tools to track these metrics and make adjustments as needed. -### Handle Errors Gracefully +### Handle errors gracefully Even though TCP handles most errors automatically, your application should still handle errors gracefully. For example, if a connection is lost, your application should attempt to reconnect or notify the user. -### Test Under Realistic Conditions +### Test under realistic conditions Test your application under realistic network conditions to ensure it performs well. Use tools that simulate network latency, packet loss, and congestion to identify potential issues. Essentially, once you're trying to test the integration between multiple dependencies connecting via multiple protocols, consider testing in a production environment with [synthetic monitoring](https://www.checklyhq.com/blog/what-is-synthetic-monitoring/) rather than trying to simulate the scenario with mocks. ## TCP and HTTP As mentioned above HTTP connections are application-level connections with TCP handling the network-layer connection. A few key concepts for those familiar with HTTP: -### 1. **Persistent Connections (HTTP Keep-Alive)** +### 1. **Persistent connections (HTTP keep-alive)** - By default, HTTP/1.1 uses **persistent connections**, meaning the same TCP connection can be reused for multiple HTTP requests and responses. - This reduces the overhead of establishing and closing TCP connections, improving performance. - The `Connection: keep-alive` header is used to enable persistent connections. -### 2. **Connection Pooling** +### 2. **Connection pooling** - To further optimize performance, applications often use [**connection pooling**](https://node-postgres.com/features/pooling), where a pool of TCP connections is maintained and reused for multiple HTTP requests. - This is especially useful for applications that make many HTTP requests to the same server (e.g., APIs, microservices). -### 3. **Latency and the Three-Way Handshake** +### 3. **Latency and the three-way handshake** - The TCP three-way handshake introduces latency, especially for short-lived HTTP requests. - Techniques like **HTTP/2 multiplexing** and **HTTP/3** (which uses QUIC instead of TCP) can reduce this latency. - Applications using many short lived requests (e.g. streaming a game to a browser) will want to switch from HTTP/1 connections. -### 4. **Error Handling** +### 4. **Error handling** - TCP handles most network-level errors (e.g., packet loss, retransmission), but your application should still handle HTTP-level errors (e.g., `4xx` and `5xx` status codes). ### 5. **SSL/TLS and HTTPS** - When using HTTPS, the SSL/TLS handshake occurs after the TCP connection is established but before the HTTP request is sent. - This adds additional latency but ensures the connection is secure. -### 6. How HTTP/2 and HTTP/3 Change the Relationship +### 6. How HTTP/2 and HTTP/3 change the relationship **HTTP/2** - HTTP/2 introduces **multiplexing**, allowing multiple HTTP requests and responses to be sent concurrently over a single TCP connection. @@ -178,7 +178,7 @@ As mentioned above HTTP connections are application-level connections with TCP h While TCP is often considered the domain of network engineers, understanding its basics is crucial for application developers. By understanding how TCP works, you can optimize your application's performance, troubleshoot issues more effectively, and build more reliable applications. Remember to monitor TCP metrics, optimize buffer sizes, and handle errors gracefully to ensure your application performs well under all conditions. -## Additional Resources +## Additional resources - [**RFC 793**](https://www.rfc-editor.org/info/rfc793): The official specification for TCP. - [**Wireshark**](https://www.wireshark.org/): A network protocol analyzer that can help you inspect TCP traffic. diff --git a/learn/opentelemetry/context-propagation.mdx b/learn/opentelemetry/context-propagation.mdx index 8fff0672b..17f2b3d44 100644 --- a/learn/opentelemetry/context-propagation.mdx +++ b/learn/opentelemetry/context-propagation.mdx @@ -1,6 +1,6 @@ --- -title: Fundamentals of Context Propagation in OpenTelemetry -sidebarTitle: Context Propagation +title: Fundamentals of context propagation in OpenTelemetry +sidebarTitle: Context propagation description: One of the most basic features of almost any OpenTelemetry tool, is support for context propagation, a fundamental component that sends information from one service to another and allows traces to cover multiple services. Context propagation turns separate service logs into complete traces. It's what makes modern observability possible. date: 2025-04-15 author: Nocnica Mellifera @@ -17,7 +17,7 @@ Imagine the impossibility of diagnosing problems found during end-to-end testing In pursuit of this lofty goal, one of the most basic features of almost any OpenTelemetry tool, is support for context propagation, a fundamental component that sends information from one service to another and allows traces to cover multiple services. -### What is Context? +### What is context? In OpenTelemetry, context is the information that flows through your system with each request. It carries important details like: @@ -27,7 +27,7 @@ In OpenTelemetry, context is the information that flows through your system with Context standards are not defined by the OpenTelemetry project but rather are baced on the [W3C Trace Context](https://www.w3.org/TR/trace-context/) standards. -### Why Context Matters +### Why context matters As mentioned above, modern architectures are complicated. Many outages and other incidents end with engineers examining the logs from a single service, but to get real insight into how requests are processed by your system as a whole, you need context. @@ -37,7 +37,7 @@ Without context: - You lose visibility in distributed systems - Debugging becomes much harder -### How Propagation Works +### How propagation works 1. **Injection**: When a request starts, the context (trace ID, etc.) gets added to headers 2. **Extraction**: When another service receives the request, it pulls the context from headers @@ -45,7 +45,7 @@ Without context: Note that while most OpenTelemetry SDKs and tools propagate context automatically, there’s also the [propagation API](https://opentelemetry.io/docs/specs/otel/context/api-propagators/) if you need to manually propagate context. For example, if you are able to see that two time spans should be part of one trace via an unusual method like examining the messages body with a regex, you’d want to work with the propagation API. -### The Standards Behind It +### The standards behind it OpenTelemetry uses the W3C Trace Context standard (traceparent header) for compatibility. This means: @@ -53,7 +53,7 @@ OpenTelemetry uses the W3C Trace Context standard (traceparent header) for compa - Supported by many observability tools - Ensures consistent behavior everywhere -### Key Components +### Key components - **Context API**: Stores and manages the current context - **Propagators**: Handle injecting/extracting context (usually from HTTP headers) @@ -61,7 +61,7 @@ OpenTelemetry uses the W3C Trace Context standard (traceparent header) for compa Baggage is worth a pointer since it’s important to know that you can add operational information beyond observability data, and thereby piggyback off the great work done for context propagation within the OTel project. This might be used to do something like marking test requests sent by [synthetic monitoring](https://www.checklyhq.com/docs/), so that your datastore knows to route these requests to a test DB. -### In Practice +### In practice When Service A calls Service B: @@ -69,7 +69,7 @@ When Service A calls Service B: 2. Service B reads those headers to continue the trace 3. All spans from both services connect automatically -### Why This is Powerful +### Why this is powerful - No manual correlation needed - Works across any protocol (HTTP, gRPC, queues, etc.) @@ -77,11 +77,11 @@ When Service A calls Service B: Context propagation turns separate operations into connected stories - making complex systems much easier to understand and troubleshoot. -## How Context Propagation Unlocks Efficient Monitoring: Checkly Traces +## How context propagation unlocks efficient monitoring: Checkly Traces At Checkly, we had a problem. We wanted to let our users connect data on the backend performance of their application when handling requests sent by Checkly as part of synthetic user monitoring. For example, if a single postgres query was taking a long time and slowing down one type of user request, we wanted to see what request had taken so long. But we didn’t want to send large amounts of unnecessary data, using up user’s bandwidth and resources. To continue the analogy, we only wanted to send the postgres query data for our specific test request, not all postgres query performance from everywhere. With OpenTelemetry context propagation, this proved feature was easy to implement, and performs well. -### How it works: Context Propagation and Checkly Traces +### How it works: Context propagation and Checkly Traces 1. A user configures their Checkly test service to send requests with an additional header, marking this request as coming from Checkly 2. The user adds a few lines of configuration to their OTel Collector, to send on relevant traces @@ -95,7 +95,7 @@ At Checkly, we had a problem. We wanted to let our users connect data on the bac This is just one example of how context propagation is a key superpower for OpenTelemetry. -## Conclusions: OpenTelemetry Context Propagation is Fundamental to Observability +## Conclusions: OpenTelemetry context propagation is fundamental to observability Context propagation turns separate service logs into complete traces. It's what makes modern observability possible. As systems grow more complex, this simple way of connecting services becomes essential for: diff --git a/learn/opentelemetry/getting-started-with-observability.mdx b/learn/opentelemetry/getting-started-with-observability.mdx index 779b69b17..0d0b08fce 100644 --- a/learn/opentelemetry/getting-started-with-observability.mdx +++ b/learn/opentelemetry/getting-started-with-observability.mdx @@ -1,7 +1,7 @@ --- -title: Getting Started with Observability +title: Getting started with observability displayTitle: Getting started with Observability -sidebarTitle: What is Observability? +sidebarTitle: What is observability? description: Learn OpenTelemetry with Checkly. Add monitoring to every piece of your stack with the open standards and open-source tools. date: 2024-10-17 author: Nocnica Mellifera @@ -18,7 +18,7 @@ canonical: 'https://www.checklyhq.com/docs/learn/opentelemetry/getting-started-w **Observability** is the practice of understanding the internal state of a system by examining the outputs it generates—such as logs, metrics, and traces. OpenTelemetry (OTel) plays a key role in modern observability by offering open standards for instrumenting code, gathering telemetry data, and managing this data through centralized collectors. -### Why Observability Matters +### Why observability matters In systems that adopt **microservices** architecture, tracking system health becomes challenging. Unlike monolithic systems, where a few experts can oversee the whole system, microservices distribute responsibilities across many independent services. This fragmentation makes it difficult to pinpoint issues and monitor end-to-end system behavior. Observability addresses these gaps by enabling better monitoring and faster resolution of incidents. @@ -47,7 +47,7 @@ Often you'll see a question posted to the effect of 'how can the OpenTelemetry c Often in these guides, we'll mention open source tools like Prometheus and Grafana for storing and displaying OpenTelemetry data. However OpenTelemetry is not preferential to these tools, and with a unified standard for transmitting data, any vendor that supports the OTLP standard should work to receive OpenTelemetry data. -### The Three Pillars of Observability +### The three pillars of observability OpenTelemetry enables observability through three core data types: @@ -64,11 +64,11 @@ OpenTelemetry enables observability through three core data types: - Tracing helps identify the components involved in a request and their performance (e.g., through waterfall charts). - Distributed tracing extends this concept to microservices, ensuring that spans from different services are correlated correctly. -### Distributed Tracing with OpenTelemetry +### Distributed tracing with OpenTelemetry Distributed tracing relies on propagating a **trace context** across services. Each service contributes spans to the trace, which are visualized in sequence to understand the request's journey. OpenTelemetry makes this possible by defining trace headers that are passed across service boundaries. -### Getting Started with OpenTelemetry +### Getting started with OpenTelemetry To begin using OpenTelemetry, you will follow three general steps: @@ -80,7 +80,7 @@ The flexibility of the collector enables smooth transitions between direct repor -### Relevant Resources on OpenTelemetry +### Relevant resources on OpenTelemetry - **Metrics Overview**: [Learn how OpenTelemetry handles metrics to provide high-level insights into your system's performance](/learn/opentelemetry/metrics). - **Logging with OpenTelemetry**: [Discover how OpenTelemetry integrates with existing logging libraries and enhances log data correlation across microservices](https://opentelemetry.io/docs/specs/otel/logs/). diff --git a/learn/opentelemetry/how-to-instrument.mdx b/learn/opentelemetry/how-to-instrument.mdx index 475c2891a..67782f7e4 100644 --- a/learn/opentelemetry/how-to-instrument.mdx +++ b/learn/opentelemetry/how-to-instrument.mdx @@ -12,7 +12,7 @@ OpenTelemetry offers two main strategies for adding observability to your applic --- -### Direct Instrumentation +### Direct instrumentation Direct instrumentation involves **manually adding code** to your application to generate telemetry data. This requires developers to use the OpenTelemetry SDK specific to their programming language, explicitly invoking functions to create traces, metrics, or logs. @@ -24,7 +24,7 @@ Direct instrumentation involves **manually adding code** to your application to This approach ensures deeper insights but requires more engineering effort upfront and ongoing maintenance to ensure proper coverage and updates as the code evolves. There are of course 1,001 ways that a clever developer could ensure that the intervention needed even for direct instrumentation was miniman. For example, by wrapping the function that first receives a request, and the function class to ensure that future function calls are reported to a tracer. Direct instrumentation doesn't mean modifying n+1 lines of code, but it does require a fair amount of effort to get launched the first time, no matter how clever your developers are. -### Auto-Instrumentation +### Auto-instrumentation Auto-instrumentation eliminates the need for manual code changes by **injecting telemetry at runtime**. This is often achieved through agents or middleware that modify existing code dynamically. For example, Java or Python applications can use agents to hook into libraries and frameworks they rely on. @@ -39,7 +39,7 @@ Auto-instrumentation eliminates the need for manual code changes by **injecting Finally, auto-instrumentation won’t generally produce useful results if something really unusual is happening inside your application. At base, automatic instrumentation assumes that your service is some kind of online application handling requests and sending responses. If that’s not the case, for example if your application is a machine learning system processing through a database and taking over 48 hours to produce results, you may get less useful information. In these cases, you may want to look into manually reporting [OpenTelemetry metrics](/learn/opentelemetry/metrics). -### When to Use Each +### When to use each - **Direct instrumentation** is ideal for teams seeking maximum flexibility, particularly for custom workflows or applications with unique behavior. - **Auto-instrumentation** is better suited for scenarios where rapid observability is needed, or when standard libraries provide sufficient coverage. diff --git a/learn/opentelemetry/logs.mdx b/learn/opentelemetry/logs.mdx index 4a31363bb..e230e1484 100644 --- a/learn/opentelemetry/logs.mdx +++ b/learn/opentelemetry/logs.mdx @@ -1,5 +1,5 @@ --- -title: Logging in OpenTelemetry, an Engineer’s Guide +title: Logging in OpenTelemetry, an engineer’s guide sidebarTitle: Logging description: This article will go over the basics, and answer common questions for those getting started with logging in OpenTelemetry. OpenTelemetry elevates logging from isolated text snippets to fully contextualized observability data that integrates seamlessly with traces and metrics. date: 2025-04-18 @@ -21,24 +21,24 @@ Taking a look at the ‘Language APIs and SDKs’ section of the OpenTelemetry d In fact only a handful of languages, such as Java, C++ and PHP, had ‘stable’ logs support at the time. See the [current status table](https://opentelemetry.io/docs/languages/) for the latest. Is this a cause for concern? In a word ‘no’, this table covers whether, when using the OpenTelemetry SDK, you can make a call to this SDK to emit logging. It is true that in many SDKs this isn’t yet fully supported, but this shouldn’t be a great concern to you because **you are already emitting logging just fine** in your production environment. There are lots of ways to add logging to the signals being handled by the OpenTelemetry collector and your OpenTelemetry datastore, which hook in to your current logging streams. -## OpenTelemetry and Structured Logging +## OpenTelemetry and structured logging When you send logs from traces or events, you could just write raw text. But raw logs are hard to read and parse later. OpenTelemetry prefers **structured logging** instead. Structured logging is a best practice recommended by AWS and other cloud providers as well, since even a simple search of past logs can become prohibitively expensive if you’re -### What is Structured Logging? +### What is structured logging? Structured logging means logs are saved in a clear, machine-readable format—like JSON—instead of plain text. Each log has: - **Fields** (key-value pairs) for details like timestamps, severity, and context. - **Consistent formatting**, making logs easier to search, filter, and analyze. -### Why OpenTelemetry Uses Structured Logs +### Why OpenTelemetry uses structured logs 1. **Better for Machines** – Tools can automatically process logs without messy parsing. 2. **Connects to Traces** – Logs can link to traces and spans, helping debug issues faster. 3. **Standardized** – OTel defines a common schema so logs work across different systems. -### How OTel Handles Logs +### How OTel handles logs - **Log Records** include: - Timestamp @@ -47,7 +47,7 @@ Structured logging means logs are saved in a clear, machine-readable format—li - Attributes (extra context like `user_id`) - **Integration** with traces and metrics for full observability. -### Example (Structured vs. Raw) +### Example (structured vs. Raw) **Raw (Hard to Parse):** @@ -88,9 +88,9 @@ If you turn high-cardinality fields (like `user_ip`) into metric labels, you’ Logging, then, should be seen as similar to event data, and be the storehouse for aggregate, specific information like IP addresses and specific page routes. -## The Promise of OpenTelemetry Logging: Full Context on Every Line +## The promise of OpenTelemetry logging: Full context on every line -### The Problem with Traditional Logging +### The problem with traditional logging Today, logs, traces, and metrics live in separate worlds. They use different tools, formats, and collection methods, making it hard to connect them. @@ -100,7 +100,7 @@ Today, logs, traces, and metrics live in separate worlds. They use different too This leads to **fragile observability**—logs tell part of the story, but not the whole picture. -### OpenTelemetry’s Solution: Built-in Context +### OpenTelemetry’s solution: Built-in context OpenTelemetry (OTel) fixes this by **propagating full context in every log line**. @@ -108,25 +108,25 @@ OpenTelemetry (OTel) fixes this by **propagating full context in every log line* - **Consistent metadata** – Kubernetes pod info, service names, and other attributes are added *automatically* by the OTel Collector—no manual tagging needed. - **Distributed systems just work** – Logs from different services share the same context, so you can follow a request across your entire system. -### How It Works +### How it works 1. **Structured logs** – Logs follow OTel’s data model (like JSON with clear fields). 2. **Automatic enrichment** – The OTel Collector adds context (e.g., `k8s.pod.name`) to logs, traces, and metrics *the same way*. 3. **No re-engineering of existing libraries** – Works with existing logging libraries (Log4j, Logback, etc.) via bridges. -### Why This Matters +### Why this matters - **No more guessing** – Every log line knows exactly where it came from and how it fits into the bigger picture. - **Better debugging** – Jump from a log error directly to the trace, metrics, and related logs—no manual searching. - **Future-proof** – Even legacy apps can join the OTel ecosystem via the Collector. -### The Promise, not yet fulfilled +### The promise, not yet fulfilled OpenTelemetry promises to turn logs from isolated snippets into **fully connected observability data**. As noted above, not every language SDK has full logging support, meaning this isn’t completely possible now. And the addition of enrichment data isn’t an easy or automatic process at the collector level (the collector is stateless and can only enrich logs based on what it’s processing at that moment). However, logging with OpenTelemetry has a bright future, and adopting now means you’re likely to be producing highly valuable logs in the next few years that prove worth the effort. -## The Collector: OpenTelemetry’s Super-Powered Logging Proxy +## The Collector: OpenTelemetry’s super-powered logging proxy -### The Problem with Legacy Log Collection +### The problem with legacy log collection Most apps today log to files or stdout—simple, but messy. To get those logs into observability tools, you need: @@ -146,21 +146,21 @@ The Collector acts as a **universal log processor**. It can: **Bonus:** It does the same for traces and metrics—enriching all signals consistently. -### Two Ways to Use It +### Two ways to use it -### Option 1: File/Stdout → Collector (No Code Changes) +### Option 1: File/stdout → Collector (no code changes) - **How it works**: The Collector tails log files, parses them, and adds context. - **Good for**: Legacy apps, third-party software. - **Tradeoff**: Parsing can be tricky if log formats are inconsistent. -### Option 2: App → Collector (Direct OTLP) +### Option 2: App → Collector (direct OTLP) - **How it works**: Use an OTel "log appender" (e.g., for Log4j) to send logs directly to the Collector. - **Good for**: New apps or those you control. - **Why?** No file parsing, no lost logs on crashes, full structured data. -### The Best Part: Zero Manual Enrichment +### The best part: Zero manual enrichment No more editing every `log.info()` call! The Collector handles: @@ -168,7 +168,7 @@ No more editing every `log.info()` call! The Collector handles: - **Resource attributes** (like `k8s.pod.name`) - **Routing** (send logs to Loki, Splunk, etc.) -### Why This Wins +### Why this wins - **No more "log soup"** – Every log line has rich, queryable fields. - **Easier correlation** – Logs that carry a trace ID link to their traces. @@ -176,7 +176,7 @@ No more editing every `log.info()` call! The Collector handles: How to get started? Start with file collection, then phase in direct OTLP for critical apps. -## Conclusions: OpenTelemetry is Critical to Logging +## Conclusions: OpenTelemetry is critical to logging Logging has always been a fundamental part of understanding software behavior, but in modern distributed systems, traditional logging approaches fall short. OpenTelemetry elevates logging from isolated text snippets to fully contextualized observability data that integrates seamlessly with traces and metrics. diff --git a/learn/opentelemetry/metrics.mdx b/learn/opentelemetry/metrics.mdx index 64c165bba..743b82d97 100644 --- a/learn/opentelemetry/metrics.mdx +++ b/learn/opentelemetry/metrics.mdx @@ -1,5 +1,5 @@ --- -title: What are OpenTelemetry Metrics? +title: What are OpenTelemetry metrics? sidebarTitle: Metrics description: OpenTelemetry Metrics play a critical role in monitoring applications by offering a way to capture and analyze key metrics in a standardized, scalable manner. Whether you're managing a complex microservices architecture or a simpler system, OpenTelemetry helps track essential statistics that reveal the health and performance of your services. Learn more about OpenTelemetry & Monitoring with Checkly. Explore metrics, one of the three pillars of observability. date: 2024-10-18 @@ -10,7 +10,7 @@ canonical: 'https://www.checklyhq.com/docs/learn/opentelemetry/metrics/' --- -## What are Metrics? +## What are metrics? Metrics represent **quantitative measurements** of your system’s health and behavior. They provide insights into performance trends, such as: @@ -21,7 +21,7 @@ Metrics represent **quantitative measurements** of your system’s health and be Metrics are lightweight and highly efficient to collect, aggregate, and query. They help identify patterns and anomalies without burdening storage, making them suitable for continuous monitoring at scale. -### Types of Metrics in OpenTelemetry: +### Types of metrics in OpenTelemetry: - **Counter**: Measures occurrences or events, such as the number of requests handled. - **Gauge**: Captures values that fluctuate, like memory usage. @@ -30,7 +30,7 @@ Metrics are lightweight and highly efficient to collect, aggregate, and query. T Explore further in the [OpenTelemetry Metrics Documentation](https://opentelemetry.io/docs/concepts/signals/metrics/). -## Why Metrics Matter +## Why metrics matter In a **microservices** environment, metrics are indispensable for: @@ -46,16 +46,16 @@ Metrics have a number of advantages over tracing. Metrics are much more data eff Should you use metrics instead of traces to monitor your service? Absolutely not. Metrics will always present average performance, and the specific information needed to really understand root causes will be elusive. Further, even with high resolution timeseries metrics it’s very hard to go from worrying metrics to find matching log data of a problem. Finally, modern traces can effectively show information about asynchronous requests as they contribute to overall request time, something that’s very hard to tease out of bare metrics. -## Setting up OpenTelemetry Metrics +## Setting up OpenTelemetry metrics -### Auto-Instrumentation vs. Manual Instrumentation +### Auto-instrumentation vs. Manual instrumentation 1. **Auto-Instrumentation**: Many popular frameworks and libraries come with automatic OpenTelemetry instrumentation, requiring minimal setup. 2. **Manual Instrumentation**: Developers can manually add metrics within the application code by using SDKs to track specific business metrics (e.g., purchases per hour). Learn more about instrumentation options in the [OpenTelemetry SDK Guide](https://opentelemetry.io/docs/instrumentation/). -## Example Metric Pipeline +## Example metric pipeline With OpenTelemetry, you can collect, process, and export metrics using **Collectors**. Here’s a high-level example of a typical metric pipeline: @@ -67,7 +67,7 @@ Learn how to configure a collector in the [OpenTelemetry Collector Guide](/learn -## Best Practices for Metrics in OpenTelemetry +## Best practices for metrics in OpenTelemetry - **Optimize cardinality**: Avoid creating too many distinct labels, as this can overwhelm storage and query systems. - **Set appropriate aggregation intervals**: Batch data intelligently to balance between real-time insights and system load. diff --git a/learn/opentelemetry/otel-agent-management-protocol.mdx b/learn/opentelemetry/otel-agent-management-protocol.mdx index e330f2263..945fb00e4 100644 --- a/learn/opentelemetry/otel-agent-management-protocol.mdx +++ b/learn/opentelemetry/otel-agent-management-protocol.mdx @@ -16,7 +16,7 @@ The OpenTelemetry Open Agent Management Protocol (OpAMP) is an emerging standard OpAMP provides a standard framework for remotely managing telemetry agents. Although current implementations primarily focus on the OpenTelemetry Collector, the protocol is flexible enough to manage various telemetry-related components, including instrumentation agents or future SDK-level integrations. The primary goal is to allow real-time configuration changes, package updates, and secure connection management without manual intervention. -### Key Features of OpAMP +### Key features of OpAMP 1. **Dynamic Configuration Management:** @@ -35,7 +35,7 @@ OpAMP provides a standard framework for remotely managing telemetry agents. Alth Tail-based sampling, a feature OpAMP aims to support, allows agents to decide which traces to retain after they are fully captured, rather than at the start. This strategy helps reduce the amount of irrelevant telemetry data, though it requires specialized architectures to handle sampling decisions across distributed collectors. -### Deployment Models for OpAMP +### Deployment models for OpAMP OpAMP supports multiple deployment models to fit different environments, including: @@ -48,7 +48,7 @@ OpAMP supports multiple deployment models to fit different environments, includi The supervisor approach runs the OpAMP client as a separate process alongside the collector. It monitors the collector’s health, applies configuration changes, and ensures that the collector restarts if it crashes or fails to start after updates. This model provides greater fault tolerance, especially in Kubernetes environments where the client and collector can run as sidecars in the same pod. -### Use Cases for OpAMP +### Use cases for OpAMP - **Remote Configuration and Management:** @@ -63,13 +63,13 @@ OpAMP supports multiple deployment models to fit different environments, includi TLS certificates and other credentials can be dynamically rotated, ensuring secure and compliant communication between agents and backends. -### Challenges and Future Developments +### Challenges and future developments Some advanced use cases, such as tail-based sampling, present challenges due to the need for stateful processing and coordinated decision-making across multiple collectors. While the protocol provides a foundation for such features, implementing them in a distributed environment requires careful architectural design. OpAMP is still evolving, with many features in beta or under active development. In the coming quarters, more user-facing tools are expected, including graphical interfaces for managing collector configurations. As vendors begin to adopt the protocol, end-users can expect smoother agent management and the ability to make configuration changes in real-time. -### The Current State of OpAMP Development +### The current state of OpAMP development The Open Agent Management Protocol (OpAMP) is evolving as a key component for managing fleets of telemetry agents, such as the OpenTelemetry Collector, at scale. As of late 2023, the protocol is still in its **beta phase**, with development focused on enabling dynamic configuration, remote updates, and secure credential management across distributed agents. diff --git a/learn/opentelemetry/otel-filtering.mdx b/learn/opentelemetry/otel-filtering.mdx index 9d33a4439..9816b50b0 100644 --- a/learn/opentelemetry/otel-filtering.mdx +++ b/learn/opentelemetry/otel-filtering.mdx @@ -1,5 +1,5 @@ --- -title: Advanced Data Filtering with the OpenTelemetry Collector +title: Advanced data filtering with the OpenTelemetry Collector sidebarTitle: Filtering description: The OpenTelemetry Collector is a stand-alone service designed to collect, process, and export telemetry data such as logs, metrics, and traces. You can filter this data with the collector. An advanced guide to filtering data with processors and the OpenTelemetry Transform Language. date: 2024-10-18 @@ -11,7 +11,7 @@ The **OpenTelemetry Collector** is a powerful tool for managing telemetry data f --- -## Why Filtering Matters +## Why filtering matters Instrumentation often generates **noisy or redundant data**. Some metrics or traces may include unnecessary information—like personal data or debug logs—leading to bloated dashboards, higher storage costs, and privacy risks. Filtering data within the OpenTelemetry Collector allows you to: @@ -22,7 +22,7 @@ Instrumentation often generates **noisy or redundant data**. Some metrics or tra --- -## How the OpenTelemetry Collector Filters Data +## How the OpenTelemetry Collector filters data The Collector consists of **receivers, processors, and exporters**. Each plays a role in data filtering: @@ -30,7 +30,7 @@ The Collector consists of **receivers, processors, and exporters**. Each plays a 2. **Processors**: Modify, filter, or batch data before it is exported. 3. **Exporters**: Send the processed data to observability backends, such as **Prometheus** or **Grafana**. -### Processor-based Filtering +### Processor-based filtering Processors allow transformations and data filtering mid-pipeline. Processors offer inherently limited transformation configuration to do the most common tasks like: @@ -52,7 +52,7 @@ processors: --- -## Transformations Using OpenTelemetry Transform Language (OTTL) +## Transformations using OpenTelemetry transform language (OTTL) The **OpenTelemetry Transform Language (OTTL)** provides enhanced flexibility for complex transformations. OTTL allows for: @@ -77,7 +77,7 @@ processors: Since OTTL allows functional changes of your data, this is really the simplest possible example of a use case: a gate that goes just beyond simple filtering. -## Stateful Operations and Their Limitations +## Stateful operations and their limitations While the collector excels at real-time data transformations, it is **stateless by design** to ensure high performance. Stateful operations—such as aggregating historical data—are not natively supported. This ensures the collector remains lightweight and efficient. @@ -88,7 +88,7 @@ Common limitations include: Note: if you are reading this section trying to figure out how to add stateful filtering, e.g. forwarding only the longest trace seen in a 24-hour period I recommend that you *stop* pursuing this within the OTel collector. The limitations of the collector exist for performance reasons, and adding state to the tool will cause unexpected downstream effects as, for example, the collector becomes too burdened to always be ready to accept OTLP data from your services. -## Filtering Use Cases +## Filtering use cases 1. **PII Masking**: Remove personal data before sending traces to public dashboards. 2. **Debug Data Suppression**: Drop debug-level logs from production pipelines. diff --git a/learn/opentelemetry/overview.mdx b/learn/opentelemetry/overview.mdx index ad47ff5bc..7c2c2759b 100644 --- a/learn/opentelemetry/overview.mdx +++ b/learn/opentelemetry/overview.mdx @@ -1,5 +1,5 @@ --- -title: Learn How to Observe and Monitor your Software with OpenTelemetry +title: Learn how to observe and monitor your software with OpenTelemetry displayTitle: Getting started with OpenTelemetry and Observability sidebarTitle: Overview description: Learn OpenTelemetry with Checkly. Add monitoring to every piece of your stack with the open standards and open-source tools. @@ -13,11 +13,11 @@ canonical: 'https://www.checklyhq.com/docs/learn/opentelemetry/overview/' Learn Observability and OpenTelemetry with Checkly. Add monitoring to every piece of your stack with the open standards and open-source tools. -## Getting Started +## Getting started Learn the basics of observability and how to get started with OpenTelemetry. @@ -30,7 +30,7 @@ and open-source tools. -## Diving Deeper +## Diving deeper @@ -51,11 +51,11 @@ Whether you're just getting started or looking to advance your monitoring skills **New to monitoring?** Start with [Monitoring fundamentals](/learn/monitoring/) to build a solid foundation, then explore Playwright for browser automation and testing. -## Popular Posts +## Popular posts @@ -63,7 +63,7 @@ Whether you're just getting started or looking to advance your monitoring skills @@ -71,7 +71,7 @@ Whether you're just getting started or looking to advance your monitoring skills diff --git a/learn/playwright/assertions.mdx b/learn/playwright/assertions.mdx index c7db73c6a..da05454d7 100644 --- a/learn/playwright/assertions.mdx +++ b/learn/playwright/assertions.mdx @@ -1,5 +1,5 @@ --- -title: Playwright Assertions - Types & Best Practices +title: Playwright assertions - Types & best practices displayTitle: Playwright Assertions - Types & Best Practices metatags: title: Playwright Assertions - Types & Best Practices @@ -17,17 +17,17 @@ import SignUpCta from "/snippets/sign-up-cta.mdx" -### What are Playwright Assertions? +### What are Playwright assertions? Playwright is more than a testing framework. With its generalized tool at simulating user behavior in a browser (or via an API), Playwright is better defined as a web automation framework. You can use Playwright to scrape websites, automate form submissions, or any other time it would be helpful to replace a human web user with a robot. For most users, Playwright is intimately associated with end-to-end tests, and for these we must stop our automated actions and check to see if everything is working right. To make an automation into a test, we have assertions. When a hard assertion fails, the execution of a Playwright test stops, and following steps are not run. -### Types of Playwright Assertions +### Types of Playwright assertions Playwright offers a variety of assertion types to accommodate different testing scenarios, and there are two broad categories for flexible, Web-first assertions and rigid, brittle, non-retrying assertions. Web-first assertions return promises, since they will return when they are successful or time out, where as non-retrying assertions throw their response immediately. -### Auto-retrying, Web-first Assertions +### Auto-retrying, web-first assertions Auto-retrying assertions automatically recheck conditions until they pass or a timeout is reached. They both make a test more stable, and can make tests execute more quickly, and in the language of game theory should be 'strictly better' than non-retrying assertions. @@ -64,7 +64,7 @@ Auto-retrying assertions automatically recheck conditions until they pass or a t | `expect(locator).toBeFocused()` | element is focused. | | `expect(locator).not.toBeFocused()` | element is not focused. | -### Non-retrying Assertions +### Non-retrying assertions Non-retrying assertions evaluate conditions only once. They are used when you expect a condition to be deterministic and want to avoid any retry logic. @@ -92,11 +92,11 @@ Non-retrying assertions evaluate conditions only once. They are used when you ex This makes the most sense when using Playwright to run single end-to-end tests in a controlled environment. If you're using Playwright to run on a cadence and monitor a production system, for example, with [Checkly](/detect/synthetic-monitoring/browser-checks/playwright-support), you generally want to stick with the auto-retrying assertions to avoid unnecessary alerts. -### Negating Assertions +### Negating assertions Negating matchers allow you to assert that a condition does not hold. For example, you can use `toBeFalsy` or `not.toContain` to make negative assertions on a value. If you're checking an element directly, use a locator assertion such as `expect(locator).not.toContainText()` instead, as it implements Playwright's auto-retries. -### Soft Assertions +### Soft assertions Soft assertions won't fail your test immediately, but rather allow the test to continue running after a failure. Using soft assertions is useful for gathering more complete information during test runs. Soft assertions are a critical component of production monitoring, as when measuring things like load times, a failing response time may not mean that we want to stop the check entirely. Any Playwright test with failing soft assertions will still be listed as failed, but the test will still run to completion (or the next hard assertion that fails). @@ -144,7 +144,7 @@ test("SpaceX-API Dragon Capsules & Next Launch", async ({ request }) => { In this case if the response has a `200` status code but the API response time is more than 200 milliseconds, the status of this check will be degraded and the slow API response time will be included as a failed step. If the response came back as a non-200 status (indicating an error) then the check would be 'failed,' whether or not `markCheckAsDegraded` was called. You can [configure alert channels](https://www.checklyhq.com/docs/communicate/alerts/channels#managing-alert-channels) to notify you when a check has degraded. -### Custom Assertions +### Custom assertions While Playwright has almost every scenario for testing supported in its core methods, it remains quite customizable, even [allowing custom assertions](https://www.youtube.com/watch?v=Fs-nM747TY4). @@ -152,7 +152,7 @@ While Playwright has almost every scenario for testing supported in its core met - `expect.poll`: Polls a condition until it passes or a timeout is reached, useful for dynamic content. - `expect.toPass`: Runs a block of assertions until all pass, [often used for testing flaky or complex scenarios.](https://www.youtube.com/watch?v=8g7FvoRToGo) -### When to Use Soft vs Hard Assertions +### When to use soft vs hard assertions Soft assertions are helpful for tests where understanding multiple failures is beneficial, such as end-to-end tests with a wide range of checks. Hard assertions are more suitable for critical conditions where a single failure should immediately terminate the test. @@ -169,18 +169,18 @@ Soft assertions are helpful for tests where understanding multiple failures is b | **Form field validations** | Yes. Allows collecting errors on multiple fields at once, providing more detailed feedback. | No. Stopping at the first validation failure can hinder broader test coverage. | | **Verifying the presence of essential elements before action** | No. If the element must exist for the test to continue, a hard assertion ensures reliability. | Yes, if the element's presence is not critical and you want the test to proceed. | -### How to Get Started with Playwright Assertions in Simple Steps +### How to get started with Playwright assertions in simple steps Follow these steps to get up and running with Playwright Assertions: 1. Install Playwright:`npm init playwright@latest`. 2. Start writing tests with various assertion types to validate application behavior. -### How to Add Custom Matchers Using `expect.extend` +### How to add custom matchers using `expect.extend` Custom matchers can be added using `expect.extend`, allowing developers to define more readable or application-specific assertions. -### Playwright Custom Matchers with Example +### Playwright custom matchers with example Here's a quick example of how to create a custom matcher for checking specific conditions: @@ -208,7 +208,7 @@ expect(100).toBeWithinRange(90, 110) This can be especially useful if we're doing complex assertions, or specialized parsing of responses. -## Common Assertion Errors and How to Debug Them +## Common assertion errors and how to debug them Understanding how to diagnose assertion failures can save significant debugging time. @@ -224,7 +224,7 @@ When you have page components you want to ensure are loading quickly, or you hav After that fixed period, if the next step doesn't work, the test will fail. Hard waits are the most common cause of unreliable or 'flaky' tests with Playwright. They're also inefficient, if the element we're checking for becomes available *before* the hard wait time has elapsed, the test runner still has to wait to the end of the wait time. Read more about this in our page on [waiting in Playwright](https://www.checklyhq.com/learn/playwright/waits-and-timeouts/). -### Manual Assertions +### Manual assertions While a hard wait is problematic since it doesn't benefit from Playwright's auto-waiting, an improperly structured assertion doesn't include waiting at all. By wrapping the `await` inside the `expect()` instead of vice versa, and by using a non-web-first assertion, we get no waiting. In this case we're checking that there is some text inside an element. @@ -240,15 +240,15 @@ Use web-first assertions such as `toBeEmpty()` instead. await expect(targetPage.locatorToSomeElement).not.toBeEmpty(); ``` -### Debugging Assertion Errors +### Debugging assertion errors Playwright provides debug tools such as `page.pause()` and verbose logging to inspect what happens when a test fails. You might also consider a visual like the Playwright VS Code extension to add a visual debugger when writing or debugging tests. [Read more about debugging Playwright scripts](https://www.checklyhq.com/learn/playwright/debugging/). -### Identifying Flaky Tests +### Identifying flaky tests Flaky tests are those that fail intermittently, often due to timing issues or unpredictable environment factors. You can use `expect.poll` and `.toPass` adjust timeouts to [stabilize flaky tests](https://www.youtube.com/watch?v=8g7FvoRToGo). To identify flaky tests you can use `--repeat-each=100` to really hammer a test and see if it passes constantly. -### Best Practices for Using Playwright Assertions +### Best practices for using Playwright assertions Implementing best practices can make your tests more reliable and easier to maintain. diff --git a/learn/playwright/authentication.mdx b/learn/playwright/authentication.mdx index 61f6d709b..527f2326b 100644 --- a/learn/playwright/authentication.mdx +++ b/learn/playwright/authentication.mdx @@ -1,5 +1,5 @@ --- -title: How to Manage Authentication in Playwright +title: How to manage authentication in Playwright subTitle: Speeding up tests by skipping login, and more description: Learn how to handle authentication in Playwright, including SSO, 2FA, Passkeys and more. Reuse authentication state across tests with storageState. displayDescription: Learn how to handle authentication in Playwright, including SSO, 2FA, Passkeys and more. Reuse authentication state across tests with storageState. @@ -39,7 +39,7 @@ For web and applications and APIs, you will typically have to run through some i > Use Playwright’s built-in [code generator](https://playwright.dev/docs/codegen-intro#running-codegen) to quickly get a script of your login steps. It will do the right thing in 90% of the cases. Just run `npx playwright codegen ` -## Basic Auth / Username & Password +## Basic auth / username & password Any flow that relies on the Basic Authentication standard or typing in a username and password will tend to look very similar to example test below. @@ -64,7 +64,7 @@ Notice the following: 3. At the end, we assert that the login actually worked, by checking for a user specific piece of content on the page. 4. All handling of cookies, hashing of username and password and other things your browser typically takes care of are handled here transparently. -## SSO & Social Login +## SSO & social login Any SSO or social login — think Google, GitHub, Microsoft, SAML-based solutions or any 3rd party auth provider like Okta— works pretty much the same as basic authentication / username & password from the perspective of the test @@ -93,7 +93,7 @@ test('Google login', async ({ page }) => { [Check the full article on Google Login.](https://www.checklyhq.com/learn/playwright/google-login-automation/) -## Two-Factor Authentication / TOTP +## Two-factor authentication / TOTP Things get a little harder when using Two-Factor Authentication (2FA) and / or Time Based One Time Passwords (TOTP). You will probably be familiar with providing an extra “factor” like a code from an SMS message, a authenticator app diff --git a/learn/playwright/bypass-totp.mdx b/learn/playwright/bypass-totp.mdx index b7a4254f0..8c91af9bf 100644 --- a/learn/playwright/bypass-totp.mdx +++ b/learn/playwright/bypass-totp.mdx @@ -1,5 +1,5 @@ --- -title: How to Bypass Time-Based 2FA Login Flows With Playwright +title: How to bypass time-based 2FA login flows with Playwright description: "Automate logins protected by time-based one-time password (TOTP) two-factor authentication in Playwright by generating valid passcodes inside your test." subTitle: Playwright for complex authentication tasks date: 2024-10-30 @@ -9,7 +9,7 @@ tags: - testing weight: 5 -sidebarTitle: TOTP Authentication +sidebarTitle: TOTP authentication learn_playwright: parent: "E2E examples" canonical: 'https://www.checklyhq.com/docs/learn/playwright/bypass-totp/' diff --git a/learn/playwright/challenging-flows.mdx b/learn/playwright/challenging-flows.mdx index 4d5c9adbc..91e282036 100644 --- a/learn/playwright/challenging-flows.mdx +++ b/learn/playwright/challenging-flows.mdx @@ -1,5 +1,5 @@ --- -title: How to Handle Challenging Automation Flows in Playwright +title: How to handle challenging automation flows in Playwright description: "Automate hard-to-test flows like signup, social login, and password reset in Playwright, and get past captchas and bot detection in test environments." subTitle: Automation countermeasures and shortcomings date: 2020-07-23 diff --git a/learn/playwright/checkout-testing-guide.mdx b/learn/playwright/checkout-testing-guide.mdx index 7bb3fd726..122bbfd7b 100644 --- a/learn/playwright/checkout-testing-guide.mdx +++ b/learn/playwright/checkout-testing-guide.mdx @@ -1,5 +1,5 @@ --- -title: Mastering E2E Checkout Testing Using Playwright +title: Mastering E2E checkout testing using Playwright description: "Write end-to-end checkout tests with Playwright, adding products to a cart, entering billing details, and confirming the purchase completes successfully." subTitle: Filling a basket and completing the transaction date: 2020-07-02 diff --git a/learn/playwright/clicking-typing-hovering.mdx b/learn/playwright/clicking-typing-hovering.mdx index 20b038f40..5e2adcd07 100644 --- a/learn/playwright/clicking-typing-hovering.mdx +++ b/learn/playwright/clicking-typing-hovering.mdx @@ -1,5 +1,5 @@ --- -title: How to Click, Type, and Hover with Playwright +title: How to click, type, and hover with Playwright description: "Replicate real user interactions in Playwright, clicking buttons, typing into fields, and hovering over elements using user-first selectors." subTitle: Basic page interactions date: 2020-06-15 diff --git a/learn/playwright/codegen.mdx b/learn/playwright/codegen.mdx index 632d165a7..ddf02fcda 100644 --- a/learn/playwright/codegen.mdx +++ b/learn/playwright/codegen.mdx @@ -1,5 +1,5 @@ --- -title: Record Automation Scripts Using Playwright Codegen +title: Record automation scripts using Playwright codegen description: "Generate Playwright scripts automatically with the codegen command, recording your browser interactions into editable test code with user-first locators." subTitle: Automatically record Playwright tests with codegen date: 2025-02-20 @@ -23,7 +23,7 @@ import { YoutubeEmbed } from "/snippets/youtube-embed.jsx" Did you know that you can use Playwright to generate your automation scripts automatically? Let's dive into how you can leverage Playwright's `codegen` feature to record scripts effortlessly. -### Step 1: Launch Playwright Codegen +### Step 1: Launch Playwright codegen To get started, you'll use the `codegen` command from the Playwright executable. Let's say you want to create a script for interacting with [Checkly](https://checklyhq.com/). You would run the following command in your terminal: @@ -39,7 +39,7 @@ Note that the inspector will populate with the basic code needed for a Playwrigh Also, the browser will automatically highlight elements, and show you a locator for them in Playwright’s preferred [user-first selector](https://www.checklyhq.com/blog/playwright-user-first-selectors/) format. -### Step 2: Interact with the Website +### Step 2: Interact with the website Now, you can start interacting with the website as you normally would. For example: @@ -63,7 +63,7 @@ test('test', async ({ page }) => { Note that codegen will make a ‘best effort’ at emulating your actions and writing ‘best practice’ code, so you should always review it before deploying. -### Step 3: Add Assertions to your tests +### Step 3: Add assertions to your tests Every action in the script above has implicit assertions about the elements we interact with. Playwright will expect these elements are stable, visible, and enabled; and if one isn’t then the test will fail we could call this done, but we generally want our tests to contain assertions beyond just navigating. There are a few reasons why you should have assertions in your test: It makes it clearer to future coders what your test was checking for, and the error message is more useful from a failed assertion rather than just failing to find an element. Right now all we’ll get if the test above fails is a timeout and a line which failed. @@ -84,23 +84,23 @@ this will generate a `.toContainText(` assertion in the inspector Note that the assertions created by codegen are fairly basic, and while they could be the whole basis for a test suite, it’s a great idea to learn about [Playwright assertions](https://www.checklyhq.com/learn/playwright/assertions/) and write more complex ones yourself. You can write any calculable value into an assertion, so the sky is the limit. -### Step 4: Write tests in Java, Python, .Net or JavaScript - Choose Your Target Environment +### Step 4: Write tests in Java, Python, .Net or JavaScript - Choose your target environment After you're done interacting with the website, you can choose the target environment for your script. Playwright allows you to generate scripts in various languages, such as JavaScript, Python, or Playwright's own test framework. For this example, let's pick JavaScript. You can copy the generated script from the inspector. -### Step 5: Save and Run Your Script +### Step 5: Save and run your script With your script copied, you can drop the test into a Playwright `spec` file, and run it with `npx playwright test` to see the results. Note that the script as generated contains no comments or further explanations. If you want to be considerate of your next coder, who let’s be honest is probably you in 6 months having forgotten everything about this test, add some comments, give the test a more helpful name than `'test'` and [divide the test into steps for readability](https://www.checklyhq.com/blog/improve-your-playwright-documentation-with-steps/). -### Step 6: Run Your Script in the Cloud +### Step 6: Run your script in the cloud If you want to take it a step further, use [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) to run your Playwright tests in the Checkly infrastructure as synthetic monitoring. -### Bonus Step 1: Add Playwright to Visual Studio Code +### Bonus step 1: Add Playwright to Visual Studio Code Many developers are now comfortable using Microsoft’s Visual Studio Code as their IDE, and Playwright has a great plugin for Visual Studio Code. Install the [VS Code extension from the marketplace](https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright) or from the extensions tab in VS Code. @@ -110,7 +110,7 @@ With the plugin installed, you can record a new test directly into your script f The plugin has a lot of other neat features including being able to run your tests right from the code editor, and show a browser running your tests. If you’re already using Visual Studio Code, or thinking about adopting it as an IDE, the Playwright plugin is worth checking out! -### Bonus Step 2: Simulate a Mobile Browser Viewport with `--viewport` +### Bonus step 2: Simulate a mobile browser viewport with `--viewport` Playwright can’t perfectly emulate a particular build of Mobile Opera running on a 10-year-old Android, but a good start is simulating a mobile viewport, to see if things render correctly and buttons are still visible. Start by setting your viewport size when you start up codegen: @@ -125,7 +125,7 @@ Your browser will start up showing the new, narrow viewport You’ll also notice in the screenshot that the inspector automatically adds a `test.use` command to set the viewport. You can go quite a bit further with these settings, altering the user-agent for your test as needed to [emulate](https://playwright.dev/docs/emulation) different devices. -## See Codegen in action +## See codegen in action To see the highly visual codegen tool in action, check out Stefan’s video below: diff --git a/learn/playwright/debugging-errors.mdx b/learn/playwright/debugging-errors.mdx index 543543a5e..c399101e6 100644 --- a/learn/playwright/debugging-errors.mdx +++ b/learn/playwright/debugging-errors.mdx @@ -1,5 +1,5 @@ --- -title: Playwright Debugging Errors - Common Issues and Solutions +title: Playwright debugging errors - Common issues and solutions description: "Recognize common categories of Playwright errors and their obvious and non-obvious root causes, with links to fixes for the most frequent failures." subTitle: Recurring non-trivial debugging situations and how to solve them date: 2021-08-05 diff --git a/learn/playwright/debugging-with-ai-agents.mdx b/learn/playwright/debugging-with-ai-agents.mdx index 31ca0d514..3df5e0e6e 100644 --- a/learn/playwright/debugging-with-ai-agents.mdx +++ b/learn/playwright/debugging-with-ai-agents.mdx @@ -1,5 +1,5 @@ --- -title: Debugging Playwright Tests with AI Agents +title: Debugging Playwright tests with AI agents description: "Let your coding agent debug failing Playwright tests: read the error-context.md attachment, analyze traces in the terminal with npx playwright trace, and step through live tests with --debug=cli." subTitle: Playwright's debugging tools went text-first tags: diff --git a/learn/playwright/debugging.mdx b/learn/playwright/debugging.mdx index 1cd0467bc..55488649e 100644 --- a/learn/playwright/debugging.mdx +++ b/learn/playwright/debugging.mdx @@ -1,5 +1,5 @@ --- -title: Playwright Debugging - Techniques for Script Troubleshooting +title: Playwright debugging - Techniques for script troubleshooting description: "Troubleshoot failing Playwright scripts by reading error messages in context, understanding expected behavior, and using the right tools to gain visibility." subTitle: How to go about fixing what is not working date: 2021-07-26 diff --git a/learn/playwright/error-click-not-executed.mdx b/learn/playwright/error-click-not-executed.mdx index eb6cef207..db253969a 100644 --- a/learn/playwright/error-click-not-executed.mdx +++ b/learn/playwright/error-click-not-executed.mdx @@ -1,5 +1,5 @@ --- -title: How to Fix the "Click Not Executed" Error in Playwright +title: How to fix the "Click Not Executed" error in Playwright description: "Diagnose why a Playwright click seems to be ignored, from duplicate element IDs to the wrong element receiving the click, and use strict mode to catch it." date: 2021-11-18 author: Giovanni Rago diff --git a/learn/playwright/error-element-not-found.mdx b/learn/playwright/error-element-not-found.mdx index 7956e891b..233526585 100644 --- a/learn/playwright/error-element-not-found.mdx +++ b/learn/playwright/error-element-not-found.mdx @@ -1,5 +1,5 @@ --- -title: How to Fix 'Element Not Found' Errors in Playwright +title: How to fix 'Element Not Found' errors in Playwright description: "Fix Playwright's element not found error, from wrong selectors and missing waits to a previous click that silently left you on the wrong page." date: 2021-08-05 author: Giovanni Rago diff --git a/learn/playwright/error-element-not-visible.mdx b/learn/playwright/error-element-not-visible.mdx index 239549e2a..77b4dd651 100644 --- a/learn/playwright/error-element-not-visible.mdx +++ b/learn/playwright/error-element-not-visible.mdx @@ -1,5 +1,5 @@ --- -title: How to Fix "Element Not Visible" Error in Playwright +title: How to fix "Element Not Visible" error in Playwright description: "Fix Playwright's element not visible error by checking whether an element is hidden or covered by another, using headful mode and screenshots to confirm state." date: 2021-08-05 author: Giovanni Rago diff --git a/learn/playwright/error-target-closed.mdx b/learn/playwright/error-target-closed.mdx index 73ba01b91..f023ac2a8 100644 --- a/learn/playwright/error-target-closed.mdx +++ b/learn/playwright/error-target-closed.mdx @@ -1,5 +1,5 @@ --- -title: How to Fix "Target Closed" Error in Playwright +title: How to fix "Target Closed" error in Playwright description: "Understand and fix Playwright's Target closed error, usually caused by a browser, context, or tab closing too early or a missing await on a promise." date: 2021-08-05 author: Giovanni Rago diff --git a/learn/playwright/error-wait-not-respected.mdx b/learn/playwright/error-wait-not-respected.mdx index 83ea3d006..9b4e4a802 100644 --- a/learn/playwright/error-wait-not-respected.mdx +++ b/learn/playwright/error-wait-not-respected.mdx @@ -1,5 +1,5 @@ --- -title: How to Fix "Wait Not Respected" Error in Playwright +title: How to fix "Wait Not Respected" error in Playwright description: "Fix Playwright waits that seem ignored, usually because the element already matches your state requirement, and confirm element state in the browser console." date: 2021-08-05 author: Giovanni Rago diff --git a/learn/playwright/file-download.mdx b/learn/playwright/file-download.mdx index f65988b05..a5046a590 100644 --- a/learn/playwright/file-download.mdx +++ b/learn/playwright/file-download.mdx @@ -1,5 +1,5 @@ --- -title: How to Download Files with Playwright +title: How to download files with Playwright description: "Download files with Playwright and verify them against a fixture, using either the download event or extracting the href and fetching it with an HTTP request." subTitle: Different ways of handling downloads date: 2020-09-09 diff --git a/learn/playwright/generating-pdfs.mdx b/learn/playwright/generating-pdfs.mdx index 50417981d..b0545c472 100644 --- a/learn/playwright/generating-pdfs.mdx +++ b/learn/playwright/generating-pdfs.mdx @@ -1,5 +1,5 @@ --- -title: How to Generate PDFs with Playwright +title: How to generate PDFs with Playwright description: "Generate PDFs from web pages with Playwright's page.pdf() command and customize the output for archiving, invoices, and other document automation." subTitle: Creating invoices, books and more from a web page date: 2020-11-19 diff --git a/learn/playwright/google-login-automation.mdx b/learn/playwright/google-login-automation.mdx index f77c70e29..cbd81f7a7 100644 --- a/learn/playwright/google-login-automation.mdx +++ b/learn/playwright/google-login-automation.mdx @@ -1,5 +1,5 @@ --- -title: How to Automate Google Login with Playwright +title: How to automate Google login with Playwright description: "Automate social login with a Google account in Playwright, injecting credentials through environment variables to sign in via an OAuth provider flow." subTitle: Dealing with Google authentication date: 2020-06-22 @@ -8,7 +8,7 @@ githubUser: tnolet tags: - login - e2e -sidebarTitle: Google Auth +sidebarTitle: Google auth weight: 9 learn_playwright: parent: "E2E examples" diff --git a/learn/playwright/handling-test-data.mdx b/learn/playwright/handling-test-data.mdx index 2e8a1fcc5..e5d3db2dc 100644 --- a/learn/playwright/handling-test-data.mdx +++ b/learn/playwright/handling-test-data.mdx @@ -1,5 +1,5 @@ --- -title: How to Handle Test Data with Playwright +title: How to handle test data with Playwright description: "Keep Playwright tests DRY by factoring out test data and fixtures into dedicated files, so complex end-to-end scenarios stay readable and maintainable." subTitle: Introduction to fixture handling date: 2020-07-16 diff --git a/learn/playwright/how-to-parameterize-playwright-projects.mdx b/learn/playwright/how-to-parameterize-playwright-projects.mdx index 90cfb90fa..29209d32d 100644 --- a/learn/playwright/how-to-parameterize-playwright-projects.mdx +++ b/learn/playwright/how-to-parameterize-playwright-projects.mdx @@ -9,7 +9,7 @@ tags: - e2e - assertions weight: 3 -sidebarTitle: Parameterizing Projects +sidebarTitle: Parameterizing projects learn_playwright: parent: "Best practices" canonical: 'https://www.checklyhq.com/docs/learn/playwright/how-to-parameterize-playwright-projects/' diff --git a/learn/playwright/how-to-set-up-locally.mdx b/learn/playwright/how-to-set-up-locally.mdx index 7695001e7..f5fae4081 100644 --- a/learn/playwright/how-to-set-up-locally.mdx +++ b/learn/playwright/how-to-set-up-locally.mdx @@ -1,5 +1,5 @@ --- -title: How to Set Up Playwright Locally +title: How to set up Playwright locally description: "Install Playwright locally with a single npm command and run your first browser automation script, using Node.js and the bundled browser." date: 2020-06-20 author: Giovanni Rago diff --git a/learn/playwright/iframe-interaction.mdx b/learn/playwright/iframe-interaction.mdx index f2c07b099..06b54d7b3 100644 --- a/learn/playwright/iframe-interaction.mdx +++ b/learn/playwright/iframe-interaction.mdx @@ -1,5 +1,5 @@ --- -title: How to Handle iFrames in Playwright +title: How to handle iFrames in Playwright description: "Access and interact with iframe content in Playwright using frameLocator to query elements inside a frame as if you were in the page context." subTitle: Accessing and interacting with iframes date: 2022-08-25 diff --git a/learn/playwright/intercept-requests.mdx b/learn/playwright/intercept-requests.mdx index 4f512c657..69bacdc9c 100644 --- a/learn/playwright/intercept-requests.mdx +++ b/learn/playwright/intercept-requests.mdx @@ -1,5 +1,5 @@ --- -title: How to Intercept Requests in Playwright +title: How to intercept requests in Playwright description: "Observe and manipulate network traffic in Playwright by intercepting requests and responses, logging them or modifying them during a test." subTitle: Monitoring and manipulating web traffic date: 2020-09-03 @@ -128,7 +128,7 @@ npx playwright test interception 1. Playwright gives us control over outgoing HTTP requests. 2. Playwright can easily stub HTTP responses. -## Avoid Network Interception in Synthetic Monitoring +## Avoid network interception in synthetic monitoring Network interception is valuable if your primary goal is to test a frontend application in isolation. However, if you want to test your application end-to-end or [use Playwright for synthetic production monitoring with Checkly](/detect/synthetic-monitoring/playwright-checks/overview) you should avoid network interception as much as possible. diff --git a/learn/playwright/login-automation.mdx b/learn/playwright/login-automation.mdx index 84a78b570..c28c6a3d1 100644 --- a/learn/playwright/login-automation.mdx +++ b/learn/playwright/login-automation.mdx @@ -1,5 +1,5 @@ --- -title: How to Automate Login with Playwright +title: How to automate login with Playwright description: "Automate a standard username-and-password login flow with Playwright and assert it succeeded by checking for an element only visible to logged-in users." subTitle: Automating one of the most common scenarios date: 2020-06-25 diff --git a/learn/playwright/microsoft-login-automation.mdx b/learn/playwright/microsoft-login-automation.mdx index c3c44c7c2..fc926dc7d 100644 --- a/learn/playwright/microsoft-login-automation.mdx +++ b/learn/playwright/microsoft-login-automation.mdx @@ -1,5 +1,5 @@ --- -title: How to Automate Microsoft Live Login with Playwright +title: How to automate Microsoft Live login with Playwright description: "Automate signing in to a Microsoft Live account with Playwright, injecting credentials through environment variables to reach the account page." subTitle: Dealing with Microsoft authentication date: 2020-06-22 @@ -8,7 +8,7 @@ githubUser: tnolet tags: - login - e2e -sidebarTitle: Microsoft Live Auth +sidebarTitle: Microsoft Live auth weight: 8 learn_playwright: parent: "E2E examples" diff --git a/learn/playwright/mock-api.mdx b/learn/playwright/mock-api.mdx index 6c85e29c6..25aeceb22 100644 --- a/learn/playwright/mock-api.mdx +++ b/learn/playwright/mock-api.mdx @@ -1,5 +1,5 @@ --- -title: Test Dynamic Content by Mocking API Responses +title: Test dynamic content by mocking API responses description: "Stabilize tests for dynamic pages by mocking API responses in Playwright, fixing unpredictable data like stock counts while leaving the rest of the page live." subTitle: Manipulating and mocking API responses date: 2025-03-12 @@ -10,7 +10,7 @@ githubUser: tags: - network weight: 125 -sidebarTitle: Mocking API Responses +sidebarTitle: Mocking API responses learn_playwright: parent: "Basics" canonical: 'https://www.checklyhq.com/docs/learn/playwright/mock-api/' @@ -65,7 +65,7 @@ Here are some of the paths we could take with dynamic information like a book’ - Not everything is particularly easy to test with regex, for example the `rating` api response here comes back as Unicode stars like “★★★★☆,” which isn’t as straightforward to test with regex as a digit. 4. Modify the API response - Finally the option that gives us high consistency in what we’re testing and what we expect in response. By modifying the API response we can set only the key value pairs that concern us to fixed values, letting the others remain dynamic. We test how the page renders with fixed data, *and* we’re still testing that the API is available. -## The Solution: Modify an API response with `await *page*.route()` +## The solution: Modify an API response with `await *page*.route()` Let’s start by looking at the API response in full, from the network tab of either our browser or the Playwright UI mode. The body looks as follows @@ -111,7 +111,7 @@ Note that, if you’re using the Playwright UI, this mocking behavior will show The ‘fulfilled’ listing will show the patched version of your response that went to the page. -## Going Further: Mocking Whole APIs +## Going further: Mocking whole APIs If we’re able to intercept a request and change a single key/value pair, can we replace an entire payload from an API request? Sure, in fact we don’t need to wait for the real API to respond. the new version would look something like this: @@ -145,7 +145,7 @@ Now we no longer wait for this API response to come back and supply the whole re The distinct disadvantage is that we’re no longer checking that this API is available. If we’re [testing against production](https://www.checklyhq.com/guides/playwright-testing-to-monitoring/) it would be a good idea to still check that this API is returning data. -## Going Further: Replacing API responses to stress test our page +## Going further: Replacing API responses to stress test our page The last use case for API mocking and response editing is simulating an unusual circumstance on a live page. For example, on our page we expect that a book with zero remaining stock should show up as sold out. @@ -190,13 +190,13 @@ As we find ourselves testing correct rendering of a page under unusual condition To go further, see our full documentation on [visual regression checks in Playwright and Checkly](/detect/synthetic-monitoring/browser-checks/visual-regressions#visual-regression--snapshot-testing). -## Results and Conclusions: Playwright Mocking and Testing in Production +## Results and conclusions: Playwright mocking and testing in production With Playwright mocking you can remain tightly in control of API responses your page is using to render pages for users. This tool can help you in testing against production by ensuring that even with your production pages and data sources, your testing always sees consistent results. The result is more in-depth testing with higher reliability and fewer false alarms. And when a feature isn’t working correctly for users, you can find out before they complain. With Playwright's powerful API mocking capabilities, you gain precise control over the responses your web pages use to render content for users. This functionality is particularly valuable when testing against production environments, as it ensures consistent results even when dealing with dynamic data sources. By leveraging tools like `page.route()`, you can simulate various scenarios—such as out-of-stock items, unusual data inputs, or edge cases—without needing to alter your production database or backend systems. -### Key Takeaways: +### Key takeaways: 1. **Consistency in Testing**: By mocking API responses, you can create stable and reliable tests that are not affected by fluctuating data, such as stock numbers or ratings. This reduces false positives and ensures your tests are always accurate. 2. **Flexibility**: Playwright allows you to modify specific parts of an API response or replace the entire payload, giving you the flexibility to test a wide range of scenarios, from stress testing to edge cases. @@ -204,14 +204,14 @@ With Playwright's powerful API mocking capabilities, you gain precise control ov 4. **Improved Debugging**: By controlling API responses, you can isolate and test specific UI behaviors, making it easier to identify and fix issues in your application. 5. **Visual Regression Testing**: Mocking dynamic content ensures that visual regression tests are consistent, allowing you to create reliable "golden files" for comparison. -### When to Use API Mocking: +### When to use API mocking: - **Testing Dynamic Content**: Use mocking to stabilize tests for elements that frequently change, such as stock levels, prices, or ratings. - **Stress Testing**: Simulate unusual or extreme conditions (e.g., zero stock, large numbers, or long text) to ensure your UI handles them gracefully. - **Edge Case Testing**: Test how your application behaves under rare or unexpected conditions without needing to replicate those conditions in your production environment. - **Visual Regression Testing**: Ensure consistent screenshots for visual comparisons by fixing dynamic content in place. -### Limitations and Considerations: +### Limitations and considerations: - **Real API Availability**: While mocking is powerful, it’s important to occasionally test against real API responses to ensure your production APIs are functioning correctly. - **Maintenance**: Mocked responses need to be updated if the structure of your API changes, so keep your mocks in sync with your API contracts. diff --git a/learn/playwright/multitab-flows.mdx b/learn/playwright/multitab-flows.mdx index d2dd8c436..b5b5a66f7 100644 --- a/learn/playwright/multitab-flows.mdx +++ b/learn/playwright/multitab-flows.mdx @@ -1,5 +1,5 @@ --- -title: Handling Multiple Tabs with Playwright +title: Handling multiple tabs with Playwright description: "Control multiple browser tabs in Playwright, opening new pages in a context and interacting with each independently within a single test." subTitle: Controlling multiple tabs date: 2021-08-29 diff --git a/learn/playwright/navigation.mdx b/learn/playwright/navigation.mdx index 3c21feff8..20ce9f051 100644 --- a/learn/playwright/navigation.mdx +++ b/learn/playwright/navigation.mdx @@ -1,5 +1,5 @@ --- -title: How to Use Playwright to Navigate and Interact with Web Pages +title: How to use Playwright to navigate and interact with web pages displayTitle: How to Use Playwright for Navigation and Interaction metatags: title: Navigation & Waiting Strategies in Playwright diff --git a/learn/playwright/overview.mdx b/learn/playwright/overview.mdx index 5607b1914..1ab6a469f 100644 --- a/learn/playwright/overview.mdx +++ b/learn/playwright/overview.mdx @@ -1,5 +1,5 @@ --- -title: Learn How to Test, Monitor, and Automate with Playwright +title: Learn how to test, monitor, and automate with Playwright displayTitle: Learn How to Test, Monitor, and Automate with Playwright description: Learn more about Playwright automation & monitoring with Checkly. Explore how to automate your web with a reliable, programmable monitoring workflow. metatags: @@ -14,7 +14,7 @@ import PlaywrightCheckSuiteTryOut from "/snippets/playwright-check-suite-tryout. Playwright serves as the foundation for Checkly's synthetic [*Monitoring as Code*](/concepts/monitoring-as-code). To get the most from Checkly, we put together a series of guides and examples to help you get started with Playwright. -## Getting Started +## Getting started -## Check our Playwright Tips YouTube channel +## Check our Playwright tips YouTube channel [The Checkly YouTube channel](https://www.youtube.com/@ChecklyHQ) includes over a hundred videos covering synthetic monitoring, Monitoring as Code and Playwright automation. Check out our [Playwright Tips playlist](https://www.youtube.com/playlist?list=PLMZDRUOi3a8NtMq3PUS5iJc2pee38rurc) for bite-sized videos on Playwright best practices, tips and tricks. -## Diving Deeper +## Diving deeper Playwright is extremely powerful and serves a wide range of use cases. We have collected in-depth articles for important scenarios and challenging automation flows. @@ -69,7 +69,7 @@ Playwright is extremely powerful and serves a wide range of use cases. We have c -## Popular Posts +## Popular posts Learn how to control HTTP requests and responses. Working with selectors is key for writing high quality scripts. diff --git a/learn/playwright/performance.mdx b/learn/playwright/performance.mdx index aae5a2df8..73c92d5bd 100644 --- a/learn/playwright/performance.mdx +++ b/learn/playwright/performance.mdx @@ -1,5 +1,5 @@ --- -title: Measuring Page Performance Using Playwright - Best Practices +title: Measuring page performance using Playwright - Best practices description: "Measure web page performance with Playwright, understand why speed affects users and revenue, and track browser performance metrics over time." subTitle: Explaining why it matters and how to assess it date: 2020-09-30 @@ -62,7 +62,7 @@ Not all of Google's Web Vitals are suitable for synthetic monitoring and perform **Interaction to Next Paint** relies on user interactions, and it's best measured using real user monitoring. Use **Total Blocking Time** as an interactivity metric in a lab setting instead. -## Web Performance evaluation with headless tools +## Web performance evaluation with headless tools As much as we should be striving to build performant applications, we should commit to monitoring and testing performance to enable continuous feedback and rapid intervention in case of degradation. Playwright provides a great toolkit to power synthetic monitoring and performance testing. @@ -70,7 +70,7 @@ As much as we should be striving to build performant applications, we should com 2. Whenever testing against Chromium, access to the Chrome DevTools Protocol for traffic inspection, network emulation and more. 3. Easy interoperability with performance libraries from the Node.js ecosystem. -### Web Performance APIs +### Web performance APIs Modern browsers support many APIs to gather web performance metrics and web vitals. diff --git a/learn/playwright/scraping-behind-login.mdx b/learn/playwright/scraping-behind-login.mdx index 7d1e17524..1efd87ef4 100644 --- a/learn/playwright/scraping-behind-login.mdx +++ b/learn/playwright/scraping-behind-login.mdx @@ -1,5 +1,5 @@ --- -title: How to Scrape Data Behind a Login with Playwright +title: How to scrape data behind a login with Playwright description: "Scrape data that sits behind a login wall with Playwright by combining UI automation and scraping, illustrated by totalling Amazon order history." subTitle: An example in accessing account-specific information date: 2020-12-23 diff --git a/learn/playwright/script-recorders.mdx b/learn/playwright/script-recorders.mdx index 4b48de6af..9f961b1ad 100644 --- a/learn/playwright/script-recorders.mdx +++ b/learn/playwright/script-recorders.mdx @@ -1,5 +1,5 @@ --- -title: Using Script Recorders with Playwright +title: Using script recorders with Playwright description: "Speed up script creation with Playwright recorders like codegen and the VS Code extension, then refine the generated selectors and waits for reliability." subTitle: Generating scripts for beginners and pros date: 2020-09-16 diff --git a/learn/playwright/selectors.mdx b/learn/playwright/selectors.mdx index 2444c5653..80995146c 100644 --- a/learn/playwright/selectors.mdx +++ b/learn/playwright/selectors.mdx @@ -1,5 +1,5 @@ --- -title: How to Work with Selectors in Playwright +title: How to work with selectors in Playwright displayTitle: How to Work with Selectors in Playwright description: Learn to write solid scripts using Playwright. Discover how to choose stable selectors and start enhancing your skills today. @@ -25,7 +25,7 @@ import { YoutubeEmbed } from "/snippets/youtube-embed.jsx" When testing and monitoring websites end to end with Playwright, choosing the right locators is crucial. Proper locators help create tests that are less flaky and more reliable. Let's explore user-first locators and how to filter locators for more robust tests. -## Example Scenario +## Example scenario Consider a simple web page with a headline, a button, and a status update box. Clicking the button updates the status and throws confetti. Here's how we can test this. @@ -45,10 +45,10 @@ If a frontend engineer changes the class for style reasons to read `button-hero- If our button text is coming from a CMS, and it breaks, the button text could change to "HEROBUTTON_TXT" and our test would still pass, despite the UI being broken for the user, a false negative. Due to the reasons above, the Playwright project encourages you to not use CSS locators, and it's a good idea to follow the standards set down in the project! -### Instead of CSS selectors, try User-First Locators +### Instead of CSS selectors, try user-first locators Playwright offers a number of locators that are based on page role, a more functional view of the page than finding by CSS or HTML. Use [the recommended built-in locators](https://playwright.dev/docs/locators#quick-guide) like `getByRole`, `getByText`, and `getByLabel`, which will all work the same in the test that they will for the user, even if the user is using an unusual browser build, mobile device, or even a screen reader! -## User-First Locators in Action +## User-first locators in action Let's replace `page.locator` with `getByRole` to locate the button by its role and accessible name: ```ts @@ -73,7 +73,7 @@ After all, if nothing has unique labels it means that screen readers and keyboar In the short term, take a look at all of Playwright's locators, as there are definitely techniques that will find any element on your page, but I encourage you to use this as a jumping off point for tech debt conversations in the future. -### Handling Multiple Matching Elements +### Handling multiple matching elements If a locator matches multiple elements, Playwright's strict mode will fail. For example, using `getByRole('button')` might match several buttons. You'll get an error that reads something like: ``` @@ -85,7 +85,7 @@ Error: locator.click: Error: strict mode violation: Note that in strict mode this test will fail even if the first result, or all the results, passes the rest of the test. Resolve this by specifying the position or filtering elements. -#### Position-Based Selection +#### Position-based selection When we first run into this error, the easiest solution is just to specify a position in a list. The simplest being to take the first result: ```ts @@ -102,7 +102,7 @@ await page.getByRole('button').nth(3).click() The .nth() function is zero-indexed, so .nth(3) will select the fourth item in the results. Positional selectors work, but they can be brittle, if we have dynamic page content, selecting anything but the first result may present a false positive. To be really sure that we're pointing to the correct element in a dynamic list, do a bit of element filtering. -#### Element Filtering in Playwright +#### Element filtering in Playwright If we imagine an e-store interface, with a number of results only some of which are available, we can see that a position selector isn't going to test reliably. ![too many matches](/images/samples/images/user-first4.png) @@ -119,7 +119,7 @@ await button.click() This test would now fail about when the user would expect it to: when they see a list of items, all marked as sold out. -## Best Practices for Page Locators +## Best practices for page locators There is no one-size-fits-all solution for locators. Here are some tips: diff --git a/learn/playwright/steps-decorators.mdx b/learn/playwright/steps-decorators.mdx index dce16c9af..f08f4e87c 100644 --- a/learn/playwright/steps-decorators.mdx +++ b/learn/playwright/steps-decorators.mdx @@ -1,5 +1,5 @@ --- -title: Self-documenting tests - add automatic Playwright steps with TypeScript Decorators +title: Self-documenting tests - add automatic Playwright steps with TypeScript decorators description: "Structure complex Playwright tests with a single @step TypeScript decorator, replacing repetitive test.step calls to make reports easier to scan." subTitle: Understand tests better with steps date: 2024-11-15 @@ -9,7 +9,7 @@ tags: - typescript weight: 7 -sidebarTitle: Automatic Steps +sidebarTitle: Automatic steps learn_playwright: parent: "Best practices" canonical: 'https://www.checklyhq.com/docs/learn/playwright/steps-decorators/' @@ -156,7 +156,7 @@ In practice this means, that you can use modern JavaScript features in TypeScrip One of these modern JavaScript features is decorators. JavaScript Decorators aren't supported anywhere but work if you use TypeScript. -### JavaScript Decorators — a proposal that's been in the making forever. +### JavaScript decorators — a proposal that's been in the making forever. [The JavaScript decorator spec proposal](https://github.com/tc39/proposal-decorators) saw the light of day eight years ago and reached ECMAScript proposal stage three. Proposals on stage three are considered "ready to implement". diff --git a/learn/playwright/taking-screenshots.mdx b/learn/playwright/taking-screenshots.mdx index 0492174a8..5cf72ab6d 100644 --- a/learn/playwright/taking-screenshots.mdx +++ b/learn/playwright/taking-screenshots.mdx @@ -1,5 +1,5 @@ --- -title: Playwright Screenshots - How to Take and Automate Screenshots +title: Playwright screenshots - How to take and automate screenshots description: "Capture screenshots with Playwright's page.screenshot command, take full-page images, and automate visual comparisons to catch regressions." subTitle: Leveraging images for troubleshooting and more date: 2020-06-23 diff --git a/learn/playwright/test-fixtures.mdx b/learn/playwright/test-fixtures.mdx index d100bd8f3..37df435e8 100644 --- a/learn/playwright/test-fixtures.mdx +++ b/learn/playwright/test-fixtures.mdx @@ -11,7 +11,7 @@ tags: - assertions weight: 7 -sidebarTitle: Test Fixtures +sidebarTitle: Test fixtures learn_playwright: parent: "Best practices" canonical: 'https://www.checklyhq.com/docs/learn/playwright/test-fixtures/' @@ -25,7 +25,7 @@ import { YoutubeEmbed } from "/snippets/youtube-embed.jsx" Playwright's test fixtures are a powerful feature for sharing setup and logic across tests, promoting code reuse and maintainability. With custom fixtures, you can share code across multiple tests, resulting in a test base that is easier to expand and easier to maintain. -## Understanding Playwright Test Fixtures +## Understanding Playwright Test fixtures At their core, fixtures in Playwright are predefined components like `page`, `context`, `browser`, and `browserName` that you can use across different test cases. They encapsulate functionality into modular blocks, simplifying test code. @@ -51,11 +51,11 @@ test('test', async ({ page }) => { This is a fine practice for a single test, but if we have dozens that all require login as a first step, we'll find ourself copying and pasting this code several times. This means a lot of copied code, such that if we ever tweak the login process, we'll have to update this copied code in dozens of places, not good! -## Playwright and Fixtures +## Playwright and fixtures Playwright and its test runner Playwright Test, were designed with a broader testing scope and includes first-class support for fixtures. This design choice streamlines the setup and teardown process, making tests cleaner and reducing redundancy. -### Built-in Support +### Built-in support Playwright's test runner provides a rich set of predefined fixtures, such as `browser`, `context`, `page`, and `request`, and allows for easy customization and extension of these fixtures. This built-in support enables more structured and maintainable tests, with less manual setup required. @@ -73,13 +73,13 @@ test('My authenticated test', async ({ page }) => { The ability to extend and customize fixtures in Playwright not only reduces boilerplate but also enhances test isolation and reusability across your test suite. -## Create a Custom Test Fixture in Playwright Test +## Create a custom test fixture in Playwright Test Imagine testing a web application where multiple tests require logging in. Repeating login logic in every test is inefficient and violates the DRY (Don't Repeat Yourself) principle. Let's implement __a fixture to reuse and share code across Playwright test cases__. -### Step 1: Extend the Test Object +### Step 1: Extend the test object First, create a new test file or use an existing one. Here, we're testing a web application with Playwright, accessing environment variables, and performing UI interactions. @@ -111,7 +111,7 @@ const test = baseTest.extend({ By using custom fixtures, test cases can reuse code defined in the `test.extend` call. In this case, all tests using the extended `test` method can rely on the `webApp` fixture. -### Step 2: Use the Custom Fixture +### Step 2: Use the custom fixture With the `webApp` fixture defined, you can use it in your tests. The fixture code will only run when a test "requests" to use it. For example, the custom `webApp` fixture will only be executed if a test case uses it. @@ -125,11 +125,11 @@ test('My webApp test', async ({ webApp }) => { The `webApp` fixture encapsulates the login logic, making it accessible to any test that requires it. -### Step 3: Debugging and Validation +### Step 3: Debugging and validation Debugging is crucial to ensure your fixture works as expected. Playwright's inspector is invaluable here, allowing you to step through test execution and verify the setup and teardown processes. -### Step 4: Sharing Across Tests +### Step 4: Sharing across tests To share your custom fixture across different test files, encapsulate it in a separate module: @@ -151,13 +151,13 @@ This approach keeps your tests clean and focused, with shared logic abstracted i -## Replace `beforeEach` / `afterEach` Hooks with Automatic Fixtures +## Replace `beforeEach` / `afterEach` hooks with automatic fixtures As explained in the previous section, fixtures enable the sharing and distributing of code across Playwright tests. By default, fixture code is only executed when a test case accesses a fixture. But there are scenarios in which you always want to run your fixture code, like global `beforeEach` and `afterEach` hooks. Let's implement __an automatic fixture to log the current time before and after every test case__. -### Define an Automatic Fixture +### Define an automatic fixture If you want to run code before and after each test case, you can reach for the commonly known `beforeEach` and `afterEach` hooks. @@ -231,7 +231,7 @@ import { expect } from '@playwright/test'; Custom test fixtures in Playwright streamline test setup and teardown, fostering code reuse and reducing boilerplate. Encapsulating common functionality, such as user logins or global setups, into fixtures ensures your tests are cleaner, more maintainable, and easier to read. -### Playwright Fixtures Explained on YouTube +### Playwright fixtures explained on YouTube To discover more practical fixture examples, check out our [YouTube playlist](https://www.youtube.com/watch?v=hegZS46J0rA&list=PLMZDRUOi3a8N067UNvkxXEThKlTII_OJ-), which covers fixtures in even more depth. diff --git a/learn/playwright/testing-apis.mdx b/learn/playwright/testing-apis.mdx index 4c1e5ac8d..40b3eb95e 100644 --- a/learn/playwright/testing-apis.mdx +++ b/learn/playwright/testing-apis.mdx @@ -33,7 +33,7 @@ In this API, you might request a list of countries along with their codes and la This is a GraphQL api, which is supported in Playwright. GraphQL works by sending a POST request with a query in the request body. Let’s see how to write a Playwright test for this API. -## The Test Case +## The test case To get started, let’s look at a basic test using Playwright. Below is an api.ts file that defines a test case doing little more than ensuring that our GraphQL API is responding with expected data. ```ts api.spec.ts @@ -142,7 +142,7 @@ test('the GraphQL API works for one country', async ({ request }) => { This test now validates a filtered response, all within the same Playwright test case. -## Continuous Monitoring with Playwright and Checkly +## Continuous monitoring with Playwright and Checkly By running multiple small API requests from within Playwright, you can verify the underlying APIs you need for your pages. If you want to monitor all your API endpoints continually, check out Checkly’s API monitors. Checkly API monitors let you run on a schedule with dynamic [notification settings](/communicate/alerts/configuration) and [retries](/communicate/alerts/retries), run from multiple geographies, and even [run setup and teardown scripts](/detect/synthetic-monitoring/api-checks/setup-and-teardown) to add logic for your test, and clean up after your test. diff --git a/learn/playwright/testing-coupons.mdx b/learn/playwright/testing-coupons.mdx index 7681dd383..3b6cfe5d9 100644 --- a/learn/playwright/testing-coupons.mdx +++ b/learn/playwright/testing-coupons.mdx @@ -1,5 +1,5 @@ --- -title: How to Test Coupons and Discounts with Playwright +title: How to test coupons and discounts with Playwright description: "Verify coupon and discount codes with Playwright by adding items to a cart and asserting the total price changes by the expected amount after applying the code." subTitle: Applying and verifying a discount date: 2020-07-13 diff --git a/learn/playwright/testing-file-uploads.mdx b/learn/playwright/testing-file-uploads.mdx index 2c7042401..9ce9c83b3 100644 --- a/learn/playwright/testing-file-uploads.mdx +++ b/learn/playwright/testing-file-uploads.mdx @@ -1,5 +1,5 @@ --- -title: How to Test File Uploads with Playwright +title: How to test file uploads with Playwright description: "Test file upload functionality with Playwright by logging in and attaching a file, using a profile-image upload as a worked example." subTitle: Modifying account settings with a file upload date: 2020-07-22 diff --git a/learn/playwright/testing-in-parallel.mdx b/learn/playwright/testing-in-parallel.mdx index 6934d0ce9..d84d014e8 100644 --- a/learn/playwright/testing-in-parallel.mdx +++ b/learn/playwright/testing-in-parallel.mdx @@ -25,7 +25,7 @@ Playwright offers robust capabilities for automating browser tests. However, a c This post describes strategies for running Playwright tests in parallel, sequence, or both while optimizing your testing workflow for efficiency and reliability. -## Understanding Test Types: stateful vs stateless +## Understanding test types: stateful vs stateless Before getting into the technicalities of test execution, you must categorize your tests into two main types: stateless and stateful. @@ -36,7 +36,7 @@ Before getting into the technicalities of test execution, you must categorize yo Tests that start and rely on a state created by a previous test are typically considered antipatterns. Tests should create and clean up their own state to avoid cluttering test environments and enable parallelization. -## Playwright's Default Test Execution +## Playwright's default test execution Before you start wondering how to parallelize all your Playwright tests, be aware that you probably run some of your tests in parallel already. @@ -54,7 +54,7 @@ The execution model can be changed in multiple ways if you want to parallelize m Let's look at common execution scenarios and their required configuration. -## Running Tests Sequentially +## Running tests sequentially While parallel execution is efficient, specific scenarios require running tests sequentially. This is especially true for destructive and stateful tests, where ensuring a predictable and unaltered environment state is crucial for test accuracy. @@ -93,7 +93,7 @@ npx playwright test --workers=1 --project=sequential You can run a subset of test files, grep for specific test tags, or define a separate project to run tests sequentially. None of these approaches is better; you must decide what fits your project best. -## Running Tests in Parallel +## Running tests in parallel Thanks to Playwright's automatic encapsulation and easy-to-use worker functionality, the test runner naturally excels at executing tests in parallel, significantly reducing the time it takes to execute your entire test suite. @@ -174,11 +174,11 @@ test('One', async () => { /* ... */ }); test('Two', async () => { /* ... */ }); ``` -## Leveraging Playwright's Flexibility +## Leveraging Playwright's flexibility Playwright's design accommodates various testing strategies, allowing developers to tailor test execution to their project's needs. Whether running tests in parallel to save time or sequentially to ensure environment stability, Playwright provides the tools necessary to configure your testing environment effectively. -### Tips for Organizing Tests +### Tips for organizing tests - Use directories, tags or projects to separate stateful and stateless tests and apply appropriate parallel or sequential execution modes. - Name your test files strategically if relying on alphabetical execution order for sequencing. diff --git a/learn/playwright/testing-pyramid.mdx b/learn/playwright/testing-pyramid.mdx index cf3ccff15..f8fd3f40b 100644 --- a/learn/playwright/testing-pyramid.mdx +++ b/learn/playwright/testing-pyramid.mdx @@ -1,5 +1,5 @@ --- -title: The Layers of the Testing Pyramid +title: The layers of the testing pyramid description: This article gives a tour of the testing pyramid’s layers with examples, and shows you how each part is required for a complete picture of system performance. date: 2025-04-01 @@ -26,7 +26,7 @@ When you begin your journey in QA, SRE, Development, or Operations, you’ll ask We know our app is working by testing, but this begs the question: who should test what, when? Let’s take the tiniest possible failure: trailing whitespace in user data. Should the React frontend refuse to submit form fields with extra whitespace, should the application automatically remove whitespace before sending database requests, or should the DB controller automatically remove whitespace? The question: “in what layer should these checks happen?” brings us to the testing pyramid. -## The Testing Pyramid in Full +## The testing pyramid in full Originally conceived by Mike Cohn, and then popularized by Martin Fowler, the testing pyramid shows categories of tests, with the slowest on top and the fastest on the bottom. @@ -39,7 +39,7 @@ The pyramid shape refers to the ideal distribution of tests: you should have doz Next let’s briefly describe the layers, along with how they work in a modern cloud native architecture. -## Unit Tests - with examples +## Unit tests - with examples A unit test is a highly isolated test that only works with a tiny chunk of code, possibly the code in a single file, or even a single function. A unit test is by its nature extremely high performance, and can run as frequently as the developer saves her work (or even with every entered newline). @@ -184,7 +184,7 @@ await page.locator('#item-to-be-dragged').dragTo(page.locator('#item-to-drop-at' At base, the advantage of end-to-end testing is that it answers the real question of testing: ‘will this work for users or not?’ the other phases of testing answer questions more akin to: ‘does this code function without throwing errors?’ or ‘is this service fulfilling its contract to other services?’ Those are important questions for earlier phases of the SDLC. But once our tests are going into the hands of users, we must simulate that real user behavior and record if everything works. -### From E2E Testing to E2E Monitoring +### From E2E testing to E2E monitoring If we agree on the importance of end-to-end testing, it begs the question if testing should stop after deploy time. Thousands of unforseen interactions can break a production service even after the code is tested post-deployment, and our users are certainly using the service all the time. Shouldn’t our testing also continue after the code is out? For end-to-end testing on a cadence, there’s Checkly, which uses the power of Playwright to test your sites, services, and APIs around the clock. [Get started today](https://www.checklyhq.com/docs/)! @@ -192,7 +192,7 @@ If we agree on the importance of end-to-end testing, it begs the question if tes While it sadly causes many arguments about which tests belong where or which layer is most important, the testing pyramid is meant to acknowledge that each test type has a role to play, and the differences in performance is natural. -## Conclusions: Every Layer of Testing Matters +## Conclusions: Every layer of testing matters We care about testing because ultimately there’s one layer of testing that no one wants to use: our users. If there’s a bug, they’ll find it, if there’s holes in a data flow, their data will fall into it. If there’s an edge case our users will find it. And every time a user is the first one to detect a problem, it hurts their trust in our service. @@ -205,7 +205,7 @@ While the boundaries between these layers can sometimes blur, their collective p Ultimately, the goal is not to rigidly categorize tests but to ensure comprehensive validation at every stage. Whether you're writing unit tests for a utility function, mocking service interactions in integration tests, or automating user journeys with Playwright, each layer contributes to a more robust, resilient application. The testing pyramid isn’t just a model—it’s a reminder that quality is built step by step, from the smallest unit to the full user experience. -## Dive Deeper into the Testing Pyramid with Real World Applications +## Dive deeper into the testing pyramid with real world applications In a recent Webinar, the Checkly team got to talk about how the Testing Pyramid affects testing strategies for real world applications like React apps. Watch the whole session here: diff --git a/learn/playwright/user-signup-automation.mdx b/learn/playwright/user-signup-automation.mdx index 0fda0d98c..a6d37341a 100644 --- a/learn/playwright/user-signup-automation.mdx +++ b/learn/playwright/user-signup-automation.mdx @@ -1,5 +1,5 @@ --- -title: Automating User Signup with Playwright +title: Automating user signup with Playwright description: "Automate user signup flows with Playwright by filling registration forms, submitting them, and confirming the account was created through a UI change." subTitle: Handling signups flows date: 2020-06-30 diff --git a/learn/playwright/web-scraping.mdx b/learn/playwright/web-scraping.mdx index 324d2d8d7..f7c9f6f47 100644 --- a/learn/playwright/web-scraping.mdx +++ b/learn/playwright/web-scraping.mdx @@ -1,5 +1,5 @@ --- -title: Playwright Web Scraping - How to Extract Data from Websites +title: Playwright web scraping - How to extract data from websites description: "Extract data from web pages with Playwright, reading element attributes and properties for testing assertions or general-purpose scraping." subTitle: Extracting valuable information through automation date: 2020-08-26 diff --git a/learn/playwright/what-is-playwright.mdx b/learn/playwright/what-is-playwright.mdx index 9ea879eae..1861ec16d 100644 --- a/learn/playwright/what-is-playwright.mdx +++ b/learn/playwright/what-is-playwright.mdx @@ -1,5 +1,5 @@ --- -title: Beginner’s Guide to Playwright Automation +title: Beginner’s guide to Playwright automation description: Learn how Playwright, a browser automation tool, simplifies testing across Chrome, Firefox, and WebKit. Start building more reliable web applications today. date: 2020-06-29 @@ -36,7 +36,7 @@ End-to-end tests have the reputation of being flaky and slow, while also requiri Playwright overcomes flaky and slow tests by communicating with rendering engines via the WebSocket protocol, instead of through multiple HTTP requests, as is done with other web automation testing tools like Selenium. Playwright communicates all requests through a single web socket connection that remains active until all tests have been completed. This reduces points of test failure during test execution, providing a stable and fast solution. -## Playwright Features +## Playwright features While taking a simplified approach to its design, Playwright offers many features that make it unique, but competitive with several other leading test automation tools, like Cypress and Puppeteer. While we’ve discussed some of the key features in more detail above, some additional noteworthy features include: @@ -61,7 +61,7 @@ While taking a simplified approach to its design, Playwright offers many feature 4. **Scraping web sites for data:** extracting data from websites for later retrieval or analysis. 5. **Automating interaction of web pages:** speed up and scale any sort of sequence of actions we would like to perform on a website automatically. -## Growth and Adoption +## Growth and adoption Since its release in January 2020 by Microsoft, Playwright has experienced a surge in usage and popularity. As of January 2026, its GitHub repository has received 80k stars and 5k forks, and is currently averaging more than 32 million NPM downloads per week. Playwright is used by enterprise and open-source development projects alike, including Adobe Spectrum, Visual Studio Code, and React Navigation. diff --git a/learn/playwright/writing-tests.mdx b/learn/playwright/writing-tests.mdx index 785c3678f..c6c2448a5 100644 --- a/learn/playwright/writing-tests.mdx +++ b/learn/playwright/writing-tests.mdx @@ -1,5 +1,5 @@ --- -title: Best Practices for Writing Tests in Playwright +title: Best practices for writing tests in Playwright description: "Write valuable, maintainable Playwright tests by keeping scripts short, simple, and readable, so they keep telling the truth about your system as it evolves." subTitle: Principles for sustainable automated testing date: 2020-07-16 diff --git a/platform/allowlisting-traffic.mdx b/platform/allowlisting-traffic.mdx index 94da9c2fe..1fcd433d0 100644 --- a/platform/allowlisting-traffic.mdx +++ b/platform/allowlisting-traffic.mdx @@ -1,7 +1,7 @@ --- -title: 'Allowlisting Traffic' +title: 'Allowlisting traffic' description: 'Allowlisting traffic to Checkly' -sidebarTitle: 'Allowlisting Traffic' +sidebarTitle: 'Allowlisting traffic' canonical: 'https://www.checklyhq.com/docs/platform/allowlisting-traffic/' --- @@ -188,7 +188,7 @@ await page.goto('https://app.checklyhq.com/login?utm_source=monitoring') For detailed instructions, see [the Google Analytics docs on custom filters](https://support.google.com/analytics/answer/1033162#CustomFilters). Note that this will take some hours for this to take effect. -## CloudFlare Verified Bot +## CloudFlare verified bot Checkly is also registered with CloudFlare as a [verified bot](https://developers.cloudflare.com/bots/concepts/bot/verified-bots/). If you are using CloudFlare's Web Application Firewall (WAF) to protect your site, you can also allow traffic from Checkly by adding a [custom WAF rule](https://developers.cloudflare.com/waf/custom-rules/) to enable traffic from verified bots. diff --git a/platform/data-storage.mdx b/platform/data-storage.mdx index b8bf2566e..257754d2e 100644 --- a/platform/data-storage.mdx +++ b/platform/data-storage.mdx @@ -1,7 +1,7 @@ --- title: 'How we store data' description: 'Learn about how Checkly stores check run data' -sidebarTitle: 'Data Storage' +sidebarTitle: 'Data storage' canonical: 'https://www.checklyhq.com/docs/platform/data-storage/' --- @@ -13,7 +13,7 @@ Every check we run generates a certain amount of data. We call these the "result - Screenshot files - Run logs with debug or `console.log` statements. -## Data Retention +## Data retention Depending on your plan we keep the results data according to the following retention policy: diff --git a/platform/dynamic-secret-scrubbing.mdx b/platform/dynamic-secret-scrubbing.mdx index b022b8ffa..dcd4ec222 100644 --- a/platform/dynamic-secret-scrubbing.mdx +++ b/platform/dynamic-secret-scrubbing.mdx @@ -1,6 +1,6 @@ --- -title: 'Dynamic Secret Scrubbing' -sidebarTitle: 'Secret Scrubbing' +title: 'Dynamic secret scrubbing' +sidebarTitle: 'Secret scrubbing' description: 'Scrub sensitive data from check results' canonical: 'https://www.checklyhq.com/docs/platform/dynamic-secret-scrubbing/' --- diff --git a/platform/groups.mdx b/platform/groups.mdx index b6b9d5082..860ef2121 100644 --- a/platform/groups.mdx +++ b/platform/groups.mdx @@ -24,7 +24,7 @@ By default, newly created check groups behave like folders, with no group-level Groups let you apply shared configuration to standardize how checks behave. Depending on the setting, group-level configuration either overrides check-level settings or is merged with them. -### Check Membership +### Check membership **Moving a check into a group:** If the group has group-level configuration defined, adding a check may change how it runs. Settings like API defaults, locations & scheduling, or retries & alerting can override the check's configuration. **Removing check from group:** Any group-level configuration will no longer apply, and the check will use its own configuration going forward. @@ -66,7 +66,7 @@ An example: 2. At the API check level, you define the same header `X-Custom` just with the value `abc` 3. Checkly will call your API with the `X-Custom: abc` header -#### Basic Auth +#### Basic auth Use the basic auth username and password to inject it into each API check in the group. @@ -114,17 +114,17 @@ Or, in other words: **check** variables trump **group** variables trump **global You can make use of this by providing a default value for a specific variable at the global or group level, but allow that variable to be overridden at the group level or check level. -### Scheduling & Locations +### Scheduling & locations - **Locations:** Override location settings for all checks in the group with selected public or private locations - **Scheduling strategy:** Override scheduling strategy (parallel, round-robin) for all checks in the group - **Frequency:** Each check runs at its own frequency. When you use the CLI, the `frequency` property of a group sets a default for the checks you define in that group. -### Retries & Alerting +### Retries & alerting - **Retries:** Configure retry strategy for failed checks (fixed, single, linear, exponential) - **Alert settings:** Set up alert channels for the group - email, SMS, Slack, webhooks, etc. When you enable the group override, these settings replace the alert settings of every check in the group. -### Testing & Runtimes +### Testing & runtimes - **Testing:** Run checks in this group as E2E tests locally or from CI/CD pipelines - **Runtimes:** Set the JavaScript runtime environment for Browser checks and scripts if different from account default @@ -132,7 +132,7 @@ that variable to be overridden at the group level or check level. -## How Grouped Checks Execute +## How grouped checks execute Understanding how grouped checks run is important for sophisticated monitoring setups: @@ -144,7 +144,7 @@ Understanding how grouped checks run is important for sophisticated monitoring s Groups are primarily configuration containers that provide shared settings and organizational structure. This approach ensures flexibility while enabling powerful configuration management at scale. -## Flexible Configuration Strategy +## Flexible configuration strategy Groups can serve different organizational needs: @@ -154,7 +154,7 @@ Groups can serve different organizational needs: - **Scaling mechanism:** Manage complexity through logical decomposition as your infrastructure grows -## Mixing Checks and Monitors in a Group +## Mixing checks and monitors in a group When you purchase a plan in Checkly, it includes access to specific monitoring features. As shown on our [pricing page](https://www.checklyhq.com/pricing), feature availability can differ between: diff --git a/platform/ip-information.mdx b/platform/ip-information.mdx index 77872f715..559496862 100644 --- a/platform/ip-information.mdx +++ b/platform/ip-information.mdx @@ -1,7 +1,7 @@ --- -title: IP Information & Versions +title: IP information & versions description: "Understand Checkly's dual-stack IPv4 and IPv6 support, how address resolution is prioritized, and where to find the static IP ranges for allowlisting." -sidebarTitle: IP Information +sidebarTitle: IP information tags: ['ip-information'] canonical: 'https://www.checklyhq.com/docs/platform/ip-information/' --- diff --git a/platform/managing-false-positives.mdx b/platform/managing-false-positives.mdx index f720fa630..2fa6d212e 100644 --- a/platform/managing-false-positives.mdx +++ b/platform/managing-false-positives.mdx @@ -1,7 +1,7 @@ --- -title: 'Managing False Positives' +title: 'Managing false positives' description: 'Managing False Positives in Checkly' -sidebarTitle: 'Managing False Positives' +sidebarTitle: 'Managing false positives' canonical: 'https://www.checklyhq.com/docs/platform/managing-false-positives/' --- @@ -13,7 +13,7 @@ At Checkly, we aim to help you achieve the lowest false positive rate in the mar Read on to learn more about common causes of performance variations and strategies to minimize the false positives they can cause. -## Common Causes of Performance Variations +## Common causes of performance variations When setting up your monitoring strategy, it's important to consider a few common factors that can affect networking performance: @@ -25,11 +25,11 @@ When setting up your monitoring strategy, it's important to consider a few commo While these factors are generally well-managed, they can't be completely avoided. However, you can take steps to make your monitoring setup more resilient. -## Best Practices to Minimize False Positives +## Best practices to minimize false positives False positives caused by network variations can lead to unnecessary alerts, but you can keep them under control by following these best practices: -### Use Retries +### Use retries Retries are your first line of defense against transient issues. By setting up retries, your checks can automatically try again if the first attempt fails because of a temporary glitch. This reduces the impact of brief disruptions and helps prevent false positives. @@ -37,7 +37,7 @@ While you might want to adjust based on specific use cases, we suggest implement Learn more about implementing retries: [Retries at Checkly](https://www.checklyhq.com/docs/communicate/alerts/configuration#retries). -### Optimize Your Regional Monitoring +### Optimize your regional monitoring Running checks from a specific region is important when you need to monitor your app’s performance in that area. To identify localized failures, implementing retries can help confirm whether the issue is temporary or persistent. However, if you want to understand whether an issue is more widespread, running checks from multiple regions can help you determine if it’s a broader problem with your app. @@ -45,7 +45,7 @@ Depending on your use case, we recommend running checks from at least two differ Learn more about setting up multi-location checks: [Global Location and Scheduling Strategies](/concepts/locations). -### Fine-Tune Your Alerting +### Fine-tune your alerting Adjust your alert settings to avoid unnecessary notifications. For example, you can require failures in multiple regions or after several retries before firing off an alert. This helps you avoid alerts for short-lived, isolated failures that don’t need immediate attention. @@ -53,7 +53,7 @@ A good starting point is to set alerts to trigger only after a check has failed Learn more about fine-tuning your alerts: [Alert Settings at Checkly](https://www.checklyhq.com/docs/communicate/alerts/configuration). -### Allowlist Checkly Traffic +### Allowlist Checkly traffic In some cases, firewalls, load balancers, or security solutions might inadvertently block Checkly's monitoring traffic, which could interfere with running checks successfully. This can happen if your system detects Checkly’s requests as suspicious or treats them as unwanted traffic. @@ -61,6 +61,6 @@ To prevent this, we recommend reviewing your security settings to ensure that Ch You can find Checkly’s current IP ranges here: [Allowlisting & filtering traffic](/platform/allowlisting-traffic#ip-range-allowlisting). -## If Issues Persist +## If issues persist Use [Checkly's Network Diagnostic Tools](/platform/network-diagnostic-tools) to inspect failed checks for issues like DNS errors, dropped packets, or failed handshakes. If that doesn't reveal the root cause, don't hesitate to reach out to [support@checklyhq.com](mailto:support@checklyhq.com), and our team will help investigate further. \ No newline at end of file diff --git a/platform/network-diagnostic-tools.mdx b/platform/network-diagnostic-tools.mdx index 7406c4d8b..a52195488 100644 --- a/platform/network-diagnostic-tools.mdx +++ b/platform/network-diagnostic-tools.mdx @@ -1,7 +1,7 @@ --- -title: 'Network Diagnostic Tools' +title: 'Network diagnostic tools' description: 'Network Diagnostic Tools in Checkly' -sidebarTitle: 'Network Diagnostic Tools' +sidebarTitle: 'Network diagnostic tools' canonical: 'https://www.checklyhq.com/docs/platform/network-diagnostic-tools/' --- diff --git a/platform/private-locations/agent-configuration.mdx b/platform/private-locations/agent-configuration.mdx index 0de8cb639..fad57795a 100644 --- a/platform/private-locations/agent-configuration.mdx +++ b/platform/private-locations/agent-configuration.mdx @@ -1,5 +1,5 @@ --- -title: 'Agent Configuration' +title: 'Agent configuration' description: "Configure the Checkly Agent for a private location with environment variables for API keys, proxies, job concurrency, log level, and dependency caching." canonical: 'https://www.checklyhq.com/docs/platform/private-locations/agent-configuration/' --- @@ -146,7 +146,7 @@ If you lose track of which agent containers are using the old API key, you can u 9. Click the delete icon next to the old API key (verified by the shown trailing characters) then click the confirmation. 10. Click Save to close the dialog. You will now only see the new API key listed for the private location. -## Trusting Enterprise TLS Certificates +## Trusting enterprise TLS certificates Some enterprise environments may use internal certificates for TLS connections. These certificates need to be trusted by the agent; otherwise, the agent's TLS connection to the Checkly platform will fail. @@ -162,7 +162,7 @@ docker run -v ~/certificate.pem:/checkly/certificate.pem -e NODE_EXTRA_CA_CERTS= Alternatively, you can tell the Node.js worker to accept unauthorized certificates with the environment variable `NODE_TLS_REJECT_UNAUTHORIZED=0`. This can be appended to your `docker run ..` command with the `-e` flag. -## Health Probe Endpoints +## Health probe endpoints The Checkly Agent exposes HTTP health probe endpoints and Prometheus metrics on port `8080` by default. You can change this port using the `AGENT_SERVER_PORT` environment variable. Agents before v8.12.0 serve health probes on port `8081` (set with `AGENT_HEALTH_PORT`) and metrics on port `8082`. @@ -175,7 +175,7 @@ Endpoint|Description These endpoints are useful for configuring [Kubernetes readiness and liveness probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/) or any other container orchestration health checks. -## External Observability +## External observability The Checkly Agent reports error-level events to Checkly to help detect crashes, bugs, and environment-related issues. This is enabled by default starting with agent v7.0.0. @@ -187,7 +187,7 @@ To disable external observability, set the `EXTERNAL_OBSERVABILITY` environment -e EXTERNAL_OBSERVABILITY=off ``` -## Agent Version and Runtimes +## Agent version and runtimes Each Checkly Agent only supports specific [runtimes](/platform/runtimes/overview/). This is to keep the container image at an acceptable size. When you change the runtime a check uses, you may also need to change to the corresponding agent version. Similarly, if you update the agent version to one using a different runtime you also need to update your checks to use the same runtime. @@ -212,7 +212,7 @@ As each agent version only supports specific runtimes, we recommend pinning agen ## Troubleshooting - + Container runtimes drop `NET_RAW` by default. Traceroute and Packet Capture need raw sockets, so the Checkly Agent needs this capability explicitly granted. **How to fix**: diff --git a/platform/private-locations/agent-images.mdx b/platform/private-locations/agent-images.mdx index e938bf7b6..fb6000fa6 100644 --- a/platform/private-locations/agent-images.mdx +++ b/platform/private-locations/agent-images.mdx @@ -1,7 +1,7 @@ --- -title: 'Agent Images' +title: 'Agent images' description: "Compare the Checkly Agent images, Standard, Dev, and Uptime, and learn the image tag format for pulling the variant and version you need." -sidebarTitle: 'Agent Images' +sidebarTitle: 'Agent images' canonical: 'https://www.checklyhq.com/docs/platform/private-locations/agent-images/' --- @@ -13,7 +13,7 @@ Checkly provides different agent images: * [Uptime](#uptime-image): A lightweight image for running uptime monitors only -## Image Tag Format +## Image tag format Image tags define which agent variant and version you run. @@ -30,7 +30,7 @@ docker pull checkly/agent-uptime:X.Y.Z Use versioned tags for reproducible deployments. Floating tags (like `:latest`) may change between pulls. Browse available versions on [Docker Hub](https://hub.docker.com/r/checkly/agent/tags). -## Standard Image +## Standard image The standard image (`checkly/agent:X.Y.Z`) is the default and recommended option for most setups. @@ -41,19 +41,19 @@ It supports the full range of Checkly monitors: Use the standard image unless you have a specific need for the dev or uptime variants. -## Uptime Image +## Uptime image The uptime image (`checkly/agent-uptime:X.Y.Z`) is a lightweight version of the agent designed for [uptime monitoring](/detect/uptime-monitoring/overview) only. It supports URL, DNS, TCP and ICMP monitors. Concurrency is controlled by `AGENT_WORKER_COUNT`; `JOB_CONCURRENCY` has no effect on this image. See [agent configuration](/platform/private-locations/agent-configuration). -## Dev Image +## Dev image If any of the checks you run on private locations rely on npm packages with native code, those packages need to be compiled during installation. The standard agent is optimized for size and doesn’t ship with build tools. In those cases, you’ll need to use the dev image instead. -#### When to Use the Dev Image +#### When to use the dev image Use the dev image (`checkly/agent-dev:X.Y.Z`) when your checks require npm packages with native dependencies that need compilation. Common examples include: @@ -62,7 +62,7 @@ Use the dev image (`checkly/agent-dev:X.Y.Z`) when your checks require npm packa If your checks only use pure JavaScript packages, the standard runtime image is recommended for its smaller size and faster startup. -#### What's Included in the Dev Image +#### What's included in the dev image The dev agent works exactly like the standard agent, but includes the build tools required to compile native modules. diff --git a/platform/private-locations/change-log.mdx b/platform/private-locations/change-log.mdx index df2c3f335..9a3aa7541 100644 --- a/platform/private-locations/change-log.mdx +++ b/platform/private-locations/change-log.mdx @@ -1,6 +1,6 @@ --- -title: Checkly Agent Changelog -sidebarTitle: Agent Changelog +title: Checkly Agent changelog +sidebarTitle: Agent changelog description: Release history for the Checkly Agent rss: true canonical: 'https://www.checklyhq.com/docs/platform/private-locations/change-log/' diff --git a/platform/private-locations/kubernetes-deployment.mdx b/platform/private-locations/kubernetes-deployment.mdx index 263710460..9b666d4aa 100644 --- a/platform/private-locations/kubernetes-deployment.mdx +++ b/platform/private-locations/kubernetes-deployment.mdx @@ -1,5 +1,5 @@ --- -title: 'Kubernetes Deployment' +title: 'Kubernetes deployment' description: "Deploy the Checkly Agent to a private location on Kubernetes using the official Helm chart for production-grade, orchestrated agent deployments." canonical: 'https://www.checklyhq.com/docs/platform/private-locations/kubernetes-deployment/' --- diff --git a/platform/private-locations/overview.mdx b/platform/private-locations/overview.mdx index c46637f4a..6e65d18da 100644 --- a/platform/private-locations/overview.mdx +++ b/platform/private-locations/overview.mdx @@ -97,24 +97,24 @@ We recommend to update the Checkly agent regularly. Please use a minimum container size of 2 CPU cores and 4 GB of RAM when running Playwright Check Suites. -## Next Steps +## Next steps Once your first agent is running, explore these topics to start using Private Locations in production: - + Detailed agent configuration options, updating your agent, runtime support, and more. - + Run production-grade agent deployments on a container orchestrator like Kubernetes. - + How to calculate the number of agents and amount of resources needed. - + Use the dev agent for npm packages that require compilation. diff --git a/platform/private-locations/proxy-setup.mdx b/platform/private-locations/proxy-setup.mdx index 8f6ac5aa1..115949d09 100644 --- a/platform/private-locations/proxy-setup.mdx +++ b/platform/private-locations/proxy-setup.mdx @@ -1,5 +1,5 @@ --- -title: 'Proxy Setup' +title: 'Proxy setup' description: 'Configure HTTP proxies for Checkly private locations in enterprise environments. Set up proxy routing for both agent management traffic and check execution.' canonical: 'https://www.checklyhq.com/docs/platform/private-locations/proxy-setup/' --- diff --git a/platform/private-locations/scaling-redundancy.mdx b/platform/private-locations/scaling-redundancy.mdx index 9ddde2cab..9e5b8df30 100644 --- a/platform/private-locations/scaling-redundancy.mdx +++ b/platform/private-locations/scaling-redundancy.mdx @@ -1,5 +1,5 @@ --- -title: 'Scaling and Redundancy' +title: 'Scaling and redundancy' description: 'Plan capacity, implement redundancy, and scale Checkly private locations for production workloads.' canonical: 'https://www.checklyhq.com/docs/platform/private-locations/scaling-redundancy/' --- diff --git a/platform/reporting/overview.mdx b/platform/reporting/overview.mdx index 720773b70..13d202a7e 100644 --- a/platform/reporting/overview.mdx +++ b/platform/reporting/overview.mdx @@ -1,5 +1,5 @@ --- -title: 'Reporting Results with Checkly' +title: 'Reporting results with Checkly' description: 'Analyze check performance and export monitoring data with Checkly reporting dashboard' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/platform/reporting/overview/' @@ -18,31 +18,31 @@ The reporting dashboard lists your checks, 25 per page, with key performance met - Compare performance between different check types - Spot patterns in success ratios and response times -## Filtering and Sorting +## Filtering and sorting Customize your view using the toolbar filters and sorting options: - + Select the time period for your analysis: Today, Last hour, Last 3 hours, Last 24 hours, Last 7 days, Last 30 days, or a custom range. The dashboard adjusts data granularity automatically based on your selection. - + Type a filter into the search bar, for example `tags:is:prod`. You can filter by status, check type, tags, project, location, creator, name, group, URL, logical ID and whether the check ran, and by the Success, Avg, P95 and P99 metrics, and combine filters with `and` and `or`. See [Filters](/platform/filters) for the syntax. You can save any filter as a [view](/platform/views). - + Click a column header to sort by Type, Name, Success, Avg, P95 or P99, in ascending or descending order. -## Performance Graphs +## Performance graphs Use the **Table** and **Chart** toggle in the toolbar to switch between the list and a chart of response times and success ratios over your selected time period. Select up to 12 checks in the table and click **Compare in chart** to chart them together. Without a selection, the chart shows the first 12 checks in the table's order, the 12 with the highest P95 unless you sorted the table. ![Reporting Dashboard Graphs](/images/docs/images/reporting/dashboard-graph.png) -### Graph Features +### Graph features **Response Time Metrics**: Toggle Avg, P95 and P99 with the Metrics buttons above the chart. P95 is shown by default. Each check keeps its color across the chart, and Avg and P99 use dotted and dashed lines. @@ -58,18 +58,18 @@ Use the **Table** and **Chart** toggle in the toolbar to switch between the list | Up to 48 months | Monthly | | Beyond 48 months | Yearly | -## Data Export +## Data export Export your monitoring data for external analysis, reporting, or archival purposes. -### CSV Export Process +### CSV export process - + Choose the time period for your export using the date range picker. - + Use check type, tags, and other filters to narrow your dataset if needed. @@ -78,7 +78,7 @@ Click **Download CSV** in the toolbar to generate your export file. -### Export Data Fields +### Export data fields The CSV export (`checkly_export.csv`) includes the following columns: @@ -99,7 +99,7 @@ The CSV export (`checkly_export.csv`) includes the following columns: All statistics are calculated based on your selected date range. The default range is "Last 24 Hours". -## Best Practices +## Best practices - **Regular exports**: Use the [Reporting API](/api-reference/reporting/generates-a-report-with-aggregate-statistics-for-checks-and-check-groups) to automate periodic exports for long-term trend analysis - **Filter strategically**: Use tags and groups to create focused reports for different teams diff --git a/platform/runtimes/overview.mdx b/platform/runtimes/overview.mdx index 969cf55e2..238f2d7b4 100644 --- a/platform/runtimes/overview.mdx +++ b/platform/runtimes/overview.mdx @@ -1,5 +1,5 @@ --- -title: 'Checkly Runtimes' +title: 'Checkly runtimes' description: 'How Checkly runtimes work.' sidebarTitle: 'Overview' canonical: 'https://www.checklyhq.com/docs/platform/runtimes/overview/' diff --git a/platform/runtimes/runtime-specification.mdx b/platform/runtimes/runtime-specification.mdx index ef065c51d..c65d57884 100644 --- a/platform/runtimes/runtime-specification.mdx +++ b/platform/runtimes/runtime-specification.mdx @@ -1,7 +1,7 @@ --- -title: 'Runtime Specification' +title: 'Runtime specification' description: 'Detailed information on specific Checkly runtimes.' -sidebarTitle: 'Runtime Specification' +sidebarTitle: 'Runtime specification' canonical: 'https://www.checklyhq.com/docs/platform/runtimes/runtime-specification/' --- diff --git a/platform/secrets.mdx b/platform/secrets.mdx index 4308a3621..48dfa5185 100644 --- a/platform/secrets.mdx +++ b/platform/secrets.mdx @@ -1,7 +1,7 @@ --- -title: 'Storing Secrets' +title: 'Storing secrets' description: 'Storing sensitive data in Checkly' -sidebarTitle: 'Storing Secrets' +sidebarTitle: 'Storing secrets' canonical: 'https://www.checklyhq.com/docs/platform/secrets/' --- @@ -21,17 +21,17 @@ Both variables and secrets are encrypted at rest and in flight. However, Secrets -## Secrets in Practice +## Secrets in practice Secrets integrate seamlessly into your monitoring workflow while maintaining security. You reference them in your code using the same syntax as regular environment variables, but they remain protected throughout the entire execution pipeline. This means you can write monitoring logic that authenticates with services, accesses protected endpoints, and performs realistic user scenarios without compromising security. Use secrets in your scripts using standard Node.js syntax: `process.env.MY_SECRET` or by using `{{handlebars}}` syntax in applicable API check fields. -## Real-World Secrets Examples +## Real-world secrets examples Here's how you might use Secrets in real monitoring scenarios: -### API Authentication Example: +### API authentication example: ```typescript import { ApiCheck, AssertionBuilder } from 'checkly/constructs' @@ -54,7 +54,7 @@ new ApiCheck('authenticated-api-check', { }) ``` -### Browser Login Flow Example: +### Browser login flow example: ```typescript import { test, expect } from '@playwright/test' @@ -73,7 +73,7 @@ test('Login flow', async ({ page }) => { }) ``` -### Database Connection Example: +### Database connection example: ```typescript import { ApiCheck } from 'checkly/constructs' @@ -94,7 +94,7 @@ new ApiCheck('database-health-check', { }) ``` -### Managing Secrets via CLI: +### Managing secrets via CLI: ```bash # Create a secret @@ -110,7 +110,7 @@ npx checkly env ls npx checkly env update API_SECRET_KEY new_secret_value --secret ``` -### Payment Processing Example: +### Payment processing example: ```typescript import { test } from '@playwright/test' @@ -131,13 +131,13 @@ test('Checkout flow with test payment', async ({ page }) => { }) ``` -## Secrets as Security Foundation +## Secrets as security foundation Secrets represent the foundation of secure monitoring practices. They enable you to test and monitor authenticated workflows, private APIs, and sensitive user journeys while maintaining the security posture that modern applications require. By centralizing secret management within your monitoring platform, you eliminate the risk of credentials being scattered across scripts, configuration files, or team communications. The power of Secrets lies in making security invisible to your monitoring logic—your Checks work exactly the same whether they're using public endpoints or accessing the most sensitive parts of your application, but the security model ensures that sensitive information never leaves the protected environment. -## Alternative: Dynamic Secret Detection +## Alternative: Dynamic secret detection For Browser checks and Multistep checks, you can also use dynamic secret detection. This approach allows you to retrieve secrets at runtime (from external vaults like Azure Key Vault, AWS Secrets Manager, etc.) and have them automatically scrubbed from logs and traces. @@ -153,7 +153,7 @@ This is particularly useful for organizations that prefer not to store secrets i Secrets also work in alert-channel configurations — webhook URLs, API keys, PagerDuty service keys, and any other literal-secret field accept the same `{{NAME}}` reference syntax. See [Alert channels](/communicate/alerts/channels) for details and the inline promote-to-secret affordance. -## Security and Usability Balance +## Security and usability balance Use dedicated test users, test cards etc. These test users should have minimal privileges in your app. Do not use your admin or root user. Make sure you can easily disable or block these users without recourse. diff --git a/platform/variables.mdx b/platform/variables.mdx index 249b4e64b..8819baf69 100644 --- a/platform/variables.mdx +++ b/platform/variables.mdx @@ -94,6 +94,6 @@ How variables are accessed depends on where you're accessing them from: Handlebar (double brackets) variables are HTML-escaped: `&`, `<`, `>`, `"`, `'`, `` ` `` and `=` are replaced with HTML entities, for example `&` becomes `&`. To insert the raw value, access your environment variables with triple brackets, i.e. `{{{VARIABLE_NAME}}}`. -## Playwright Check Suite Variables +## Playwright Check Suite variables Checkly provides a set of [built-in environment variables](/detect/synthetic-monitoring/playwright-checks/environment-variables) that you can use in your [Playwright Check Suites](/detect/synthetic-monitoring/playwright-checks/overview) to distinguish between Checkly executions and local runs. diff --git a/platform/views.mdx b/platform/views.mdx index 89f6f1013..2469d57ce 100644 --- a/platform/views.mdx +++ b/platform/views.mdx @@ -175,7 +175,7 @@ New views start with no counter. The counter is part of the view. Everyone sees Test sessions has no counters. -## Passing, Degraded and Failing on Monitors +## Passing, degraded and failing on monitors Every account starts with three shared views on Monitors: **Passing**, **Degraded** and **Failing**. Each one filters on its status and counts those checks. diff --git a/quickstart.mdx b/quickstart.mdx index c3f2c170b..016abdbb7 100644 --- a/quickstart.mdx +++ b/quickstart.mdx @@ -1,5 +1,5 @@ --- -title: 'Checkly Quickstart' +title: 'Checkly quickstart' description: 'Add synthetic monitoring to your existing project in minutes. Let your AI agent set up Checkly, or follow the steps yourself.' sidebarTitle: 'Quickstart' canonical: 'https://www.checklyhq.com/docs/quickstart/' diff --git a/resolve/ai-root-cause-analysis/overview.mdx b/resolve/ai-root-cause-analysis/overview.mdx index 3246d0f3d..f751bf9ac 100644 --- a/resolve/ai-root-cause-analysis/overview.mdx +++ b/resolve/ai-root-cause-analysis/overview.mdx @@ -1,11 +1,11 @@ --- -title: "Rocky AI Root Cause Analysis" +title: "Rocky AI root cause analysis" description: "Automatically perform root cause and user impact analysis with Rocky AI" -sidebarTitle: "AI Root Cause Analysis" +sidebarTitle: "AI root cause analysis" canonical: 'https://www.checklyhq.com/docs/resolve/ai-root-cause-analysis/overview/' --- -## What is Rocky AI Root Cause Analysis? +## What is Rocky AI root cause analysis? Rocky AI — Checkly's Agent — can automatically analyze, categorize and summarize any failure or error from one of Checkly's synthetic checks and / or monitoring checks. @@ -24,7 +24,7 @@ Rocky AI — Checkly's Agent — can automatically analyze, categorize and summa Using any available artifacts like error message, user code, check description, logs, metrics, trace routes, OpenTelemetry traces, packet captures, Playwright traces, screenshots and other evidence, it will quickly assess what the impact is of a failure and what the underlying (possible) root cause is. It will also provide a suggested code fix for any check based on (Playwright) code. -## Getting Started with Rocky AI Root Cause Analysis +## Getting started with Rocky AI root cause analysis To use Rocky AI Root Cause Analysis, make sure [Rocky AI is enabled on its settings page](https://app.checklyhq.com/accounts/rocky-ai). @@ -111,7 +111,7 @@ For API, Browser, Multistep, and Playwright Checks, the **Check intent** card be For Browser and Multistep checks, select **Repair with AI** on a completed analysis to attempt a script fix. See [Start a manual repair](../automatic-check-repair#start-a-manual-repair) for prerequisites, repair history, and restoring the original script. -## Key Capabilities +## Key capabilities - **Categorize**: Rocky AI determines if an error is of a specific category. For example: is it a typo in your code or is it an infrastructure error? - **Root cause**: Rocky AI analyzes the failure and provides you with a root cause analysis, helping you quickly remediate the issue. It uses any and all available artifacts to come to this analysis and list these artifacts as "evidence". diff --git a/resolve/automatic-check-repair.mdx b/resolve/automatic-check-repair.mdx index a3ed8fbd9..eda1fc1e9 100644 --- a/resolve/automatic-check-repair.mdx +++ b/resolve/automatic-check-repair.mdx @@ -1,6 +1,6 @@ --- title: 'Automatic check repair' -sidebarTitle: 'Automatic Repair' +sidebarTitle: 'Automatic repair' description: 'Configure automatic repair, start a manual attempt, and restore a Browser or Multistep check script.' canonical: 'https://www.checklyhq.com/docs/resolve/automatic-check-repair/' --- diff --git a/resolve/overview.mdx b/resolve/overview.mdx index cbc6e77bc..66ed7234a 100644 --- a/resolve/overview.mdx +++ b/resolve/overview.mdx @@ -11,24 +11,24 @@ canonical: 'https://www.checklyhq.com/docs/resolve/overview/' Analyze request flows with distributed tracing to identify performance bottlenecks and failures - + Let Rocky AI analyze errors, metrics, traces and logs and determine impact and root cause -## Key Benefits +## Key benefits - **Fast Root Cause Analysis** — Identify the exact source of issues with detailed request tracing across your entire application stack. - **AI-Powered Insights** — Get intelligent analysis and recommendations from Rocky AI to resolve incidents faster than ever. - **Full Request Visibility** — See complete request flows from frontend to backend, including database queries and external API calls. - **Performance Optimization** — Identify slow operations and bottlenecks to proactively improve application performance. -## Getting Started +## Getting started Ready to accelerate your incident resolution? Choose the approach that best fits your current needs: - + Begin collecting distributed traces for your applications @@ -36,11 +36,11 @@ Begin collecting distributed traces for your applications Experience AI-powered root cause analysis and insights - + Add OpenTelemetry instrumentation to your codebase - + Connect traces with your existing observability platform diff --git a/resolve/traces/export/dash0.mdx b/resolve/traces/export/dash0.mdx index ae86dd365..933fc3d33 100644 --- a/resolve/traces/export/dash0.mdx +++ b/resolve/traces/export/dash0.mdx @@ -1,5 +1,5 @@ --- -title: 'Exporting Traces to Dash0' +title: 'Exporting traces to Dash0' description: 'Learn how to export traces from Checkly to Dash0.' sidebarTitle: 'Dash0' canonical: 'https://www.checklyhq.com/docs/resolve/traces/export/dash0/' diff --git a/resolve/traces/export/grafana-tempo.mdx b/resolve/traces/export/grafana-tempo.mdx index bc5b27fca..c03036bd0 100644 --- a/resolve/traces/export/grafana-tempo.mdx +++ b/resolve/traces/export/grafana-tempo.mdx @@ -1,5 +1,5 @@ --- -title: 'Exporting Traces to Grafana Tempo' +title: 'Exporting traces to Grafana Tempo' description: 'Learn how to export traces from Checkly to Grafana Tempo.' sidebarTitle: 'Grafana Tempo' canonical: 'https://www.checklyhq.com/docs/resolve/traces/export/grafana-tempo/' diff --git a/resolve/traces/export/honeycomb.mdx b/resolve/traces/export/honeycomb.mdx index 0ed70bc42..58f189e55 100644 --- a/resolve/traces/export/honeycomb.mdx +++ b/resolve/traces/export/honeycomb.mdx @@ -1,5 +1,5 @@ --- -title: 'Exporting Traces to Honeycomb' +title: 'Exporting traces to Honeycomb' description: 'Learn how to export traces from Checkly to Honeycomb.' sidebarTitle: 'Honeycomb' canonical: 'https://www.checklyhq.com/docs/resolve/traces/export/honeycomb/' diff --git a/resolve/traces/export/new-relic.mdx b/resolve/traces/export/new-relic.mdx index 2b46db7de..cf2b82528 100644 --- a/resolve/traces/export/new-relic.mdx +++ b/resolve/traces/export/new-relic.mdx @@ -1,5 +1,5 @@ --- -title: 'Exporting Traces to New Relic' +title: 'Exporting traces to New Relic' description: 'Learn how to export traces from Checkly to New Relic.' sidebarTitle: 'New Relic' canonical: 'https://www.checklyhq.com/docs/resolve/traces/export/new-relic/' diff --git a/resolve/traces/export/to-chronosphere.mdx b/resolve/traces/export/to-chronosphere.mdx index 507e6da65..c9bfeb1fc 100644 --- a/resolve/traces/export/to-chronosphere.mdx +++ b/resolve/traces/export/to-chronosphere.mdx @@ -1,5 +1,5 @@ --- -title: 'Exporting Traces to Chronosphere' +title: 'Exporting traces to Chronosphere' description: 'Learn how to export traces from Checkly to Chronosphere.' sidebarTitle: 'To Chronosphere' canonical: 'https://www.checklyhq.com/docs/resolve/traces/export/to-chronosphere/' diff --git a/resolve/traces/how-it-works.mdx b/resolve/traces/how-it-works.mdx index acacf903c..8a82d0ce5 100644 --- a/resolve/traces/how-it-works.mdx +++ b/resolve/traces/how-it-works.mdx @@ -1,5 +1,5 @@ --- -title: 'How It Works' +title: 'How it works' description: 'Understand how Checkly traces work with OpenTelemetry to provide comprehensive observability.' canonical: 'https://www.checklyhq.com/docs/resolve/traces/how-it-works/' --- @@ -8,10 +8,10 @@ Checkly Traces use OpenTelemetry to correlate synthetic check results with your ![Checkly OpenTelemetry diagram](/images/docs/images/otel/checkly_otel_diagram.png) -## The Flow +## The flow - + When enabling the integration, Checkly automatically instruments all HTTP requests made by your checks with `traceparent` and `tracestate` headers. These HTTP requests hit your web application and/or API when running checks. All synthetic check types, including API, Browser and Multistep checks, include these headers: @@ -22,7 +22,7 @@ All synthetic check types, including API, Browser and Multistep checks, include Together, these headers propagate the trace context along the request chain. This is the most basic way of tying a synthetic check to your backend traces, though it won't provide much context about the check run itself, like the check name or location. - + You can configure your 3rd party backend in the Checkly UI so we can export every check result as a span to your backend. This correlates all backend spans with the check run that triggered them, together with full context of the check run. Check details are stored in the `checkly` namespace as attributes on the span: @@ -47,7 +47,7 @@ Tag caveats: - + **No 3rd party backend needed.** This is what kicks Checkly's OpenTelemetry integration into high gear, and it works even if you don't have a 3rd party OTel backend already set up. By adding the correct OTel libraries and simple filter statements, you can send ONLY the traces related to your Checkly checks back to Checkly: @@ -59,7 +59,7 @@ By adding the correct OTel libraries and simple filter statements, you can send Checkly's trace ingestion endpoint is a standard OTel backend endpoint that only accepts traces related to synthetic checks. This keeps your OpenTelemetry setup lean while providing full trace correlation benefits. - + When your check breaks, you get an alert that points to a check result containing a full trace of the check run, including all backend spans: - Complete trace of the check run diff --git a/resolve/traces/import/https-grpc.mdx b/resolve/traces/import/https-grpc.mdx index ccd44d392..915dda0ce 100644 --- a/resolve/traces/import/https-grpc.mdx +++ b/resolve/traces/import/https-grpc.mdx @@ -1,5 +1,5 @@ --- -title: 'HTTPS vs GRPC Traces' +title: 'HTTPS vs GRPC traces' description: 'Learn how to import traces from HTTPS/GRPC' sidebarTitle: 'HTTPS vs GRPC' canonical: 'https://www.checklyhq.com/docs/resolve/traces/import/https-grpc/' diff --git a/resolve/traces/import/missing-spans.mdx b/resolve/traces/import/missing-spans.mdx index dcfe7338f..ef598a065 100644 --- a/resolve/traces/import/missing-spans.mdx +++ b/resolve/traces/import/missing-spans.mdx @@ -1,7 +1,7 @@ --- -title: 'Missing Spans' +title: 'Missing spans' description: 'Learn how to import traces from OpenTelemetry' -sidebarTitle: 'Missing Spans' +sidebarTitle: 'Missing spans' canonical: 'https://www.checklyhq.com/docs/resolve/traces/import/missing-spans/' --- @@ -55,7 +55,7 @@ Missing spans can happen due to various reasons. Whether you're sending data to #### Sampling directly in your applications' code. Choose the specific [instrumentation language guide](/resolve/traces/instrumentation/nodejs) and review your configuration against Step 2 in the guides. -### Review OpenTelemetry Exporter configuration +### Review OpenTelemetry exporter configuration Ensure the right Authorization keys and endpoints are in use. @@ -79,7 +79,7 @@ Ensure the right Authorization keys and endpoints are in use. exporters: [otlp/checkly] ``` -#### Exporting directly from your Application's code +#### Exporting directly from your application's code Confirm your environment variables use the correct endpoint and authorization: diff --git a/resolve/traces/import/open-telemetry.mdx b/resolve/traces/import/open-telemetry.mdx index c6e4aceb8..dc63d8935 100644 --- a/resolve/traces/import/open-telemetry.mdx +++ b/resolve/traces/import/open-telemetry.mdx @@ -1,5 +1,5 @@ --- -title: 'Setting Up The OpenTelemetry Collector' +title: 'Setting up the OpenTelemetry Collector' description: 'Learn how to import traces from OpenTelemetry' sidebarTitle: 'From OpenTelemetry' canonical: 'https://www.checklyhq.com/docs/resolve/traces/import/open-telemetry/' diff --git a/resolve/traces/import/overview.mdx b/resolve/traces/import/overview.mdx index 86fa879cc..349582198 100644 --- a/resolve/traces/import/overview.mdx +++ b/resolve/traces/import/overview.mdx @@ -1,8 +1,8 @@ --- -title: "Importing Traces To Checkly" +title: "Importing traces to Checkly" description: "Send OpenTelemetry traces from your infrastructure to Checkly so you can drill into why a check failed or degraded, right from the check result." -sidebarTitle: "Importing Traces" +sidebarTitle: "Importing traces" canonical: 'https://www.checklyhq.com/docs/resolve/traces/import/overview/' --- diff --git a/resolve/traces/instrumentation/nextjs.mdx b/resolve/traces/instrumentation/nextjs.mdx index a2834b8b6..84f840cec 100644 --- a/resolve/traces/instrumentation/nextjs.mdx +++ b/resolve/traces/instrumentation/nextjs.mdx @@ -92,7 +92,7 @@ This is however not required, the above configuration should work just fine on N Also notice the `sampler` configuration. This is a custom, **head-based sampler** that will only sample spans that are generated by Checkly by inspecting the trace state. This way you only pay for the egress traffic generated by Checkly and not for any other traffic. -## Step 5 (Local development). Start your app with the instrumentation +## Step 5 (local development). Start your app with the instrumentation Toggle on **Import Traces** and grab your OTel API key in the **OTel API keys** section of the [Traces page in the Checkly app](https://app.checklyhq.com/settings/account/traces) and take a note of the endpoint for the region you want to use. diff --git a/resolve/traces/overview.mdx b/resolve/traces/overview.mdx index 1b6e8d0f6..b3216046a 100644 --- a/resolve/traces/overview.mdx +++ b/resolve/traces/overview.mdx @@ -10,7 +10,7 @@ canonical: 'https://www.checklyhq.com/docs/resolve/traces/overview/' alt="Check result with OpenTelemetry trace" /> -## What is Distributed Tracing? +## What is distributed tracing? Distributed tracing tracks requests as they flow through your application's services and infrastructure. It helps you: @@ -25,7 +25,7 @@ With telemetry traces configured, you will have access to traces in all the plac - **Test sessions:** understand any failures during test session execution. - **Check editors:** get a live trace while building, editing and debugging check code. -## Getting Started with Checkly Traces +## Getting started with Checkly Traces To get started with Checkly Traces using OpenTelemetry, pick the scenario that best fits your needs. @@ -38,7 +38,7 @@ To get started with Checkly Traces using OpenTelemetry, pick the scenario that b Send your infrastructure traces to Checkly to get contextualized check failure analysis. - + Export check results as traces to your 3rd party OTel tooling @@ -81,22 +81,22 @@ Here's an actual example from Checkly's own backend. 2. The OTeL trace indicates this was actually do to our **Clickhouse** server returning a 500 errors, immediately telling our on-call team where to start looking. 3. Without the trace, we would have to look at all the various logging, error tracking and other tools that are integrated into the various middleware and infrastructure this request passes through (our load balancer, REST API server, Redis datastore etc. -## Key Benefits +## Key benefits - + Only traces generated by Checkly checks are forwarded to third-party tools, significantly reducing data transfer costs while maintaining comprehensive monitoring coverage. - + Combine synthetic monitoring data with application traces in your existing observability platform for a complete picture of system health. - + When checks fail, trace data provides immediate context about what happened in your application stack, accelerating root cause analysis. - + Works with existing OpenTelemetry instrumentation and popular observability platforms without requiring changes to your application logic. diff --git a/what-is-checkly.mdx b/what-is-checkly.mdx index 0d05a8e0a..f4403053b 100644 --- a/what-is-checkly.mdx +++ b/what-is-checkly.mdx @@ -40,25 +40,25 @@ Checkly helps developers increase uptime and reliability, improve shipping veloc Define your entire monitoring setup with TypeScript constructs instead of manual UI configuration. - + Browser monitoring powered natively by Playwright for fast, reliable end-to-end scenario monitoring. - + Code-driven platform with constructs, APIs, and a CLI that manages the entire lifecycle of your monitors. - + Unify testing, monitoring, and observability into a single workflow using Playwright and OpenTelemetry. - + Detect both functional and performance errors in pre-production and production environments. -## Use Cases +## Use cases - **[Run checks on every deploy](/guides/sdlc-monitoring)** — Validate functionality and performance in staging before deployment, catching regressions early. - **[Production Monitoring](/learn/monitoring/api-monitoring)** — Continuously monitor critical user journeys, API endpoints, and application performance. @@ -67,7 +67,7 @@ Detect both functional and performance errors in pre-production and production e - **[Multi-Environment Validation](/concepts/environments)** — Test across different environments, browsers, and devices for consistent functionality. - **[Compliance and SLA Monitoring](/learn/incidents/slo-sla-sli)** — Track uptime and performance metrics to meet SLAs and regulatory requirements. -## Checkly Is Best Fit For +## Checkly is best fit for **DevOps and SRE Teams** looking for programmable monitoring that integrates seamlessly with their existing infrastructure-as-code and GitOps workflows. **Full-Stack Engineering Teams** who want to shift monitoring left and treat monitoring as an integral part of their development process rather than an afterthought.