Skip to content

[ AGNTLOG-172 ] document the close_timeout setting for log rotations in the datadog agent #29890

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

[ AGNTLOG-172 ] document the close_timeout setting for log rotations in the datadog agent #29890

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
95feec9
update information on how to handle log rotation timeouts in the data…
ddrthall Jun 11, 2025
bf25c19
avoid temporal words like 'will'
ddrthall Jun 18, 2025
84a85e7
Update content/en/logs/guide/mechanisms-ensure-logs-not-lost.md
ddrthall Jun 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/en/logs/guide/mechanisms-ensure-logs-not-lost.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 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

Expand Down
Loading