datadog_api_client 1.1.0 → 1.2.0

data/docs/v1/MetricsQueryMetadata.md

@@ -12,8 +12,10 @@
 | **length** | **Integer** | Number of data samples. | [optional][readonly] |
 | **metric** | **String** | Metric name. | [optional][readonly] |
 | **pointlist** | **Array<Array>** | List of points of the time series. | [optional][readonly] |
+| **query_index** | **Integer** | The index of the series' query within the request. | [optional][readonly] |
 | **scope** | **String** | Metric scope, comma separated list of tags. | [optional][readonly] |
 | **start** | **Integer** | Start of the time window, milliseconds since Unix epoch. | [optional][readonly] |
+| **tag_set** | **Array<String>** | Unique tags identifying this series. | [optional][readonly] |
 | **unit** | [**Array<MetricsQueryUnit>**](MetricsQueryUnit.md) | Detailed information about the metric unit. First element describes the \"primary unit\" (for example, `bytes` in `bytes per second`), second describes the \"per unit\" (for example, `second` in `bytes per second`). | [optional][readonly] |
 
 ## Example
@@ -30,8 +32,10 @@ instance = DatadogAPIClient::V1::MetricsQueryMetadata.new(
   length: null,
   metric: system.cpu.idle,
   pointlist: null,
+  query_index: null,
   scope: host:foo,env:test,
   start: null,
+  tag_set: null,
   unit: null
 )
 ```

data/docs/v1/MonitorsAPI.md

@@ -19,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
@@ -81,9 +79,138 @@ 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`
+
+#### 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 #`
 
