You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When configuring a redisdb monitor in the datadog cookbook, the cookbook creates file /etc/datadog-agent/conf.d/redisdb.yaml. In agent version 6, the path is supposed to be /etc/datadog-agent/conf.d/redisdb.d/conf.yaml.
It does not appear that there is code to differentiate this location change (I'm assuming such code would live approximately here?)
Are there plans to fix where the yaml files are populated for the new layout?
The text was updated successfully, but these errors were encountered:
iancward
added a commit
to iancward/chef-datadog
that referenced
this issue
Sep 10, 2018
This was recently discussed in #558 (comment). TL;DR: Agent version 6 still supports reading from the /etc/datadog-agent/conf.d/redisdb.yaml config file, so this cookbook works fine with Agent 6, but it'd be a welcome improvement to allow writing files in /etc/datadog-agent/conf.d/redisdb.d/<arbitrary_name>.yaml, with arbitrary_name a user-provided name.
When configuring a redisdb monitor in the datadog cookbook, the cookbook creates file
/etc/datadog-agent/conf.d/redisdb.yaml
. In agent version 6, the path is supposed to be/etc/datadog-agent/conf.d/redisdb.d/conf.yaml
.It does not appear that there is code to differentiate this location change (I'm assuming such code would live approximately here?)
Are there plans to fix where the yaml files are populated for the new layout?
The text was updated successfully, but these errors were encountered: