datadog_api_client 1.2.0 → 1.6.0

data/spec/v1/api/logs_api_spec.rb

@@ -47,4 +47,18 @@ describe 'LogsAPI' do
     end
   end
 
+  # unit tests for submit_log
+  # Send logs
+  # Send your logs to your Datadog platform over HTTP. Limits per HTTP request are:  - Maximum content size per payload (uncompressed): 5MB - Maximum size for a single log: 1MB - Maximum array size if sending multiple logs in an array: 1000 entries  Any log exceeding 1MB is accepted and truncated by Datadog: - For a single log request, the API truncates the log at 1MB and returns a 2xx. - For a multi-logs request, the API processes all logs, truncates only logs larger than 1MB, and returns a 2xx.  Datadog recommends sending your logs compressed. Add the `Content-Encoding: gzip` header to the request when sending compressed logs.  The status codes answered by the HTTP API are: - 200: OK - 400: Bad request (likely an issue in the payload formatting) - 403: Permission issue (likely using an invalid API Key) - 413: Payload too large (batch is above 5MB uncompressed) - 5xx: Internal error, request should be retried after some time
+  # @param body Log to send (JSON format).
+  # @param [Hash] opts the optional parameters
+  # @option opts [ContentEncoding] :content_encoding HTTP header used to compress the media-type.
+  # @option opts [String] :ddtags Log tags can be passed as query parameters with `text/plain` content type.
+  # @return [Object]
+  describe 'submit_log test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
 end

data/spec/v1/api/metrics_api_spec.rb

@@ -87,6 +87,19 @@ describe 'MetricsAPI' do
     end
   end
 
+  # unit tests for submit_metrics
+  # Submit metrics
+  # The metrics end-point allows you to post time-series data that can be graphed on Datadog’s dashboards. The maximum payload size is 3.2 megabytes (3200000 bytes). Compressed payloads must have a decompressed size of less than 62 megabytes (62914560 bytes).  If you’re submitting metrics directly to the Datadog API without using DogStatsD, expect:  - 64 bits for the timestamp - 32 bits for the value - 20 bytes for the metric names - 50 bytes for the timeseries - The full payload is approximately 100 bytes. However, with the DogStatsD API, compression is applied, which reduces the payload size.
+  # @param body 
+  # @param [Hash] opts the optional parameters
+  # @option opts [MetricContentEncoding] :content_encoding HTTP header used to compress the media-type.
+  # @return [IntakePayloadAccepted]
+  describe 'submit_metrics test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
   # unit tests for update_metric_metadata
   # Edit metric metadata
   # Edit metadata of a specific metric. Find out more about [supported types](https://docs.datadoghq.com/developers/metrics).

data/spec/v1/api/monitors_api_spec.rb

@@ -49,7 +49,7 @@ describe 'MonitorsAPI' do
 
   # unit tests for create_monitor
   # 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` - watchdog: `event alert` - event-v2: `event-v2 alert`  #### Query Types  **Metric Alert Query**  Example: `time_aggr(time_window):space_aggr:metric{tags} [by {key}] operator #`  - `time_aggr`: avg, sum, max, min, change, or pct_change - `time_window`: `last_#m` (with `#` between 1 and 2880 depending on the monitor type) or `last_#h`(with `#` between 1 and 48 depending on the monitor type), or `last_1d` - `space_aggr`: avg, sum, min, or max - `tags`: one or more tags (comma-separated), or * - `key`: a 'key' in key:value tag syntax; defines a separate alert for each tag in the group (multi-alert) - `operator`: <, <=, >, >=, ==, or != - `#`: an integer or decimal number used to set the threshold  If you are using the `_change_` or `_pct_change_` time aggregator, instead use `change_aggr(time_aggr(time_window), timeshift):space_aggr:metric{tags} [by {key}] operator #` with:  - `change_aggr` change, pct_change - `time_aggr` avg, sum, max, min [Learn more](https://docs.datadoghq.com/monitors/monitor_types/#define-the-conditions) - `time_window` last\\_#m (between 1 and 2880 depending on the monitor type), last\\_#h (between 1 and 48 depending on the monitor type), or last_#d (1 or 2) - `timeshift` #m_ago (5, 10, 15, or 30), #h_ago (1, 2, or 4), or 1d_ago  Use this to create an outlier monitor using the following query: `avg(last_30m):outliers(avg:system.cpu.user{role:es-events-data} by {host}, 'dbscan', 7) > 0`  **Service Check Query**  Example: `\"check\".over(tags).last(count).count_by_status()`  - **`check`** name of the check, e.g. `datadog.agent.up` - **`tags`** one or more quoted tags (comma-separated), or \"*\". e.g.: `.over(\"env:prod\", \"role:db\")` - **`count`** must be at >= your max threshold (defined in the `options`). e.g. if you want to notify on 1 critical, 3 ok and 2 warn statuses count should be 3. It is limited to 100.  **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.
