datadog_api_client 1.1.0 → 1.2.0

data/docs/v2/SecurityMonitoringListRulesResponse.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **data** | [**Array<SecurityMonitoringRuleResponse>**](SecurityMonitoringRuleResponse.md) | TODO. | [optional] |
+| **data** | [**Array<SecurityMonitoringRuleResponse>**](SecurityMonitoringRuleResponse.md) | Array containing the list of rules. | [optional] |
 | **meta** | [**ResponseMetaAttributes**](ResponseMetaAttributes.md) |  | [optional] |
 
 ## Example

data/docs/v2/SecurityMonitoringRuleCreatePayload.md

@@ -6,6 +6,7 @@
 | ---- | ---- | ----------- | ----- |
 | **cases** | [**Array<SecurityMonitoringRuleCaseCreate>**](SecurityMonitoringRuleCaseCreate.md) | Cases for generating signals. |  |
 | **filters** | [**Array<SecurityMonitoringFilter>**](SecurityMonitoringFilter.md) | Additional queries to filter matched events before they are processed. | [optional] |
+| **has_extended_title** | **Boolean** | Whether the notifications include the triggering group-by values in their title. | [optional] |
 | **is_enabled** | **Boolean** | Whether the rule is enabled. |  |
 | **message** | **String** | Message for generated signals. |  |
 | **name** | **String** | The name of the rule. |  |
