Skip to content

Configure a frozen phase from the Streams data retention page #7283

Description

@florent-leborgne

Summary

On Elastic Stack, streams that use a specific retention period (data stream lifecycle) now get an Add data phase popover on the Streams Retention tab, replacing the previous Add delete phase button. It lets you add, edit, and remove a Frozen phase (hot to frozen to delete) and a Delete phase through a new Edit data phases flyout and timeline actions. The Frozen option requires an Enterprise license and a default snapshot repository: the popover shows badges for each missing requirement, selecting Frozen opens a gating modal that guides you to upgrade or create a repository, and Frozen is hidden entirely when there is no default repository and you lack the privilege to create one. Serverless keeps the Add delete phase flow with no frozen phase, and per-phase storage stats now count frozen searchable-snapshot data using total (primaries plus replicas) size.

Why this needs docs: The Streams retention page documents Add data phase and the Edit data phases flyout only for ILM-managed streams, so the new data-stream-lifecycle flow with its Enterprise license and default snapshot repository gating is a workflow users would otherwise miss.

Resources

  • PR #275706 — Streams: Introduce add data phases flow to Streams UI

Availability

Channel Details
Stack v9.5.0
Serverless N/A
Feature flag None — active by default

Created with Docs Quest Scanner by @florent-leborgne

Suggested edits

Manage data retention for Streams > Modify data lifecycle

  • What the docs say: When a stream follows an ILM policy, the Data lifecycle panel on the Retention tab displays the phases defined in that policy as a visual bar. [...] To add a new phase, click Add data phase and select the phase you want to add.
  • What to add: Phase editing is documented only for ILM-managed streams, and the section is tagged serverless-unavailable. On Elastic Stack, streams that use a specific retention period (data stream lifecycle) now also get an Add data phase popover offering Frozen and Delete, an Edit data phases flyout, and edit/remove actions from the timeline phase popovers. Document the frozen-phase requirements: an Enterprise license (badge on the option; selecting it opens a subscription gating modal) and a default snapshot repository, set by the persistent.repositories.default_repository cluster setting (badge plus a modal linking to repository creation, with a refresh to resume the flow); Frozen is hidden entirely when there is no default repository and the user lacks the privilege to create one, and editing an already-configured frozen phase always opens the flyout regardless of gating. State explicitly that serverless streams keep the Add delete phase button and have no frozen phase. Preserve the existing ILM-scoped content and scope the new flow separately. Stack only, from 9.5.0 (not available in serverless).

Metadata

Metadata

Assignees

Labels

Confidence: 1Scope and value are clearEffort: 0.5~2-3 days (0.5 week)Impact: 2Marginal improvement or harmReach: 3Common task or moderate surfaceTeam:SKIIssues owned by the SKI Docs Team

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions