Skip to content

[Alerting V2] [DOCS] [M2] Monitor alert health at a glance with KPI panels on the Alerting v2 episodes list #6876

Description

@nastasha-solomon

Summary

PR #271147 adds two KPI stat panels above the Alerting v2 alert episodes list, surfacing quick-glance metrics: total alerts, distinct firing rules, alerts assigned to the current user, unassigned alerts, acknowledged alerts, and snoozed alerts. The stats respect the page's active filter state and time range and are fetched via a single ES|QL STATS query. No Alerting v2 documentation exists yet; when it is created, the episodes list page documentation will need to describe these panels and explain how they respond to filters.

Why this needs docs: New prominent UI elements on a core page (episodes list) that change how users interpret alert health; the panels and their semantics need to be documented.

Resources

  • PR #271147 — [ResponseOps][Alerting v2] Add KPIs to episodes list page

Availability

Channel Details
Stack v9.5.0
Serverless Jun 8–Jun 12
Feature flag disabled

Created with Docs Quest Scanner by @nastasha-solomon

Suggested edits

Alerting v2 episodes list (page to be created) > KPI summary panels

  • What the docs say: No Alerting v2 documentation currently exists on the Elastic docs site.
  • What to add: When the episodes list page is documented, describe the two KPI panels displayed above the list: (1) Alerts — total alert count, distinct firing rules, and alerts assigned to the current user; (2) Alert actions — unassigned, acknowledged, and snoozed alerts. Explain that both panels update dynamically to reflect the active filter state and time range. Stack only (technical preview, feature flag required: xpack.alerting_v2.enabled: true), from 9.5.0.

Metadata

Metadata

Labels

Planned-S24SKI work planned for Sprint 24 (Jun 7-20)Team:ExperienceIssues owned by the Experience Docs Teamalerting-v2

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions