From 10ce4f638ba98f759973830920adc4a4d762fb89 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 25 Nov 2025 09:27:21 +0000 Subject: [PATCH 1/2] docs: document config-db default retention periods Co-authored-by: adityathebe <13419481+adityathebe@users.noreply.github.com> --- .../docs/guide/config-db/concepts/retention.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/mission-control/docs/guide/config-db/concepts/retention.md b/mission-control/docs/guide/config-db/concepts/retention.md index a06ae8be..c022377b 100644 --- a/mission-control/docs/guide/config-db/concepts/retention.md +++ b/mission-control/docs/guide/config-db/concepts/retention.md @@ -7,6 +7,18 @@ sidebar_custom_props: After scraping we can choose to retain results on the basis of name, age, count and more. +## Default Retention Periods + +When retention rules are not explicitly configured, config-db applies the following default retention periods: + +| Type | Default Period | Description | +| --------------- | -------------- | --------------------------------------------------- | +| Config Items | 7 days | Configuration items are retained for 7 days | +| Changes | 60 days | Change records are retained for 60 days | +| Config Analysis | 60 days | Configuration analysis data is retained for 60 days | + +These defaults ensure that your database doesn't grow unbounded while maintaining a reasonable history of configuration changes and analysis. + The retention rules are applied for each unique catalog item. If `changes` is specified with type `X` and count `20`, last 20 changes of `X` type would be kept for each catalog item | Field | Description | Scheme | @@ -53,7 +65,7 @@ metadata: name: kubernetes-scraper spec: retention: - //highlight-next-line + //highlight-next-line staleItemAge: 30m kubernetes: clusterName: local From e16d1c6a1374bb82c09f30a94e9cd38eb36d7959 Mon Sep 17 00:00:00 2001 From: Aditya Thebe Date: Thu, 20 Aug 2026 12:10:25 +0000 Subject: [PATCH 2/2] docs(config-db): align retention defaults with cleanup jobs Clarify when each default period starts and document the evidence exemptions used by cleanup jobs. Update the config-db submodule to current main so fixture and source references match the documented behavior. Amp-Thread-ID: https://ampcode.com/threads/T-01a01f09-6251-76ce-8687-0455cc5fd6f8 --- .../docs/guide/config-db/concepts/retention.md | 16 ++++++++-------- modules/config-db | 2 +- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/mission-control/docs/guide/config-db/concepts/retention.md b/mission-control/docs/guide/config-db/concepts/retention.md index c022377b..8cef2aa5 100644 --- a/mission-control/docs/guide/config-db/concepts/retention.md +++ b/mission-control/docs/guide/config-db/concepts/retention.md @@ -7,17 +7,17 @@ sidebar_custom_props: After scraping we can choose to retain results on the basis of name, age, count and more. -## Default Retention Periods +## Default retention periods -When retention rules are not explicitly configured, config-db applies the following default retention periods: +Config DB cleanup jobs use the following retention periods by default: -| Type | Default Period | Description | -| --------------- | -------------- | --------------------------------------------------- | -| Config Items | 7 days | Configuration items are retained for 7 days | -| Changes | 60 days | Change records are retained for 60 days | -| Config Analysis | 60 days | Configuration analysis data is retained for 60 days | +| Record | Default period | Cleanup behavior | +| --------------- | ------------------------------ | -------------------------------------------- | +| Config item | 7 days after soft deletion | Permanently delete soft-deleted config items | +| Config change | 60 days after creation | Delete changes not linked to evidence | +| Config analysis | 60 days after last observation | Delete analysis not linked to evidence | -These defaults ensure that your database doesn't grow unbounded while maintaining a reasonable history of configuration changes and analysis. +The cleanup jobs run once per day. The `staleItemAge` field controls when Config DB soft-deletes an unseen config item; the 7-day default controls when Config DB permanently deletes that item. The retention rules are applied for each unique catalog item. If `changes` is specified with type `X` and count `20`, last 20 changes of `X` type would be kept for each catalog item diff --git a/modules/config-db b/modules/config-db index 57489d95..5b096223 160000 --- a/modules/config-db +++ b/modules/config-db @@ -1 +1 @@ -Subproject commit 57489d95c2952521e16c2914a167777d29299a2b +Subproject commit 5b09622395da0609f9364bfb14654c567424ac16