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 9cd56eebbe9 docs(blog): point Horizon UI posts' doc handoffs at real
doc pages (#864)
9cd56eebbe9 is described below
commit 9cd56eebbe9c1ab62b2d38de8e93896a8f875439
Author: 吴晟 Wu Sheng <[email protected]>
AuthorDate: Mon Jun 22 20:45:19 2026 +0800
docs(blog): point Horizon UI posts' doc handoffs at real doc pages (#864)
P1/P2/P3 linked the generic https://skywalking.apache.org/docs/ root as a
placeholder. Point each at its real Horizon UI doc page: intro -> readme,
dashboards -> components/dashboard-widgets + components/charts, topology ->
customization/layer-templates.
---
content/blog/2026-06-21-horizon-ui-dashboards-and-mqe/index.md | 2 +-
content/blog/2026-06-21-horizon-ui-topology-and-dependency/index.md | 2 +-
content/blog/2026-06-21-skywalking-horizon-ui-introduction/index.md | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
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
index c2b1882b1e9..b011c00fd36 100644
--- 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
@@ -84,6 +84,6 @@ The topbar time range drives everything on the page — the
header KPI strip, th
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.
+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/skywalking-horizon-ui/next/components/dashboard-widgets/)
and [charts](https://sk [...]
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-horizon-ui-topology-and-dependency/index.md
b/content/blog/2026-06-21-horizon-ui-topology-and-dependency/index.md
index 3f9a3470502..0642f731636 100644
--- a/content/blog/2026-06-21-horizon-ui-topology-and-dependency/index.md
+++ b/content/blog/2026-06-21-horizon-ui-topology-and-dependency/index.md
@@ -67,6 +67,6 @@ Figure 7: One service, every layer it reports through — the
cross-layer hierar
## Where to go next
-Every metric, threshold, and edge weight on these maps lives in the layer
template's `topology` block — which means you tune them the same config-driven
way you tune dashboards, the subject of a later post in this series. For the
field reference, see the [layer-template](https://skywalking.apache.org/docs/)
topology docs.
+Every metric, threshold, and edge weight on these maps lives in the layer
template's `topology` block — which means you tune them the same config-driven
way you tune dashboards, the subject of a later post in this series. For the
field reference, see the
[layer-template](https://skywalking.apache.org/docs/skywalking-horizon-ui/next/customization/layer-templates/)
topology docs.
Next up: **the Deployment tab and BanyanDB self-observability** — where the
same map technique turns *inward* to show how one clustered service's own
instances are deployed and talk to each other.
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 e1e4a2ce8c8..9f2576cefaa 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
@@ -138,7 +138,7 @@ auth:
Open `http://<host>:8081/`, log in, and the first stop is **Cluster Status**
to confirm Horizon and OAP are talking. From there, the sidebar fills in with
your estate.
-For the full setup path — binary tarball, Kubernetes, LDAP, TLS, and the
production checklist — see the [Horizon UI
documentation](https://skywalking.apache.org/docs/), which covers setup,
compatibility, access control, customization, components, and operations from
its left-side menu.
+For the full setup path — binary tarball, Kubernetes, LDAP, TLS, and the
production checklist — see the [Horizon UI
documentation](https://skywalking.apache.org/docs/skywalking-horizon-ui/next/readme/),
which covers setup, compatibility, access control, customization, components,
and operations from its left-side menu.
## Other notable points
