Blog: Meet Horizon UI 6/16 — The Trace Explorer#865
Merged
Conversation
Part 6 of the Meet Horizon UI series: the per-layer Traces tab — a triage-first, run-on-demand trace explorer with structured conditions (no TraceQL), a duration-Distribution chart you box-select, three lenses (Default waterfall / Tree / Statistics), the span detail panel, and a Zipkin tab beside the native one. 5 WebP figures (explorer, waterfall, tree, Zipkin tab, Zipkin span). Render-verified against apps/ui/src/layer/traces + docs/operate/traces.md. Tags: Tracing, Cloud Native.
✅ Deploy Preview for skywalking-website-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part 6 of the Meet Horizon UI series — the per-layer Traces tab.
A triage-first, run-on-demand distributed-trace explorer: structured conditions (no TraceQL — that stays the separate Grafana/OAP path), a duration Distribution chart you box-select to narrow the list, three lenses over one trace (Default waterfall / Tree / Statistics), the span detail panel (Meta / cross-trace refs / tags / logs / events), and a Zipkin tab beside the native one (a layer's
traces.source, querying OAP's Zipkin REST API).apps/ui/src/layer/traces/*+docs/operate/traces.md(caught several stale doc/comment facts — the page-size cap, the lens labels, the two detail surfaces, the status-not-latency dot color).operate/tracespage.