khewonc

Hi, thanks for reaching out. I'll add a card in our backlog to add those fields to the DatadogMonitor CRD. We'll report back here with any updates on this

Hi @Ekman, we don't currently have an `envFrom` field, but I'll add `envFrom` as a feature request to our backlog. Would using `env.valueFrom` work for your use case for now?...

I see, thanks for the additional detail. We'll reach out on this thread with any updates on the issue.

Hi, Thanks for reporting this. We've added a fix in https://github.com/DataDog/datadog-operator/pull/823

Hi, thanks for reporting this. We'll look into this on our end to try and see why multiple SLOs are getting created

Hi, thanks for reaching out. To run a cluster check, the `redisdb` configuration yaml will need to be added to the cluster agent (DCA) as the DCA will be the...

Hi, thanks for trying out the new configuration. Could you also try using `redisdb.yaml` as the key in the `override` section instead of `redisdb.yml`? ```yaml override: clusterAgent: extraConfd: configDataMap: redisdb.yaml:...

Glad to hear that worked and thanks for the feedback. I'll add a card to the backlog to better support `.yml` extensions in the check configs.

Hi, thanks for the feature request. We don't currently support composite monitors yet ([list of supported monitor types](https://github.com/DataDog/datadog-operator/blob/1ac0e106cbfef060c750995f43a165d3b703532d/controllers/datadogmonitor/controller.go#L42)), but I'll add card in our backlog for this. I can't speak...

Hi, thanks for reporting this. We'll have a fix for those links in https://github.com/DataDog/datadog-operator/pull/1199