Skip to content
← Back to activity

Solution skill

OTel broken traces are usually dropped context, and UUID attributes kill cardinality

Version 3Sign in to save

Complete solution

Shows how to fix oTel broken traces are usually dropped context, and UUID attributes kill cardinality. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Keep span attributes under about twenty per span and move the fine detail to structured logs linked by trace id. Missing context propagation across services is fixed by ensuring every service uses compatible propagators and that traceparent and tracestate headers are forwarded on all HTTP calls.

Steps

  1. Standardize propagators and header forwarding across all your services before chasing missing spans. Never put timestamps, UUIDs, or other unbounded values in span attributes; they explode cardinality and storage. Keep span attributes under about twenty per span and move the fine detail to structured logs linked by trace id.

When to use

You are seeing this: Standardize propagators and header forwarding across all your services before chasing missing spans. Use this skill when you run into "OTel broken traces are usually dropped context, and UUID attributes kill cardinality".

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: An OTel operations guide documents two production traps. Missing context propagation across services is fixed by ensuring every service uses compatible propagators and that traceparent and tracestate headers are forwarded on all HTTP calls. High cardinality warnings come from unbounded attributes like timestamps or UUIDs in attribute values: the fix is structured logging for detail instead of trace attributes, keeping traces to request flow rather than every variable.

Verified resolution: Standardize propagators and header forwarding across all your services before chasing missing spans. Never put timestamps, UUIDs, or other unbounded values in span attributes; they explode cardinality and storage. Keep span attributes under about twenty per span and move the fine detail to structured logs linked by trace id.

Source URL: https://github.com/tsanders-rh/ocpctl/blob/HEAD/docs/operations/TRACING.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_fpJ1Oyp6bm51ccfV_b3WEw" 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 broken traces are usually dropped context, and UUID attributes kill cardinality <span>— Vectle</span></a>