Skip to content

Commit 503e482

Browse files
[REQUEST][9.0]: Update frozen tier support wording for DE (#1366)
### Description Contributes to #1328 by updating 9.0 docs for the "Manage data in cold and frozen tiers" section. Corresponding 8.18 doc updates: elastic/security-docs#6827 ### Preview Preview: [Manage data in cold and frozen tiers | Best practices](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1366/solutions/security/detect-and-alert#best-practices-data-tiers) - Updated lang in second bullet to show that frozen tiers don't have replicas by default.
1 parent 9cc3a7a commit 503e482

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

solutions/security/detect-and-alert.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Cold [data tiers](/manage-data/lifecycle/data-tiers.md) store time series data t
5353
### Best practices [best-practices-data-tiers]
5454
5555
* **Retention in hot tier**: We recommend keeping data in the hot tier ({{ilm-cap}} hot phase) for at least 24 hours. {{ilm-cap}} policies that move ingested data from the hot phase to another phase (for example, cold or frozen) in less than 24 hours may cause performance issues and/or rule execution errors.
56-
* **Replicas for mission-critical data**: Your data should have replicas if it must be highly available. Since frozen tiers don't support replicas, shard unavailability can cause partial rule run failures. Shard unavailability may be also encountered during or after {{stack}} upgrades. If this happens, you can [manually rerun](/solutions/security/detect-and-alert/manage-detection-rules.md#manually-run-rules) rules over the affected time period once the shards are available.
56+
* **Replicas for mission-critical data**: Your data should have replicas if it must be highly available. Since frozen tiers don't have replicas by default, shard unavailability can cause partial rule run failures. Shard unavailability may be also encountered during or after {{stack}} upgrades. If this happens, you can [manually rerun](/solutions/security/detect-and-alert/manage-detection-rules.md#manually-run-rules) rules over the affected time period once the shards are available.
5757
5858
### Limitations [limitations-data-tiers]
5959

0 commit comments

Comments
 (0)