7 posts tagged with "Traces"

Reading what your models cost is not the same as being able to act on it. This release closes that gap — and it opens by fixing a way of reading those spans that turned out to be wrong.

v0.11.0 adds no collection at all. Every feature in it reads spans avuru obs has been storing since your first five minutes, and asks them questions the product could not previously ask — so an install that upgrades sees its history, not just what arrives next.

avuru obs v0.1.0 is tagged: install the Helm chart on a fresh Kubernetes cluster and watch a live service map appear in under five minutes, zero app changes — a promise enforced in CI, not a demo.

The Metrics screen is live: request rate, error percentage and latency percentiles over time for the busiest services of the window — derived from the same spans the trace explorer uses, so there is nothing extra to instrument or operate.

The trace explorer moved to a split layout: the trace list stays on the left while the detail opens on the right, so hopping between traces is one click. Clicking a span now opens a side panel (no more inline expand), and a maximize button pops the whole thing to a full-window view.

Open any trace in a full-window explorer and switch between six different views of the same trace — no context lost.

The trace search grew a proper filter panel — so you can slice by what actually matters.