Olivier Vielpeau

Hi @kbruner and thanks for your feedback! I think we could implement the feature this way: - when `node['datadog']['cassandra']['init_config']` is `nil`, use the default configuration for `init_config` in `cassandra.yaml` -...

Hi @red8888! The `datadog_monitor` resource doesn't support custom checks right now, but it'd make sense to make it support it. Feel free to open a PR implementing this, if you...

@theckman @martinisoft: Could you have a look at the approach of #395 (see discussion in #345)? It makes the cookbook pull the `api_key` and the `application_key` from the `run_state` first,...

Hi @PeterGrace and sorry for the late reply. This was recently discussed in https://github.com/DataDog/chef-datadog/pull/558#issuecomment-433050683. TL;DR: Agent version 6 still supports reading from the `/etc/datadog-agent/conf.d/redisdb.yaml` config file, so this cookbook works...

Hi @haidangwa, sorry I'm only looking at your issue now. The cookbook's logic here is to ignore any endpoint defined in `node['datadog']['extra_endpoints']` for which the nested key `enabled` is not...

Hi @rmoriz, As you wrote, this could mainly addressed through some improved documentation. Just to be sure I understand, could you give an example of what you mean by "custom...

Thanks @rmoriz for detailing your use case! `1.` could be addressed through some improved documentation. If the use case is common enough we could also consider adding a `dd-custom-check` recipe...

Hi @ianrossi, thanks for opening this PR! Instead of creating a new recipe/template, is there any reason you didn't update the existing `jmx` recipe and template with the additional `init_config`...

Thanks for your quick reply! Even with one common `jmx` template, you could let the users not define `node['datadog']['jmx']['init_config']` at all, and the `init_config` section in the generated yaml file...

Great, thanks again!