-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RAM} Add refine search prompt to rule execution log #128982
[RAM} Add refine search prompt to rule execution log #128982
Conversation
@elasticmachine merge upstream |
@elasticmachine merge upstream |
Pinging @elastic/response-ops (Team:ResponseOps) |
💛 Build succeeded, but was flakyTest FailuresMetrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: |
@@ -256,6 +257,10 @@ export const RuleErrorLog = (props: RuleErrorLogProps) => { | |||
} | |||
}} | |||
/> | |||
<RefineSearchPrompt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
* Refine search prompt * Add refine prompt to error log table Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit 2fd6772)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
* Refine search prompt * Add refine prompt to error log table Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit 2fd6772) Co-authored-by: Jiawei Wu <[email protected]>
Summary
Resolves: #128811
Adds a prompt to notify the use that they should refine their search if it is too broad. Similar to how it is done in the discover plugin. The current threshold is 500 as discussed here: #127339 (comment)