From 6fe32fa2ded1df4649850762e84d5c783b24cac2 Mon Sep 17 00:00:00 2001 From: Aldrick Castro Date: Thu, 13 Aug 2026 16:44:00 -0400 Subject: [PATCH] [DBM] Clarify secret_refresh_interval default behavior on resolution failure --- hugo/content/en/agent/configuration/secrets-management.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/hugo/content/en/agent/configuration/secrets-management.md b/hugo/content/en/agent/configuration/secrets-management.md index ad06a7c4f1a..59211233b2b 100644 --- a/hugo/content/en/agent/configuration/secrets-management.md +++ b/hugo/content/en/agent/configuration/secrets-management.md @@ -1830,6 +1830,10 @@ Set a refresh interval: secret_refresh_interval: 3600 # refresh every hour ``` +
+secret_refresh_interval defaults to 0, which disables automatic refresh. If a secret fails to resolve at Agent startup—for example, because of a transient network or authentication error against your secrets backend, such as Azure Key Vault when using managed identity—it is not retried automatically and remains unresolved until the Agent is restarted. If calls to your secrets backend can be transiently unreliable, set secret_refresh_interval to a non-zero value (for example, 3600) so failed resolutions are retried automatically. +
+ Or, trigger a refresh manually: ```shell datadog-agent secret refresh