You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
resource"datadog_monitor""agent_running" {
name="${local.prefix} Agent is not running"type="metric alert"query="min(last_1m):min:datadog.agent.running{${local.filters}} by {host} < 1"message=<<EOT${var.alert_handles}EOTnotify_no_data=true
}
Expected Behavior
According to the docs the default value for datadog_monitor.no_data_timeframe should be
Default: 2x timeframe for metric alerts, 2 minutes for service checks.
To be honest this default seems randomly chosen and I am not sure if it makes a lot of sense.
Actual Behavior
datadog_monitor.no_data_timeframe is set to 0 by default. This bring the strange side effect that editing a monitor created from terraform with datadog_monitor.no_data_timeframe equal to 0 in the web app will make the UI reset the value to the web app default (10 minutes).
The text was updated successfully, but these errors were encountered:
Terraform Version
Terraform v0.11.13
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
According to the docs the default value for
datadog_monitor.no_data_timeframe
should beTo be honest this default seems randomly chosen and I am not sure if it makes a lot of sense.
Actual Behavior
datadog_monitor.no_data_timeframe
is set to 0 by default. This bring the strange side effect that editing a monitor created from terraform withdatadog_monitor.no_data_timeframe
equal to 0 in the web app will make the UI reset the value to the web app default (10 minutes).The text was updated successfully, but these errors were encountered: