docs/v1/MonitorOptions.md in datadog_api_client-1.2.0 vs docs/v1/MonitorOptions.md in datadog_api_client-1.3.0

- old
+ new

@@ -12,11 +12,12 @@ | **groupby_simple_monitor** | **Boolean** | Whether the log alert monitor triggers a single alert or multiple alerts when any group breaches a threshold. | [optional] | | **include_tags** | **Boolean** | A Boolean indicating whether notifications from this monitor automatically inserts its triggering tags into the title. **Examples** - If `True`, `[Triggered on {host:h1}] Monitor Title` - If `False`, `[Triggered] Monitor Title` | [optional][default to true] | | **locked** | **Boolean** | Whether or not the monitor is locked (only editable by creator and admins). | [optional] | | **min_failure_duration** | **Integer** | How long the test should be in failure before alerting (integer, number of seconds, max 7200). | [optional][default to 0] | | **min_location_failed** | **Integer** | The minimum number of locations in failure at the same time during at least one moment in the `min_failure_duration` period (`min_location_failed` and `min_failure_duration` are part of the advanced alerting rules - integer, >= 1). | [optional][default to 1] | -| **new_host_delay** | **Integer** | Time (in seconds) to allow a host to boot and applications to fully start before starting the evaluation of monitor results. Should be a non negative integer. | [optional][default to 300] | +| **new_group_delay** | **Integer** | Time (in seconds) to skip evaluations for new groups. For example, this option can be used to skip evaluations for new hosts while they initialize. Must be a non negative integer. | [optional] | +| **new_host_delay** | **Integer** | Time (in seconds) to allow a host to boot and applications to fully start before starting the evaluation of monitor results. Should be a non negative integer. Use new_group_delay instead. | [optional][default to 300] | | **no_data_timeframe** | **Integer** | The number of minutes before a monitor notifies after data stops reporting. Datadog recommends at least 2x the monitor timeframe for metric alerts or 2 minutes for service checks. If omitted, 2x the evaluation timeframe is used for metric alerts, and 24 hours is used for service checks. | [optional] | | **notify_audit** | **Boolean** | A Boolean indicating whether tagged users is notified on changes to this monitor. | [optional][default to false] | | **notify_no_data** | **Boolean** | A Boolean indicating whether this monitor notifies when data stops reporting. | [optional][default to false] | | **renotify_interval** | **Integer** | The number of minutes after the last notification before a monitor re-notifies on the current status. It only re-notifies if it’s not resolved. | [optional] | | **require_full_window** | **Boolean** | A Boolean indicating whether this monitor needs a full window of data before it’s evaluated. We highly recommend you set this to `false` for sparse metrics, otherwise some evaluations are skipped. Default is false. | [optional] | @@ -40,9 +41,10 @@ groupby_simple_monitor: null, include_tags: null, locked: null, min_failure_duration: null, min_location_failed: null, + new_group_delay: null, new_host_delay: null, no_data_timeframe: null, notify_audit: null, notify_no_data: null, renotify_interval: null,