-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
docker agent [auto-] configuration for agent v6 #1381
Comments
got this after turning
|
from agent.log
|
Hi @n0mer , The You docker.d config looks OK, what could happen is:
|
@xvello Xavier, i executed command DD_UPGRADE=true bash -c "$(curl -L https://raw.githubusercontent.com/DataDog/datadog-agent/master/cmd/agent/install_script.sh)" from https://github.com/DataDog/datadog-agent/blob/master/docs/agent/upgrade.md , and i got 2 folders |
@xvello are those error log messages so, i removed Anyway, docker agent working with I opened support case #132559 , submitted flares with configs and logs. Brian B. is looking into it. |
@xvello i'm running datadog agent w/out docker image
i had tmpfs excluded in conf.d/disk.d/conf.yaml , now tmpfs is not excluded (please also init_config:
instances:
# The use_mount parameter will instruct the check to collect disk
# and fs metrics using mount points instead of volumes
- use_mount: yes
# The (optional) excluded_filesystems parameter will instruct the check to
# ignore disks using these filesystems. Note: On some linux distributions,
# rootfs will be found and tagged as a device, add rootfs here to exclude.
excluded_filesystems:
# - tmpfs
# - none
# - shm
# - nsfs
# - tracefs |
hello,
after migration from dd-agent v5 i've got 2 folders in /etc/datadog-agent/conf.d:
docker.d
anddocker_daemon.d
Collector says there are following
Loading Errors
indocker_daemon
:docker-daemon.yaml in v5 had very simple configuration:
So, there are several post-migration questions:
docker.d
anddocker_daemon.d
? If yes - what's the difference between them?host "dashboard" contents:
The text was updated successfully, but these errors were encountered: