October 24th, 2024
New
When instrumenting the different services and applications with telemetry in a distributed system, it’s easy for one to be misconfigured. Causing missing spans in your Traces visualization.
Now, on the Trace Detail page, Checkly infers which spans are missing, using the contextual information of the spans around it.
This is especially helpful when debugging your Open Telemetry setup, given the timeline in which the missing spans (or spans) show up, their children spans, and which services are called right before and after; you can detect which service is the one amiss.
Read the guide to troubleshoot missing spans to get help figuring this out.
If you haven’t done so already, set up Checkly Traces and get to the root of your checks’ failures faster.
Are you new to observability and Open Telemetry? Book an onboarding call to get help onboarding into OpenTelemetry and Checkly Traces.
Otherwise, join our Slack community to talk with fellow devs.