datadog_api_client 1.0.0 → 1.4.0

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 |
 
@@ -17,8 +19,6 @@ All URIs are relative to *https://api.datadoghq.com*
 
 > <CheckCanDeleteMonitorResponse> check_can_delete_monitor(monitor_ids)
 
-Check if a monitor can be deleted
-
 Check if the given monitors can be deleted.
 
 ### Examples
@@ -67,7 +67,7 @@ end
 
 ### Authorization
 
-[apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
+[AuthZ](README.md#AuthZ), [apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
 
 ### HTTP request headers
 
@@ -79,16 +79,159 @@ end
 
 > <Monitor> create_monitor(body)
 
-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`
+- audit: `audit 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 10080 depending on the monitor type) or `last_#h`(with `#` between 1 and 168 depending on the monitor type) or `last_1d`, or `last_1w`
+- `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/create/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 (between 1 and 2880), #h (between 1 and 48).
+- **`operator`** `<`, `<=`, `>`, `>=`, `==`, or `!=`.
+- **`#`** an integer or decimal number used to set the threshold.
+
+**NOTE** Only available on US1-FED, US3, US5 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).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 `>`
+**Audit Alert Query**
+
+Example: `audits(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 (between 1 and 2880), #h (between 1 and 48).
+- **`operator`** `<`, `<=`, `>`, `>=`, `==`, or `!=`.
+- **`#`** an integer or decimal number used to set the threshold.
+
+**NOTE** Only available on US1-FED and in closed beta on US1, EU, US3, and US5.
 
 ### 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
@@ -129,7 +272,7 @@ end
 
 ### Authorization
 
