wankai123 opened a new pull request, #34:
URL: https://github.com/apache/skywalking-horizon-ui/pull/34

   ### Alerting rules — running entities show their OAP node
   
   The **Operate › Alerting rules** detail pane's **Currently watching**
   list now spans the whole cluster and tags each entity with the OAP
   node evaluating it. Each OAP instance evaluates a rule independently
   over the slice of entities it holds, so the watched set is the union
   across nodes — the page previously showed only the first responding
   node's entities, which misread as "these are all the entities the rule
   watches." The list now aggregates every instance's entities and labels
   each row with its node (e.g. `SERVICE  agent::app  NODE 10.116.3.26_11800`),
   with the per-entity alarm message on hover. The per-node load-state
   table is unchanged. Single-instance deployments simply show one node
   label per row.
   
   Clicking a watched entity now opens a **running-context popup** — the
   live evaluation window the rule is
    computing for that entity, per OAP
   node. It shows the current state (`FIRING` / `SILENCED_FIRING` /
   `RECOVERY_OBSERVATION`), the window size and silence / recovery
   countdowns, the window end, the last-alarm time and message, and the
   per-metric snapshot the expression was evaluated against — rendered as
   a sparkline plus per-bucket values so an operator can see exactly why a
   rule is (or isn't) firing. Nodes not evaluating the entity are marked
   as such, and a raw-JSON disclosure carries the full payload.
   
   <img width="2526" height="1404" alt="7f9a495c2f475a86657306a09c058864" 
src="https://github.com/user-attachments/assets/1c3379d9-2648-4780-9a58-bc85a75f92ed";
 />
   <img width="2976" height="1756" alt="e318fe867de409774ffd03fe133bb33b" 
src="https://github.com/user-attachments/assets/8a032b87-7ba6-4165-8061-5eba112c4399";
 />
   


-- 
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]

Reply via email to