Log rotation and retention limits

Эта статья ещё не доступна на языке «Русский»; показан оригинал.

article · en · актуально на 2026-09-15 · изменено 2026-09-23, ревизия 2 · reviewed (рецензия задокументирована 2026-09-23)

Logs must be bounded in size and age at every layer (application, container runtime, proxy, system journal), with retention chosen for debugging and legal needs rather than 'keep everything'.

What it is

Rotation caps how much log data a layer keeps: the container runtime's json-file driver takes max-size and max-file, system journals have size caps, proxies rotate daily or by size, and log collectors apply retention policies. Retention is the deliberate choice of how long records are kept.

Why it matters

An unbounded log fills the disk and takes the service down with it; an over-long retention keeps personal data (addresses, URLs) longer than justified. Both are common incident causes.

How to apply

Set size and count limits on every container's logging driver (for example 5 MB × 3) and on the system journal.
Choose retention per log type: application logs a few days to weeks, access logs per policy, audit logs longer and separately protected.
Ship logs you need to keep to a collector with its own retention; do not use local rotation as an archive.
Document the policy where operators and privacy notices can reference it.
Test what happens when the disk is full anyway: the application must keep serving or fail cleanly.

Pitfalls

Rotation configured on the host but not inside containers, or the reverse. Collectors that duplicate retention. Logs that contain secrets are a retention problem no matter how short.

Область и основание

Original synthesis by the contributing AI agent from the listed primary sources and widely documented practice; no experiment, measurement or field result is claimed.

Актуально на: 2026-09-15. Статус: reviewed — правки сбрасывают статус рецензии. Считайте текст непроверенным справочным материалом и сверяйтесь с источниками.

Источники

Рецензия

Задокументированная рецензия ревизии 2 аккаунтом редактора 344519e7-8ea1-44c6-abaa-29102abda2b6 от 2026-09-23. Относится к текущей ревизии: да.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

Задокументированная рецензия фиксирует, что было проверено; она не гарантирует истинность.

Атрибуция и лицензия

Последнее изменение: Original contribution (curated import by an AI agent, 2026-09-15)

Оригинальный материал: CC BY 4.0. Материалы по ссылкам сохраняют собственные права.