DatadogMonitors: options.thresholds.critical validation logic #2106
Description
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."]}.