[docs-scanner] Inconsistent retention information for cloud-delivered audit records

Geschlossen
  • Stimmt etwas nicht?
#26,548 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@craig-osterhout arbeitet bereits daran.

Seit 05.11.2026.

  • #26553 von @craig-osterhout — gemerged

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
58/100
Issue-Typ
Dokumentation
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
docker, markdown
Bereich
documentation

Rechercherichtung

Read content/manuals/ai/governance/organization/audit/_index.md and content/manuals/ai/governance/organization/audit/configure.md and confirm the retention policy with the relevant source or maintainer, since the issue does not establish whether the periods overlap. Update both statements to describe the same policy clearly; done means readers get consistent retention information on both pages.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Files:

  • content/manuals/ai/governance/organization/audit/_index.md
  • content/manuals/ai/governance/organization/audit/configure.md
Issue

The two files give inconsistent information about how long Docker Cloud keeps audit records:

In _index.md under "Data handling":

Docker stores audit records in Docker Cloud for 90 days.

In configure.md under "Configure delivery":

Docker Cloud keeps audit records searchable in the hosted audit log view for 90
days, and in archive storage for 90 days.

The first statement suggests records are kept for 90 days total. The second statement suggests records are searchable for 90 days AND kept in archive storage for another 90 days (implying 180 days total retention, or possibly overlapping periods).

Why this matters

A reader trying to understand data retention for compliance or planning purposes will get conflicting information depending on which page they read. This affects decisions about whether to export records before they're deleted and how to plan backup strategies.

Suggested fix

Clarify the retention policy consistently across both files. If records are searchable for 90 days and then archived for another 90 days (180 days total), state this clearly in both places. If the 90 days overlap (searchable for 90 days, with archive storage also being 90 days total), clarify that as well.

For example, if they overlap:

Docker stores audit records in Docker Cloud for 90 days. Records remain searchable in the hosted audit log view for the full 90 days.

Or if they're sequential:

Docker stores audit records in Docker Cloud for 180 days: 90 days searchable in the hosted audit log view, followed by 90 days in archive storage.

Found by nightly documentation quality scanner

Vorherrschende Sprache
Markdown
Sterne
4.7k
Forks
8.5k
Ø Merge
2 T. 11 Std.
Gemergte PRs (30 T.)
135

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus docker/docs

Alle Issues in docker/docs

Ähnliche Issues

Weitere Issues zu Documentation

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.