-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 `>`
+- **`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 `>`
 
 ### Examples
 
@@ -143,8 +270,6 @@ end
 
 > <DeletedMonitor> delete_monitor(monitor_id, opts)
 
-Delete a monitor
-
 Delete the specified monitor
 
 ### Examples
@@ -209,8 +334,6 @@ end
 
 > <Monitor> get_monitor(monitor_id, opts)
 
-Get a monitor's details
-
 Get details about the specified monitor from your organization.
 
 ### Examples
@@ -275,8 +398,6 @@ end
 
 > <Array<Monitor>> list_monitors(opts)
 
-Get all monitor details
-
 Get details about the specified monitor from your organization.
 
 ### Examples
@@ -353,8 +474,6 @@ end
 
 > <MonitorGroupSearchResponse> search_monitor_groups(opts)
 
-Monitors group search
-
 Search and filter your monitor groups details.
 
 ### Examples
@@ -423,8 +542,6 @@ end
 
 > <MonitorSearchResponse> search_monitors(opts)
 
-Monitors search
-
 Search and filter your monitors details.
 
 ### Examples
@@ -493,8 +610,6 @@ end
 
 > <Monitor> update_monitor(monitor_id, body)
 
-Edit a monitor
-
 Edit the specified monitor.
 
 ### Examples
@@ -557,8 +672,6 @@ end
 
 > Object validate_monitor(body)
 
-Validate a monitor
-
 Validate the monitor provided in the request.
 
 ### Examples

data/docs/v1/NotebooksAPI.md

@@ -15,8 +15,6 @@ All URIs are relative to *https://api.datadoghq.com*
 
 > <NotebookResponse> create_notebook(body)
 
-Create a notebook
-
 Create a notebook using the specified options.
 
 ### Examples
@@ -77,8 +75,6 @@ end
 
 > delete_notebook(notebook_id)
 
-Delete a notebook
-
 Delete a notebook using the specified ID.
 
 ### Examples
@@ -138,8 +134,6 @@ nil (empty response body)
 
 > <NotebookResponse> get_notebook(notebook_id)
 
-Get a notebook
-
 Get a notebook using the specified notebook ID.
 
 ### Examples
@@ -200,9 +194,8 @@ end
 
 > <NotebooksResponse> list_notebooks(opts)
 
-Get all notebooks
-
-Get all notebooks. This can also be used to search for notebooks with a particular `query` in the notebook `name` or author `handle`.
+Get all notebooks. This can also be used to search for notebooks with a particular `query` in the notebook
+`name` or author `handle`.
 
 ### Examples
 
@@ -278,8 +271,6 @@ end
 
 > <NotebookResponse> update_notebook(notebook_id, body)
 
-Update a notebook
-
 Update a notebook using the specified ID.
 
 ### Examples

data/docs/v1/OrganizationsAPI.md

@@ -15,9 +15,16 @@ All URIs are relative to *https://api.datadoghq.com*
 
 > <OrganizationCreateResponse> create_child_org(body)
 
-Create a child organization
+Create a child organization.
 
-Create a child organization.  This endpoint requires the [multi-organization account](https://docs.datadoghq.com/account_management/multi_organization/) feature and must be enabled by [contacting support](https://docs.datadoghq.com/help/).  Once a new child organization is created, you can interact with it by using the `org.public_id`, `pi_key.key`, and `application_key.hash` provided in the response.
+This endpoint requires the
+[multi-organization account](https://docs.datadoghq.com/account_management/multi_organization/)
+feature and must be enabled by
+[contacting support](https://docs.datadoghq.com/help/).
+
+Once a new child organization is created, you can interact with it
+by using the `org.public_id`, `pi_key.key`, and
+`application_key.hash` provided in the response.
 
 ### Examples
 
@@ -77,8 +84,6 @@ end
 
 > <OrganizationResponse> get_org(public_id)
 
-Get organization information
-
 Get organization information.
 
 ### Examples
@@ -139,8 +144,6 @@ end
 
 > <OrganizationListResponse> list_orgs
 
-List your managed organizations
-
 List your managed organizations.
 
 ### Examples
@@ -198,8 +201,6 @@ This endpoint does not need any parameter.
 
 > <OrganizationResponse> update_org(public_id, body)
 
-Update your organization
-
 Update your organization.
 
 ### Examples
@@ -262,9 +263,12 @@ end
 
 > <IdpResponse> upload_id_p_for_org(public_id, idp_file)
 
-Upload IdP metadata
+There are a couple of options for updating the Identity Provider (IdP)
+metadata from your SAML IdP.
+
+* **Multipart Form-Data**: Post the IdP metadata file using a form post.
 
-There are a couple of options for updating the Identity Provider (IdP) metadata from your SAML IdP.  * **Multipart Form-Data**: Post the IdP metadata file using a form post.  * **XML Body:** Post the IdP metadata file as the body of the request.
+* **XML Body:** Post the IdP metadata file as the body of the request.
 
 ### Examples
 

data/docs/v1/PagerDutyIntegrationAPI.md

@@ -14,8 +14,6 @@ All URIs are relative to *https://api.datadoghq.com*
 
 > <PagerDutyServiceName> create_pager_duty_integration_service(body)
 
-Create a new service object
-
 Create a new service object in the PagerDuty integration.
 
 ### Examples
@@ -76,8 +74,6 @@ end
 
 > delete_pager_duty_integration_service(service_name)
 
-Delete a single service object
-
 Delete a single service object in the Datadog-PagerDuty integration.
 
 ### Examples
@@ -137,8 +133,6 @@ nil (empty response body)
 
 > <PagerDutyServiceName> get_pager_duty_integration_service(service_name)
 
-Get a single service object
-
 Get service name in the Datadog-PagerDuty integration.
 
 ### Examples
@@ -199,8 +193,6 @@ end
 
 > update_pager_duty_integration_service(service_name, body)
 
-Update a single service object
-
 Update a single service object in the Datadog-PagerDuty integration.
 
 ### Examples

data/docs/v1/Pagination.md

@@ -0,0 +1,20 @@
+# DatadogAPIClient::V1::Pagination
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **total_count** | **Integer** | Total count. | [optional] |
+| **total_filtered_count** | **Integer** | Total count of elements matched by the filter. | [optional] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::Pagination.new(
+  total_count: null,
+  total_filtered_count: null
+)
+```
+

data/docs/v1/README.md

