From 95feec9c2a1d9a6acfa773de284b64468a92f47e Mon Sep 17 00:00:00 2001 From: Ryan Hall Date: Wed, 11 Jun 2025 15:51:27 -0400 Subject: [PATCH 1/3] update information on how to handle log rotation timeouts in the datadog agent --- content/en/logs/guide/mechanisms-ensure-logs-not-lost.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/logs/guide/mechanisms-ensure-logs-not-lost.md b/content/en/logs/guide/mechanisms-ensure-logs-not-lost.md index c5032c55936dd..1abbae4ca5f9f 100644 --- a/content/en/logs/guide/mechanisms-ensure-logs-not-lost.md +++ b/content/en/logs/guide/mechanisms-ensure-logs-not-lost.md @@ -20,7 +20,7 @@ further_reading: ## Log rotate When a file is rotated, the Agent keeps [tailing][1] the old file while starting to tail the newly created file in parallel. -Although the Agent continues to tail the old file, a 60-second timeout after the log rotation is set to ensure the agent is using its resources to tail the most up-to-date files. +Although the Agent continues to tail the old file, it will prioritize using its resources to tail the most up-to-date files. 60 seconds after the rotation has been detected, the agent will close the rotated file and all remaining data will be lost. If this window is too short for your environment, it can be adjusted through the `logs_config.close_timeout` setting or the `DD_LOGS_CONFIG_CLOSE_TIMEOUT` env variable. ## Network issues From bf25c198c5b06a3d053ef02a24948c8b25417eec Mon Sep 17 00:00:00 2001 From: Ryan Hall Date: Wed, 18 Jun 2025 11:38:38 -0400 Subject: [PATCH 2/3] avoid temporal words like 'will' --- content/en/logs/guide/mechanisms-ensure-logs-not-lost.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/logs/guide/mechanisms-ensure-logs-not-lost.md b/content/en/logs/guide/mechanisms-ensure-logs-not-lost.md index 1abbae4ca5f9f..7922110fbc2bd 100644 --- a/content/en/logs/guide/mechanisms-ensure-logs-not-lost.md +++ b/content/en/logs/guide/mechanisms-ensure-logs-not-lost.md @@ -20,7 +20,7 @@ further_reading: ## Log rotate When a file is rotated, the Agent keeps [tailing][1] the old file while starting to tail the newly created file in parallel. -Although the Agent continues to tail the old file, it will prioritize using its resources to tail the most up-to-date files. 60 seconds after the rotation has been detected, the agent will close the rotated file and all remaining data will be lost. If this window is too short for your environment, it can be adjusted through the `logs_config.close_timeout` setting or the `DD_LOGS_CONFIG_CLOSE_TIMEOUT` env variable. +Although the Agent continues to tail the old file, it prioritizes using its resources to tail the most up-to-date files. 60 seconds after the rotation has been detected, the agent closes the rotated file and all remaining data is lost. If this window is too short for your environment, it can be adjusted through the `logs_config.close_timeout` setting or the `DD_LOGS_CONFIG_CLOSE_TIMEOUT` env variable. ## Network issues From 84a85e7764b325d2c88e89e68cde81bb9ee2733a Mon Sep 17 00:00:00 2001 From: Ryan Date: Fri, 20 Jun 2025 09:50:12 -0400 Subject: [PATCH 3/3] Update content/en/logs/guide/mechanisms-ensure-logs-not-lost.md Co-authored-by: Bryce Eadie --- content/en/logs/guide/mechanisms-ensure-logs-not-lost.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/logs/guide/mechanisms-ensure-logs-not-lost.md b/content/en/logs/guide/mechanisms-ensure-logs-not-lost.md index 7922110fbc2bd..c3fb3ff24e665 100644 --- a/content/en/logs/guide/mechanisms-ensure-logs-not-lost.md +++ b/content/en/logs/guide/mechanisms-ensure-logs-not-lost.md @@ -20,7 +20,7 @@ further_reading: ## Log rotate When a file is rotated, the Agent keeps [tailing][1] the old file while starting to tail the newly created file in parallel. -Although the Agent continues to tail the old file, it prioritizes using its resources to tail the most up-to-date files. 60 seconds after the rotation has been detected, the agent closes the rotated file and all remaining data is lost. If this window is too short for your environment, it can be adjusted through the `logs_config.close_timeout` setting or the `DD_LOGS_CONFIG_CLOSE_TIMEOUT` env variable. +Although the Agent continues to tail the old file, it prioritizes using its resources to tail the most up-to-date files. 60 seconds after the rotation has been detected, the Agent closes the rotated file and all remaining data is lost. If this window is too short for your environment, it can be adjusted through the `logs_config.close_timeout` setting or the `DD_LOGS_CONFIG_CLOSE_TIMEOUT` environment variable. ## Network issues