/oss · 1 merged

jaegertracing/jaeger

A tool for following requests as they move through many services, to find where things are slow or failing.

the project on GitHub (opens in a new tab)
  1. 16 Oct 2026

    Repeated spans no longer leave empty entries in a trace

    What was broken
    When the same piece of a trace arrived twice, for example after a retry, Jaeger removed the copy but kept the empty groups that had held it. Its newer trace API then returned entries with nothing in them.
    What I changed
    After removing copies, I made it also remove any groups left empty.
    Why it matters
    Tools that read traces from Jaeger get only real data, with no empty entries to trip over.

    see the code, #9836 (opens in a new tab)

← every project