@@ -192,7 +192,6 @@ Class | Method | HTTP request | Description
 *DatadogAPIClient::V1::UsageMeteringAPI* | [**get_monthly_custom_reports**](UsageMeteringAPI.md#get_monthly_custom_reports) | **GET** /api/v1/monthly_custom_reports | Get the list of available monthly custom reports
 *DatadogAPIClient::V1::UsageMeteringAPI* | [**get_specified_daily_custom_reports**](UsageMeteringAPI.md#get_specified_daily_custom_reports) | **GET** /api/v1/daily_custom_reports/{report_id} | Get specified daily custom reports
 *DatadogAPIClient::V1::UsageMeteringAPI* | [**get_specified_monthly_custom_reports**](UsageMeteringAPI.md#get_specified_monthly_custom_reports) | **GET** /api/v1/monthly_custom_reports/{report_id} | Get specified monthly custom reports
-*DatadogAPIClient::V1::UsageMeteringAPI* | [**get_tracing_without_limits**](UsageMeteringAPI.md#get_tracing_without_limits) | **GET** /api/v1/usage/tracing-without-limits | Get hourly usage for tracing without limits
 *DatadogAPIClient::V1::UsageMeteringAPI* | [**get_usage_analyzed_logs**](UsageMeteringAPI.md#get_usage_analyzed_logs) | **GET** /api/v1/usage/analyzed_logs | Get hourly usage for analyzed logs
 *DatadogAPIClient::V1::UsageMeteringAPI* | [**get_usage_attribution**](UsageMeteringAPI.md#get_usage_attribution) | **GET** /api/v1/usage/attribution | Get Usage Attribution
 *DatadogAPIClient::V1::UsageMeteringAPI* | [**get_usage_audit_logs**](UsageMeteringAPI.md#get_usage_audit_logs) | **GET** /api/v1/usage/audit_logs | Get hourly usage for audit logs
@@ -218,7 +217,6 @@ Class | Method | HTTP request | Description
 *DatadogAPIClient::V1::UsageMeteringAPI* | [**get_usage_synthetics_browser**](UsageMeteringAPI.md#get_usage_synthetics_browser) | **GET** /api/v1/usage/synthetics_browser | Get hourly usage for Synthetics Browser Checks
 *DatadogAPIClient::V1::UsageMeteringAPI* | [**get_usage_timeseries**](UsageMeteringAPI.md#get_usage_timeseries) | **GET** /api/v1/usage/timeseries | Get hourly usage for custom metrics
 *DatadogAPIClient::V1::UsageMeteringAPI* | [**get_usage_top_avg_metrics**](UsageMeteringAPI.md#get_usage_top_avg_metrics) | **GET** /api/v1/usage/top_avg_metrics | Get all custom metrics by hourly average
-*DatadogAPIClient::V1::UsageMeteringAPI* | [**get_usage_trace**](UsageMeteringAPI.md#get_usage_trace) | **GET** /api/v1/usage/traces | Get hourly usage for Trace Search
 *DatadogAPIClient::V1::UsersAPI* | [**create_user**](UsersAPI.md#create_user) | **POST** /api/v1/user | Create a user
 *DatadogAPIClient::V1::UsersAPI* | [**disable_user**](UsersAPI.md#disable_user) | **DELETE** /api/v1/user/{user_handle} | Disable a user
 *DatadogAPIClient::V1::UsersAPI* | [**get_user**](UsersAPI.md#get_user) | **GET** /api/v1/user/{user_handle} | Get user details
@@ -232,6 +230,7 @@ Class | Method | HTTP request | Description
  - [DatadogAPIClient::V1::AWSAccount](AWSAccount.md)
  - [DatadogAPIClient::V1::AWSAccountAndLambdaRequest](AWSAccountAndLambdaRequest.md)
  - [DatadogAPIClient::V1::AWSAccountCreateResponse](AWSAccountCreateResponse.md)
+ - [DatadogAPIClient::V1::AWSAccountDeleteRequest](AWSAccountDeleteRequest.md)
  - [DatadogAPIClient::V1::AWSAccountListResponse](AWSAccountListResponse.md)
  - [DatadogAPIClient::V1::AWSLogsAsyncError](AWSLogsAsyncError.md)
  - [DatadogAPIClient::V1::AWSLogsAsyncResponse](AWSLogsAsyncResponse.md)
@@ -513,11 +512,13 @@ Class | Method | HTTP request | Description
  - [DatadogAPIClient::V1::PagerDutyService](PagerDutyService.md)
  - [DatadogAPIClient::V1::PagerDutyServiceKey](PagerDutyServiceKey.md)
  - [DatadogAPIClient::V1::PagerDutyServiceName](PagerDutyServiceName.md)
+ - [DatadogAPIClient::V1::Pagination](Pagination.md)
  - [DatadogAPIClient::V1::ProcessQueryDefinition](ProcessQueryDefinition.md)
  - [DatadogAPIClient::V1::QuerySortOrder](QuerySortOrder.md)
  - [DatadogAPIClient::V1::QueryValueWidgetDefinition](QueryValueWidgetDefinition.md)
  - [DatadogAPIClient::V1::QueryValueWidgetDefinitionType](QueryValueWidgetDefinitionType.md)
  - [DatadogAPIClient::V1::QueryValueWidgetRequest](QueryValueWidgetRequest.md)
+ - [DatadogAPIClient::V1::ResponseMetaAttributes](ResponseMetaAttributes.md)
  - [DatadogAPIClient::V1::SLOBulkDeleteError](SLOBulkDeleteError.md)
  - [DatadogAPIClient::V1::SLOBulkDeleteResponse](SLOBulkDeleteResponse.md)
  - [DatadogAPIClient::V1::SLOBulkDeleteResponseData](SLOBulkDeleteResponseData.md)
@@ -654,7 +655,6 @@ Class | Method | HTTP request | Description
  - [DatadogAPIClient::V1::SyntheticsTestRequest](SyntheticsTestRequest.md)
  - [DatadogAPIClient::V1::SyntheticsTestRequestCertificate](SyntheticsTestRequestCertificate.md)
  - [DatadogAPIClient::V1::SyntheticsTestRequestCertificateItem](SyntheticsTestRequestCertificateItem.md)
- - [DatadogAPIClient::V1::SyntheticsTickInterval](SyntheticsTickInterval.md)
  - [DatadogAPIClient::V1::SyntheticsTiming](SyntheticsTiming.md)
  - [DatadogAPIClient::V1::SyntheticsTriggerCITestLocation](SyntheticsTriggerCITestLocation.md)
  - [DatadogAPIClient::V1::SyntheticsTriggerCITestRunResult](SyntheticsTriggerCITestRunResult.md)
@@ -678,6 +678,12 @@ Class | Method | HTTP request | Description
  - [DatadogAPIClient::V1::ToplistWidgetDefinition](ToplistWidgetDefinition.md)
  - [DatadogAPIClient::V1::ToplistWidgetDefinitionType](ToplistWidgetDefinitionType.md)
  - [DatadogAPIClient::V1::ToplistWidgetRequest](ToplistWidgetRequest.md)
+ - [DatadogAPIClient::V1::TreeMapColorBy](TreeMapColorBy.md)
+ - [DatadogAPIClient::V1::TreeMapGroupBy](TreeMapGroupBy.md)
+ - [DatadogAPIClient::V1::TreeMapSizeBy](TreeMapSizeBy.md)
+ - [DatadogAPIClient::V1::TreeMapWidgetDefinition](TreeMapWidgetDefinition.md)
+ - [DatadogAPIClient::V1::TreeMapWidgetDefinitionType](TreeMapWidgetDefinitionType.md)
+ - [DatadogAPIClient::V1::TreeMapWidgetRequest](TreeMapWidgetRequest.md)
  - [DatadogAPIClient::V1::UsageAnalyzedLogsHour](UsageAnalyzedLogsHour.md)
  - [DatadogAPIClient::V1::UsageAnalyzedLogsResponse](UsageAnalyzedLogsResponse.md)
  - [DatadogAPIClient::V1::UsageAttributionAggregatesBody](UsageAttributionAggregatesBody.md)
@@ -756,10 +762,6 @@ Class | Method | HTTP request | Description
  - [DatadogAPIClient::V1::UsageTopAvgMetricsHour](UsageTopAvgMetricsHour.md)
  - [DatadogAPIClient::V1::UsageTopAvgMetricsMetadata](UsageTopAvgMetricsMetadata.md)
  - [DatadogAPIClient::V1::UsageTopAvgMetricsResponse](UsageTopAvgMetricsResponse.md)
- - [DatadogAPIClient::V1::UsageTraceHour](UsageTraceHour.md)
- - [DatadogAPIClient::V1::UsageTraceResponse](UsageTraceResponse.md)
- - [DatadogAPIClient::V1::UsageTracingWithoutLimitsHour](UsageTracingWithoutLimitsHour.md)
- - [DatadogAPIClient::V1::UsageTracingWithoutLimitsResponse](UsageTracingWithoutLimitsResponse.md)
  - [DatadogAPIClient::V1::User](User.md)
  - [DatadogAPIClient::V1::UserDisableResponse](UserDisableResponse.md)
  - [DatadogAPIClient::V1::UserListResponse](UserListResponse.md)