+  # 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.
   # @param body Create a monitor request body.
   # @param [Hash] opts the optional parameters
   # @return [Monitor]
@@ -64,7 +64,7 @@ describe 'MonitorsAPI' do
   # Delete the specified monitor
   # @param monitor_id The ID of the monitor.
   # @param [Hash] opts the optional parameters
-  # @option opts [String] :force Delete the monitor even if it's referenced by other resources (e.g. SLO, composite monitor).
+  # @option opts [String] :force Delete the monitor even if it's referenced by other resources (for example SLO, composite monitor).
   # @return [DeletedMonitor]
   describe 'delete_monitor test' do
     it 'should work' do
@@ -93,8 +93,8 @@ describe 'MonitorsAPI' do
   # @option opts [String] :name A string to filter monitors by name.
   # @option opts [String] :tags A comma separated list indicating what tags, if any, should be used to filter the list of monitors by scope. For example, `host:host0`.
   # @option opts [String] :monitor_tags A comma separated list indicating what service and/or custom tags, if any, should be used to filter the list of monitors. Tags created in the Datadog UI automatically have the service key prepended. For example, `service:my-app`.
-  # @option opts [Boolean] :with_downtimes If this argument is set to true, then the returned data includes all current downtimes for each monitor.
-  # @option opts [Integer] :id_offset Monitor ID offset.
+  # @option opts [Boolean] :with_downtimes If this argument is set to true, then the returned data includes all current active downtimes for each monitor.
+  # @option opts [Integer] :id_offset 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.
   # @option opts [Integer] :page The page to start paginating from. If this argument is not specified, the request returns all monitors without pagination.
   # @option opts [Integer] :page_size The number of monitors to return per page. If the page argument is not specified, the default behavior returns all monitors without a `page_size` limit. However, if page is specified and `page_size` is not, the argument defaults to 100.
   # @return [Array<Monitor>]
@@ -104,6 +104,36 @@ describe 'MonitorsAPI' do
     end
   end
 
+  # unit tests for search_monitor_groups
+  # Monitors group search
+  # Search and filter your monitor groups details.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :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
+  # @option opts [Integer] :page Page to start paginating from.
+  # @option opts [Integer] :per_page Number of monitors to return per page.
+  # @option opts [String] :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;
+  # @return [MonitorGroupSearchResponse]
+  describe 'search_monitor_groups test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for search_monitors
+  # Monitors search
+  # Search and filter your monitors details.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :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
+  # @option opts [Integer] :page Page to start paginating from.
+  # @option opts [Integer] :per_page Number of monitors to return per page.
+  # @option opts [String] :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;
+  # @return [MonitorSearchResponse]
+  describe 'search_monitors test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
   # unit tests for update_monitor
   # Edit a monitor
   # Edit the specified monitor.
@@ -122,7 +152,7 @@ describe 'MonitorsAPI' do
   # Validate the monitor provided in the request.
   # @param body Monitor request object
   # @param [Hash] opts the optional parameters
-  # @return [Monitor]
+  # @return [Object]
   describe 'validate_monitor test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers

data/spec/v1/api/notebooks_api_spec.rb

@@ -79,10 +79,12 @@ describe 'NotebooksAPI' do
   # @option opts [String] :exclude_author_handle Return notebooks not created by the given `author_handle`.
   # @option opts [Integer] :start The index of the first notebook you want returned.
   # @option opts [Integer] :count The number of notebooks to be returned.
-  # @option opts [String] :sort_field Sort by field `modified` or `name`.
+  # @option opts [String] :sort_field Sort by field `modified`, `name`, or `created`.
   # @option opts [String] :sort_dir Sort by direction `asc` or `desc`.
   # @option opts [String] :query Return only notebooks with `query` string in notebook name or author handle.
   # @option opts [Boolean] :include_cells Value of `false` excludes the `cells` and global `time` for each notebook.
+  # @option opts [Boolean] :is_template True value returns only template notebooks. Default is false (returns only non-template notebooks).
+  # @option opts [String] :type If type is provided, returns only notebooks with that metadata type. Default does not have type filtering.
   # @return [NotebooksResponse]
   describe 'list_notebooks test' do
     it 'should work' do

data/spec/v1/api/organizations_api_spec.rb

@@ -37,7 +37,7 @@ describe 'OrganizationsAPI' do
 
   # unit tests for create_child_org
   # 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.
+  # 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`, `api_key.key`, and `application_key.hash` provided in the response.
   # @param body Organization object that needs to be created
   # @param [Hash] opts the optional parameters
   # @return [OrganizationCreateResponse]

data/spec/v1/api/service_checks_api_spec.rb

@@ -37,7 +37,7 @@ describe 'ServiceChecksAPI' do
 
   # unit tests for submit_service_check
   # Submit a Service Check
-  # Submit a list of Service Checks.  **Note**: A valid API key is required.
+  # Submit a list of Service Checks.  **Notes**: - A valid API key is required. - Service checks can be submitted up to 10 minutes in the past.
   # @param body Service Check request body.
   # @param [Hash] opts the optional parameters
   # @return [IntakePayloadAccepted]

data/spec/v1/api/service_level_objective_corrections_api_spec.rb

@@ -37,7 +37,7 @@ describe 'ServiceLevelObjectiveCorrectionsAPI' do
 
   # unit tests for create_slo_correction
   # Create an SLO correction
-  # Create an SLO Correction
+  # Create an SLO Correction.
   # @param body Create an SLO Correction
   # @param [Hash] opts the optional parameters
   # @return [SLOCorrectionResponse]
@@ -48,9 +48,9 @@ describe 'ServiceLevelObjectiveCorrectionsAPI' do
   end
 
   # unit tests for delete_slo_correction
-  # Delete an SLO Correction
-  # Permanently delete the specified SLO Correction object
-  # @param slo_correction_id The ID of the SLO correction object
+  # Delete an SLO correction
+  # Permanently delete the specified SLO correction object.
+  # @param slo_correction_id The ID of the SLO correction object.
   # @param [Hash] opts the optional parameters
   # @return [nil]
   describe 'delete_slo_correction test' do
@@ -61,8 +61,8 @@ describe 'ServiceLevelObjectiveCorrectionsAPI' do
 
   # unit tests for get_slo_correction
   # Get an SLO correction for an SLO
-  # Get an SLO Correction
-  # @param slo_correction_id The ID of the SLO correction object
+  # Get an SLO correction.
+  # @param slo_correction_id The ID of the SLO correction object.
   # @param [Hash] opts the optional parameters
   # @return [SLOCorrectionResponse]
   describe 'get_slo_correction test' do
@@ -73,7 +73,7 @@ describe 'ServiceLevelObjectiveCorrectionsAPI' do
 
   # unit tests for list_slo_correction
   # Get all SLO corrections
-  # Get all Service Level Objective Corrections
+  # Get all Service Level Objective corrections.
   # @param [Hash] opts the optional parameters
   # @return [SLOCorrectionListResponse]
   describe 'list_slo_correction test' do
@@ -83,9 +83,9 @@ describe 'ServiceLevelObjectiveCorrectionsAPI' do
   end
 
   # unit tests for update_slo_correction
-  # Update an SLO Correction
-  # Update the specified SLO correction object object
-  # @param slo_correction_id The ID of the SLO correction object
+  # Update an SLO correction
+  # Update the specified SLO correction object object.
+  # @param slo_correction_id The ID of the SLO correction object.
   # @param body The edited SLO correction object.
   # @param [Hash] opts the optional parameters
   # @return [SLOCorrectionResponse]

data/spec/v1/api/service_level_objectives_api_spec.rb

@@ -64,7 +64,7 @@ describe 'ServiceLevelObjectivesAPI' do
   # 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.
   # @param slo_id The ID of the service level objective.
   # @param [Hash] opts the optional parameters
-  # @option opts [String] :force Delete the monitor even if it's referenced by other resources (e.g. SLO, composite monitor).
+  # @option opts [String] :force Delete the monitor even if it's referenced by other resources (for example SLO, composite monitor).
   # @return [SLODeleteResponse]
   describe 'delete_slo test' do
     it 'should work' do
@@ -89,6 +89,7 @@ describe 'ServiceLevelObjectivesAPI' do
   # Get a service level objective object.
   # @param slo_id The ID of the service level objective object.
   # @param [Hash] opts the optional parameters
