Skip to main content
Turn on trace export and every API check, URL monitor, Browser check and Multistep check run is sent to your tracing backend as one OpenTelemetry span with the check name, location, tags and verdict, joined to your application’s spans when your app honors the traceparent header. Point any scraper that sends a bearer token at one URL and it reads the status of every check type, plus timings and Browser check web vitals.

​
Choose an integration

​
Coverage and limits

  • Metrics cover every check type, including Heartbeat monitors, plus queue and agent metrics for your private locations.
  • Traces are sent for API check, URL monitor, Browser check and Multistep check runs.
  • The span’s OpenTelemetry status is always OK. Filter on checkly.check.status to find failed and degraded runs in your tool.
  • Traces carry no metrics, the Prometheus endpoint carries no traces, and neither carries logs.
  • Export is account-wide to one endpoint. Failed exports are not shown in Checkly.
  • Timings are averages only. Histograms expose only the +Inf bucket, and counters reset every hour.

​
Integration pages

Prometheus

Scrape check, heartbeat and private location metrics from one endpoint.

Export traces over OTLP

Send one span per check run to any backend or collector that accepts OTLP/HTTP.

Coralogix

Send traces, RUM and alerts to Coralogix.
Backend not listed? Use Export traces over OTLP for traces and Prometheus for metrics. Pages for specific backends: Chronosphere, ClickStack, Cribl Stream, Dash0, Datadog, Grafana Tempo, Honeycomb, New Relic. New to traces and spans? OpenTelemetry concepts covers the basics.