@datadog/datadog-api-client 1.0.0-beta.6 → 1.0.0-beta.7

package/dist/packages/datadog-api-client-v1/types/PromiseAPI.d.ts

@@ -48,6 +48,8 @@ import { HostMuteResponse } from "../models/HostMuteResponse";
 import { HostMuteSettings } from "../models/HostMuteSettings";
 import { HostTags } from "../models/HostTags";
 import { HostTotals } from "../models/HostTotals";
+import { HourlyUsageAttributionResponse } from "../models/HourlyUsageAttributionResponse";
+import { HourlyUsageAttributionUsageType } from "../models/HourlyUsageAttributionUsageType";
 import { IPRanges } from "../models/IPRanges";
 import { IdpResponse } from "../models/IdpResponse";
 import { IntakePayloadAccepted } from "../models/IntakePayloadAccepted";
@@ -69,6 +71,8 @@ import { Monitor } from "../models/Monitor";
 import { MonitorGroupSearchResponse } from "../models/MonitorGroupSearchResponse";
 import { MonitorSearchResponse } from "../models/MonitorSearchResponse";
 import { MonitorUpdateRequest } from "../models/MonitorUpdateRequest";
+import { MonthlyUsageAttributionResponse } from "../models/MonthlyUsageAttributionResponse";
+import { MonthlyUsageAttributionSupportedMetrics } from "../models/MonthlyUsageAttributionSupportedMetrics";
 import { NotebookCreateRequest } from "../models/NotebookCreateRequest";
 import { NotebookResponse } from "../models/NotebookResponse";
 import { NotebookUpdateRequest } from "../models/NotebookUpdateRequest";
@@ -112,6 +116,7 @@ import { SyntheticsLocations } from "../models/SyntheticsLocations";
 import { SyntheticsPrivateLocation } from "../models/SyntheticsPrivateLocation";
 import { SyntheticsPrivateLocationCreationResponse } from "../models/SyntheticsPrivateLocationCreationResponse";
 import { SyntheticsTestDetails } from "../models/SyntheticsTestDetails";
+import { SyntheticsTriggerBody } from "../models/SyntheticsTriggerBody";
 import { SyntheticsTriggerCITestsResponse } from "../models/SyntheticsTriggerCITestsResponse";
 import { SyntheticsUpdateTestPauseStatusPayload } from "../models/SyntheticsUpdateTestPauseStatusPayload";
 import { TagToHosts } from "../models/TagToHosts";
@@ -139,6 +144,7 @@ import { UsageNetworkFlowsResponse } from "../models/UsageNetworkFlowsResponse";
 import { UsageNetworkHostsResponse } from "../models/UsageNetworkHostsResponse";
 import { UsageProfilingResponse } from "../models/UsageProfilingResponse";
 import { UsageRumSessionsResponse } from "../models/UsageRumSessionsResponse";
+import { UsageRumUnitsResponse } from "../models/UsageRumUnitsResponse";
 import { UsageSDSResponse } from "../models/UsageSDSResponse";
 import { UsageSNMPResponse } from "../models/UsageSNMPResponse";
 import { UsageSort } from "../models/UsageSort";
