[Alerting V2][Serverless & 9.5][M2] Alert changes from June 22, 2026#7078
Draft
nastasha-solomon wants to merge 3 commits into
Draft
[Alerting V2][Serverless & 9.5][M2] Alert changes from June 22, 2026#7078nastasha-solomon wants to merge 3 commits into
nastasha-solomon wants to merge 3 commits into
Conversation
This was referenced Jun 23, 2026
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates two alerts docs for the experimental alerting system with content from four M2 doc issues. Following the tech preview principle of accuracy over comprehensiveness, additions focus on stable concepts — what these features help users understand, when to use them, and how they fit into the system. Specific UI labels, breakdown option lists, color coding details, URL persistence specifics, and step-by-step procedures are deferred to post-preview docs.
Histogram chart and KPI panels on the alert episodes list (#6872, #6876)
PR #270922 added a histogram chart above the alert episodes table. PR #271147 added two KPI stat panels to the same page. Both surface aggregate information about alert episodes and respond to the active filter state and time range.
alerts/view-and-manage-alerts.md— Added a "Monitor alert health and trends" section between the space-scoping section and the filter/search section, which reflects where these panels sit in the UI. Covers KPI panels (aggregate counts that update as filters change) and the episode histogram (trend over time, brushing to narrow the global time filter, breakdown by dimensions). Includes a:::noteblock for the 10,000-episode query cap — included because it's an operational constraint users in large environments will encounter, not just a UI detail. A<!-- CONTENT NEEDED -->comment flags that the specific KPI panel labels and layout should be documented once the UI stabilizes before GA.What was omitted: specific KPI metric labels by panel name, all histogram breakdown option names, color coding for status badges, and URL persistence of selections. These are UI details likely to shift before GA.
Discover Alerts menu access and v2 flyout routing (#6878, #7010)
PR #267469 fixed a bug where the Discover Alerts menu was hidden for users with only
{{alerting-v2-system}}access. PR #272724 redesigned the Alerts menu and, when{{alerting-v2-system}}is enabled, routes rule creation to the v2 rule form instead of the Kibana alerting form.alerts/query-alerts-and-signals-in-discover.md— Added a "Create rules from Discover" section. This page is the only Discover-facing page in the alerts set, making it the appropriate home for Discover integration concepts until a dedicatedrules/create-rule-from-discover.mdpage is written. The section covers the access rule (either Kibana alerting access or{{alerting-v2-system}}access is sufficient; both are not required) and the routing behavior (v2 form when enabled, Kibana alerting form when disabled). A<!-- CONTENT NEEDED -->comment calls for step-by-step instructions and a link to the rules page once written, and notes that the Alerts menu UI was redesigned in 9.5.0 and should be verified before screenshots are added.What was omitted: the specific redesigned menu structure, screenshots, and detailed creation steps. These are deferred to the dedicated rule creation page.
Generative AI disclosure