Skip to content

Page related updates to synthetics #3531

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
api-clients-generation-pipeline merged 1 commit into from
Jul 8, 2026
Merged

Page related updates to synthetics #3531

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .generator/schemas/v1/openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11815,7 +11815,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.
It is also required for metric monitors that use `scheduling_options.custom_schedule`.
enum:
- "default"
- "show_no_data"
Expand Down
3 changes: 2 additions & 1 deletion lib/datadog_api_client/v1/models/monitor_options.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
# It 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.
Expand Down
3 changes: 2 additions & 1 deletion lib/datadog_api_client/v1/models/on_missing_data_option.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
# It is also required for metric monitors that use `scheduling_options.custom_schedule`.
class OnMissingDataOption
include BaseEnumModel

Expand Down
Loading