@@ -21,9 +22,10 @@ require 'datadog_api_client/v2'
 instance = DatadogAPIClient::V2::SecurityMonitoringRuleCreatePayload.new(
   cases: [],
   filters: null,
+  has_extended_title: true,
   is_enabled: true,
   message: ,
-  name: ,
+  name: My security monitoring rule.,
   options: null,
   queries: [],
   tags: ["env:prod","team:security"]

data/docs/v2/SecurityMonitoringRuleQueryCreate.md

@@ -24,7 +24,7 @@ instance = DatadogAPIClient::V2::SecurityMonitoringRuleQueryCreate.new(
   group_by_fields: null,
   metric: null,
   name: null,
-  query: a < 3
+  query: a > 3
 )
 ```
 

data/docs/v2/SecurityMonitoringRuleResponse.md

@@ -8,6 +8,7 @@
 | **created_at** | **Integer** | When the rule was created, timestamp in milliseconds. | [optional] |
 | **creation_author_id** | **Integer** | User ID of the user who created the rule. | [optional] |
 | **filters** | [**Array<SecurityMonitoringFilter>**](SecurityMonitoringFilter.md) | Additional queries to filter matched events before they are processed. | [optional] |
+| **has_extended_title** | **Boolean** | Whether the notifications include the triggering group-by values in their title. | [optional] |
 | **id** | **String** | The ID of the rule. | [optional] |
 | **is_default** | **Boolean** | Whether the rule is included by default. | [optional] |
 | **is_deleted** | **Boolean** | Whether the rule has been deleted. | [optional] |
@@ -17,6 +18,7 @@
 | **options** | [**SecurityMonitoringRuleOptions**](SecurityMonitoringRuleOptions.md) |  | [optional] |
 | **queries** | [**Array<SecurityMonitoringRuleQuery>**](SecurityMonitoringRuleQuery.md) | Queries for selecting logs which are part of the rule. | [optional] |
 | **tags** | **Array<String>** | Tags for generated signals. | [optional] |
+| **update_author_id** | **Integer** | User ID of the user who updated the rule. | [optional] |
 | **version** | **Integer** | The version of the rule. | [optional] |
 
 ## Example
@@ -29,6 +31,7 @@ instance = DatadogAPIClient::V2::SecurityMonitoringRuleResponse.new(
   created_at: null,
   creation_author_id: null,
   filters: null,
+  has_extended_title: null,
   id: null,
   is_default: null,
   is_deleted: null,
@@ -38,6 +41,7 @@ instance = DatadogAPIClient::V2::SecurityMonitoringRuleResponse.new(
   options: null,
   queries: null,
   tags: null,
+  update_author_id: null,
   version: null
 )
 ```

data/docs/v2/SecurityMonitoringRuleUpdatePayload.md

@@ -6,12 +6,14 @@
 | ---- | ---- | ----------- | ----- |
 | **cases** | [**Array<SecurityMonitoringRuleCase>**](SecurityMonitoringRuleCase.md) | Cases for generating signals. | [optional] |
 | **filters** | [**Array<SecurityMonitoringFilter>**](SecurityMonitoringFilter.md) | Additional queries to filter matched events before they are processed. | [optional] |
+| **has_extended_title** | **Boolean** | Whether the notifications include the triggering group-by values in their title. | [optional] |
 | **is_enabled** | **Boolean** | Whether the rule is enabled. | [optional] |
 | **message** | **String** | Message for generated signals. | [optional] |
 | **name** | **String** | Name of the rule. | [optional] |
 | **options** | [**SecurityMonitoringRuleOptions**](SecurityMonitoringRuleOptions.md) |  | [optional] |
 | **queries** | [**Array<SecurityMonitoringRuleQuery>**](SecurityMonitoringRuleQuery.md) | Queries for selecting logs which are part of the rule. | [optional] |
 | **tags** | **Array<String>** | Tags for generated signals. | [optional] |
+| **version** | **Integer** | The version of the rule being updated. | [optional] |
 
 ## Example
 
@@ -21,12 +23,14 @@ require 'datadog_api_client/v2'
 instance = DatadogAPIClient::V2::SecurityMonitoringRuleUpdatePayload.new(
   cases: null,
   filters: null,
+  has_extended_title: true,
   is_enabled: null,
   message: null,
   name: null,
   options: null,
   queries: null,
-  tags: null
+  tags: null,
+  version: 1
 )
 ```
 

data/docs/v2/UsersAPI.md

@@ -19,8 +19,6 @@ All URIs are relative to *https://api.datadoghq.com*
 
 > <UserResponse> create_user(body)
 
-Create a user
-
 Create a user for your organization.
 
 ### Examples
@@ -81,9 +79,8 @@ end
 
 > disable_user(user_id)
 
-Disable a user
-
-Disable a user. Can only be used with an application key belonging to an administrator user.
+Disable a user. Can only be used with an application key belonging
+to an administrator user.
 
 ### Examples
 
@@ -142,8 +139,6 @@ nil (empty response body)
 
 > <UserInvitationResponse> get_invitation(user_invitation_uuid)
 
-Get a user invitation
-
 Returns a single user invitation by its UUID.
 
 ### Examples
@@ -204,8 +199,6 @@ end
 
 > <UserResponse> get_user(user_id)
 
-Get user details
-
 Get a user in the organization specified by the user’s `user_id`.
 
 ### Examples
@@ -266,9 +259,8 @@ end
 
 > <UserResponse> list_user_organizations(user_id)
 
-Get a user organization
-
-Get a user organization. Returns the user information and all organizations joined by this user.
+Get a user organization. Returns the user information and all organizations
+joined by this user.
 
 ### Examples
 
@@ -328,9 +320,8 @@ end
 
 > <PermissionsResponse> list_user_permissions(user_id)
 
-Get a user permissions
-
-Get a user permission set. Returns a list of the user’s permissions granted by the associated user's roles.
+Get a user permission set. Returns a list of the user’s permissions
+granted by the associated user's roles.
 
 ### Examples
 
@@ -390,9 +381,8 @@ end
 
 > <UsersResponse> list_users(opts)
 
-List all users
-
-Get the list of all users in the organization. This list includes all users even if they are deactivated or unverified.
+Get the list of all users in the organization. This list includes
+all users even if they are deactivated or unverified.
 
 ### Examples
 
@@ -464,8 +454,6 @@ end
 
 > <UserInvitationsResponse> send_invitations(body)
 
-Send invitation emails
-
 Sends emails to one or more users inviting them to join the organization.
 
 ### Examples
@@ -526,9 +514,8 @@ end
 
 > <UserResponse> update_user(user_id, body)
 
-Update a user
-
-Edit a user. Can only be used with an application key belonging to an administrator user.
+Edit a user. Can only be used with an application key belonging
+to an administrator user.
 
 ### Examples
 

data/lib/datadog_api_client/v1.rb

@@ -24,6 +24,7 @@ require 'datadog_api_client/v1/models/api_error_response'
 require 'datadog_api_client/v1/models/aws_account'
 require 'datadog_api_client/v1/models/aws_account_and_lambda_request'
 require 'datadog_api_client/v1/models/aws_account_create_response'
+require 'datadog_api_client/v1/models/aws_account_delete_request'
 require 'datadog_api_client/v1/models/aws_account_list_response'
 require 'datadog_api_client/v1/models/aws_logs_async_error'
 require 'datadog_api_client/v1/models/aws_logs_async_response'
@@ -305,11 +306,13 @@ require 'datadog_api_client/v1/models/organization_subscription'
 require 'datadog_api_client/v1/models/pager_duty_service'
 require 'datadog_api_client/v1/models/pager_duty_service_key'
 require 'datadog_api_client/v1/models/pager_duty_service_name'
+require 'datadog_api_client/v1/models/pagination'
 require 'datadog_api_client/v1/models/process_query_definition'
 require 'datadog_api_client/v1/models/query_sort_order'
 require 'datadog_api_client/v1/models/query_value_widget_definition'
 require 'datadog_api_client/v1/models/query_value_widget_definition_type'
 require 'datadog_api_client/v1/models/query_value_widget_request'
+require 'datadog_api_client/v1/models/response_meta_attributes'
 require 'datadog_api_client/v1/models/slo_bulk_delete_error'
 require 'datadog_api_client/v1/models/slo_bulk_delete_response'
 require 'datadog_api_client/v1/models/slo_bulk_delete_response_data'
@@ -446,7 +449,6 @@ require 'datadog_api_client/v1/models/synthetics_test_process_status'
 require 'datadog_api_client/v1/models/synthetics_test_request'
 require 'datadog_api_client/v1/models/synthetics_test_request_certificate'
 require 'datadog_api_client/v1/models/synthetics_test_request_certificate_item'
-require 'datadog_api_client/v1/models/synthetics_tick_interval'
 require 'datadog_api_client/v1/models/synthetics_timing'
 require 'datadog_api_client/v1/models/synthetics_trigger_ci_test_location'
 require 'datadog_api_client/v1/models/synthetics_trigger_ci_test_run_result'
@@ -470,6 +472,12 @@ require 'datadog_api_client/v1/models/timeseries_widget_request'
 require 'datadog_api_client/v1/models/toplist_widget_definition'
 require 'datadog_api_client/v1/models/toplist_widget_definition_type'
 require 'datadog_api_client/v1/models/toplist_widget_request'
+require 'datadog_api_client/v1/models/tree_map_color_by'
+require 'datadog_api_client/v1/models/tree_map_group_by'
+require 'datadog_api_client/v1/models/tree_map_size_by'
+require 'datadog_api_client/v1/models/tree_map_widget_definition'
+require 'datadog_api_client/v1/models/tree_map_widget_definition_type'
+require 'datadog_api_client/v1/models/tree_map_widget_request'
 require 'datadog_api_client/v1/models/usage_analyzed_logs_hour'
 require 'datadog_api_client/v1/models/usage_analyzed_logs_response'
 require 'datadog_api_client/v1/models/usage_attribution_aggregates_body'
@@ -548,10 +556,6 @@ require 'datadog_api_client/v1/models/usage_timeseries_response'
 require 'datadog_api_client/v1/models/usage_top_avg_metrics_hour'
 require 'datadog_api_client/v1/models/usage_top_avg_metrics_metadata'
 require 'datadog_api_client/v1/models/usage_top_avg_metrics_response'
-require 'datadog_api_client/v1/models/usage_trace_hour'
-require 'datadog_api_client/v1/models/usage_trace_response'
-require 'datadog_api_client/v1/models/usage_tracing_without_limits_hour'
-require 'datadog_api_client/v1/models/usage_tracing_without_limits_response'
 require 'datadog_api_client/v1/models/user'
 require 'datadog_api_client/v1/models/user_disable_response'
 require 'datadog_api_client/v1/models/user_list_response'

data/lib/datadog_api_client/v1/api/aws_integration_api.rb

@@ -174,7 +174,7 @@ module DatadogAPIClient::V1
 
     # Generate a new external ID
     # Generate a new AWS external ID for a given AWS account ID and role name pair.
-    # @param body [AWSAccount] Your Datadog role delegation name. For more information about your AWS account Role name, see the [Datadog AWS integration configuration info](https://github.com/DataDog/documentation/blob/master/integrations/amazon_web_services/#installation).
+    # @param body [AWSAccount] Your Datadog role delegation name. For more information about your AWS account Role name, see the [Datadog AWS integration configuration info](https://docs.datadoghq.com/integrations/amazon_web_services/#setup).
     # @param [Hash] opts the optional parameters
     # @return [AWSAccountCreateResponse]
     def create_new_aws_external_id(body, opts = {})
@@ -184,7 +184,7 @@ module DatadogAPIClient::V1
 
     # Generate a new external ID
     # Generate a new AWS external ID for a given AWS account ID and role name pair.
-    # @param body [AWSAccount] Your Datadog role delegation name. For more information about your AWS account Role name, see the [Datadog AWS integration configuration info](https://github.com/DataDog/documentation/blob/master/integrations/amazon_web_services/#installation).
+    # @param body [AWSAccount] Your Datadog role delegation name. For more information about your AWS account Role name, see the [Datadog AWS integration configuration info](https://docs.datadoghq.com/integrations/amazon_web_services/#setup).
     # @param [Hash] opts the optional parameters
     # @return [Array<(AWSAccountCreateResponse, Integer, Hash)>] AWSAccountCreateResponse data, response status code and response headers
     def create_new_aws_external_id_with_http_info(body, opts = {})
@@ -249,7 +249,7 @@ module DatadogAPIClient::V1
 
     # Delete an AWS integration
     # Delete a Datadog-AWS integration matching the specified `account_id` and `role_name parameters`.
-    # @param body [AWSAccount] AWS request object
+    # @param body [AWSAccountDeleteRequest] AWS request object
     # @param [Hash] opts the optional parameters
     # @return [Object]
     def delete_aws_account(body, opts = {})
@@ -259,7 +259,7 @@ module DatadogAPIClient::V1
 
     # Delete an AWS integration
     # Delete a Datadog-AWS integration matching the specified &#x60;account_id&#x60; and &#x60;role_name parameters&#x60;.
-    # @param body [AWSAccount] AWS request object
+    # @param body [AWSAccountDeleteRequest] AWS request object
     # @param [Hash] opts the optional parameters
     # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers
     def delete_aws_account_with_http_info(body, opts = {})

data/lib/datadog_api_client/v1/api/monitors_api.rb

@@ -97,7 +97,7 @@ module DatadogAPIClient::V1
     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).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 `>`
+    # 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 (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, 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 `>`
     # @param body [Monitor] Create a monitor request body.
     # @param [Hash] opts the optional parameters
     # @return [Monitor]
@@ -107,7 +107,7 @@ module DatadogAPIClient::V1
     end
 
     # Create a monitor
-    # Create a monitor using the specified options.  #### Monitor Types  The type of monitor chosen from:  - anomaly: &#x60;query alert&#x60; - APM: &#x60;query alert&#x60; or &#x60;trace-analytics alert&#x60; - composite: &#x60;composite&#x60; - custom: &#x60;service check&#x60; - event: &#x60;event alert&#x60; - forecast: &#x60;query alert&#x60; - host: &#x60;service check&#x60; - integration: &#x60;query alert&#x60; or &#x60;service check&#x60; - live process: &#x60;process alert&#x60; - logs: &#x60;log alert&#x60; - metric: &#x60;metric alert&#x60; - network: &#x60;service check&#x60; - outlier: &#x60;query alert&#x60; - process: &#x60;service check&#x60; - rum: &#x60;rum alert&#x60; - SLO: &#x60;slo alert&#x60; - watchdog: &#x60;event alert&#x60; - event-v2: &#x60;event-v2 alert&#x60;  #### Query Types  **Metric Alert Query**  Example: &#x60;time_aggr(time_window):space_aggr:metric{tags} [by {key}] operator #&#x60;  - &#x60;time_aggr&#x60;: avg, sum, max, min, change, or pct_change - &#x60;time_window&#x60;: &#x60;last_#m&#x60; (with &#x60;#&#x60; between 1 and 2880 depending on the monitor type) or &#x60;last_#h&#x60;(with &#x60;#&#x60; between 1 and 48 depending on the monitor type), or &#x60;last_1d&#x60; - &#x60;space_aggr&#x60;: avg, sum, min, or max - &#x60;tags&#x60;: one or more tags (comma-separated), or * - &#x60;key&#x60;: a &#39;key&#39; in key:value tag syntax; defines a separate alert for each tag in the group (multi-alert) - &#x60;operator&#x60;: &lt;, &lt;&#x3D;, &gt;, &gt;&#x3D;, &#x3D;&#x3D;, or !&#x3D; - &#x60;#&#x60;: an integer or decimal number used to set the threshold  If you are using the &#x60;_change_&#x60; or &#x60;_pct_change_&#x60; time aggregator, instead use &#x60;change_aggr(time_aggr(time_window), timeshift):space_aggr:metric{tags} [by {key}] operator #&#x60; with:  - &#x60;change_aggr&#x60; change, pct_change - &#x60;time_aggr&#x60; avg, sum, max, min [Learn more](https://docs.datadoghq.com/monitors/monitor_types/#define-the-conditions) - &#x60;time_window&#x60; 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) - &#x60;timeshift&#x60; #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: &#x60;avg(last_30m):outliers(avg:system.cpu.user{role:es-events-data} by {host}, &#39;dbscan&#39;, 7) &gt; 0&#x60;  **Service Check Query**  Example: &#x60;\&quot;check\&quot;.over(tags).last(count).by(group).count_by_status()&#x60;  - **&#x60;check&#x60;** name of the check, e.g. &#x60;datadog.agent.up&#x60; - **&#x60;tags&#x60;** one or more quoted tags (comma-separated), or \&quot;*\&quot;. e.g.: &#x60;.over(\&quot;env:prod\&quot;, \&quot;role:db\&quot;)&#x60;; **&#x60;over&#x60;** cannot be blank. - **&#x60;count&#x60;** must be at greater than or equal to your max threshold (defined in the &#x60;options&#x60;). It is limited to 100. For example, if you&#39;ve specified to notify on 1 critical, 3 ok, and 2 warn statuses, &#x60;count&#x60; should be at least 3. - **&#x60;group&#x60;** 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 &#x60;db&#x60;, &#x60;host&#x60;, and &#x60;port&#x60;, and Network monitors by &#x60;host&#x60;, &#x60;instance&#x60;, and &#x60;url&#x60;. See [Service Checks](https://docs.datadoghq.com/api/latest/service-checks/) documentation for more information.  **Event Alert Query**  Example: &#x60;events(&#39;sources:nagios status:error,warning priority:normal tags: \&quot;string query\&quot;&#39;).rollup(\&quot;count\&quot;).last(\&quot;1h\&quot;)\&quot;&#x60;  - **&#x60;event&#x60;**, the event query string: - **&#x60;string_query&#x60;** free text query to match against event title and text. - **&#x60;sources&#x60;** event sources (comma-separated). - **&#x60;status&#x60;** event statuses (comma-separated). Valid options: error, warn, and info. - **&#x60;priority&#x60;** event priorities (comma-separated). Valid options: low, normal, all. - **&#x60;host&#x60;** event reporting host (comma-separated). - **&#x60;tags&#x60;** event tags (comma-separated). - **&#x60;excluded_tags&#x60;** excluded event tags (comma-separated). - **&#x60;rollup&#x60;** the stats roll-up method. &#x60;count&#x60; is the only supported method now. - **&#x60;last&#x60;** 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: &#x60;events(query).rollup(rollup_method[, measure]).last(time_window) operator #&#x60;  - **&#x60;query&#x60;** The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/). - **&#x60;rollup_method&#x60;** The stats roll-up method - supports &#x60;count&#x60;, &#x60;avg&#x60; and &#x60;cardinality&#x60;. - **&#x60;measure&#x60;** For &#x60;avg&#x60; and cardinality &#x60;rollup_method&#x60; - specify the measure or the facet name you want to use. - **&#x60;time_window&#x60;** #m (5, 10, 15, or 30), #h (1, 2, or 4, 24). - **&#x60;operator&#x60;** &#x60;&lt;&#x60;, &#x60;&lt;&#x3D;&#x60;, &#x60;&gt;&#x60;, &#x60;&gt;&#x3D;&#x60;, &#x60;&#x3D;&#x3D;&#x60;, or &#x60;!&#x3D;&#x60;. - **&#x60;#&#x60;** 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: &#x60;processes(search).over(tags).rollup(&#39;count&#39;).last(timeframe) operator #&#x60;  - **&#x60;search&#x60;** free text search string for querying processes. Matching processes match results on the [Live Processes](https://docs.datadoghq.com/infrastructure/process/?tab&#x3D;linuxwindows) page. - **&#x60;tags&#x60;** one or more tags (comma-separated) - **&#x60;timeframe&#x60;** the timeframe to roll up the counts. Examples: 10m, 4h. Supported timeframes: s, m, h and d - **&#x60;operator&#x60;** &lt;, &lt;&#x3D;, &gt;, &gt;&#x3D;, &#x3D;&#x3D;, or !&#x3D; - **&#x60;#&#x60;** an integer or decimal number used to set the threshold  **Logs Alert Query**  Example: &#x60;logs(query).index(index_name).rollup(rollup_method[, measure]).last(time_window) operator #&#x60;  - **&#x60;query&#x60;** The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/). - **&#x60;index_name&#x60;** For multi-index organizations, the log index in which the request is performed. - **&#x60;rollup_method&#x60;** The stats roll-up method - supports &#x60;count&#x60;, &#x60;avg&#x60; and &#x60;cardinality&#x60;. - **&#x60;measure&#x60;** For &#x60;avg&#x60; and cardinality &#x60;rollup_method&#x60; - specify the measure or the facet name you want to use. - **&#x60;time_window&#x60;** #m (between 1 and 2880), #h (between 1 and 48) - **&#x60;operator&#x60;** &#x60;&lt;&#x60;, &#x60;&lt;&#x3D;&#x60;, &#x60;&gt;&#x60;, &#x60;&gt;&#x3D;&#x60;, &#x60;&#x3D;&#x3D;&#x60;, or &#x60;!&#x3D;&#x60;. - **&#x60;#&#x60;** an integer or decimal number used to set the threshold.  **Composite Query**  Example: &#x60;12345 &amp;&amp; 67890&#x60;, where &#x60;12345&#x60; and &#x60;67890&#x60; are the IDs of non-composite monitors  * **&#x60;name&#x60;** [*required*, *default* &#x3D; **dynamic, based on query**]: The name of the alert. * **&#x60;message&#x60;** [*required*, *default* &#x3D; **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 &#39;@username&#39; notation as events. * **&#x60;tags&#x60;** [*optional*, *default* &#x3D; **empty list**]: A list of tags to associate with your monitor. When getting all monitor details via the API, use the &#x60;monitor_tags&#x60; argument to filter results by these tags. It is only available via the API and isn&#39;t visible or editable in the Datadog UI.  **SLO Alert Query**  Example: &#x60;error_budget(\&quot;slo_id\&quot;).over(\&quot;time_window\&quot;) operator #&#x60;  - **&#x60;slo_id&#x60;**: The alphanumeric SLO ID of the SLO you are configuring the alert for. - **&#x60;time_window&#x60;**: The time window of the SLO target you wish to alert on. Valid options: &#x60;7d&#x60;, &#x60;30d&#x60;, &#x60;90d&#x60;. - **&#x60;operator&#x60;**: &#x60;&gt;&#x3D;&#x60; or &#x60;&gt;&#x60;
+    # Create a monitor using the specified options.  #### Monitor Types  The type of monitor chosen from:  - anomaly: &#x60;query alert&#x60; - APM: &#x60;query alert&#x60; or &#x60;trace-analytics alert&#x60; - composite: &#x60;composite&#x60; - custom: &#x60;service check&#x60; - event: &#x60;event alert&#x60; - forecast: &#x60;query alert&#x60; - host: &#x60;service check&#x60; - integration: &#x60;query alert&#x60; or &#x60;service check&#x60; - live process: &#x60;process alert&#x60; - logs: &#x60;log alert&#x60; - metric: &#x60;metric alert&#x60; - network: &#x60;service check&#x60; - outlier: &#x60;query alert&#x60; - process: &#x60;service check&#x60; - rum: &#x60;rum alert&#x60; - SLO: &#x60;slo alert&#x60; - watchdog: &#x60;event alert&#x60; - event-v2: &#x60;event-v2 alert&#x60;  #### Query Types  **Metric Alert Query**  Example: &#x60;time_aggr(time_window):space_aggr:metric{tags} [by {key}] operator #&#x60;  - &#x60;time_aggr&#x60;: avg, sum, max, min, change, or pct_change - &#x60;time_window&#x60;: &#x60;last_#m&#x60; (with &#x60;#&#x60; between 1 and 2880 depending on the monitor type) or &#x60;last_#h&#x60;(with &#x60;#&#x60; between 1 and 48 depending on the monitor type), or &#x60;last_1d&#x60; - &#x60;space_aggr&#x60;: avg, sum, min, or max - &#x60;tags&#x60;: one or more tags (comma-separated), or * - &#x60;key&#x60;: a &#39;key&#39; in key:value tag syntax; defines a separate alert for each tag in the group (multi-alert) - &#x60;operator&#x60;: &lt;, &lt;&#x3D;, &gt;, &gt;&#x3D;, &#x3D;&#x3D;, or !&#x3D; - &#x60;#&#x60;: an integer or decimal number used to set the threshold  If you are using the &#x60;_change_&#x60; or &#x60;_pct_change_&#x60; time aggregator, instead use &#x60;change_aggr(time_aggr(time_window), timeshift):space_aggr:metric{tags} [by {key}] operator #&#x60; with:  - &#x60;change_aggr&#x60; change, pct_change - &#x60;time_aggr&#x60; avg, sum, max, min [Learn more](https://docs.datadoghq.com/monitors/monitor_types/#define-the-conditions) - &#x60;time_window&#x60; 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) - &#x60;timeshift&#x60; #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: &#x60;avg(last_30m):outliers(avg:system.cpu.user{role:es-events-data} by {host}, &#39;dbscan&#39;, 7) &gt; 0&#x60;  **Service Check Query**  Example: &#x60;\&quot;check\&quot;.over(tags).last(count).by(group).count_by_status()&#x60;  - **&#x60;check&#x60;** name of the check, e.g. &#x60;datadog.agent.up&#x60; - **&#x60;tags&#x60;** one or more quoted tags (comma-separated), or \&quot;*\&quot;. e.g.: &#x60;.over(\&quot;env:prod\&quot;, \&quot;role:db\&quot;)&#x60;; **&#x60;over&#x60;** cannot be blank. - **&#x60;count&#x60;** must be at greater than or equal to your max threshold (defined in the &#x60;options&#x60;). It is limited to 100. For example, if you&#39;ve specified to notify on 1 critical, 3 ok, and 2 warn statuses, &#x60;count&#x60; should be at least 3. - **&#x60;group&#x60;** 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 &#x60;db&#x60;, &#x60;host&#x60;, and &#x60;port&#x60;, and Network monitors by &#x60;host&#x60;, &#x60;instance&#x60;, and &#x60;url&#x60;. See [Service Checks](https://docs.datadoghq.com/api/latest/service-checks/) documentation for more information.  **Event Alert Query**  Example: &#x60;events(&#39;sources:nagios status:error,warning priority:normal tags: \&quot;string query\&quot;&#39;).rollup(\&quot;count\&quot;).last(\&quot;1h\&quot;)\&quot;&#x60;  - **&#x60;event&#x60;**, the event query string: - **&#x60;string_query&#x60;** free text query to match against event title and text. - **&#x60;sources&#x60;** event sources (comma-separated). - **&#x60;status&#x60;** event statuses (comma-separated). Valid options: error, warn, and info. - **&#x60;priority&#x60;** event priorities (comma-separated). Valid options: low, normal, all. - **&#x60;host&#x60;** event reporting host (comma-separated). - **&#x60;tags&#x60;** event tags (comma-separated). - **&#x60;excluded_tags&#x60;** excluded event tags (comma-separated). - **&#x60;rollup&#x60;** the stats roll-up method. &#x60;count&#x60; is the only supported method now. - **&#x60;last&#x60;** 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: &#x60;events(query).rollup(rollup_method[, measure]).last(time_window) operator #&#x60;  - **&#x60;query&#x60;** The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/). - **&#x60;rollup_method&#x60;** The stats roll-up method - supports &#x60;count&#x60;, &#x60;avg&#x60; and &#x60;cardinality&#x60;. - **&#x60;measure&#x60;** For &#x60;avg&#x60; and cardinality &#x60;rollup_method&#x60; - specify the measure or the facet name you want to use. - **&#x60;time_window&#x60;** #m (between 1 and 2880), #h (between 1 and 48). - **&#x60;operator&#x60;** &#x60;&lt;&#x60;, &#x60;&lt;&#x3D;&#x60;, &#x60;&gt;&#x60;, &#x60;&gt;&#x3D;&#x60;, &#x60;&#x3D;&#x3D;&#x60;, or &#x60;!&#x3D;&#x60;. - **&#x60;#&#x60;** 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: &#x60;processes(search).over(tags).rollup(&#39;count&#39;).last(timeframe) operator #&#x60;  - **&#x60;search&#x60;** free text search string for querying processes. Matching processes match results on the [Live Processes](https://docs.datadoghq.com/infrastructure/process/?tab&#x3D;linuxwindows) page. - **&#x60;tags&#x60;** one or more tags (comma-separated) - **&#x60;timeframe&#x60;** the timeframe to roll up the counts. Examples: 10m, 4h. Supported timeframes: s, m, h and d - **&#x60;operator&#x60;** &lt;, &lt;&#x3D;, &gt;, &gt;&#x3D;, &#x3D;&#x3D;, or !&#x3D; - **&#x60;#&#x60;** an integer or decimal number used to set the threshold  **Logs Alert Query**  Example: &#x60;logs(query).index(index_name).rollup(rollup_method[, measure]).last(time_window) operator #&#x60;  - **&#x60;query&#x60;** The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/). - **&#x60;index_name&#x60;** For multi-index organizations, the log index in which the request is performed. - **&#x60;rollup_method&#x60;** The stats roll-up method - supports &#x60;count&#x60;, &#x60;avg&#x60; and &#x60;cardinality&#x60;. - **&#x60;measure&#x60;** For &#x60;avg&#x60; and cardinality &#x60;rollup_method&#x60; - specify the measure or the facet name you want to use. - **&#x60;time_window&#x60;** #m (between 1 and 2880), #h (between 1 and 48). - **&#x60;operator&#x60;** &#x60;&lt;&#x60;, &#x60;&lt;&#x3D;&#x60;, &#x60;&gt;&#x60;, &#x60;&gt;&#x3D;&#x60;, &#x60;&#x3D;&#x3D;&#x60;, or &#x60;!&#x3D;&#x60;. - **&#x60;#&#x60;** an integer or decimal number used to set the threshold.  **Composite Query**  Example: &#x60;12345 &amp;&amp; 67890&#x60;, where &#x60;12345&#x60; and &#x60;67890&#x60; are the IDs of non-composite monitors  * **&#x60;name&#x60;** [*required*, *default* &#x3D; **dynamic, based on query**]: The name of the alert. * **&#x60;message&#x60;** [*required*, *default* &#x3D; **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 &#39;@username&#39; notation as events. * **&#x60;tags&#x60;** [*optional*, *default* &#x3D; **empty list**]: A list of tags to associate with your monitor. When getting all monitor details via the API, use the &#x60;monitor_tags&#x60; argument to filter results by these tags. It is only available via the API and isn&#39;t visible or editable in the Datadog UI.  **SLO Alert Query**  Example: &#x60;error_budget(\&quot;slo_id\&quot;).over(\&quot;time_window\&quot;) operator #&#x60;  - **&#x60;slo_id&#x60;**: The alphanumeric SLO ID of the SLO you are configuring the alert for. - **&#x60;time_window&#x60;**: The time window of the SLO target you wish to alert on. Valid options: &#x60;7d&#x60;, &#x60;30d&#x60;, &#x60;90d&#x60;. - **&#x60;operator&#x60;**: &#x60;&gt;&#x3D;&#x60; or &#x60;&gt;&#x60;
     # @param body [Monitor] Create a monitor request body.
     # @param [Hash] opts the optional parameters
     # @return [Array<(Monitor, Integer, Hash)>] Monitor data, response status code and response headers

data/lib/datadog_api_client/v1/api/service_level_objectives_api.rb

@@ -404,7 +404,7 @@ module DatadogAPIClient::V1
     # @param from_ts [Integer] The `from` timestamp for the query window in epoch seconds.
     # @param to_ts [Integer] The `to` timestamp for the query window in epoch seconds.
     # @param [Hash] opts the optional parameters
-    # @option opts [Float] :target The SLO target. If `target` is passed in, the response will include the error budget that remains.
+    # @option opts [Float] :target The SLO target. If `target` is passed in, the response will include the remaining error budget and a timeframe value of `custom`.
     # @return [SLOHistoryResponse]
     def get_slo_history(slo_id, from_ts, to_ts, opts = {})
       data, _status_code, _headers = get_slo_history_with_http_info(slo_id, from_ts, to_ts, opts)
@@ -417,7 +417,7 @@ module DatadogAPIClient::V1
     # @param from_ts [Integer] The `from` timestamp for the query window in epoch seconds.
     # @param to_ts [Integer] The `to` timestamp for the query window in epoch seconds.
     # @param [Hash] opts the optional parameters
-    # @option opts [Float] :target The SLO target. If `target` is passed in, the response will include the error budget that remains.
+    # @option opts [Float] :target The SLO target. If `target` is passed in, the response will include the remaining error budget and a timeframe value of `custom`.
     # @return [Array<(SLOHistoryResponse, Integer, Hash)>] SLOHistoryResponse data, response status code and response headers
     def get_slo_history_with_http_info(slo_id, from_ts, to_ts, opts = {})
 
@@ -503,6 +503,8 @@ module DatadogAPIClient::V1
     # @option opts [String] :query The query string to filter results based on SLO names.
     # @option opts [String] :tags_query The query string to filter results based on a single SLO tag.
     # @option opts [String] :metrics_query The query string to filter results based on SLO numerator and denominator.
+    # @option opts [Integer] :limit The number of SLOs to return in the response.
+    # @option opts [Integer] :offset The specific offset to use as the beginning of the returned response.
     # @return [SLOListResponse]
     def list_slos(opts = {})
       data, _status_code, _headers = list_slos_with_http_info(opts)
@@ -516,6 +518,8 @@ module DatadogAPIClient::V1
     # @option opts [String] :query The query string to filter results based on SLO names.
     # @option opts [String] :tags_query The query string to filter results based on a single SLO tag.
     # @option opts [String] :metrics_query The query string to filter results based on SLO numerator and denominator.
+    # @option opts [Integer] :limit The number of SLOs to return in the response.
+    # @option opts [Integer] :offset The specific offset to use as the beginning of the returned response.
     # @return [Array<(SLOListResponse, Integer, Hash)>] SLOListResponse data, response status code and response headers
     def list_slos_with_http_info(opts = {})
 
@@ -540,6 +544,8 @@ module DatadogAPIClient::V1
       query_params[:'query'] = opts[:'query'] if !opts[:'query'].nil?
       query_params[:'tags_query'] = opts[:'tags_query'] if !opts[:'tags_query'].nil?
       query_params[:'metrics_query'] = opts[:'metrics_query'] if !opts[:'metrics_query'].nil?
+      query_params[:'limit'] = opts[:'limit'] if !opts[:'limit'].nil?
+      query_params[:'offset'] = opts[:'offset'] if !opts[:'offset'].nil?
 
       # header parameters
       header_params = opts[:header_params] || {}

data/lib/datadog_api_client/v1/api/usage_metering_api.rb

@@ -336,7 +336,7 @@ module DatadogAPIClient::V1
 
     # Get specified daily custom reports
     # Get specified daily custom reports.
-    # @param report_id [String] The specified ID to search results for.
+    # @param report_id [String] Date of the report in the format `YYYY-MM-DD`.
     # @param [Hash] opts the optional parameters
     # @return [UsageSpecifiedCustomReportsResponse]
     def get_specified_daily_custom_reports(report_id, opts = {})
@@ -346,7 +346,7 @@ module DatadogAPIClient::V1
 
     # Get specified daily custom reports
     # Get specified daily custom reports.
-    # @param report_id [String] The specified ID to search results for.
+    # @param report_id [String] Date of the report in the format `YYYY-MM-DD`.
     # @param [Hash] opts the optional parameters
     # @return [Array<(UsageSpecifiedCustomReportsResponse, Integer, Hash)>] UsageSpecifiedCustomReportsResponse data, response status code and response headers
     def get_specified_daily_custom_reports_with_http_info(report_id, opts = {})
@@ -409,7 +409,7 @@ module DatadogAPIClient::V1
 
     # Get specified monthly custom reports
     # Get specified monthly custom reports.
-    # @param report_id [String] The specified ID to search results for.
+    # @param report_id [String] Date of the report in the format &#x60;YYYY-MM-DD&#x60;.
     # @param [Hash] opts the optional parameters
     # @return [UsageSpecifiedCustomReportsResponse]
     def get_specified_monthly_custom_reports(report_id, opts = {})
@@ -419,7 +419,7 @@ module DatadogAPIClient::V1
 
     # Get specified monthly custom reports
     # Get specified monthly custom reports.
-    # @param report_id [String] The specified ID to search results for.
+    # @param report_id [String] Date of the report in the format &#x60;YYYY-MM-DD&#x60;.
     # @param [Hash] opts the optional parameters
     # @return [Array<(UsageSpecifiedCustomReportsResponse, Integer, Hash)>] UsageSpecifiedCustomReportsResponse data, response status code and response headers
     def get_specified_monthly_custom_reports_with_http_info(report_id, opts = {})
@@ -480,83 +480,6 @@ module DatadogAPIClient::V1
       return data, status_code, headers
     end
 
-    # Get hourly usage for tracing without limits
-    # Get hourly usage for tracing without limits.  **Note** This endpoint has been renamed to `/api/v1/usage/ingested-spans`.
-    # @param start_hr [Time] Datetime in ISO-8601 format, UTC, precise to hour: &#x60;[YYYY-MM-DDThh]&#x60; for usage beginning at this hour.
-    # @param [Hash] opts the optional parameters
-    # @option opts [Time] :end_hr Datetime in ISO-8601 format, UTC, precise to hour: &#x60;[YYYY-MM-DDThh]&#x60; for usage ending **before** this hour.
-    # @return [UsageTracingWithoutLimitsResponse]
-    def get_tracing_without_limits(start_hr, opts = {})
-      data, _status_code, _headers = get_tracing_without_limits_with_http_info(start_hr, opts)
-      data
-    end
-
-    # Get hourly usage for tracing without limits
-    # Get hourly usage for tracing without limits.  **Note** This endpoint has been renamed to &#x60;/api/v1/usage/ingested-spans&#x60;.
-    # @param start_hr [Time] Datetime in ISO-8601 format, UTC, precise to hour: &#x60;[YYYY-MM-DDThh]&#x60; for usage beginning at this hour.
-    # @param [Hash] opts the optional parameters
-    # @option opts [Time] :end_hr Datetime in ISO-8601 format, UTC, precise to hour: &#x60;[YYYY-MM-DDThh]&#x60; for usage ending **before** this hour.
-    # @return [Array<(UsageTracingWithoutLimitsResponse, Integer, Hash)>] UsageTracingWithoutLimitsResponse data, response status code and response headers
-    def get_tracing_without_limits_with_http_info(start_hr, opts = {})
-
-      if @api_client.config.unstable_operations.has_key?(:get_tracing_without_limits)
-        unstable_enabled = @api_client.config.unstable_operations[:get_tracing_without_limits]
-        if unstable_enabled
-          @api_client.config.logger.warn format("Using unstable operation '%s'", "get_tracing_without_limits")
-        else
-          raise APIError.new(message: format("Unstable operation '%s' is disabled", "get_tracing_without_limits"))
-        end
-      end
-
-      if @api_client.config.debugging
-        @api_client.config.logger.debug 'Calling API: UsageMeteringAPI.get_tracing_without_limits ...'
-      end
-      # verify the required parameter 'start_hr' is set
-      if @api_client.config.client_side_validation && start_hr.nil?
-        fail ArgumentError, "Missing the required parameter 'start_hr' when calling UsageMeteringAPI.get_tracing_without_limits"
-      end
-      # resource path
-      local_var_path = '/api/v1/usage/tracing-without-limits'
-
-      # query parameters
-      query_params = opts[:query_params] || {}
-      query_params[:'start_hr'] = start_hr
-      query_params[:'end_hr'] = opts[:'end_hr'] if !opts[:'end_hr'].nil?
-
-      # header parameters
-      header_params = opts[:header_params] || {}
-      # HTTP header 'Accept' (if needed)
-      header_params['Accept'] = @api_client.select_header_accept(['application/json;datetime-format=rfc3339'])
-
-      # form parameters
-      form_params = opts[:form_params] || {}
-
-      # http body (model)
-      post_body = opts[:debug_body]
-
-      # return_type
-      return_type = opts[:debug_return_type] || 'UsageTracingWithoutLimitsResponse'
-
-      # auth_names
-      auth_names = opts[:debug_auth_names] || [:apiKeyAuth, :appKeyAuth]
-
-      new_options = opts.merge(
-        :operation => :get_tracing_without_limits,
-        :header_params => header_params,
-        :query_params => query_params,
-        :form_params => form_params,
-        :body => post_body,
-        :auth_names => auth_names,
-        :return_type => return_type
-      )
-
-      data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options)
-      if @api_client.config.debugging
-        @api_client.config.logger.debug "API called: UsageMeteringAPI#get_tracing_without_limits\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
-      end
-      return data, status_code, headers
-    end
-
     # Get hourly usage for analyzed logs
     # Get hourly usage for analyzed logs (Security Monitoring).
     # @param start_hr [Time] Datetime in ISO-8601 format, UTC, precise to hour: &#x60;[YYYY-MM-DDThh]&#x60; for usage beginning at this hour.
@@ -2509,82 +2432,5 @@ module DatadogAPIClient::V1
       end
       return data, status_code, headers
     end
-
-    # Get hourly usage for Trace Search
-    # Get hourly usage for trace search.  **Note** This endpoint has been renamed to `/api/v1/usage/indexed-spans`.
-    # @param start_hr [Time] Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage beginning at this hour.
-    # @param [Hash] opts the optional parameters
-    # @option opts [Time] :end_hr Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage ending **before** this hour.
-    # @return [UsageTraceResponse]
-    def get_usage_trace(start_hr, opts = {})
-      data, _status_code, _headers = get_usage_trace_with_http_info(start_hr, opts)
-      data
-    end
-
-    # Get hourly usage for Trace Search
-    # Get hourly usage for trace search.  **Note** This endpoint has been renamed to &#x60;/api/v1/usage/indexed-spans&#x60;.
-    # @param start_hr [Time] Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage beginning at this hour.
-    # @param [Hash] opts the optional parameters
-    # @option opts [Time] :end_hr Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage ending **before** this hour.
-    # @return [Array<(UsageTraceResponse, Integer, Hash)>] UsageTraceResponse data, response status code and response headers
-    def get_usage_trace_with_http_info(start_hr, opts = {})
-
-      if @api_client.config.unstable_operations.has_key?(:get_usage_trace)
-        unstable_enabled = @api_client.config.unstable_operations[:get_usage_trace]
-        if unstable_enabled
-          @api_client.config.logger.warn format("Using unstable operation '%s'", "get_usage_trace")
-        else
-          raise APIError.new(message: format("Unstable operation '%s' is disabled", "get_usage_trace"))
-        end
-      end
-
-      if @api_client.config.debugging
-        @api_client.config.logger.debug 'Calling API: UsageMeteringAPI.get_usage_trace ...'
-      end
-      # verify the required parameter 'start_hr' is set
-      if @api_client.config.client_side_validation && start_hr.nil?
-        fail ArgumentError, "Missing the required parameter 'start_hr' when calling UsageMeteringAPI.get_usage_trace"
-      end
-      # resource path
-      local_var_path = '/api/v1/usage/traces'
-
-      # query parameters
-      query_params = opts[:query_params] || {}
-      query_params[:'start_hr'] = start_hr
-      query_params[:'end_hr'] = opts[:'end_hr'] if !opts[:'end_hr'].nil?
-
-      # header parameters
-      header_params = opts[:header_params] || {}
-      # HTTP header 'Accept' (if needed)
-      header_params['Accept'] = @api_client.select_header_accept(['application/json;datetime-format=rfc3339'])
-
-      # form parameters
-      form_params = opts[:form_params] || {}
-
-      # http body (model)
-      post_body = opts[:debug_body]
-
-      # return_type
-      return_type = opts[:debug_return_type] || 'UsageTraceResponse'
-
-      # auth_names
-      auth_names = opts[:debug_auth_names] || [:apiKeyAuth, :appKeyAuth]
-
-      new_options = opts.merge(
-        :operation => :get_usage_trace,
-        :header_params => header_params,
-        :query_params => query_params,
-        :form_params => form_params,
-        :body => post_body,
-        :auth_names => auth_names,
-        :return_type => return_type
-      )
-
-      data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options)
-      if @api_client.config.debugging
-        @api_client.config.logger.debug "API called: UsageMeteringAPI#get_usage_trace\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
-      end
-      return data, status_code, headers
-    end
   end
 end