The Checkly OpenTelemetry (OTel) Tracing integration is now in public beta. With this integration you can correlate your synthetic checks with backend traces, cut through the noise and find out the root cause of a slow or failing check 10x faster than before.

• Slow TTFB? We can point you to any slow database queries or high latency third party services.

• Got a 500 error? We can show you where it went wrong in your application stack.

Check out the short Loom video below to get a quick demo 👇

In a nutshell, it works as follows:

1. All HTTP requests made by your checks are automatically instrumented with W3C traceparent and tracestate headers.

2. Ingest traces into Checkly from your OTel setup and display them in the Checkly UI, allowing you to correlate check results with backend traces.

3. Send every check run to your 3rd party OTel backend as a span, enabling you to correlate check runs and their metadata like check run location, check name etc. with other telemetry data.

Head over to the dedicated OpenTelemetry section in the app to get started.

Check our docs for more information.

• Instrumenting your code with OpenTelemetry SDKs

• Sending traces to Checkly using the OpenTelemetry collector

• Exporting traces to 3rd party services

This feature is available for free on all plans during the beta.

Questions or feedback? Join our Slack community.