datadog_api_client 1.0.0 → 1.1.0

data/docs/v1/Downtime.md

@@ -5,6 +5,7 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **active** | **Boolean** | If a scheduled downtime currently exists. | [optional][readonly] |
+| **active_child** | [**DowntimeChild**](DowntimeChild.md) |  | [optional] |
 | **canceled** | **Integer** | If a scheduled downtime is canceled. | [optional][readonly] |
 | **creator_id** | **Integer** | User ID of the downtime creator. | [optional][readonly] |
 | **disabled** | **Boolean** | If a downtime has been disabled. | [optional] |
@@ -28,6 +29,7 @@ require 'datadog_api_client/v1'
 
 instance = DatadogAPIClient::V1::Downtime.new(
   active: true,
+  active_child: null,
   canceled: 1412799983,
   creator_id: 123456,
   disabled: false,

data/docs/v1/DowntimeChild.md

@@ -0,0 +1,48 @@
+# DatadogAPIClient::V1::DowntimeChild
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **active** | **Boolean** | If a scheduled downtime currently exists. | [optional][readonly] |
+| **canceled** | **Integer** | If a scheduled downtime is canceled. | [optional][readonly] |
+| **creator_id** | **Integer** | User ID of the downtime creator. | [optional][readonly] |
+| **disabled** | **Boolean** | If a downtime has been disabled. | [optional] |
+| **downtime_type** | **Integer** | `0` for a downtime applied on `*` or all, `1` when the downtime is only scoped to hosts, or `2` when the downtime is scoped to anything but hosts. | [optional][readonly] |
+| **_end** | **Integer** | POSIX timestamp to end the downtime. If not provided, the downtime is in effect indefinitely until you cancel it. | [optional] |
+| **id** | **Integer** | The downtime ID. | [optional][readonly] |
+| **message** | **String** | A message to include with notifications for this downtime. Email notifications can be sent to specific users by using the same `@username` notation as events. | [optional] |
+| **monitor_id** | **Integer** | A single monitor to which the downtime applies. If not provided, the downtime applies to all monitors. | [optional] |
+| **monitor_tags** | **Array<String>** | A comma-separated list of monitor tags. For example, tags that are applied directly to monitors, not tags that are used in monitor queries (which are filtered by the scope parameter), to which the downtime applies. The resulting downtime applies to monitors that match ALL provided monitor tags. For example, `service:postgres` **AND** `team:frontend`. | [optional] |
+| **parent_id** | **Integer** | ID of the parent Downtime. | [optional] |
+| **recurrence** | [**DowntimeRecurrence**](DowntimeRecurrence.md) |  | [optional] |
+| **scope** | **Array<String>** | The scope(s) to which the downtime applies. For example, `host:app2`. Provide multiple scopes as a comma-separated list like `env:dev,env:prod`. The resulting downtime applies to sources that matches ALL provided scopes (`env:dev` **AND** `env:prod`). | [optional] |
+| **start** | **Integer** | POSIX timestamp to start the downtime. If not provided, the downtime starts the moment it is created. | [optional] |
+| **timezone** | **String** | The timezone in which to display the downtime's start and end times in Datadog applications. | [optional] |
+| **updater_id** | **Integer** | ID of the last user that updated the downtime. | [optional][readonly] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::DowntimeChild.new(
+  active: true,
+  canceled: 1412799983,
+  creator_id: 123456,
+  disabled: false,
+  downtime_type: 2,
+  _end: 1412793983,
+  id: 1626,
+  message: Message on the downtime,
+  monitor_id: 123456,
+  monitor_tags: ["*"],
+  parent_id: 123,
+  recurrence: null,
+  scope: ["env:staging"],
+  start: 1412792983,
+  timezone: America/New_York,
+  updater_id: 123456
+)
+```
+

data/docs/v1/MetricsAPI.md

@@ -276,7 +276,7 @@ end
 
 Submit metrics
 
-The metrics end-point allows you to post time-series data that can be graphed on Datadog’s dashboards. The maximum payload size is 3.2 megabytes (3200000). Compressed payloads must have a decompressed size of up to 62 megabytes (62914560).  If you’re submitting metrics directly to the Datadog API without using DogStatsD, expect  - 64 bits for the timestamp - 32 bits for the value - 20 bytes for the metric names - 50 bytes for the timeseries - The full payload is approximately ~ 100 bytes. However, with the DogStatsD API, compression is applied, which reduces the payload size.
+The metrics end-point allows you to post time-series data that can be graphed on Datadog’s dashboards. The maximum payload size is 3.2 megabytes (3200000 bytes). Compressed payloads must have a decompressed size of less than 62 megabytes (62914560 bytes).  If you’re submitting metrics directly to the Datadog API without using DogStatsD, expect:  - 64 bits for the timestamp - 32 bits for the value - 20 bytes for the metric names - 50 bytes for the timeseries - The full payload is approximately 100 bytes. However, with the DogStatsD API, compression is applied, which reduces the payload size.
 
 ### Examples
 

data/docs/v1/Monitor.md

@@ -15,11 +15,11 @@
 | **options** | [**MonitorOptions**](MonitorOptions.md) |  | [optional] |
 | **overall_state** | [**MonitorOverallStates**](MonitorOverallStates.md) |  | [optional] |
 | **priority** | **Integer** | Integer from 1 (high) to 5 (low) indicating alert severity. | [optional] |
-| **query** | **String** | The monitor query. | [optional] |
+| **query** | **String** | The monitor query. |  |
 | **restricted_roles** | **Array<String>** | A list of role identifiers that can be pulled from the Roles API. Cannot be used with `locked` option. | [optional] |
 | **state** | [**MonitorState**](MonitorState.md) |  | [optional] |
 | **tags** | **Array<String>** | Tags associated to your monitor. | [optional] |
-| **type** | [**MonitorType**](MonitorType.md) |  | [optional] |
+| **type** | [**MonitorType**](MonitorType.md) |  |  |
 
 ## Example
 
@@ -38,7 +38,7 @@ instance = DatadogAPIClient::V1::Monitor.new(
   options: null,
   overall_state: null,
   priority: null,
-  query: null,
+  query: avg(last_5m):sum:system.net.bytes_rcvd{host:host0} > 100,
   restricted_roles: null,
   state: null,
   tags: null,

data/docs/v1/MonitorGroupSearchResponse.md

@@ -0,0 +1,22 @@
+# DatadogAPIClient::V1::MonitorGroupSearchResponse
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **counts** | [**MonitorGroupSearchResponseCounts**](MonitorGroupSearchResponseCounts.md) |  | [optional] |
+| **groups** | [**Array<MonitorGroupSearchResult>**](MonitorGroupSearchResult.md) | The list of found monitor groups. | [optional][readonly] |
+| **metadata** | [**MonitorSearchResponseMetadata**](MonitorSearchResponseMetadata.md) |  | [optional] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::MonitorGroupSearchResponse.new(
+  counts: null,
+  groups: null,
+  metadata: null
+)
+```
+

data/docs/v1/MonitorGroupSearchResponseCounts.md

@@ -0,0 +1,20 @@
+# DatadogAPIClient::V1::MonitorGroupSearchResponseCounts
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **status** | **Array<Object>** | Search facets. | [optional] |
+| **type** | **Array<Object>** | Search facets. | [optional] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::MonitorGroupSearchResponseCounts.new(
+  status: null,
+  type: null
+)
+```
+

data/docs/v1/MonitorGroupSearchResult.md

@@ -0,0 +1,30 @@
+# DatadogAPIClient::V1::MonitorGroupSearchResult
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **group** | **String** | The name of the group. | [optional][readonly] |
+| **group_tags** | **Array<String>** | The list of tags of the monitor group. | [optional][readonly] |
+| **last_nodata_ts** | **Integer** | Latest timestamp the monitor group was in NO_DATA state. | [optional][readonly] |
+| **last_triggered_ts** | **Integer** | Latest timestamp the monitor group triggered. | [optional][readonly] |
+| **monitor_id** | **Integer** | The ID of the monitor. | [optional][readonly] |
+| **monitor_name** | **String** | The name of the monitor. | [optional][readonly] |
+| **status** | [**MonitorOverallStates**](MonitorOverallStates.md) |  | [optional] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::MonitorGroupSearchResult.new(
+  group: null,
+  group_tags: null,
+  last_nodata_ts: null,
+  last_triggered_ts: null,
+  monitor_id: null,
+  monitor_name: null,
+  status: null
+)
+```
+

data/docs/v1/MonitorOptions.md

@@ -7,7 +7,7 @@
 | **aggregation** | [**MonitorOptionsAggregation**](MonitorOptionsAggregation.md) |  | [optional] |
 | **device_ids** | [**Array<MonitorDeviceID>**](MonitorDeviceID.md) | IDs of the device the Synthetics monitor is running on. | [optional][readonly] |
 | **enable_logs_sample** | **Boolean** | Whether or not to send a log sample when the log monitor triggers. | [optional] |
-| **escalation_message** | **String** | A message to include with a re-notification. Supports the `@username` notification we allow elsewhere. Not applicable if `renotify_interval` is `None`. | [optional][default to 'none'] |
+| **escalation_message** | **String** | We recommend using the [is_renotify](https://docs.datadoghq.com/monitors/notifications/?tab=is_alert#renotify), block in the original message instead. A message to include with a re-notification. Supports the `@username` notification we allow elsewhere. Not applicable if `renotify_interval` is `None`. | [optional][default to 'none'] |
 | **evaluation_delay** | **Integer** | Time (in seconds) to delay evaluation, as a non-negative integer. For example, if the value is set to `300` (5min), the timeframe is set to `last_5m` and the time is 7:00, the monitor evaluates data from 6:50 to 6:55. This is useful for AWS CloudWatch and other backfilled metrics to ensure the monitor always has data during evaluation. | [optional] |
 | **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] |

data/docs/v1/MonitorSearchResponse.md

@@ -0,0 +1,22 @@
+# DatadogAPIClient::V1::MonitorSearchResponse
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **counts** | [**MonitorSearchResponseCounts**](MonitorSearchResponseCounts.md) |  | [optional] |
+| **metadata** | [**MonitorSearchResponseMetadata**](MonitorSearchResponseMetadata.md) |  | [optional] |
+| **monitors** | [**Array<MonitorSearchResult>**](MonitorSearchResult.md) | The list of found monitors. | [optional][readonly] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::MonitorSearchResponse.new(
+  counts: null,
+  metadata: null,
+  monitors: null
+)
+```
+

data/docs/v1/MonitorSearchResponseCounts.md

@@ -0,0 +1,24 @@
+# DatadogAPIClient::V1::MonitorSearchResponseCounts
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **muted** | **Array<Object>** | Search facets. | [optional] |
+| **status** | **Array<Object>** | Search facets. | [optional] |
+| **tag** | **Array<Object>** | Search facets. | [optional] |
+| **type** | **Array<Object>** | Search facets. | [optional] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::MonitorSearchResponseCounts.new(
+  muted: null,
+  status: null,
+  tag: null,
+  type: null
+)
+```
+

data/docs/v1/MonitorSearchResponseMetadata.md

@@ -0,0 +1,24 @@
+# DatadogAPIClient::V1::MonitorSearchResponseMetadata
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **page** | **Integer** | The page to start paginating from. | [optional][readonly] |
+| **page_count** | **Integer** | The number of pages. | [optional][readonly] |
+| **per_page** | **Integer** | The number of monitors to return per page. | [optional][readonly] |
+| **total_count** | **Integer** | The total number of monitors. | [optional][readonly] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::MonitorSearchResponseMetadata.new(
+  page: null,
+  page_count: null,
+  per_page: null,
+  total_count: null
+)
+```
+

data/docs/v1/MonitorSearchResult.md

@@ -0,0 +1,40 @@
+# DatadogAPIClient::V1::MonitorSearchResult
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **classification** | **String** | Classification of the monitor. | [optional][readonly] |
+| **creator** | [**Creator**](Creator.md) |  | [optional] |
+| **id** | **Integer** | ID of the monitor. | [optional][readonly] |
+| **last_triggered_ts** | **Integer** | Latest timestamp the monitor triggered. | [optional][readonly] |
+| **metrics** | **Array<String>** | Metrics used by the monitor. | [optional][readonly] |
+| **name** | **String** | The monitor name. | [optional][readonly] |
+| **notifications** | [**Array<MonitorSearchResultNotification>**](MonitorSearchResultNotification.md) | The notification triggered by the monitor. | [optional][readonly] |
+| **org_id** | **Integer** | The ID of the organization. | [optional][readonly] |
+| **scopes** | **Array<String>** | The scope(s) to which the downtime applies, e.g. `host:app2`. Provide multiple scopes as a comma-separated list, e.g. `env:dev,env:prod`. The resulting downtime applies to sources that matches ALL provided scopes (i.e. `env:dev AND env:prod`), NOT any of them. | [optional] |
+| **status** | [**MonitorOverallStates**](MonitorOverallStates.md) |  | [optional] |
+| **tags** | **Array<String>** | Tags associated with the monitor. | [optional][readonly] |
+| **type** | [**MonitorType**](MonitorType.md) |  | [optional] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::MonitorSearchResult.new(
+  classification: null,
+  creator: null,
+  id: null,
+  last_triggered_ts: null,
+  metrics: null,
+  name: null,
+  notifications: null,
+  org_id: null,
+  scopes: ["host:app2","env:dev,env:prod"],
+  status: null,
+  tags: null,
+  type: null
+)
+```
+

data/docs/v1/MonitorSearchResultNotification.md

@@ -0,0 +1,20 @@
+# DatadogAPIClient::V1::MonitorSearchResultNotification
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **handle** | **String** | The email address that received the notification. | [optional][readonly] |
+| **name** | **String** | The username receiving the notification | [optional][readonly] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::MonitorSearchResultNotification.new(
+  handle: null,
+  name: null
+)
+```
+

data/docs/v1/MonitorsAPI.md

@@ -9,6 +9,8 @@ All URIs are relative to *https://api.datadoghq.com*
 | [**delete_monitor**](MonitorsAPI.md#delete_monitor) | **DELETE** /api/v1/monitor/{monitor_id} | Delete a monitor |
 | [**get_monitor**](MonitorsAPI.md#get_monitor) | **GET** /api/v1/monitor/{monitor_id} | Get a monitor's details |
 | [**list_monitors**](MonitorsAPI.md#list_monitors) | **GET** /api/v1/monitor | Get all monitor details |
+| [**search_monitor_groups**](MonitorsAPI.md#search_monitor_groups) | **GET** /api/v1/monitor/groups/search | Monitors group search |
+| [**search_monitors**](MonitorsAPI.md#search_monitors) | **GET** /api/v1/monitor/search | Monitors search |
 | [**update_monitor**](MonitorsAPI.md#update_monitor) | **PUT** /api/v1/monitor/{monitor_id} | Edit a monitor |
 | [**validate_monitor**](MonitorsAPI.md#validate_monitor) | **POST** /api/v1/monitor/validate | Validate a monitor |
 
@@ -81,14 +83,14 @@ end
 
 Create a monitor
 
-Create a monitor using the specified options.  #### Monitor Types  The type of monitor chosen from:  - anomaly: `query alert` - APM: `query alert` or `trace-analytics alert` - composite: `composite` - custom: `service check` - event: `event alert` - forecast: `query alert` - host: `service check` - integration: `query alert` or `service check` - live process: `process alert` - logs: `log alert` - metric: `metric alert` - network: `service check` - outlier: `query alert` - process: `service check` - rum: `rum alert` - SLO: `slo alert` - watchdog: `event alert` - event-v2: `event-v2 alert`  #### Query Types  **Metric Alert Query**  Example: `time_aggr(time_window):space_aggr:metric{tags} [by {key}] operator #`  - `time_aggr`: avg, sum, max, min, change, or pct_change - `time_window`: `last_#m` (with `#` between 1 and 2880 depending on the monitor type) or `last_#h`(with `#` between 1 and 48 depending on the monitor type), or `last_1d` - `space_aggr`: avg, sum, min, or max - `tags`: one or more tags (comma-separated), or * - `key`: a 'key' in key:value tag syntax; defines a separate alert for each tag in the group (multi-alert) - `operator`: <, <=, >, >=, ==, or != - `#`: an integer or decimal number used to set the threshold  If you are using the `_change_` or `_pct_change_` time aggregator, instead use `change_aggr(time_aggr(time_window), timeshift):space_aggr:metric{tags} [by {key}] operator #` with:  - `change_aggr` change, pct_change - `time_aggr` avg, sum, max, min [Learn more](https://docs.datadoghq.com/monitors/monitor_types/#define-the-conditions) - `time_window` last\\_#m (between 1 and 2880 depending on the monitor type), last\\_#h (between 1 and 48 depending on the monitor type), or last_#d (1 or 2) - `timeshift` #m_ago (5, 10, 15, or 30), #h_ago (1, 2, or 4), or 1d_ago  Use this to create an outlier monitor using the following query: `avg(last_30m):outliers(avg:system.cpu.user{role:es-events-data} by {host}, 'dbscan', 7) > 0`  **Service Check Query**  Example: `\"check\".over(tags).last(count).count_by_status()`  - **`check`** name of the check, e.g. `datadog.agent.up` - **`tags`** one or more quoted tags (comma-separated), or \"*\". e.g.: `.over(\"env:prod\", \"role:db\")` - **`count`** must be at greater than or equal to your max threshold (defined in the `options`). It is limited to 100. For example, if you've specified to notify on 1 critical, 3 ok, and 2 warn statuses, `count` should be 3.  **Event Alert Query**  Example: `events('sources:nagios status:error,warning priority:normal tags: \"string query\"').rollup(\"count\").last(\"1h\")\"`  - **`event`**, the event query string: - **`string_query`** free text query to match against event title and text. - **`sources`** event sources (comma-separated). - **`status`** event statuses (comma-separated). Valid options: error, warn, and info. - **`priority`** event priorities (comma-separated). Valid options: low, normal, all. - **`host`** event reporting host (comma-separated). - **`tags`** event tags (comma-separated). - **`excluded_tags`** excluded event tags (comma-separated). - **`rollup`** the stats roll-up method. `count` is the only supported method now. - **`last`** the timeframe to roll up the counts. Examples: 45m, 4h. Supported timeframes: m, h and d. This value should not exceed 48 hours.  **NOTE** Only available on US1 and EU.  **Event V2 Alert Query**  Example: `events(query).rollup(rollup_method[, measure]).last(time_window) operator #`  - **`query`** The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/). - **`rollup_method`** The stats roll-up method - supports `count`, `avg` and `cardinality`. - **`measure`** For `avg` and cardinality `rollup_method` - specify the measure or the facet name you want to use. - **`time_window`** #m (5, 10, 15, or 30), #h (1, 2, or 4, 24). - **`operator`** `<`, `<=`, `>`, `>=`, `==`, or `!=`. - **`#`** an integer or decimal number used to set the threshold.  **NOTE** Only available on US1-FED, US3, and in closed beta on EU and US1.  **Process Alert Query**  Example: `processes(search).over(tags).rollup('count').last(timeframe) operator #`  - **`search`** free text search string for querying processes. Matching processes match results on the [Live Processes](https://docs.datadoghq.com/infrastructure/process/?tab=linuxwindows) page. - **`tags`** one or more tags (comma-separated) - **`timeframe`** the timeframe to roll up the counts. Examples: 10m, 4h. Supported timeframes: s, m, h and d - **`operator`** <, <=, >, >=, ==, or != - **`#`** an integer or decimal number used to set the threshold  **Logs Alert Query**  Example: `logs(query).index(index_name).rollup(rollup_method[, measure]).last(time_window) operator #`  - **`query`** The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/). - **`index_name`** For multi-index organizations, the log index in which the request is performed. - **`rollup_method`** The stats roll-up method - supports `count`, `avg` and `cardinality`. - **`measure`** For `avg` and cardinality `rollup_method` - specify the measure or the facet name you want to use. - **`time_window`** #m (between 1 and 2880), #h (between 1 and 48) - **`operator`** `<`, `<=`, `>`, `>=`, `==`, or `!=`. - **`#`** an integer or decimal number used to set the threshold.  **Composite Query**  Example: `12345 && 67890`, where `12345` and `67890` are the IDs of non-composite monitors  * **`name`** [*required*, *default* = **dynamic, based on query**]: The name of the alert. * **`message`** [*required*, *default* = **dynamic, based on query**]: A message to include with notifications for this monitor. Email notifications can be sent to specific users by using the same '@username' notation as events. * **`tags`** [*optional*, *default* = **empty list**]: A list of tags to associate with your monitor. When getting all monitor details via the API, use the `monitor_tags` argument to filter results by these tags. It is only available via the API and isn't visible or editable in the Datadog UI.  **SLO Alert Query**  Example: `error_budget(\"slo_id\").over(\"time_window\") operator #`  - **`slo_id`**: The alphanumeric SLO ID of the SLO you are configuring the alert for. - **`time_window`**: The time window of the SLO target you wish to alert on. Valid options: `7d`, `30d`, `90d`. - **`operator`**: `>=` or `>`
+Create a monitor using the specified options.  #### Monitor Types  The type of monitor chosen from:  - anomaly: `query alert` - APM: `query alert` or `trace-analytics alert` - composite: `composite` - custom: `service check` - event: `event alert` - forecast: `query alert` - host: `service check` - integration: `query alert` or `service check` - live process: `process alert` - logs: `log alert` - metric: `metric alert` - network: `service check` - outlier: `query alert` - process: `service check` - rum: `rum alert` - SLO: `slo alert` - watchdog: `event alert` - event-v2: `event-v2 alert`  #### Query Types  **Metric Alert Query**  Example: `time_aggr(time_window):space_aggr:metric{tags} [by {key}] operator #`  - `time_aggr`: avg, sum, max, min, change, or pct_change - `time_window`: `last_#m` (with `#` between 1 and 2880 depending on the monitor type) or `last_#h`(with `#` between 1 and 48 depending on the monitor type), or `last_1d` - `space_aggr`: avg, sum, min, or max - `tags`: one or more tags (comma-separated), or * - `key`: a 'key' in key:value tag syntax; defines a separate alert for each tag in the group (multi-alert) - `operator`: <, <=, >, >=, ==, or != - `#`: an integer or decimal number used to set the threshold  If you are using the `_change_` or `_pct_change_` time aggregator, instead use `change_aggr(time_aggr(time_window), timeshift):space_aggr:metric{tags} [by {key}] operator #` with:  - `change_aggr` change, pct_change - `time_aggr` avg, sum, max, min [Learn more](https://docs.datadoghq.com/monitors/monitor_types/#define-the-conditions) - `time_window` last\\_#m (between 1 and 2880 depending on the monitor type), last\\_#h (between 1 and 48 depending on the monitor type), or last_#d (1 or 2) - `timeshift` #m_ago (5, 10, 15, or 30), #h_ago (1, 2, or 4), or 1d_ago  Use this to create an outlier monitor using the following query: `avg(last_30m):outliers(avg:system.cpu.user{role:es-events-data} by {host}, 'dbscan', 7) > 0`  **Service Check Query**  Example: `\"check\".over(tags).last(count).by(group).count_by_status()`  - **`check`** name of the check, e.g. `datadog.agent.up` - **`tags`** one or more quoted tags (comma-separated), or \"*\". e.g.: `.over(\"env:prod\", \"role:db\")`; **`over`** cannot be blank. - **`count`** must be at greater than or equal to your max threshold (defined in the `options`). It is limited to 100. For example, if you've specified to notify on 1 critical, 3 ok, and 2 warn statuses, `count` should be at least 3. - **`group`** must be specified for check monitors. Per-check grouping is already explicitly known for some service checks. For example, Postgres integration monitors are tagged by `db`, `host`, and `port`, and Network monitors by `host`, `instance`, and `url`. See [Service Checks](https://docs.datadoghq.com/api/latest/service-checks/) documentation for more information.  **Event Alert Query**  Example: `events('sources:nagios status:error,warning priority:normal tags: \"string query\"').rollup(\"count\").last(\"1h\")\"`  - **`event`**, the event query string: - **`string_query`** free text query to match against event title and text. - **`sources`** event sources (comma-separated). - **`status`** event statuses (comma-separated). Valid options: error, warn, and info. - **`priority`** event priorities (comma-separated). Valid options: low, normal, all. - **`host`** event reporting host (comma-separated). - **`tags`** event tags (comma-separated). - **`excluded_tags`** excluded event tags (comma-separated). - **`rollup`** the stats roll-up method. `count` is the only supported method now. - **`last`** the timeframe to roll up the counts. Examples: 45m, 4h. Supported timeframes: m, h and d. This value should not exceed 48 hours.  **NOTE** Only available on US1 and EU.  **Event V2 Alert Query**  Example: `events(query).rollup(rollup_method[, measure]).last(time_window) operator #`  - **`query`** The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/). - **`rollup_method`** The stats roll-up method - supports `count`, `avg` and `cardinality`. - **`measure`** For `avg` and cardinality `rollup_method` - specify the measure or the facet name you want to use. - **`time_window`** #m (5, 10, 15, or 30), #h (1, 2, or 4, 24). - **`operator`** `<`, `<=`, `>`, `>=`, `==`, or `!=`. - **`#`** an integer or decimal number used to set the threshold.  **NOTE** Only available on US1-FED, US3, and in closed beta on EU and US1.  **Process Alert Query**  Example: `processes(search).over(tags).rollup('count').last(timeframe) operator #`  - **`search`** free text search string for querying processes. Matching processes match results on the [Live Processes](https://docs.datadoghq.com/infrastructure/process/?tab=linuxwindows) page. - **`tags`** one or more tags (comma-separated) - **`timeframe`** the timeframe to roll up the counts. Examples: 10m, 4h. Supported timeframes: s, m, h and d - **`operator`** <, <=, >, >=, ==, or != - **`#`** an integer or decimal number used to set the threshold  **Logs Alert Query**  Example: `logs(query).index(index_name).rollup(rollup_method[, measure]).last(time_window) operator #`  - **`query`** The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/). - **`index_name`** For multi-index organizations, the log index in which the request is performed. - **`rollup_method`** The stats roll-up method - supports `count`, `avg` and `cardinality`. - **`measure`** For `avg` and cardinality `rollup_method` - specify the measure or the facet name you want to use. - **`time_window`** #m (between 1 and 2880), #h (between 1 and 48) - **`operator`** `<`, `<=`, `>`, `>=`, `==`, or `!=`. - **`#`** an integer or decimal number used to set the threshold.  **Composite Query**  Example: `12345 && 67890`, where `12345` and `67890` are the IDs of non-composite monitors  * **`name`** [*required*, *default* = **dynamic, based on query**]: The name of the alert. * **`message`** [*required*, *default* = **dynamic, based on query**]: A message to include with notifications for this monitor. Email notifications can be sent to specific users by using the same '@username' notation as events. * **`tags`** [*optional*, *default* = **empty list**]: A list of tags to associate with your monitor. When getting all monitor details via the API, use the `monitor_tags` argument to filter results by these tags. It is only available via the API and isn't visible or editable in the Datadog UI.  **SLO Alert Query**  Example: `error_budget(\"slo_id\").over(\"time_window\") operator #`  - **`slo_id`**: The alphanumeric SLO ID of the SLO you are configuring the alert for. - **`time_window`**: The time window of the SLO target you wish to alert on. Valid options: `7d`, `30d`, `90d`. - **`operator`**: `>=` or `>`
 
 ### Examples
 
 ```ruby
 require 'datadog_api_client'
 api_instance = DatadogAPIClient::V1::MonitorsAPI.new
-body = DatadogAPIClient::V1::Monitor.new # Monitor | Create a monitor request body.
+body = DatadogAPIClient::V1::Monitor.new({query: 'avg(last_5m):sum:system.net.bytes_rcvd{host:host0} > 100', type: DatadogAPIClient::V1::MonitorType::COMPOSITE}) # Monitor | Create a monitor request body.
 
 begin
   # Create a monitor
@@ -152,7 +154,7 @@ require 'datadog_api_client'
 api_instance = DatadogAPIClient::V1::MonitorsAPI.new
 monitor_id = 789 # Integer | The ID of the monitor.
 opts = {
-  force: 'force_example' # String | Delete the monitor even if it's referenced by other resources (e.g. SLO, composite monitor).
+  force: 'false' # String | Delete the monitor even if it's referenced by other resources (e.g. SLO, composite monitor).
 }
 
 begin
@@ -283,14 +285,14 @@ Get details about the specified monitor from your organization.
 require 'datadog_api_client'
 api_instance = DatadogAPIClient::V1::MonitorsAPI.new
 opts = {
-  group_states: 'group_states_example', # String | When specified, shows additional information about the group states. Choose one or more from `all`, `alert`, `warn`, and `no data`.
+  group_states: 'alert', # String | When specified, shows additional information about the group states. Choose one or more from `all`, `alert`, `warn`, and `no data`.
   name: 'name_example', # String | A string to filter monitors by name.
-  tags: 'tags_example', # String | A comma separated list indicating what tags, if any, should be used to filter the list of monitors by scope. For example, `host:host0`.
-  monitor_tags: 'monitor_tags_example', # String | A comma separated list indicating what service and/or custom tags, if any, should be used to filter the list of monitors. Tags created in the Datadog UI automatically have the service key prepended. For example, `service:my-app`.
+  tags: 'host:host0', # String | A comma separated list indicating what tags, if any, should be used to filter the list of monitors by scope. For example, `host:host0`.
+  monitor_tags: 'service:my-app', # String | A comma separated list indicating what service and/or custom tags, if any, should be used to filter the list of monitors. Tags created in the Datadog UI automatically have the service key prepended. For example, `service:my-app`.
   with_downtimes: true, # Boolean | If this argument is set to true, then the returned data includes all current downtimes for each monitor.
   id_offset: 789, # Integer | Monitor ID offset.
-  page: 789, # Integer | The page to start paginating from. If this argument is not specified, the request returns all monitors without pagination.
-  page_size: 56 # Integer | The number of monitors to return per page. If the page argument is not specified, the default behavior returns all monitors without a `page_size` limit. However, if page is specified and `page_size` is not, the argument defaults to 100.
+  page: 0, # Integer | The page to start paginating from. If this argument is not specified, the request returns all monitors without pagination.
+  page_size: 20 # Integer | The number of monitors to return per page. If the page argument is not specified, the default behavior returns all monitors without a `page_size` limit. However, if page is specified and `page_size` is not, the argument defaults to 100.
 }
 
 begin
@@ -347,6 +349,146 @@ end
 - **Accept**: application/json
 
 
+## search_monitor_groups
+
+> <MonitorGroupSearchResponse> search_monitor_groups(opts)
+
+Monitors group search
+
+Search and filter your monitor groups details.
+
+### Examples
+
+```ruby
+require 'datadog_api_client'
+api_instance = DatadogAPIClient::V1::MonitorsAPI.new
+opts = {
+  query: 'query_example', # String | After entering a search query in your [Manage Monitor page][1] use the query parameter value in the URL of the page as value for this parameter. Consult the dedicated [manage monitor documentation][2] page to learn more.  The query can contain any number of space-separated monitor attributes, for instance `query=\"type:metric status:alert\"`.  [1]: https://app.datadoghq.com/monitors/manage [2]: /monitors/manage_monitor/#find-the-monitors
+  page: 789, # Integer | Page to start paginating from.
+  per_page: 789, # Integer | Number of monitors to return per page.
+  sort: 'sort_example' # String | String for sort order, composed of field and sort order separate by a comma, e.g. `name,asc`. Supported sort directions: `asc`, `desc`. Supported fields:  * `name` * `status` * `tags`
+}
+
+begin
+  # Monitors group search
+  result = api_instance.search_monitor_groups(opts)
+  p result
+rescue DatadogAPIClient::V1::APIError => e
+  puts "Error when calling MonitorsAPI->search_monitor_groups: #{e}"
+end
+```
+
+#### Using the search_monitor_groups_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<MonitorGroupSearchResponse>, Integer, Hash)> search_monitor_groups_with_http_info(opts)
+
+```ruby
+begin
+  # Monitors group search
+  data, status_code, headers = api_instance.search_monitor_groups_with_http_info(opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <MonitorGroupSearchResponse>
+rescue DatadogAPIClient::V1::APIError => e
+  puts "Error when calling MonitorsAPI->search_monitor_groups_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **query** | **String** | After entering a search query in your [Manage Monitor page][1] use the query parameter value in the URL of the page as value for this parameter. Consult the dedicated [manage monitor documentation][2] page to learn more.  The query can contain any number of space-separated monitor attributes, for instance &#x60;query&#x3D;\&quot;type:metric status:alert\&quot;&#x60;.  [1]: https://app.datadoghq.com/monitors/manage [2]: /monitors/manage_monitor/#find-the-monitors | [optional] |
+| **page** | **Integer** | Page to start paginating from. | [optional][default to 0] |
+| **per_page** | **Integer** | Number of monitors to return per page. | [optional][default to 30] |
+| **sort** | **String** | String for sort order, composed of field and sort order separate by a comma, e.g. &#x60;name,asc&#x60;. Supported sort directions: &#x60;asc&#x60;, &#x60;desc&#x60;. Supported fields:  * &#x60;name&#x60; * &#x60;status&#x60; * &#x60;tags&#x60; | [optional] |
+
+### Return type
+
+[**MonitorGroupSearchResponse**](MonitorGroupSearchResponse.md)
+
+### Authorization
+
+[apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## search_monitors
+
+> <MonitorSearchResponse> search_monitors(opts)
+
+Monitors search
+
+Search and filter your monitors details.
+
+### Examples
+
+```ruby
+require 'datadog_api_client'
+api_instance = DatadogAPIClient::V1::MonitorsAPI.new
+opts = {
+  query: 'query_example', # String | After entering a search query in your [Manage Monitor page][1] use the query parameter value in the URL of the page as value for this parameter. Consult the dedicated [manage monitor documentation][2] page to learn more.  The query can contain any number of space-separated monitor attributes, for instance `query=\"type:metric status:alert\"`.  [1]: https://app.datadoghq.com/monitors/manage [2]: /monitors/manage_monitor/#find-the-monitors
+  page: 789, # Integer | Page to start paginating from.
+  per_page: 789, # Integer | Number of monitors to return per page.
+  sort: 'sort_example' # String | String for sort order, composed of field and sort order separate by a comma, e.g. `name,asc`. Supported sort directions: `asc`, `desc`. Supported fields:  * `name` * `status` * `tags`
+}
+
+begin
+  # Monitors search
+  result = api_instance.search_monitors(opts)
+  p result
+rescue DatadogAPIClient::V1::APIError => e
+  puts "Error when calling MonitorsAPI->search_monitors: #{e}"
+end
+```
+
+#### Using the search_monitors_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<MonitorSearchResponse>, Integer, Hash)> search_monitors_with_http_info(opts)
+
+```ruby
+begin
+  # Monitors search
+  data, status_code, headers = api_instance.search_monitors_with_http_info(opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <MonitorSearchResponse>
+rescue DatadogAPIClient::V1::APIError => e
+  puts "Error when calling MonitorsAPI->search_monitors_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **query** | **String** | After entering a search query in your [Manage Monitor page][1] use the query parameter value in the URL of the page as value for this parameter. Consult the dedicated [manage monitor documentation][2] page to learn more.  The query can contain any number of space-separated monitor attributes, for instance &#x60;query&#x3D;\&quot;type:metric status:alert\&quot;&#x60;.  [1]: https://app.datadoghq.com/monitors/manage [2]: /monitors/manage_monitor/#find-the-monitors | [optional] |
+| **page** | **Integer** | Page to start paginating from. | [optional][default to 0] |
+| **per_page** | **Integer** | Number of monitors to return per page. | [optional][default to 30] |
+| **sort** | **String** | String for sort order, composed of field and sort order separate by a comma, e.g. &#x60;name,asc&#x60;. Supported sort directions: &#x60;asc&#x60;, &#x60;desc&#x60;. Supported fields:  * &#x60;name&#x60; * &#x60;status&#x60; * &#x60;tags&#x60; | [optional] |
+
+### Return type
+
+[**MonitorSearchResponse**](MonitorSearchResponse.md)
+
+### Authorization
+
+[apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
 ## update_monitor
 
 > <Monitor> update_monitor(monitor_id, body)
@@ -413,7 +555,7 @@ end
 
 ## validate_monitor
 
-> <Monitor> validate_monitor(body)
+> Object validate_monitor(body)
 
 Validate a monitor
 
@@ -424,7 +566,7 @@ Validate the monitor provided in the request.
 ```ruby
 require 'datadog_api_client'
 api_instance = DatadogAPIClient::V1::MonitorsAPI.new
-body = DatadogAPIClient::V1::Monitor.new # Monitor | Monitor request object
+body = DatadogAPIClient::V1::Monitor.new({query: 'avg(last_5m):sum:system.net.bytes_rcvd{host:host0} > 100', type: DatadogAPIClient::V1::MonitorType::COMPOSITE}) # Monitor | Monitor request object
 
 begin
   # Validate a monitor
@@ -439,7 +581,7 @@ end
 
 This returns an Array which contains the response data, status code and headers.
 
-> <Array(<Monitor>, Integer, Hash)> validate_monitor_with_http_info(body)
+> <Array(Object, Integer, Hash)> validate_monitor_with_http_info(body)
 
 ```ruby
 begin
@@ -447,7 +589,7 @@ begin
   data, status_code, headers = api_instance.validate_monitor_with_http_info(body)
   p status_code # => 2xx
   p headers # => { ... }
-  p data # => <Monitor>
+  p data # => Object
 rescue DatadogAPIClient::V1::APIError => e
   puts "Error when calling MonitorsAPI->validate_monitor_with_http_info: #{e}"
 end
@@ -461,7 +603,7 @@ end
 
 ### Return type
 
-[**Monitor**](Monitor.md)
+**Object**
 
 ### Authorization