-[apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
+[AuthZ](README.md#AuthZ), [apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
 
 ### HTTP request headers
 
@@ -141,8 +284,6 @@ end
 
 > <DeletedMonitor> delete_monitor(monitor_id, opts)
 
-Delete a monitor
-
 Delete the specified monitor
 
 ### Examples
@@ -152,7 +293,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
@@ -195,7 +336,7 @@ end
 
 ### Authorization
 
-[apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
+[AuthZ](README.md#AuthZ), [apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
 
 ### HTTP request headers
 
@@ -207,8 +348,6 @@ end
 
 > <Monitor> get_monitor(monitor_id, opts)
 
-Get a monitor's details
-
 Get details about the specified monitor from your organization.
 
 ### Examples
@@ -261,7 +400,7 @@ end
 
 ### Authorization
 
-[apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
+[AuthZ](README.md#AuthZ), [apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
 
 ### HTTP request headers
 
@@ -273,8 +412,6 @@ end
 
 > <Array<Monitor>> list_monitors(opts)
 
-Get all monitor details
-
 Get details about the specified monitor from your organization.
 
 ### Examples
@@ -283,14 +420,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`.
-  with_downtimes: true, # Boolean | If this argument is set to true, then the returned data includes all current downtimes for each monitor.
+  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 active 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
@@ -328,7 +465,7 @@ end
 | **name** | **String** | A string to filter monitors by name. | [optional] |
 | **tags** | **String** | A comma separated list indicating what tags, if any, should be used to filter the list of monitors by scope. For example, &#x60;host:host0&#x60;. | [optional] |
 | **monitor_tags** | **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, &#x60;service:my-app&#x60;. | [optional] |
-| **with_downtimes** | **Boolean** | If this argument is set to true, then the returned data includes all current downtimes for each monitor. | [optional] |
+| **with_downtimes** | **Boolean** | If this argument is set to true, then the returned data includes all current active downtimes for each monitor. | [optional] |
 | **id_offset** | **Integer** | Monitor ID offset. | [optional] |
 | **page** | **Integer** | The page to start paginating from. If this argument is not specified, the request returns all monitors without pagination. | [optional] |
 | **page_size** | **Integer** | The number of monitors to return per page. If the page argument is not specified, the default behavior returns all monitors without a &#x60;page_size&#x60; limit. However, if page is specified and &#x60;page_size&#x60; is not, the argument defaults to 100. | [optional] |
@@ -339,7 +476,143 @@ end
 
 ### Authorization
 
-[apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
+[AuthZ](README.md#AuthZ), [apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## search_monitor_groups
+
+> <MonitorGroupSearchResponse> search_monitor_groups(opts)
+
+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/#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/#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
+
+[AuthZ](README.md#AuthZ), [apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## search_monitors
+
+> <MonitorSearchResponse> search_monitors(opts)
+
+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/#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/#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
+
+[AuthZ](README.md#AuthZ), [apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
 
 ### HTTP request headers
 
@@ -351,8 +624,6 @@ end
 
 > <Monitor> update_monitor(monitor_id, body)
 
-Edit a monitor
-
 Edit the specified monitor.
 
 ### Examples
@@ -403,7 +674,7 @@ end
 
 ### Authorization
 
-[apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
+[AuthZ](README.md#AuthZ), [apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
 
 ### HTTP request headers
 
@@ -413,9 +684,7 @@ end
 
 ## validate_monitor
 
-> <Monitor> validate_monitor(body)
-
-Validate a monitor
+> Object validate_monitor(body)
 
 Validate the monitor provided in the request.
 
@@ -424,7 +693,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 +708,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 +716,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,11 +730,11 @@ end
 
 ### Return type
 
-[**Monitor**](Monitor.md)
+**Object**
 
 ### Authorization
 
-[apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
+[AuthZ](README.md#AuthZ), [apiKeyAuth](README.md#apiKeyAuth), [appKeyAuth](README.md#appKeyAuth)
 
 ### HTTP request headers
 

data/docs/v1/NotebookCreateDataAttributes.md

@@ -5,7 +5,8 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **cells** | [**Array<NotebookCellCreateRequest>**](NotebookCellCreateRequest.md) | List of cells to display in the notebook. |  |
-| **name** | **String** | Notebook name. |  |
+| **metadata** | [**NotebookMetadata**](NotebookMetadata.md) |  | [optional] |
+| **name** | **String** | The name of the notebook. |  |
 | **status** | [**NotebookStatus**](NotebookStatus.md) |  | [optional][default to 'published'] |
 | **time** | [**NotebookGlobalTime**](NotebookGlobalTime.md) |  |  |
 
@@ -16,6 +17,7 @@ require 'datadog_api_client/v1'
 
 instance = DatadogAPIClient::V1::NotebookCreateDataAttributes.new(
   cells: [{"attributes":{"definition":{"text":"## Some test markdown\n\n```js\nvar x, y;\nx = 5;\ny = 6;\n```","type":"markdown"}},"type":"notebook_cells"},{"attributes":{"definition":{"requests":[{"display_type":"line","q":"avg:system.load.1{*}","style":{"line_type":"solid","line_width":"normal","palette":"dog_classic"}}],"show_legend":true,"type":"timeseries","yaxis":{"scale":"linear"}},"graph_size":"m","split_by":{"keys":[],"tags":[]},"time":null},"type":"notebook_cells"}],
+  metadata: null,
   name: Example Notebook,
   status: null,
   time: null

data/docs/v1/NotebookMetadata.md

@@ -0,0 +1,22 @@
+# DatadogAPIClient::V1::NotebookMetadata
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **is_template** | **Boolean** | Whether or not the notebook is a template. | [optional][default to false] |
+| **take_snapshots** | **Boolean** | Whether or not the notebook takes snapshot image backups of the notebook's fixed-time graphs. | [optional][default to false] |
+| **type** | [**NotebookMetadataType**](NotebookMetadataType.md) |  | [optional][default to 'null'] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::NotebookMetadata.new(
+  is_template: false,
+  take_snapshots: false,
+  type: null
+)
+```
+

data/docs/v1/NotebookMetadataType.md

@@ -0,0 +1,15 @@
+# DatadogAPIClient::V1::NotebookMetadataType
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::NotebookMetadataType.new()
+```
+

data/docs/v1/NotebookResponseDataAttributes.md

@@ -6,9 +6,10 @@
 | ---- | ---- | ----------- | ----- |
 | **author** | [**NotebookAuthor**](NotebookAuthor.md) |  | [optional] |
 | **cells** | [**Array<NotebookCellResponse>**](NotebookCellResponse.md) | List of cells to display in the notebook. |  |
-| **created** | **Time** | UTC time stamp. | [optional][readonly] |
-| **modified** | **Time** | UTC time stamp. | [optional][readonly] |
-| **name** | **String** | Notebook name. |  |
+| **created** | **Time** | UTC time stamp for when the notebook was created. | [optional][readonly] |
+| **metadata** | [**NotebookMetadata**](NotebookMetadata.md) |  | [optional] |
+| **modified** | **Time** | UTC time stamp for when the notebook was last modified. | [optional][readonly] |
+| **name** | **String** | The name of the notebook. |  |
 | **status** | [**NotebookStatus**](NotebookStatus.md) |  | [optional][default to 'published'] |
 | **time** | [**NotebookGlobalTime**](NotebookGlobalTime.md) |  |  |
 
@@ -21,6 +22,7 @@ instance = DatadogAPIClient::V1::NotebookResponseDataAttributes.new(
   author: null,
   cells: [{"attributes":{"definition":{"text":"## Some test markdown\n\n```js\nvar x, y;\nx = 5;\ny = 6;\n```","type":"markdown"}},"id":"bzbycoya","type":"notebook_cells"},{"attributes":{"definition":{"requests":[{"display_type":"line","q":"avg:system.load.1{*}","style":{"line_type":"solid","line_width":"normal","palette":"dog_classic"}}],"show_legend":true,"type":"timeseries","yaxis":{"scale":"linear"}},"graph_size":"m","split_by":{"keys":[],"tags":[]},"time":null},"id":"9k6bc6xc","type":"notebook_cells"}],
   created: 2021-02-24T23:14:15.173964Z,
+  metadata: null,
   modified: 2021-02-24T23:15:23.274966Z,
   name: Example Notebook,
   status: null,

data/docs/v1/NotebookUpdateDataAttributes.md

@@ -5,7 +5,8 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **cells** | [**Array<NotebookUpdateCell>**](NotebookUpdateCell.md) | List of cells to display in the notebook. |  |
-| **name** | **String** | Notebook name. |  |
+| **metadata** | [**NotebookMetadata**](NotebookMetadata.md) |  | [optional] |
+| **name** | **String** | The name of the notebook. |  |
 | **status** | [**NotebookStatus**](NotebookStatus.md) |  | [optional][default to 'published'] |
 | **time** | [**NotebookGlobalTime**](NotebookGlobalTime.md) |  |  |
 
@@ -16,6 +17,7 @@ require 'datadog_api_client/v1'
 
 instance = DatadogAPIClient::V1::NotebookUpdateDataAttributes.new(
   cells: [{"attributes":{"definition":{"text":"## Some test markdown\n\n```js\nvar x, y;\nx = 5;\ny = 6;\n```","type":"markdown"}},"id":"bzbycoya","type":"notebook_cells"},{"attributes":{"definition":{"requests":[{"display_type":"line","q":"avg:system.load.1{*}","style":{"line_type":"solid","line_width":"normal","palette":"dog_classic"}}],"show_legend":true,"type":"timeseries","yaxis":{"scale":"linear"}},"graph_size":"m","split_by":{"keys":[],"tags":[]},"time":null},"id":"9k6bc6xc","type":"notebook_cells"}],
+  metadata: null,
   name: Example Notebook,
   status: null,
   time: null