From fe249c012ca26159867b1db87ed3d6295642ec11 Mon Sep 17 00:00:00 2001 From: Gnani Rahul Date: Mon, 10 Aug 2026 18:10:06 -0500 Subject: [PATCH] fix(common-services): add connector.log retention to curator connector.log is shipped to Elasticsearch by the fid-exporter sidecar (fid chart source 'connector' -> index connector.log) but has no delete_indices action in curator.logs, so its daily indices are never reclaimed while every other shipped log is pruned at 7 days. Observed on the BSWH clusters before cleanup: bswh-use1 90 indices 55.8 GB oldest 2026-05-13 (78% of index data) bswh-use2 348 indices 167.6 GB oldest 2025-08-28 (85% of index data) Adds connector.log to curator.logs so it inherits the same 7-day delete_indices action as the other 24 prefixes. --- charts/common-services/values.yaml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/charts/common-services/values.yaml b/charts/common-services/values.yaml index 9bbe9f19..54fb6505 100644 --- a/charts/common-services/values.yaml +++ b/charts/common-services/values.yaml @@ -1200,6 +1200,10 @@ curator: - name: "periodiccache.log" - name: "admin_rest_api_access.log" - name: "sync_engine.log" + # Sync-agent connector logs. Highest-volume index the fid-exporter ships + # (one document per connector event, across every sync agent); without a + # retention action these indices accumulate indefinitely. + - name: "connector.log" - name: "alerts.log" - name: "approvals_audit.log" - name: "scim.log"