wu-sheng opened a new pull request, #875: URL: https://github.com/apache/skywalking-website/pull/875
Part 10 of the **Meet Horizon UI** series — the first of Act 3 (operate). Horizon's active-alarms surface and how it answers "what is on fire right now, and why?" ### Content - **Incidents, not a wall of events** — raw firings merged by (entity, rule) into one incident; firing / recovered / **unstable** (flapping) states; `triggered N×` badge; the page owns its own 20m/2h/4h window (4h cap), independent of the global topbar. - **Replay why it fired** (hero) — the rule's MQE trigger expression plus the metric snapshot OAP captured at fire time, drawn back on a real-time axis with the window shaded and the trigger marked. - **From one incident to its whole history** — expand a `triggered N×` row into its per-firing timeline; brush the timeline to slice the list. - **Alarms follow you everywhere** — the same incident model on the topbar badge, the Active-alarms dashboard widget, and the topology / 3D map. - **Where it runs, and what it isn't** — observe-only off the query host (`alarms:read`); a read-only mirror of OAP's evaluation state; rules live in OAP's `alarm-settings.yml`, not edited here. ### Figures (4, WebP) 1. The incident list — ACTIVE KPI strip, firing/recovered timeline, `triggered N×` rows 2. The MQE snapshot replay — trigger expression + captured values, window shaded, trigger marked 3. A `triggered 4×` incident expanded into #1→#4 4. Alarms across the console — topbar badge, reddened topology, Active-alarms widget Render-verified against the alarm code and adversarially fact-checked; screenshots captured live from the demo backend. -- 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]
