Many Clusters - Many Monitors - Impossible to Use

[xavixendit]

We also looking to migrate TF to CRD but we have thousands of monitors per cluster, a dozen clusters. What happens to the DD API at this point?

Whats the point on knowing the monitor status wether is Triggered or not? Is not that you will make "alerts" or "monitors" out of this.. in fact, im not sure wether you can even make alerts out of the status field of a CRD in a cluster with datadog at all..

The operator is handy, a good idea.. but seems over-engineered with behaviours like this, if you were in need to receive this status update.. u should consider integrations/webhooks or communication between the DD agent and the operator.

Can we get some flag to turn off this unnecessary overhead ? In theory projecting the creation, deletion and modification of the CRD into the monitor should be enough from a controller perspective.

[tbavelier]

Hello @xavixendit , if you are solely looking for CRUD operations, you might be interested in https://github.com/DataDog/datadog-operator/blob/main/docs/datadog_generic_resource.md. Monitors support is coming with 1.13 (only release candidate versions are available yet, but it should be released in a few weeks top), and doesn't include the monitor status field, only its ID in the app, and you can create/update/delete all types of monitors (supproted by the API). Please let us know if that would work for you

[dd-octo-sts[bot]]

This issue has been automatically marked as stale because it has not had activity in the past 15 days.

It will be closed in 30 days if no further activity occurs. If this issue is still relevant, adding a comment will keep it open. Also, you can always reopen the issue if you missed the window.

Thank you for your contributions!