Skip to content
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.

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

Even with DD_LOGS_STDOUT=true the agent logs to the container filesystem #310

Open
wheelybird opened this issue Jun 19, 2018 · 2 comments
Open

Comments

@wheelybird
Copy link

Hello. We find that with DD_LOGS_STDOUT=true there are several logs that are logged to /var/log/datadog within the container. Even though these are rotated nightly, as the container is using an overlay filesystem the size of the overlay volume steadily grows.
This is problematic for some of our smaller cloud instances that aren't configured with large amounts of disk space.

Would it be possible to redirect those logs to STDOUT instead of logging to the filesystem?

@JohnLZeller
Copy link

@wheelybird try setting DD_LOGS_STDOUT to yes instead of true.

@duxing
Copy link

duxing commented Aug 31, 2022

I think this is what you need.

in a non-container environment, this is located at /etc/datadog-agent/datadog.yaml

2 options for k8s / helm:

  • use DD_LOG_TO_CONSOLE environment variable (value key: datadog.env)
  • add log_to_console: true to datadog.agents.customAgentConfig and make sure datadog.agents.useConfigMap is set to true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants