wu-sheng opened a new pull request, #860: URL: https://github.com/apache/skywalking-website/pull/860
## Meet Horizon UI · 4/16: The Deployment Tab & BanyanDB Self-Observability Part 4 of the *Meet Horizon UI* series (follows #859). ### What this post covers - **The Deployment tab** — turns the topology map inward to show one clustered service's *own* instances: hexagon pods (main + sibling containers), clustered into role/tier boxes, tiered by call depth, with role-pair edges and a Flows table. - **BanyanDB self-observability (SWIP-15)** — SkyWalking's own database modeled as the cluster it is: **Cluster** (service) / **Container** (instance, carrying `container_name` role + `node_type` tier) / **Group** (endpoint = storage catalog), scraped via the FODC proxy. - The **Cluster** war-room dashboard, the role-adaptive **Container** dashboard (shown on a data/liaison node *and* the lifecycle sidecar), the per-data-model **Group** dashboard, and the **Flows** role-pair edge table. ### Assets - 6 figures under `static/screenshots/horizon-0.7.0/`, captured from the demo's clustered BanyanDB (liaison + data hot/warm/cold + lifecycle). - Tags: `Cloud Native`, `Storage`. ### Notes - Reviewed against the 0.7.0 render code and layer template (hexagon pods, `clusterBy`/`siblingBy`/`roleBy` rules, role-gated Container panels, per-data-model Group panels, role-pair edge families) — all verified. - The two Container figures show the role-gating directly (a data/liaison node vs the lifecycle node). - Container-edge metrics and the Flows table assume the OAP build exposes `SERVICE_INSTANCE_RELATION`; the post notes that precondition. - Part 4 of the series; later posts follow as separate PRs. Publish date `2026-06-21` adjustable before merge. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
