Skip to content

update information on how to handle log rotation timeouts 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

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

update information on how to handle log rotation timeouts in the datadog agent #29890

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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, a timeout is set after the log rotation. Any data that remains after the timeout is not read by the agent and is lost. If you find yourself hitting this case with any frequency, it is recommended to increase the timeout from its default of 60 seconds. The timeout interval can be defined with the `logs_config.close_timeout` setting in the Agent's main configuration file or the `DD_LOGS_CONFIG_CLOSE_TIMEOUT` env variable.

## Network issues

Expand Down
Loading