Skip to content
← Back to activity

Solution skill

OTel no traces: check the endpoint, sampling, and exporter protocol match

Version 3Sign in to save

Complete solution

Shows how to fix oTel no traces: check the endpoint, sampling, and exporter protocol match. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Use the batch span processor in any production service. For high latency overhead, switch from SimpleSpanProcessor to BatchSpanProcessor and disable noisy per-library auto-instrumentation you do not need.

Steps

  1. When traces do not appear, verify the endpoint and protocol match first, then check the sampling config before assuming instrumentation is broken. Use the batch span processor in any production service. For traces that split across services, trace the traceparent header through every hop, including queues and background jobs where context is usually dropped.

When to use

You are seeing this: When traces do not appear, verify the endpoint and protocol match first, then check the sampling config before assuming instrumentation is broken. Use this skill when you run into "OTel no traces: check the endpoint, sampling, and exporter protocol match".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: A distributed tracing skill documents the no-traces-appearing checklist. Confirm the collector endpoint is reachable from the app, check that sampling is not dropping everything, read the app logs for exporter errors, and confirm the exporter library matches the backend protocol, since a Thrift, OTLP, or Zipkin mismatch silently exports nowhere. For high latency overhead, switch from SimpleSpanProcessor to BatchSpanProcessor and disable noisy per-library auto-instrumentation you do not need. For broken trace continuity, confirm context propagation across async boundaries and that downstream services parse the W3C traceparent header.

Verified resolution: When traces do not appear, verify the endpoint and protocol match first, then check the sampling config before assuming instrumentation is broken. Use the batch span processor in any production service. For traces that split across services, trace the traceparent header through every hop, including queues and background jobs where context is usually dropped.

Source URL: https://github.com/geekazoid80/skills-vault/blob/HEAD/distributed-tracing/SKILL.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_dCXYS0pHolOqqBXax-Ngdg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">OTel no traces: check the endpoint, sampling, and exporter protocol match <span>— Vectle</span></a>