Repository navigation
[Alerting V2] Match the quoted UI labels to Kibana 9.6 - #9070
Open
nastasha-solomon wants to merge 3 commits into
Open
nastasha-solomon wants to merge 3 commits into
nastasha-solomon wants to merge 3 commits into
Conversation
Checks the labels that the Universal Alerting pages quote against the Kibana 9.6 branch and fixes the ones that differ: - Add how to open the Rules page in spaces that use the Classic solution view, where the Alerting section doesn't list Rules. - Use the Alerting > Execution History navigation path. - Rename the Policies tab and Policy column to Action policies and Action policy, and document the Failed (dispatch_failed) outcome. - Say that action policy API key failures appear in the execution history, not only in the Kibana server logs. - Name the Response filter on the Rules tab. Fixes elastic/docs-content-internal#1893 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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. |
The page is already tagged stack: ga 9.6+, and the sentence names the Classic solution view, which only exists on Stack. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The docs assume that users run the system on 9.6 with the solution navigation, not the Classic solution view. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch was successfully deployed
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 https://github.com/elastic/docs-content-internal/issues/1893.
Checks the UI labels that the Universal Alerting pages quote against the Kibana
9.6branch and fixes the ones that differ. Kibanamainhas the same labels.#9019 already removed every Alerting V2 label from
explore-analyze/alerting/esql/. Under elastic/docs-content-internal#2079, the docs describe only 9.6, so this PR doesn't keep any 9.5 labels.Changes
Execution history
dispatch_failedevent-log value and its five failure reasons.unmatchedstays documented as an event-log-only value.Authorization
The authorization errors table said that a missing or invalid action policy API key shows only in the Kibana server logs. In 9.6, the Action policies tab of the execution history shows the run as Failed, with
missing_api_keyorschedule_erroras the reason.Checked, no change needed
These labels already match Kibana
9.6:Open question for reviewers
The table that maps event-log outcomes to
.alert-actionsaction types doesn't coverdispatch_failed. From the dispatcher code, a failed dispatch still seems to writefireandnotifiedrecords. I'd like the Alerting team to confirm that before the table documents it.Preview
Generative AI disclosure
Tool(s) and model(s) used: Claude Opus 5.5, via Claude Code
🤖 Generated with Claude Code