+  # @option opts [Boolean] :with_configured_alert_ids Get the IDs of SLO monitors that reference this SLO.
   # @return [SLOResponse]
   describe 'get_slo test' do
     it 'should work' do
@@ -96,6 +97,18 @@ describe 'ServiceLevelObjectivesAPI' do
     end
   end
 
+  # unit tests for get_slo_corrections
+  # Get Corrections For an SLO
+  # Get corrections applied to an SLO
+  # @param slo_id The ID of the service level objective object.
+  # @param [Hash] opts the optional parameters
+  # @return [SLOCorrectionListResponse]
+  describe 'get_slo_corrections test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
   # unit tests for get_slo_history
   # Get an SLO's history
   # 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.
@@ -103,6 +116,8 @@ describe 'ServiceLevelObjectivesAPI' do
   # @param from_ts The `from` timestamp for the query window in epoch seconds.
   # @param to_ts The `to` timestamp for the query window in epoch seconds.
   # @param [Hash] opts the optional parameters
+  # @option opts [Float] :target The SLO target. If `target` is passed in, the response will include the remaining error budget and a timeframe value of `custom`.
+  # @option opts [Boolean] :apply_correction Defaults to `true`. If any SLO corrections are applied and this parameter is set to `false`, then the corrections will not be applied and the SLI values will not be affected.
   # @return [SLOHistoryResponse]
   describe 'get_slo_history test' do
     it 'should work' do
@@ -118,6 +133,8 @@ describe 'ServiceLevelObjectivesAPI' do
   # @option opts [String] :query The query string to filter results based on SLO names.
   # @option opts [String] :tags_query The query string to filter results based on a single SLO tag.
   # @option opts [String] :metrics_query The query string to filter results based on SLO numerator and denominator.
+  # @option opts [Integer] :limit The number of SLOs to return in the response.
+  # @option opts [Integer] :offset The specific offset to use as the beginning of the returned response.
   # @return [SLOListResponse]
   describe 'list_slos test' do
     it 'should work' do

data/spec/v1/api/synthetics_api_spec.rb

@@ -83,18 +83,6 @@ describe 'SyntheticsAPI' do
     end
   end
 
-  # unit tests for create_test
-  # Create a test
-  # Create a Synthetic test.
-  # @param body Details of the test to create.
-  # @param [Hash] opts the optional parameters
-  # @return [SyntheticsTestDetails]
-  describe 'create_test test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for delete_global_variable
   # Delete a global variable
   # Delete a Synthetics global variable.
@@ -157,12 +145,12 @@ describe 'SyntheticsAPI' do
   end
 
   # unit tests for get_api_test_latest_results
-  # Get the test's latest results summaries (API)
+  # Get an API test's latest results summaries
   # Get the last 50 test results summaries for a given Synthetics API test.
   # @param public_id The public ID of the test for which to search results for.
   # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :from_ts Timestamp from which to start querying results.
-  # @option opts [Integer] :to_ts Timestamp up to which to query results.
+  # @option opts [Integer] :from_ts Timestamp in milliseconds from which to start querying results.
+  # @option opts [Integer] :to_ts Timestamp in milliseconds up to which to query results.
   # @option opts [Array<String>] :probe_dc Locations for which to query results.
   # @return [SyntheticsGetAPITestLatestResultsResponse]
   describe 'get_api_test_latest_results test' do
@@ -172,7 +160,7 @@ describe 'SyntheticsAPI' do
   end
 
   # unit tests for get_api_test_result
-  # Get a test result (API)
+  # Get an API test result
   # Get a specific full result from a given (API) Synthetic test.
   # @param public_id The public ID of the API test to which the target result belongs.
   # @param result_id The ID of the result to get.
@@ -185,11 +173,11 @@ describe 'SyntheticsAPI' do
   end
 
   # unit tests for get_browser_test
-  # Get a test configuration (browser)
+  # Get a browser test
   # Get the detailed configuration (including steps) associated with a Synthetic browser test.
   # @param public_id The public ID of the test to get details from.
   # @param [Hash] opts the optional parameters
-  # @return [SyntheticsTestDetails]
+  # @return [SyntheticsBrowserTest]
   describe 'get_browser_test test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -197,12 +185,12 @@ describe 'SyntheticsAPI' do
   end
 
   # unit tests for get_browser_test_latest_results
