DatadogMonitors: options.thresholds.critical validation logic

[bazilmarkov]

When creating a datadog monitor, I always have to set up a condition in the query and the value for options.thresholds.critical equal. If they are not aligned, I get a validation error: 400 Bad Request: {"errors":["Alert threshold (X) does not match that used in the query (Y)."]}.

But if I skip setting options.thresholds.critical, this value seems to be populated based on the query condition correctly. I want to ask if this is an expected behavior and I can leave options.thresholds.critical empty most of the time, or if it's just due to a missing validation when options.thresholds is left empty.

Because when I set options.thresholds.warning but do not specify options.thresholds.critical, expecting it to be automatically populated from the query, I receive another validation error: 400 Bad Request: {"errors":["Alert status is required."]}.

[dd-octo-sts]

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!

[bazilmarkov]

The question remains relevant, and I would appreciate attention to it.

[chouetz]

Hi @bazilmarkov,

Thank you for taking the time to share your feedback. We recently introduced a system to help manage long-standing issues through automated stale management. We understand this may have come as a surprise for some existing issues. We want to apologize if it felt that way. It was not our intent, and we want to reassure you that every issue is important to us and reviewed carefully. For your specific issue, we’re reviewing it to ensure the discussion progresses and receives the right level of attention. Thank you for helping improve the Datadog Agent.

— The Datadog Agent Team