table of contents Table of contents

Getting started with OpenTelemetry

On this page
The OpenTelemetry integration is currently in beta and available for free on all plans. Need help getting started? We offer a free, 1:1 valet onboarding service to help you instrument your stack with the correct OpenTelemetry SDKs and enable tracing inside Checkly. Book an onboarding session right here

The Checkly OpenTelemetry (OTel) integration allows you to correlate synthetic monitoring checks with traces from your backend services. This integration is especially useful for two types of users:

  • Resolve issues quicker: Resolve failing synthetic checks much quicker by correlating failing checks with backend & infrastructure traces. No more flipping between various 3rd party observability (o11y) systems.
  • Increase signal vs. noise: Cut through the sea of o11y and focus on the data that correlates to critical and known business processes as exercised by synthetic monitoring checks.
  • Save money: Send traces directly to Checkly, without signing up for another product or hosting an OTel solution yourself.

Check result with OpenTelemetry trace

With OpenTelemetry enabled, you will have access to traces in all the places where it matters to more quickly resolve issues:

  • Check results: resolve production outages faster by correlating failing checks with backend traces.
  • Test sessions: understand any failures during test session execution.
  • Check Editors get a live trace while building, editing and debugging check code.

See this in action in the video below:


To get started with the Checkly OpenTelemetry integration, pick a scenario that best fits your needs.

If you want to learn more about how this all works, check out the How it works under the hood section.


Last updated on June 7, 2024. You can contribute to this documentation by editing this page on Github