Open kvitaly2005 opened 2 years ago
Hi 👋 thanks for opening the issue. The log line you provided seems to suggest that you're using datadog-iot-agent instead of datadog-agent (the simplified Go version of the check is running instead of the full Python version). Is this correct and intentional?
In between 6.18 and 7.32 we renamed the *_blacklist
arguments to *_exclude
, so the configuration value you're using will not work in 7.32.4. Now, the way to fix this is slightly different for Python and Go versions of the check.
mount_point_exclude
instead of mount_point_blacklist
.excluded_mountpoint_re
, which accepts only a single string value as a regexp (so to transform what you have, you would have to use something like <first_exclude>|<second_exclude>|<third_exclude>
).Let me know if this helps.
the config values excluded_filesystems
and excluded_disks
are simply not being parsed, I submitted a fix in #13954
Output of the info page (if this is a bug)
Describe what happened: After upgrade to 7.32.4 logs are filled with spam from disk_nix.go messages hundreds of the same every minute
Describe what you expected: I expect logs to be clear as in version 6.18 Adding following blacklists configuration does not help:
/etc/datadog-agent/conf.d/disk.d/conf.yaml init_config: instances:
Steps to reproduce the issue: Install 7.32.4 on Linux with Docker daemon running.
Additional environment details (Operating System, Cloud provider, etc): Debian Linux / Docker