Table of contents

Getting started with OpenTelemetry

With the Checkly OpenTelemetry (OTel) integration, you can find out why your business critical checks are failing and resolve issues 10x faster than before. This works as follows:

1. All HTTP requests made by your checks are automatically instrumented with W3C traceparent and tracestate headers.
2. 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.
3. Ingest traces into Checkly from your OTel setup and display them in the Checkly UI, allowing you to correlate check results with traces.

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 May 1, 2024. You can contribute to this documentation by editing this page on Github