You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
latitude spans query gains sort control (order-by on startTime / duration / cost, ascending or descending) and a status span filter (error / ok / unset) — enabling "top-N slowest/costliest spans" and error-only drill-downs.
latitude analytics query breakdown results now include a label — the human name for opaque signalId / cluster keys (the signal name / behavior-cluster name), so by-signal and by-behavior series are self-describing.
Changed
latitude analytics query percentile metric is now an arbitrary {kind:"percentile", field, p} (p in [1,99]) instead of the fixed p95. Use p: 95 for the previous p95 behavior.
Fixed
latitude spans query pagination no longer skips or duplicates spans that share a startTime (common in batch ingest). Paging now uses a stable keyset cursor over (sort key, spanId) instead of an offset, so results stay consistent even as new spans arrive mid-pagination. The --cursor value stays opaque — no usage change.