Documents ML anomaly detection and Stack Management alerts on the Observability Alerts page#6848
Merged
Conversation
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. |
Contributor
🔍 Preview links for changed docs |
Contributor
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Contributor
There was a problem hiding this comment.
Docs review summary
Focus areas
- Style and clarity: One minor wording suggestion to simplify the RBAC note. Vale found no issues with the modified lines.
- Jargon: No issues. The {{ml}} and {{stack-manage-app}} substitution variables are appropriate for UI labels.
- Frontmatter and applies_to: The
{applies_to}syntax is correct:stack: ga 9.5+properly indicates that ML and Stack Management alerts became visible starting in 9.5.0. Page-level frontmatter is complete with description, products, and applies_to fields. - Content type fit: The page functions as an overview, and the added content appropriately clarifies which alert types appear on the Alerts page without changing the page's purpose.
- Parent issue satisfaction: Satisfied. The PR fully addresses issue #6602 by enumerating the three supported alert type categories and explaining visibility based on feature privileges.
Notes
- The {{ml}} and {{stack-manage-app}} substitution variables appropriately represent UI labels and do not require spelling out the abbreviations.
- No additional inline comments were needed beyond the one minor style suggestion.
Generated by Docs review agent for issue #6848 · ● 582.4K
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
benironside
approved these changes
Jun 4, 2026
benironside
left a comment
Contributor
There was a problem hiding this comment.
text and preview LGTM!
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
Fixes #6602.
Updates the Observability Alerting overview to clarify which rule types surface alerts on the Alerts page. Previously, the page described how to view and filter alerts but gave no indication of which alert consumers were included, leaving users who create ML anomaly detection or Stack Management rules without any explanation for why those alerts might not appear.
Changes
solutions/observability/incident-management/alerting.md{applies_to} stack: ga 9.5to reflect that these alert types became visible on the Observability Alerts page in 9.5.0. Serverless inherits the page-levelserverless: gatag.Generative AI disclosure