Regenerate client from commit a88bcc5 of spec repo

Author: ci.datadog-api-spec

.generator/schemas/v1/openapi.yaml

@@ -11798,7 +11798,8 @@ components:
         The default option results in different behavior depending on the monitor query type.
         For monitors using Count queries, an empty monitor evaluation is treated as 0 and is compared to the threshold conditions.
         For monitors using any query type other than Count, for example Gauge, Measure, or Rate, the monitor shows the last known status.
-        This option is only available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+        This option is available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+        The option is also required for metric monitors that use `scheduling_options.custom_schedule`.
       enum:
         - "default"
         - "show_no_data"

features/v1/monitors.feature

@@ -119,7 +119,7 @@ Feature: Monitors
     And the response "name" is equal to "{{ unique }}"
     And the response "query" is equal to "avg(current_1mo):avg:system.load.5{*} > 0.5"
 
-  @team:DataDog/monitor-app
+  @oncall-page:monitor-app @team:DataDog/monitor-app
   Scenario: Create a metric monitor with a custom schedule returns "OK" response
     Given new "CreateMonitor" request
     And body with value {"message":"some message Notify: @hipchat-channel","name":"{{ unique }}","query":"avg(current_1mo):avg:system.load.5{*} > 0.5","tags":[],"options":{"thresholds":{"critical":0.5},"notify_audit":false,"include_tags":false,"on_missing_data":"default","scheduling_options":{"evaluation_window":{"day_starts":"04:00", "month_starts":1},"custom_schedule":{"recurrences":[{"rrule":"FREQ=DAILY;INTERVAL=1","timezone":"America/Los_Angeles","start":"2024-10-26T09:13:00"}]}}},"type":"query alert", "draft_status": "published"}

lib/datadog_api_client/v1/models/monitor_options.rb

@@ -111,7 +111,8 @@ class MonitorOptions
     # The default option results in different behavior depending on the monitor query type.
     # For monitors using Count queries, an empty monitor evaluation is treated as 0 and is compared to the threshold conditions.
     # For monitors using any query type other than Count, for example Gauge, Measure, or Rate, the monitor shows the last known status.
-    # This option is only available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+    # This option is available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+    # The option is also required for metric monitors that use `scheduling_options.custom_schedule`.
     attr_accessor :on_missing_data
 
     # The number of minutes after the last notification before a monitor re-notifies on the current status.

lib/datadog_api_client/v1/models/on_missing_data_option.rb

@@ -21,7 +21,8 @@ module DatadogAPIClient::V1
   # The default option results in different behavior depending on the monitor query type.
   # For monitors using Count queries, an empty monitor evaluation is treated as 0 and is compared to the threshold conditions.
   # For monitors using any query type other than Count, for example Gauge, Measure, or Rate, the monitor shows the last known status.
-  # This option is only available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+  # This option is available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+  # The option is also required for metric monitors that use `scheduling_options.custom_schedule`.
   class OnMissingDataOption
     include BaseEnumModel