Skip to content
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

Provide Kibana Setting to Hide Shard Failure Warnings in UI #106516

Closed
therealdwright opened this issue Jul 22, 2021 · 3 comments
Closed

Provide Kibana Setting to Hide Shard Failure Warnings in UI #106516

therealdwright opened this issue Jul 22, 2021 · 3 comments
Labels
enhancement New value added to drive a business result Feature:Search Querying infrastructure in Kibana impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:medium Medium Level of Effort Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.

Comments

@therealdwright
Copy link

therealdwright commented Jul 22, 2021

Describe the feature:
I would like to propose a configuration setting to hide shard failure warnings from displaying in the Kibana UI. Failures would still be logged and could be alerted on but would not be displayed in the search/discover UI like the screenshot below.
Screen Shot 2021-07-22 at 8 35 52 pm

Describe a specific use case for the feature:

Sometimes users will perform inefficient queries such as a plaintext query across multiple indices. While this is not ideal, it's to be expected of non-technical users. Administrators want to monitor for such events (through cluster logs) and alert accordingly. From here a decision can be made to adjust the max_clause_count or disregard.

However, the current UX is very intrusive and leads to users reporting that the search functionality is broken.

Suggested solution:

Provide a setting in Kibana, for example hide_ui_shard_warnings (defaults to false) to suppress this behaviour.

@botelastic botelastic bot added the needs-team Issues missing a team label label Jul 22, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServices)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jul 26, 2021
@lukasolson lukasolson added the Feature:Search Querying infrastructure in Kibana label Jul 29, 2021
@lukasolson lukasolson added the enhancement New value added to drive a business result label Sep 20, 2021
@exalate-issue-sync exalate-issue-sync bot added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Apr 18, 2022
@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels May 23, 2022
@exalate-issue-sync exalate-issue-sync bot added impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. and removed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Oct 20, 2022
@petrklapka petrklapka added Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. and removed Team:AppServicesSv labels Nov 23, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@lukasolson
Copy link
Member

Thanks for contributing this issue. At this time, we don't plan to expose an advanced setting for this purpose, but we are actively working on improving the content and frequency of these warnings.

The following issues give a better idea of our plans:

Please comment if you think there's a reason to re-open this issue if those improvements are made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Search Querying infrastructure in Kibana impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:medium Medium Level of Effort Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
Projects
None yet
Development

No branches or pull requests

5 participants