Part 13 of the Meet Horizon UI series: three read-only introspection surfaces that turn the lens on the backend itself — Cluster Status (is OAP healthy, across which ports), OAP Configuration (the effective runtime config), and Data Retention (how long each class of data lives, including BanyanDB's hot/warm/cold lifecycle).
Part 14 of the Meet Horizon UI series: Horizon's own access control — server-enforced RBAC with four roles, local and LDAP/AD authentication, an append-only audit log, an LDAP-only break-glass hatch, and five themes. All of it lives in Horizon's BFF and works the same on any OAP version.
Part 15 of the Meet Horizon UI series: the whole console is driven by templates you can edit. Open any layer or overview as a template, change its widgets, components, and labels in a local draft, preview it, and publish it to OAP for the whole org — with diff-before-push and export/import.
Part 10 of the Meet Horizon UI series: the incident-centric active-alarms surface — re-fires merged into one row, the MQE snapshot that fired a rule replayed on a single chart, and the same incident model carried across the topbar badge, dashboards, and the 3D map.
Part 7 of the Meet Horizon UI series: two log surfaces — a stored, indexed, trace-correlated log stream with a level histogram, and an on-demand live tail of a Kubernetes pod's container logs.
Part 5 of the Meet Horizon UI series: a single WebGL view of your whole deployment — every layer's services as cubes stacked on tiers, with live traffic, alarm beacons, and the calls between them.
Part 6 of the Meet Horizon UI series: a per-layer distributed-trace explorer — staged conditions, a duration-distribution chart you can box-select, three ways to read one trace, and a Zipkin tab beside the native one.
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.
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.
Part 3 of the Meet Horizon UI series: one template-driven topology engine that repaints for every layer, a filter to cut the noise, drill-down from a call into instances, the endpoint-dependency graph, and the cross-layer Smartscape overlay.
Part 4 of the Meet Horizon UI series: the Deployment tab turns the topology map inward to show one clustered service's own instances, and BanyanDB is modeled as the role- and tier-aware cluster it is — SkyWalking finally watching its own database the way it watches everything else.
Set up full-stack observability for your AI/LLM traffic using Envoy AI Gateway, SkyWalking OAP 10.4.0, and BanyanDB 0.10.0.