-  # Get the test&#39;s latest results summaries (browser)
+  # Get a browser test&#39;s latest results summaries
   # Get the last 50 test results summaries for a given Synthetics Browser test.
   # @param public_id The public ID of the browser test for which to search results for.
   # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :from_ts Timestamp from which to start querying results.
-  # @option opts [Integer] :to_ts Timestamp up to which to query results.
+  # @option opts [Integer] :from_ts Timestamp in milliseconds from which to start querying results.
+  # @option opts [Integer] :to_ts Timestamp in milliseconds up to which to query results.
   # @option opts [Array<String>] :probe_dc Locations for which to query results.
   # @return [SyntheticsGetBrowserTestLatestResultsResponse]
   describe 'get_browser_test_latest_results test' do
@@ -212,7 +200,7 @@ describe 'SyntheticsAPI' do
   end
 
   # unit tests for get_browser_test_result
-  # Get a test result (browser)
+  # Get a browser test result
   # Get a specific full result from a given (browser) Synthetic test.
   # @param public_id The public ID of the browser test to which the target result belongs.
   # @param result_id The ID of the result to get.
@@ -248,8 +236,20 @@ describe 'SyntheticsAPI' do
     end
   end
 
+  # unit tests for get_synthetics_ci_batch
+  # Get details of batch
+  # Get a batch&#39;s updated details.
+  # @param batch_id The ID of the batch.
+  # @param [Hash] opts the optional parameters
+  # @return [SyntheticsBatchDetails]
+  describe 'get_synthetics_ci_batch test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
   # unit tests for get_test
-  # Get a test configuration (API)
+  # Get a test configuration
   # Get the detailed configuration associated with a Synthetics test.
   # @param public_id The public ID of the test to get details from.
   # @param [Hash] opts the optional parameters
@@ -260,6 +260,17 @@ describe 'SyntheticsAPI' do
     end
   end
 
+  # unit tests for list_global_variables
+  # Get all global variables
+  # Get the list of all Synthetics global variables.
+  # @param [Hash] opts the optional parameters
+  # @return [SyntheticsListGlobalVariablesResponse]
+  describe 'list_global_variables test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
   # unit tests for list_locations
   # Get all locations (public and private)
   # Get the list of public and private locations available for Synthetic tests. No arguments required.
@@ -283,7 +294,7 @@ describe 'SyntheticsAPI' do
   end
 
   # unit tests for trigger_ci_tests
-  # Trigger some Synthetics tests for CI
+  # Trigger tests from CI/CD pipelines
   # Trigger a set of Synthetics tests for continuous integration.
   # @param body Details of the test to trigger.
   # @param [Hash] opts the optional parameters
@@ -294,6 +305,18 @@ describe 'SyntheticsAPI' do
     end
   end
 
+  # unit tests for trigger_tests
+  # Trigger Synthetics tests
+  # Trigger a set of Synthetics tests.
+  # @param body The identifiers of the tests to trigger.
+  # @param [Hash] opts the optional parameters
+  # @return [SyntheticsTriggerCITestsResponse]
+  describe 'trigger_tests test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
   # unit tests for update_api_test
   # Edit an API test
   # Edit the configuration of a Synthetic API test.
@@ -333,19 +356,6 @@ describe 'SyntheticsAPI' do
     end
   end
 
-  # unit tests for update_test
-  # Edit a test
-  # Edit the configuration of a Synthetic test.
-  # @param public_id The public ID of the test to get details from.
-  # @param body New test details to be saved.
-  # @param [Hash] opts the optional parameters
-  # @return [SyntheticsTestDetails]
-  describe 'update_test test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for update_test_pause_status
   # Pause or start a test
   # Pause or start a Synthetics test by changing the status.

data/spec/v1/api/tags_api_spec.rb

@@ -54,7 +54,7 @@ describe 'TagsAPI' do
   # This endpoint allows you to remove all user-assigned tags for a single host.
   # @param host_name This endpoint allows you to remove all user-assigned tags for a single host.
   # @param [Hash] opts the optional parameters
-  # @option opts [String] :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).
+  # @option opts [String] :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).
   # @return [nil]
   describe 'delete_host_tags test' do
     it 'should work' do
@@ -93,7 +93,7 @@ describe 'TagsAPI' do
   # @param host_name 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 [Hash] opts the optional parameters
-  # @option opts [String] :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)
+  # @option opts [String] :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)
   # @return [HostTags]
   describe 'update_host_tags test' do
     it 'should work' do