-
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
Create search:search_excluded_data_tiers setting #192276
Create search:search_excluded_data_tiers setting #192276
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
d525cca
to
c555f1b
Compare
/ci |
ff94759
to
94d1444
Compare
94d1444
to
1e4487c
Compare
@elasticmachine merge upstream |
/ci |
/ci |
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
Co-authored-by: Nathan L Smith <[email protected]>
💚 Build Succeeded
Metrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
Would this also be applied to the Synthetics (being part of O11y I would say so)? |
The filtering out of data tiers won't be automatic. Teams will have to implement that usage of the parameter created here to decide when the filter needs to be applied. |
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.
Thx for taking care of this, however need to block this for now. we need internal alignment about introducing a new setting for this, will follow up in slack
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.
Did not test locally, but Core changes LGTM
I had a chat with @elastic/kibana-data-discovery and we've agreed that it will be better to move forward with a solution-specific setting. I'm closing this in favor of #192570 |
…ata tiers from queries (#192570) part of [#190559](#190559) ## Summary This PR introduces a new `Advanced Settings` under `Observabilty` to provide a way of configuring the exclusion of indices in the `data_cold` and/or `data_frozen` tiers from queries. The change will help to address issues encountered in O11y, most specifically in APM, and could also affect Infra and other features, with unbounded queries targeting the frozen tier. ### For reviewers This PR replaces #192276 --------- Co-authored-by: Elastic Machine <[email protected]>
…ata tiers from queries (elastic#192570) part of [elastic#190559](elastic#190559) ## Summary This PR introduces a new `Advanced Settings` under `Observabilty` to provide a way of configuring the exclusion of indices in the `data_cold` and/or `data_frozen` tiers from queries. The change will help to address issues encountered in O11y, most specifically in APM, and could also affect Infra and other features, with unbounded queries targeting the frozen tier. ### For reviewers This PR replaces elastic#192276 --------- Co-authored-by: Elastic Machine <[email protected]> (cherry picked from commit f029f80)
…ding data tiers from queries (#192570) (#193784) # Backport This will backport the following commits from `main` to `8.x`: - [[Observability] Create observability-specific setting for excluding data tiers from queries (#192570)](#192570) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Carlos Crespo","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-09-16T14:58:13Z","message":"[Observability] Create observability-specific setting for excluding data tiers from queries (#192570)\n\npart of [#190559](https://github.com/elastic/kibana/issues/190559)\r\n\r\n## Summary\r\n\r\nThis PR introduces a new `Advanced Settings` under `Observabilty` to\r\nprovide a way of configuring the exclusion of indices in the `data_cold`\r\nand/or `data_frozen` tiers from queries.\r\n\r\nThe change will help to address issues encountered in O11y, most\r\nspecifically in APM, and could also affect Infra and other features,\r\nwith unbounded queries targeting the frozen tier.\r\n\r\n### For reviewers\r\n\r\nThis PR replaces https://github.com/elastic/kibana/pull/192276\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"f029f8086a6731b5f435775c915d46e110a34658","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","v9.0.0","ci:project-deploy-observability","Team:obs-ux-infra_services","Team:obs-ux-management"],"number":192570,"url":"https://github.com/elastic/kibana/pull/192570","mergeCommit":{"message":"[Observability] Create observability-specific setting for excluding data tiers from queries (#192570)\n\npart of [#190559](https://github.com/elastic/kibana/issues/190559)\r\n\r\n## Summary\r\n\r\nThis PR introduces a new `Advanced Settings` under `Observabilty` to\r\nprovide a way of configuring the exclusion of indices in the `data_cold`\r\nand/or `data_frozen` tiers from queries.\r\n\r\nThe change will help to address issues encountered in O11y, most\r\nspecifically in APM, and could also affect Infra and other features,\r\nwith unbounded queries targeting the frozen tier.\r\n\r\n### For reviewers\r\n\r\nThis PR replaces https://github.com/elastic/kibana/pull/192276\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"f029f8086a6731b5f435775c915d46e110a34658"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/192570","number":192570,"mergeCommit":{"message":"[Observability] Create observability-specific setting for excluding data tiers from queries (#192570)\n\npart of [#190559](https://github.com/elastic/kibana/issues/190559)\r\n\r\n## Summary\r\n\r\nThis PR introduces a new `Advanced Settings` under `Observabilty` to\r\nprovide a way of configuring the exclusion of indices in the `data_cold`\r\nand/or `data_frozen` tiers from queries.\r\n\r\nThe change will help to address issues encountered in O11y, most\r\nspecifically in APM, and could also affect Infra and other features,\r\nwith unbounded queries targeting the frozen tier.\r\n\r\n### For reviewers\r\n\r\nThis PR replaces https://github.com/elastic/kibana/pull/192276\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"f029f8086a6731b5f435775c915d46e110a34658"}}]}] BACKPORT-->
part of #190559
Summary
This PR introduces a new Kibana-wide
Advanced Settings
underSearch
, enabling solutions to exclude indices in thedata_cold
and/ordata_frozen
tiers from their queries.The change will help to address issues encountered by O11y, Stack Monitoring, and Security Solutions with unbounded queries targeting the frozen tier. By centralizing this setting, we prevent each solution from implementing its own version.
For example, the
securitySolution:excludedDataTiersForRuleExecution
setting in Security could be replaced by the one introduced in this PR.Additionally, this setting could potentially replace the soon to be deprecated
includeFrozen
setting.Follow-up
It might be a good idea to change the
get_search_params.ts
and other places in thedata
plugin to look at the configuration.