@@ -378,8 +384,9 @@ export declare class PromiseDashboardsApi {
      * Get all dashboards.  **Note**: This query will only return custom created or cloned dashboards. This query will not return preset dashboards.
      * Get all dashboards
      * @param filterShared When `true`, this query only returns shared custom created or cloned dashboards.
+     * @param filterDeleted When `true`, this query returns only deleted custom-created or cloned dashboards. This parameter is incompatible with `filter[shared]`.
      */
-    listDashboards(filterShared?: boolean, _options?: Configuration): Promise<DashboardSummary>;
+    listDashboards(filterShared?: boolean, filterDeleted?: boolean, _options?: Configuration): Promise<DashboardSummary>;
     /**
      * Restore dashboards using the specified IDs. If there are any failures, no dashboards will be restored (partial success is not allowed).
      * Restore deleted dashboards
@@ -429,7 +436,7 @@ export declare class PromiseDowntimesApi {
      */
     listDowntimes(currentOnly?: boolean, _options?: Configuration): Promise<Array<Downtime>>;
     /**
-     * Get all downtimes for the specified monitor
+     * Get all active downtimes for the specified monitor.
      * Get all downtimes for a monitor
      * @param monitorId The id of the monitor
      */
@@ -775,7 +782,7 @@ export declare class PromiseMonitorsApi {
      */
     checkCanDeleteMonitor(monitorIds: Array<number>, _options?: Configuration): Promise<CheckCanDeleteMonitorResponse>;
     /**
-     * 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 `>`  **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.
+     * 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: `query 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, for example `datadog.agent.up` - **`tags`** one or more quoted tags (comma-separated), or \"*\". for example: `.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 `>`  **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.  **CI Pipelines Alert Query**  Example: `ci-pipelines(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 in closed beta on US1, EU, US3 and US5.
      * Create a monitor
      * @param body Create a monitor request body.
      */
@@ -784,7 +791,7 @@ export declare class PromiseMonitorsApi {
      * Delete the specified monitor
      * Delete a monitor
      * @param monitorId The ID of the monitor.
-     * @param force Delete the monitor even if it&#39;s referenced by other resources (e.g. SLO, composite monitor).
+     * @param force Delete the monitor even if it&#39;s referenced by other resources (for example SLO, composite monitor).
      */
     deleteMonitor(monitorId: number, force?: string, _options?: Configuration): Promise<DeletedMonitor>;
     /**
@@ -802,7 +809,7 @@ export declare class PromiseMonitorsApi {
      * @param tags 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;.
      * @param monitorTags 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;.
      * @param withDowntimes If this argument is set to true, then the returned data includes all current active downtimes for each monitor.
-     * @param idOffset Monitor ID offset.
+     * @param idOffset Use this parameter for paginating through large sets of monitors. Start with a value of zero, make a request, set the value to the last ID of result set, and then repeat until the response is empty.
      * @param page The page to start paginating from. If this argument is not specified, the request returns all monitors without pagination.
      * @param pageSize 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.
      */
@@ -813,7 +820,7 @@ export declare class PromiseMonitorsApi {
      * @param query 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
      * @param page Page to start paginating from.
      * @param perPage Number of monitors to return per page.
-     * @param sort 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;
+     * @param sort String for sort order, composed of field and sort order separate by a comma, for example &#x60;name,asc&#x60;. Supported sort directions: &#x60;asc&#x60;, &#x60;desc&#x60;. Supported fields:  * &#x60;name&#x60; * &#x60;status&#x60; * &#x60;tags&#x60;
      */
     searchMonitorGroups(query?: string, page?: number, perPage?: number, sort?: string, _options?: Configuration): Promise<MonitorGroupSearchResponse>;
     /**
@@ -822,7 +829,7 @@ export declare class PromiseMonitorsApi {
      * @param query 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
      * @param page Page to start paginating from.
      * @param perPage Number of monitors to return per page.
-     * @param sort 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;
+     * @param sort String for sort order, composed of field and sort order separate by a comma, for example &#x60;name,asc&#x60;. Supported sort directions: &#x60;asc&#x60;, &#x60;desc&#x60;. Supported fields:  * &#x60;name&#x60; * &#x60;status&#x60; * &#x60;tags&#x60;
      */
     searchMonitors(query?: string, page?: number, perPage?: number, sort?: string, _options?: Configuration): Promise<MonitorSearchResponse>;
     /**
@@ -1016,7 +1023,7 @@ export declare class PromiseServiceLevelObjectivesApi {
      * Permanently delete the specified service level objective object.  If an SLO is used in a dashboard, the `DELETE /v1/slo/` endpoint returns a 409 conflict error because the SLO is referenced in a dashboard.
      * Delete an SLO
      * @param sloId The ID of the service level objective.
-     * @param force Delete the monitor even if it&#39;s referenced by other resources (e.g. SLO, composite monitor).
+     * @param force Delete the monitor even if it&#39;s referenced by other resources (for example SLO, composite monitor).
      */
     deleteSLO(sloId: string, force?: string, _options?: Configuration): Promise<SLODeleteResponse>;
     /**
@@ -1034,6 +1041,12 @@ export declare class PromiseServiceLevelObjectivesApi {
      * @param withConfiguredAlertIds Get the IDs of SLO monitors that reference this SLO.
      */
     getSLO(sloId: string, withConfiguredAlertIds?: boolean, _options?: Configuration): Promise<SLOResponse>;
+    /**
+     * Get corrections applied to an SLO
+     * Get Corrections For an SLO
+     * @param sloId The ID of the service level objective object.
+     */
+    getSLOCorrections(sloId: string, _options?: Configuration): Promise<SLOCorrectionListResponse>;
     /**
      * Get a specific SLO’s history, regardless of its SLO type.  The detailed history data is structured according to the source data type. For example, metric data is included for event SLOs that use the metric source, and monitor SLO types include the monitor transition history.  **Note:** There are different response formats for event based and time based SLOs. Examples of both are shown.
      * Get an SLO's history
@@ -1041,8 +1054,9 @@ export declare class PromiseServiceLevelObjectivesApi {
      * @param fromTs The &#x60;from&#x60; timestamp for the query window in epoch seconds.
      * @param toTs The &#x60;to&#x60; timestamp for the query window in epoch seconds.
      * @param target The SLO target. If &#x60;target&#x60; is passed in, the response will include the remaining error budget and a timeframe value of &#x60;custom&#x60;.
+     * @param applyCorrection Defaults to &#x60;true&#x60;. If any SLO corrections are applied and this parameter is set to &#x60;false&#x60;, then the corrections will not be applied and the SLI values will not be affected.
      */
-    getSLOHistory(sloId: string, fromTs: number, toTs: number, target?: number, _options?: Configuration): Promise<SLOHistoryResponse>;
+    getSLOHistory(sloId: string, fromTs: number, toTs: number, target?: number, applyCorrection?: boolean, _options?: Configuration): Promise<SLOHistoryResponse>;
     /**
      * Get a list of service level objective objects for your organization.
      * Get all SLOs
@@ -1260,6 +1274,12 @@ export declare class PromiseSyntheticsApi {
      * @param body Details of the test to trigger.
      */
     triggerCITests(body: SyntheticsCITestBody, _options?: Configuration): Promise<SyntheticsTriggerCITestsResponse>;
+    /**
+     * Trigger a set of Synthetics tests.
+     * Trigger Synthetics tests
+     * @param body The identifiers of the tests to trigger.
+     */
+    triggerTests(body: SyntheticsTriggerBody, _options?: Configuration): Promise<SyntheticsTriggerCITestsResponse>;
     /**
      * Edit the configuration of a Synthetic API test.
      * Edit an API test
@@ -1305,7 +1325,7 @@ export declare class PromiseTagsApi {
      * This endpoint allows you to remove all user-assigned tags for a single host.
      * Remove host tags
      * @param hostName This endpoint allows you to remove all user-assigned tags for a single host.
-     * @param source The source of the tags (e.g. chef, puppet). [Complete list of source attribute values](https://docs.datadoghq.com/integrations/faq/list-of-api-source-attribute-value).
+     * @param source The source of the tags (for example chef, puppet). [Complete list of source attribute values](https://docs.datadoghq.com/integrations/faq/list-of-api-source-attribute-value).
      */
     deleteHostTags(hostName: string, source?: string, _options?: Configuration): Promise<void>;
     /**
@@ -1326,7 +1346,7 @@ export declare class PromiseTagsApi {
      * Update host tags
      * @param hostName This endpoint allows you to update/replace all in an integration source with those supplied in the request.
      * @param body Add tags to host
-     * @param source The source of the tags (e.g. chef, puppet). [Complete list of source attribute values](https://docs.datadoghq.com/integrations/faq/list-of-api-source-attribute-value)
+     * @param source The source of the tags (for example chef, puppet). [Complete list of source attribute values](https://docs.datadoghq.com/integrations/faq/list-of-api-source-attribute-value)
      */
     updateHostTags(hostName: string, body: HostTags, source?: string, _options?: Configuration): Promise<HostTags>;
 }
@@ -1343,6 +1363,16 @@ export declare class PromiseUsageMeteringApi {
      * @param sort The field to sort by: &#x60;[computed_on, size, start_date, end_date]&#x60;.
      */
     getDailyCustomReports(pageSize?: number, pageNumber?: number, sortDir?: UsageSortDirection, sort?: UsageSort, _options?: Configuration): Promise<UsageCustomReportsResponse>;
+    /**
+     * Get Hourly Usage Attribution.
+     * Get Hourly Usage Attribution
+     * @param startHr Datetime in ISO-8601 format, UTC, precise to hour: &#x60;[YYYY-MM-DDThh]&#x60; for usage beginning at this hour.
+     * @param usageType Usage type to retrieve.
+     * @param endHr Datetime in ISO-8601 format, UTC, precise to hour: &#x60;[YYYY-MM-DDThh]&#x60; for usage ending **before** this hour.
+     * @param nextRecordId List following results with a next_record_id provided in the previous query.
+     * @param tagBreakdownKeys Comma separated list of tags used to group usage. If no value is provided the usage will not be broken down by tags.
+     */
+    getHourlyUsageAttribution(startHr: Date, usageType: HourlyUsageAttributionUsageType, endHr?: Date, nextRecordId?: string, tagBreakdownKeys?: string, _options?: Configuration): Promise<HourlyUsageAttributionResponse>;
     /**
      * Get hourly usage for incident management.
      * Get hourly usage for incident management
@@ -1366,6 +1396,18 @@ export declare class PromiseUsageMeteringApi {
      * @param sort The field to sort by: &#x60;[computed_on, size, start_date, end_date]&#x60;.
      */
     getMonthlyCustomReports(pageSize?: number, pageNumber?: number, sortDir?: UsageSortDirection, sort?: UsageSort, _options?: Configuration): Promise<UsageCustomReportsResponse>;
+    /**
+     * Get Monthly Usage Attribution.
+     * Get Monthly Usage Attribution
+     * @param startMonth Datetime in ISO-8601 format, UTC, precise to month: &#x60;[YYYY-MM]&#x60; for usage beginning in this month. Maximum of 15 months ago.
+     * @param fields Comma-separated list of usage types to return, or &#x60;*&#x60; for all usage types.
+     * @param endMonth Datetime in ISO-8601 format, UTC, precise to month: &#x60;[YYYY-MM]&#x60; for usage ending this month.
+     * @param sortDirection The direction to sort by: &#x60;[desc, asc]&#x60;.
+     * @param sortName The field to sort by.
+     * @param tagBreakdownKeys Comma separated list of tags used to group usage. If no value is provided the usage will not be broken down by tags.
+     * @param nextRecordId List following results with a next_record_id provided in the previous query.
+     */
+    getMonthlyUsageAttribution(startMonth: Date, fields: MonthlyUsageAttributionSupportedMetrics, endMonth?: Date, sortDirection?: UsageSortDirection, sortName?: MonthlyUsageAttributionSupportedMetrics, tagBreakdownKeys?: string, nextRecordId?: string, _options?: Configuration): Promise<MonthlyUsageAttributionResponse>;
     /**
      * Get specified daily custom reports.
      * Get specified daily custom reports
@@ -1394,8 +1436,10 @@ export declare class PromiseUsageMeteringApi {
      * @param sortDirection The direction to sort by: &#x60;[desc, asc]&#x60;.
      * @param sortName The field to sort by.
      * @param includeDescendants Include child org usage in the response. Defaults to false.
+     * @param offset Number of records to skip before beginning to return.
+     * @param limit Maximum number of records to be returned.
      */
-    getUsageAttribution(startMonth: Date, fields: UsageAttributionSupportedMetrics, endMonth?: Date, sortDirection?: UsageSortDirection, sortName?: UsageAttributionSort, includeDescendants?: boolean, _options?: Configuration): Promise<UsageAttributionResponse>;
+    getUsageAttribution(startMonth: Date, fields: UsageAttributionSupportedMetrics, endMonth?: Date, sortDirection?: UsageSortDirection, sortName?: UsageAttributionSort, includeDescendants?: boolean, offset?: number, limit?: number, _options?: Configuration): Promise<UsageAttributionResponse>;
     /**
      * Get hourly usage for audit logs.
      * Get hourly usage for audit logs
@@ -1516,6 +1560,13 @@ export declare class PromiseUsageMeteringApi {
      * @param type RUM type: &#x60;[browser, mobile]&#x60;. Defaults to &#x60;browser&#x60;.
      */
     getUsageRumSessions(startHr: Date, endHr?: Date, type?: string, _options?: Configuration): Promise<UsageRumSessionsResponse>;
+    /**
+     * Get hourly usage for [RUM](https://docs.datadoghq.com/real_user_monitoring/) Units.
+     * Get hourly usage for RUM Units
+     * @param startHr Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage beginning at this hour.
+     * @param endHr Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage ending **before** this hour.
+     */
+    getUsageRumUnits(startHr: Date, endHr?: Date, _options?: Configuration): Promise<UsageRumUnitsResponse>;
     /**
      * Get hourly usage for Sensitive Data Scanner.
      * Get hourly usage for Sensitive Data Scanner

package/dist/packages/datadog-api-client-v1/types/PromiseAPI.js

@@ -329,9 +329,10 @@ var PromiseDashboardsApi = /** @class */ (function () {
      * Get all dashboards.  **Note**: This query will only return custom created or cloned dashboards. This query will not return preset dashboards.
      * Get all dashboards
      * @param filterShared When `true`, this query only returns shared custom created or cloned dashboards.
+     * @param filterDeleted When `true`, this query returns only deleted custom-created or cloned dashboards. This parameter is incompatible with `filter[shared]`.
      */
-    PromiseDashboardsApi.prototype.listDashboards = function (filterShared, _options) {
-        var result = this.api.listDashboards(filterShared, _options);
+    PromiseDashboardsApi.prototype.listDashboards = function (filterShared, filterDeleted, _options) {
+        var result = this.api.listDashboards(filterShared, filterDeleted, _options);
         return result.toPromise();
     };
     /**
@@ -407,7 +408,7 @@ var PromiseDowntimesApi = /** @class */ (function () {
         return result.toPromise();
     };
     /**
-     * Get all downtimes for the specified monitor
+     * Get all active downtimes for the specified monitor.
      * Get all downtimes for a monitor
      * @param monitorId The id of the monitor
      */
@@ -921,7 +922,7 @@ var PromiseMonitorsApi = /** @class */ (function () {
         return result.toPromise();
     };
     /**
-     * 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 `>`  **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.
+     * 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: `query 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, for example `datadog.agent.up` - **`tags`** one or more quoted tags (comma-separated), or \"*\". for example: `.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 `>`  **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.  **CI Pipelines Alert Query**  Example: `ci-pipelines(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 in closed beta on US1, EU, US3 and US5.
      * Create a monitor
      * @param body Create a monitor request body.
      */
@@ -933,7 +934,7 @@ var PromiseMonitorsApi = /** @class */ (function () {
      * Delete the specified monitor
      * Delete a monitor
      * @param monitorId The ID of the monitor.
-     * @param force Delete the monitor even if it&#39;s referenced by other resources (e.g. SLO, composite monitor).
+     * @param force Delete the monitor even if it&#39;s referenced by other resources (for example SLO, composite monitor).
      */
     PromiseMonitorsApi.prototype.deleteMonitor = function (monitorId, force, _options) {
         var result = this.api.deleteMonitor(monitorId, force, _options);
@@ -957,7 +958,7 @@ var PromiseMonitorsApi = /** @class */ (function () {
      * @param tags 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;.
      * @param monitorTags 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;.
      * @param withDowntimes If this argument is set to true, then the returned data includes all current active downtimes for each monitor.
-     * @param idOffset Monitor ID offset.
+     * @param idOffset Use this parameter for paginating through large sets of monitors. Start with a value of zero, make a request, set the value to the last ID of result set, and then repeat until the response is empty.
      * @param page The page to start paginating from. If this argument is not specified, the request returns all monitors without pagination.
      * @param pageSize 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.
      */
@@ -971,7 +972,7 @@ var PromiseMonitorsApi = /** @class */ (function () {
      * @param query 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
      * @param page Page to start paginating from.
      * @param perPage Number of monitors to return per page.
-     * @param sort 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;
+     * @param sort String for sort order, composed of field and sort order separate by a comma, for example &#x60;name,asc&#x60;. Supported sort directions: &#x60;asc&#x60;, &#x60;desc&#x60;. Supported fields:  * &#x60;name&#x60; * &#x60;status&#x60; * &#x60;tags&#x60;
      */
     PromiseMonitorsApi.prototype.searchMonitorGroups = function (query, page, perPage, sort, _options) {
         var result = this.api.searchMonitorGroups(query, page, perPage, sort, _options);
@@ -983,7 +984,7 @@ var PromiseMonitorsApi = /** @class */ (function () {
      * @param query 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
      * @param page Page to start paginating from.
      * @param perPage Number of monitors to return per page.
-     * @param sort 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;
+     * @param sort String for sort order, composed of field and sort order separate by a comma, for example &#x60;name,asc&#x60;. Supported sort directions: &#x60;asc&#x60;, &#x60;desc&#x60;. Supported fields:  * &#x60;name&#x60; * &#x60;status&#x60; * &#x60;tags&#x60;
      */
     PromiseMonitorsApi.prototype.searchMonitors = function (query, page, perPage, sort, _options) {
         var result = this.api.searchMonitors(query, page, perPage, sort, _options);
@@ -1270,7 +1271,7 @@ var PromiseServiceLevelObjectivesApi = /** @class */ (function () {
      * Permanently delete the specified service level objective object.  If an SLO is used in a dashboard, the `DELETE /v1/slo/` endpoint returns a 409 conflict error because the SLO is referenced in a dashboard.
      * Delete an SLO
      * @param sloId The ID of the service level objective.
-     * @param force Delete the monitor even if it&#39;s referenced by other resources (e.g. SLO, composite monitor).
+     * @param force Delete the monitor even if it&#39;s referenced by other resources (for example SLO, composite monitor).
      */
     PromiseServiceLevelObjectivesApi.prototype.deleteSLO = function (sloId, force, _options) {
         var result = this.api.deleteSLO(sloId, force, _options);
@@ -1295,6 +1296,15 @@ var PromiseServiceLevelObjectivesApi = /** @class */ (function () {
         var result = this.api.getSLO(sloId, withConfiguredAlertIds, _options);
         return result.toPromise();
     };
+    /**
+     * Get corrections applied to an SLO
+     * Get Corrections For an SLO
+     * @param sloId The ID of the service level objective object.
+     */
+    PromiseServiceLevelObjectivesApi.prototype.getSLOCorrections = function (sloId, _options) {
+        var result = this.api.getSLOCorrections(sloId, _options);
+        return result.toPromise();
+    };
     /**
      * Get a specific SLO’s history, regardless of its SLO type.  The detailed history data is structured according to the source data type. For example, metric data is included for event SLOs that use the metric source, and monitor SLO types include the monitor transition history.  **Note:** There are different response formats for event based and time based SLOs. Examples of both are shown.
      * Get an SLO's history
@@ -1302,9 +1312,10 @@ var PromiseServiceLevelObjectivesApi = /** @class */ (function () {
      * @param fromTs The &#x60;from&#x60; timestamp for the query window in epoch seconds.
      * @param toTs The &#x60;to&#x60; timestamp for the query window in epoch seconds.
      * @param target The SLO target. If &#x60;target&#x60; is passed in, the response will include the remaining error budget and a timeframe value of &#x60;custom&#x60;.
+     * @param applyCorrection Defaults to &#x60;true&#x60;. If any SLO corrections are applied and this parameter is set to &#x60;false&#x60;, then the corrections will not be applied and the SLI values will not be affected.
      */
-    PromiseServiceLevelObjectivesApi.prototype.getSLOHistory = function (sloId, fromTs, toTs, target, _options) {
-        var result = this.api.getSLOHistory(sloId, fromTs, toTs, target, _options);
+    PromiseServiceLevelObjectivesApi.prototype.getSLOHistory = function (sloId, fromTs, toTs, target, applyCorrection, _options) {
+        var result = this.api.getSLOHistory(sloId, fromTs, toTs, target, applyCorrection, _options);
         return result.toPromise();
     };
     /**
@@ -1623,6 +1634,15 @@ var PromiseSyntheticsApi = /** @class */ (function () {
         var result = this.api.triggerCITests(body, _options);
         return result.toPromise();
     };
+    /**
+     * Trigger a set of Synthetics tests.
+     * Trigger Synthetics tests
+     * @param body The identifiers of the tests to trigger.
+     */
+    PromiseSyntheticsApi.prototype.triggerTests = function (body, _options) {
+        var result = this.api.triggerTests(body, _options);
+        return result.toPromise();
+    };
     /**
      * Edit the configuration of a Synthetic API test.
      * Edit an API test
@@ -1686,7 +1706,7 @@ var PromiseTagsApi = /** @class */ (function () {
      * This endpoint allows you to remove all user-assigned tags for a single host.
      * Remove host tags
      * @param hostName This endpoint allows you to remove all user-assigned tags for a single host.
-     * @param source The source of the tags (e.g. chef, puppet). [Complete list of source attribute values](https://docs.datadoghq.com/integrations/faq/list-of-api-source-attribute-value).
+     * @param source The source of the tags (for example chef, puppet). [Complete list of source attribute values](https://docs.datadoghq.com/integrations/faq/list-of-api-source-attribute-value).
      */
     PromiseTagsApi.prototype.deleteHostTags = function (hostName, source, _options) {
         var result = this.api.deleteHostTags(hostName, source, _options);
@@ -1716,7 +1736,7 @@ var PromiseTagsApi = /** @class */ (function () {
      * Update host tags
      * @param hostName This endpoint allows you to update/replace all in an integration source with those supplied in the request.
      * @param body Add tags to host
-     * @param source The source of the tags (e.g. chef, puppet). [Complete list of source attribute values](https://docs.datadoghq.com/integrations/faq/list-of-api-source-attribute-value)
+     * @param source The source of the tags (for example chef, puppet). [Complete list of source attribute values](https://docs.datadoghq.com/integrations/faq/list-of-api-source-attribute-value)
      */
     PromiseTagsApi.prototype.updateHostTags = function (hostName, body, source, _options) {
         var result = this.api.updateHostTags(hostName, body, source, _options);
@@ -1742,6 +1762,19 @@ var PromiseUsageMeteringApi = /** @class */ (function () {
         var result = this.api.getDailyCustomReports(pageSize, pageNumber, sortDir, sort, _options);
         return result.toPromise();
     };
+    /**
+     * Get Hourly Usage Attribution.
+     * Get Hourly Usage Attribution
+     * @param startHr Datetime in ISO-8601 format, UTC, precise to hour: &#x60;[YYYY-MM-DDThh]&#x60; for usage beginning at this hour.
+     * @param usageType Usage type to retrieve.
+     * @param endHr Datetime in ISO-8601 format, UTC, precise to hour: &#x60;[YYYY-MM-DDThh]&#x60; for usage ending **before** this hour.
+     * @param nextRecordId List following results with a next_record_id provided in the previous query.
+     * @param tagBreakdownKeys Comma separated list of tags used to group usage. If no value is provided the usage will not be broken down by tags.
+     */
+    PromiseUsageMeteringApi.prototype.getHourlyUsageAttribution = function (startHr, usageType, endHr, nextRecordId, tagBreakdownKeys, _options) {
+        var result = this.api.getHourlyUsageAttribution(startHr, usageType, endHr, nextRecordId, tagBreakdownKeys, _options);
+        return result.toPromise();
+    };
     /**
      * Get hourly usage for incident management.
      * Get hourly usage for incident management
@@ -1774,6 +1807,21 @@ var PromiseUsageMeteringApi = /** @class */ (function () {
         var result = this.api.getMonthlyCustomReports(pageSize, pageNumber, sortDir, sort, _options);
         return result.toPromise();
     };
+    /**
+     * Get Monthly Usage Attribution.
+     * Get Monthly Usage Attribution
+     * @param startMonth Datetime in ISO-8601 format, UTC, precise to month: &#x60;[YYYY-MM]&#x60; for usage beginning in this month. Maximum of 15 months ago.
+     * @param fields Comma-separated list of usage types to return, or &#x60;*&#x60; for all usage types.
+     * @param endMonth Datetime in ISO-8601 format, UTC, precise to month: &#x60;[YYYY-MM]&#x60; for usage ending this month.
+     * @param sortDirection The direction to sort by: &#x60;[desc, asc]&#x60;.
+     * @param sortName The field to sort by.
+     * @param tagBreakdownKeys Comma separated list of tags used to group usage. If no value is provided the usage will not be broken down by tags.
+     * @param nextRecordId List following results with a next_record_id provided in the previous query.
+     */
+    PromiseUsageMeteringApi.prototype.getMonthlyUsageAttribution = function (startMonth, fields, endMonth, sortDirection, sortName, tagBreakdownKeys, nextRecordId, _options) {
+        var result = this.api.getMonthlyUsageAttribution(startMonth, fields, endMonth, sortDirection, sortName, tagBreakdownKeys, nextRecordId, _options);
+        return result.toPromise();
+    };
     /**
      * Get specified daily custom reports.
      * Get specified daily custom reports
@@ -1811,9 +1859,11 @@ var PromiseUsageMeteringApi = /** @class */ (function () {
      * @param sortDirection The direction to sort by: &#x60;[desc, asc]&#x60;.
      * @param sortName The field to sort by.
      * @param includeDescendants Include child org usage in the response. Defaults to false.
+     * @param offset Number of records to skip before beginning to return.
+     * @param limit Maximum number of records to be returned.
      */
-    PromiseUsageMeteringApi.prototype.getUsageAttribution = function (startMonth, fields, endMonth, sortDirection, sortName, includeDescendants, _options) {
-        var result = this.api.getUsageAttribution(startMonth, fields, endMonth, sortDirection, sortName, includeDescendants, _options);
+    PromiseUsageMeteringApi.prototype.getUsageAttribution = function (startMonth, fields, endMonth, sortDirection, sortName, includeDescendants, offset, limit, _options) {
+        var result = this.api.getUsageAttribution(startMonth, fields, endMonth, sortDirection, sortName, includeDescendants, offset, limit, _options);
         return result.toPromise();
     };
     /**
@@ -1987,6 +2037,16 @@ var PromiseUsageMeteringApi = /** @class */ (function () {
         var result = this.api.getUsageRumSessions(startHr, endHr, type, _options);
         return result.toPromise();
     };
+    /**
+     * Get hourly usage for [RUM](https://docs.datadoghq.com/real_user_monitoring/) Units.
+     * Get hourly usage for RUM Units
+     * @param startHr Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage beginning at this hour.
+     * @param endHr Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage ending **before** this hour.
+     */
+    PromiseUsageMeteringApi.prototype.getUsageRumUnits = function (startHr, endHr, _options) {
+        var result = this.api.getUsageRumUnits(startHr, endHr, _options);
+        return result.toPromise();
+    };
     /**
      * Get hourly usage for Sensitive Data Scanner.
      * Get hourly usage for Sensitive Data Scanner