You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by wu...@apache.org on 2026/06/21 12:25:06 UTC

(skywalking-website) branch master updated: Blog: Meet Horizon UI series — part 2 (Dashboards & MQE) + part-1 title alignment (#856)

This is an automated email from the ASF dual-hosted git repository.

wu-sheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/skywalking-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 81c4e732f0b Blog: Meet Horizon UI series — part 2 (Dashboards & MQE) + part-1 title alignment (#856)
81c4e732f0b is described below

commit 81c4e732f0bfef4044f397b919db3d2d6f97c07c
Author: 吴晟 Wu Sheng <wu...@foxmail.com>
AuthorDate: Sun Jun 21 20:25:00 2026 +0800

    Blog: Meet Horizon UI series — part 2 (Dashboards & MQE) + part-1 title alignment (#856)
    
    * docs(blog): add Horizon UI dashboards & MQE post (Horizon UI series, part 2)
    
    Second post of the Horizon UI series: how dashboards are built from MQE expressions, hide widgets that don't apply to the selected entity (skipping their queries server-side), render coded and raw-byte values readably (enum / duration / SI suffixes), tie every chart on the page to one synced crosshair, and jump from a slow-statement record straight into its trace. Six figures captured from the demo deployment.
---
 .../index.md                                       |  86 +++++++++++++++++++++
 .../index.md                                       |   2 +-
 .../p02-dashboards-01-instance-jvm.png             | Bin 0 -> 202568 bytes
 .../p02-dashboards-02-instance-go.png              | Bin 0 -> 186376 bytes
 .../p02-dashboards-03-si-suffix-axis.png           | Bin 0 -> 53621 bytes
 .../p02-dashboards-04-enum-duration-cards.png      | Bin 0 -> 101751 bytes
 .../p02-dashboards-05-synced-crosshair.png         | Bin 0 -> 86985 bytes
 .../p02-dashboards-06-record-jump-to-trace.png     | Bin 0 -> 309421 bytes
 8 files changed, 87 insertions(+), 1 deletion(-)

diff --git a/content/blog/2026-06-21-horizon-ui-dashboards-and-mqe/index.md b/content/blog/2026-06-21-horizon-ui-dashboards-and-mqe/index.md
new file mode 100644
index 00000000000..381151d309f
--- /dev/null
+++ b/content/blog/2026-06-21-horizon-ui-dashboards-and-mqe/index.md
@@ -0,0 +1,86 @@
+---
+title: "Meet Horizon UI · 2/16: Dashboards That Adapt — MQE, Smart Widgets, and Numbers Humans Can Read"
+date: 2026-06-21
+author: Sheng Wu
+description: "Part 2 of the Horizon UI series: how its dashboards are built from MQE expressions, hide the widgets that don't apply to the entity in front of you (skipping their queries on the server), and render OK instead of 1 and 45.1k instead of 4.51e4."
+tags:
+  - Metrics
+  - Cloud Native
+---
+
+This is the second post in the [Apache SkyWalking Horizon UI](/blog/2026-06-21-skywalking-horizon-ui-introduction/) series. The first one introduced the console and its layered navigation; this one is about the surface you spend most of your day on — the **dashboards**.
+
+Every dashboard in Horizon is the same machine: a grid of widgets, each one an **MQE expression** the BFF resolves against OAP. What makes the surface worth a post of its own is what that machine does *around* the numbers — it hides the widgets that don't apply to the entity you're looking at (and skips their queries entirely), it renders coded values and raw byte counts as things a human can read, it ties every chart on the page to one cursor, and it drops you from a slow-SQL row straig [...]
+
+## Every widget is one MQE expression
+
+A layer dashboard is a dense **12-column grid** (120px rows, gaps backfilled so a wall of tiles has no holes, collapsing to one column under ~1100px). Each tile is one of five widget types, and the type follows the *shape* of its MQE expression:
+
+- **`card`** — the expression collapses to a single scalar (`latest(...)`, `avg(...)`, `service_sla/100`). One big number.
+- **`line`** — a time series; one line per expression, optional dual y-axis for mixed units (throughput on the left, latency on the right).
+- **`top`** — a ranked list from `top_n(endpoint_cpm, 20, des)`, with a small tab switcher to flip the ranking between Traffic / Slow / Successful Rate.
+- **`record`** — record-shaped output like slow database statements or slow cache commands: rows of text + value.
+- **`table`** — a labeled `latest(...)` metric, one row per label combination (pod phase per service, node condition, replicas per deployment).
+
+You don't pick the chart; you write the MQE and the right widget renders it. And it's the *same* grid system at every altitude — the `dashboards.<scope>` map on a layer template carries a different widget set for the **service**, **instance**, and **endpoint** pages, so drilling down swaps the whole dashboard to the right scope. (All of these run on the BFF tier introduced in [part 1](/blog/2026-06-21-skywalking-horizon-ui-introduction/) — the browser never talks to OAP directly.)
+
+## A dashboard that adapts to the entity in front of you
+
+Here's the feature that changes how a dashboard *feels*. A widget can carry a **`visibleWhen`** gate, and when the gate doesn't hold, the widget doesn't render — and, crucially, **its query never runs**.
+
+There are two kinds of gate:
+
+- **MQE metric** — show the widget only when an expression *has value* (`op: exists`), or when its value crosses a threshold (`gt` / `lt`). Point a widget at its own metric and it self-gates: the JVM widgets carry `"visibleWhen": { "kind": "mqe", "expression": "instance_jvm_cpu", "op": "exists" }`, so they appear on a Java instance and vanish on a Go one.
+- **Entity attribute** — on the Instance scope, gate on the selected instance's attributes (`language eq JAVA`, or an attribute simply being present).
+
+Because the gate is evaluated **server-side**, a non-JVM instance doesn't just hide the JVM tiles — the BFF never sends their queries to OAP at all. Open the same Instance dashboard for a JVM service and a non-JVM one and you're looking at one template adapting itself, not two hand-built pages:
+
+![Figure 1: A Java service's Instance dashboard — the JVM widget group (CPU, heap, GC, threads, classes) is present because `instance_jvm_cpu` returns data.](/screenshots/horizon-0.7.0/p02-dashboards-01-instance-jvm.png)
+Figure 1: On a JVM instance the JVM widgets render — their `visibleWhen` gate holds.</br>
+
+![Figure 2: The same Instance dashboard on the Go "rating" service — the JVM group is simply absent and the grid has reflowed; those widgets' queries were never sent to OAP.](/screenshots/horizon-0.7.0/p02-dashboards-02-instance-go.png)
+Figure 2: The same dashboard on a Go instance — the JVM widgets aren't there, and their queries never ran. One template, adapting to the entity.</br>
+
+## Numbers humans can read
+
+Raw metrics are not always readable metrics. Horizon's widgets format three cases that used to make operators do math in their heads:
+
+- **`enum`** — a value→label map turns a coded gauge into words: a `1/0` success metric renders **`OK`** / **`Failed`** instead of the bare number. The labels are translatable per locale.
+- **`duration`** — a metric in seconds renders as a human time-ago: **`5m 20s ago`**, compact to `5m` / `2h` on an axis.
+- **SI suffixes** — large magnitudes on chart axes and tooltips read as **`45.1k`**, **`1.34M`**, **`2.5G`** rather than `4.51e4`, with the axis tick and its hovered value sharing one notation.
+
+![Figure 3: A line chart whose y-axis and crosshair tooltip both read in compact SI suffixes (45.1k, 1.34M) — the tick and the hovered value in one notation.](/screenshots/horizon-0.7.0/p02-dashboards-03-si-suffix-axis.png)
+Figure 3: Dense byte and count series get compact SI suffixes, axis and tooltip in step.</br>
+
+![Figure 4: Two BanyanDB cards — "Last Sync" showing OK (from a coded 1 via an enum map) and "Time Since Last Sync" showing "5m 20s ago" (from a seconds metric via the duration format).](/screenshots/horizon-0.7.0/p02-dashboards-04-enum-duration-cards.png)
+Figure 4: The `enum` and `duration` formats in action on BanyanDB's lifecycle cards — `OK` instead of `1`, "5m 20s ago" instead of a seconds count.</br>
+
+## Read the whole grid as one timeline
+
+Every `line` chart on a page shares **one hover cursor**. Point at minute 32 on the throughput chart and minute 32 lights up on the latency chart, the error-rate chart, and every sparkline tile. The contract is enforced at the chart-wrapper level — no widget can opt out — so the page reads as a single coordinated view of one moment, not a dozen independent charts. The multi-series tooltip is a fixed, aligned table that shows each series' **title** (never the raw MQE), with values in one  [...]
+
+![Figure 5: The synced crosshair sweeping across the throughput, error-rate and latency panels — one cursor, one moment, every chart aligned.](/screenshots/horizon-0.7.0/p02-dashboards-05-synced-crosshair.png)
+Figure 5: One cursor moves across every line chart on the page, so you read the same instant everywhere at once.</br>
+
+## From a slow row to its trace, in one click
+
+`record` widgets — Slow Statements, Slow Commands, Slow Database Statements — are lists of sampled records, and each row that carries a trace id gets a **jump-to-trace** icon at its head that opens the originating trace's waterfall. It resolves the trace **by id, not by layer**, which matters: the Slow Statements on a Virtual Database / Cache / MQ service belong to the *caller* on another layer, and a virtual-target layer has no traces tab of its own — yet the jump still lands. The state [...]
+
+![Figure 6: A Slow Statements record widget — each sampled row with a jump-to-trace icon (where the sample has a trace id), the statement text click-to-copy, one row showing the "copied" flash.](/screenshots/horizon-0.7.0/p02-dashboards-06-record-jump-to-trace.png)
+Figure 6: From a slow statement to the trace that ran it — resolved by trace id, so it works even on a virtual layer with no traces tab of its own.</br>
+
+## Pin and compare entities *(preview)*
+
+Sometimes one entity isn't enough. Horizon 0.7.0 ships an opt-in preview that lets you **lock several services, instances, or endpoints — even ones from different services — and compare them in place**. The entity you're viewing is always part of the cohort (tagged `CURRENT`), and each pin adds its own hue; every widget then compares inline — line widgets overlay one series per entity, cards show a row each, `top` and `record` widgets get per-entity tabs, tables gain an Entity column. It [...]
+
+## The time picker moves the *whole* dashboard
+
+The topbar time range drives everything on the page — the header KPI strip, the widget body, and (on BanyanDB's tiered hot/warm/cold storage) the **Cold** pill flow end-to-end. Earlier the landing and topology routes were pinned to the last 60 minutes, so picking "12 days ago" quietly kept showing recent numbers; now the picker is honored everywhere, and when an upstream control changes, each dependent tile visibly resets and shows a "Reading data…" hint rather than leaving a stale value [...]
+
+## Where to go next
+
+It's worth stressing that this is *one* system. The same five widgets, the same MQE, the same gating render every layer's dashboard — the JVM panels above, BanyanDB's lifecycle cards, the percentile latency on a mesh service, and purpose-built panels for things like an Envoy AI Gateway (token throughput, time-to-first-token) or a GenAI virtual layer (per-model estimated cost). What changes from layer to layer is the MQE, not the machinery.
+
+Everything above is the *reading* experience. Each widget's MQE, its `visibleWhen` gate, its format, and the per-scope grids are all editable from the **Layer dashboards** admin — but that authoring story (draft → preview → publish, with the inline-and-expand MQE editor) is its own post later in the series. For the field-level reference, see the docs on [dashboard widgets](https://skywalking.apache.org/docs/) and charts.
+
+Next up: **topology and service dependency** — the same data Horizon charts here, drawn as a map you can walk.
diff --git a/content/blog/2026-06-21-skywalking-horizon-ui-introduction/index.md b/content/blog/2026-06-21-skywalking-horizon-ui-introduction/index.md
index 03002b9c206..54edabd03ef 100644
--- a/content/blog/2026-06-21-skywalking-horizon-ui-introduction/index.md
+++ b/content/blog/2026-06-21-skywalking-horizon-ui-introduction/index.md
@@ -1,5 +1,5 @@
 ---
-title: "Meet Horizon UI: SkyWalking's New Observability Console"
+title: "Meet Horizon UI · 1/16: SkyWalking's New Observability Console"
 date: 2026-06-21
 author: Sheng Wu
 description: "Introducing Apache SkyWalking Horizon UI — the next-generation web UI. A greenfield rewrite on the same OAP backend that you can observe, operate, govern, and customize, starting with a sidebar that mirrors your whole estate."
diff --git a/static/screenshots/horizon-0.7.0/p02-dashboards-01-instance-jvm.png b/static/screenshots/horizon-0.7.0/p02-dashboards-01-instance-jvm.png
new file mode 100644
index 00000000000..ede09deef46
Binary files /dev/null and b/static/screenshots/horizon-0.7.0/p02-dashboards-01-instance-jvm.png differ
diff --git a/static/screenshots/horizon-0.7.0/p02-dashboards-02-instance-go.png b/static/screenshots/horizon-0.7.0/p02-dashboards-02-instance-go.png
new file mode 100644
index 00000000000..9f438af7749
Binary files /dev/null and b/static/screenshots/horizon-0.7.0/p02-dashboards-02-instance-go.png differ
diff --git a/static/screenshots/horizon-0.7.0/p02-dashboards-03-si-suffix-axis.png b/static/screenshots/horizon-0.7.0/p02-dashboards-03-si-suffix-axis.png
new file mode 100644
index 00000000000..e1b4cd1dcd8
Binary files /dev/null and b/static/screenshots/horizon-0.7.0/p02-dashboards-03-si-suffix-axis.png differ
diff --git a/static/screenshots/horizon-0.7.0/p02-dashboards-04-enum-duration-cards.png b/static/screenshots/horizon-0.7.0/p02-dashboards-04-enum-duration-cards.png
new file mode 100644
index 00000000000..41fa6a46814
Binary files /dev/null and b/static/screenshots/horizon-0.7.0/p02-dashboards-04-enum-duration-cards.png differ
diff --git a/static/screenshots/horizon-0.7.0/p02-dashboards-05-synced-crosshair.png b/static/screenshots/horizon-0.7.0/p02-dashboards-05-synced-crosshair.png
new file mode 100644
index 00000000000..089104ace1f
Binary files /dev/null and b/static/screenshots/horizon-0.7.0/p02-dashboards-05-synced-crosshair.png differ
diff --git a/static/screenshots/horizon-0.7.0/p02-dashboards-06-record-jump-to-trace.png b/static/screenshots/horizon-0.7.0/p02-dashboards-06-record-jump-to-trace.png
new file mode 100644
index 00000000000..f45248be5f4
Binary files /dev/null and b/static/screenshots/horizon-0.7.0/p02-dashboards-06-record-jump-to-trace.png differ