[braxtonj]

One model, told once: Checkly exposes metrics on one Prometheus endpoint, sends API check, URL monitor, Browser check and Multistep check runs as OpenTelemetry spans to one OTLP/HTTP URL, sends alerts anywhere via webhooks, and takes your application's traces in over OTLP. Today those pages are split between Integrations > Observability and Resolve > Traces > Exporting, Chronosphere is not in the nav at all, and two customers asked for "the OTel and Prometheus docs" in the last month with no single page to send.

What changes

• Integrations > Observability now holds everything that leaves Checkly: an Overview with a decision table, a Metrics subgroup with one Prometheus page, and a Traces subgroup with a generic OTLP page, Coralogix and thin vendor pages (Chronosphere, ClickStack, Cribl Stream, Dash0, Datadog, Grafana Tempo, Honeycomb, New Relic).
• Resolve > Traces > Exporting becomes one router page that links the Integrations pages. No page path appears in two nav groups.
• Prometheus is one page. The v2 content is the page, with the labels, windows and edge cases documented from the current API code. The v1 endpoint is a clearly labeled legacy section at the end with a deprecation warning. /integrations/observability/prometheus-v2 redirects to /integrations/observability/prometheus and the #heartbeat-metrics anchor survives.
• The OTLP page is new and carries the span schema, the trace headers, the tags rules, a tested Collector receiver recipe, transport facts and troubleshooting. Vendor pages only carry the values each vendor needs and link back for everything else.
• Coralogix is corrected in place: key location, endpoint derivation, the attribute list, the custom trace header behavior, and current RUM key names.
• Resolve > Traces pages point at the new locations; how-it-works gets a vendor-neutral Mermaid diagram and the four-type coverage wording.

Moves and redirects

Old	New
resolve/traces/export/grafana-tempo	integrations/observability/traces/grafana-tempo
resolve/traces/export/honeycomb	integrations/observability/traces/honeycomb
resolve/traces/export/new-relic	integrations/observability/traces/new-relic
resolve/traces/export/dash0	integrations/observability/traces/dash0
resolve/traces/export/to-chronosphere	integrations/observability/traces/chronosphere
integrations/observability/prometheus-v2	merged into integrations/observability/prometheus

All six have docs.json redirects. The web app still links the old paths from Settings > Traces and from the check result page; they resolve through the redirects, and updating them is a follow-up for the app team.

Sources and verification

• Schemas come from the monorepo at 63758c4b70 (2026-10-21), not from the old pages. Research notes with path:line citations are available from me on request.
• Live verification on 2026-10-30 against a sandbox account: real spans captured for every check type from public and private locations through a bearer-authenticated OpenTelemetry Collector, which is the exact receiver recipe on the OTLP page; the Prometheus scrape config, every PromQL example, the Collector prometheus receiver block and the legacy v1 config were run in Prometheus 3.0.0 and otelcol-contrib 0.160.0; both Prometheus endpoints were scraped and diffed against the code research (35 of 35 v2 families, 6 of 6 v1). Verification notes with masked captures are available on request.
• Vendor pages were validated against vendor documentation only (no vendor accounts). Anything the fact-check could not confirm was left off the page.
• Screenshots are Checkly-side only: the Prometheus integration card, the Export Traces settings and the Coralogix form, all freshly captured with values masked.

Deliberately dropped

• Vendor UI screenshots: Grafana's five and Dash0's two captures of vendor screens, plus the Coralogix UI captures cx_otel_int2.png and cx_rum_api_creation.png. The image files stay on disk; only the references are gone. The old Checkly screens export-traces-to-grafana-config.png, dash0-checkly.png, prometheus_step1.png, prometheus_step2.png and prometheus_v2_step2.png are superseded by the new captures.
• Grafana's "check that Tempo is installed" step and the third-party base64 website (replaced by a shell one-liner).
• New Relic's "Traces feature enabled" step (not in New Relic's documentation).
• The checkly_otel_diagram.png on how-it-works (hardcoded tracestate: checkly=true and a vendor list with Baselime), replaced by Mermaid; the file stays on disk.
• The v2 page's top Info banner and the v1 page's Warning (replaced by one deprecation Warning), the v1 "inactive after six hours" sentence (not in code), the v1 "30 to 60 s interval" advice, and the enable_compression tip with its Prometheus 2.49 note (the endpoint gzips when the scraper asks, which Prometheus does by default).
• The link to the Private Location agent metrics page, because that branch is unmerged. Add one sentence on the Prometheus page once platform/private-locations/agent-metrics lands, and point its Prometheus link at /integrations/observability/prometheus.
• The deprecated agentic check type from the check_type enumeration.

Conflicts with in-flight branches

docs-audit/doc-238-casing-consistency touches coralogix.mdx, prometheus-v2.mdx (deleted here), resolve/traces/overview.mdx and the Dashboards overview title. All new text already uses its casing. If DOC-238 lands first: merge main into this branch (never rebase), resolve prometheus-v2.mdx as deleted, port its two "Traceroute" rows into prometheus.mdx if they still differ, take ours for coralogix.mdx, regenerate the sitemap. edvinas/agent-prometheus-metrics-docs only collides on sitemap.xml; regenerate it.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
checkly-422f444a	🟢 Ready	View Preview	Oct 30, 2026, 1:43 PM