Skip to content

[8.16]excludedDataTiersForRuleExecution advanced setting applies to ES|QL rules #5957

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Oct 23, 2024
Merged

[8.16]excludedDataTiersForRuleExecution advanced setting applies to ES|QL rules #5957

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e2c2d1f
First draft
nastasha-solomon Oct 18, 2024
7e6d064
Merge branch 'main' into issue-5955-frozen-cold-tier-esql
nastasha-solomon Oct 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/getting-started/advanced-setting.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -182,7 +182,7 @@ The `securitySolution:alertTags` field determines which options display in the a

To ensure rules don't search cold and frozen data when executing, specify cold and frozen {ref}/data-tiers.html[data tiers] in the `excludedDataTiersForRuleExecution` field. Multiple data tiers must be separated by commas, for example: `data_frozen`, `data_cold`. This setting is turned off by default; turning it on can improve rule performance and reduce execution time.

This setting does not apply to {esql} or {ml} rules.
This setting does not apply to {ml} rules.

[TIP]
====
Expand Down