[Alerting] Surface guidance for rules missing an Elastic Cloud API key - #7827
Open
nastasha-solomon wants to merge 9 commits into
Open
[Alerting] Surface guidance for rules missing an Elastic Cloud API key#7827nastasha-solomon wants to merge 9 commits into
nastasha-solomon wants to merge 9 commits into
Conversation
The check for rules running on a fallback Elasticsearch API key was buried in a 90-day post-migration dropdown, but it applies any time a rule is created or updated via the public APIs with a personal key. Pull it into a standalone, always-visible section and update the tag label to match the current Kibana source (Missing Universal Api Key). Fixes #7826. Co-authored-by: Cursor <cursoragent@cursor.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
✅ 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
🔍 Preview links for changed docs |
nastasha-solomon
marked this pull request as ready for review
August 7, 2026 19:59
bmorelli25
reviewed
Aug 11, 2026
|
|
||
| :::{dropdown} Right after migration | ||
| - **Check rule execution status**: Go to **{{stack-manage-app}} > {{rules-ui}}** or your app's rules page and review the last run status for all rules. Investigate any rules showing a failed or warning status before moving on. If you use Elastic Security detection rules, also check for gaps caused by the migration. Refer to [Fill rule execution gaps](/solutions/security/detect-and-alert/fill-rule-gaps.md) for instructions. | ||
| - **Check rule execution status**: Go to **{{stack-manage-app}} > {{rules-ui}}** or your app's rules page and review the last run status for all rules. Investigate any rules showing a failed or warning status before moving on. If you use {{elastic-sec}} detection rules, also check for gaps caused by the migration. Refer to [Fill rule execution gaps](/solutions/security/detect-and-alert/fill-rule-gaps.md) for instructions. |
Member
There was a problem hiding this comment.
Does this need to be updated to use Rules or Detection rules (SIEM) depending on the project type? (like you did above)
Member
Author
There was a problem hiding this comment.
yeah, being more precise wouldn't hurt. Consistency across the page is good too, I suppose! I'll fix it.
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
2 participants
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
Makes the guidance for rules missing an Elastic Cloud API key visible without expanding a dropdown, and updates the tag label to match the current Kibana source.
Fixes #7826.
Preview
Missing Elastic Cloud API Keytag (formerly namedMissing Universal Api Key).Generative AI disclosure
Made with Cursor