datadog_api_client 1.0.0.beta.3 → 1.0.0

data/docs/v1/DashboardsAPI.md

@@ -199,7 +199,7 @@ end
 
 ## list_dashboards
 
-> <DashboardSummary> list_dashboards
+> <DashboardSummary> list_dashboards(opts)
 
 Get all dashboards
 
@@ -210,10 +210,13 @@ Get all dashboards.  **Note**: This query will only return custom created or clo
 ```ruby
 require 'datadog_api_client'
 api_instance = DatadogAPIClient::V1::DashboardsAPI.new
+opts = {
+  filter_shared: true # Boolean | When `true`, this query only returns shared custom created or cloned dashboards.
+}
 
 begin
   # Get all dashboards
-  result = api_instance.list_dashboards
+  result = api_instance.list_dashboards(opts)
   p result
 rescue DatadogAPIClient::V1::APIError => e
   puts "Error when calling DashboardsAPI->list_dashboards: #{e}"
@@ -224,12 +227,12 @@ end
 
 This returns an Array which contains the response data, status code and headers.
 
-> <Array(<DashboardSummary>, Integer, Hash)> list_dashboards_with_http_info
+> <Array(<DashboardSummary>, Integer, Hash)> list_dashboards_with_http_info(opts)
 
 ```ruby
 begin
   # Get all dashboards
-  data, status_code, headers = api_instance.list_dashboards_with_http_info
+  data, status_code, headers = api_instance.list_dashboards_with_http_info(opts)
   p status_code # => 2xx
   p headers # => { ... }
   p data # => <DashboardSummary>
@@ -240,7 +243,9 @@ end
 
 ### Parameters
 
-This endpoint does not need any parameter.
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **filter_shared** | **Boolean** | When &#x60;true&#x60;, this query only returns shared custom created or cloned dashboards. | [optional] |
 
 ### Return type
 

data/docs/v1/DistributionWidgetDefinition.md

@@ -4,14 +4,17 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **legend_size** | **String** | Available legend sizes for a widget. Should be one of \"0\", \"2\", \"4\", \"8\", \"16\", or \"auto\". | [optional] |
+| **legend_size** | **String** | (Deprecated) The widget legend was replaced by a tooltip and sidebar. | [optional] |
+| **markers** | [**Array<WidgetMarker>**](WidgetMarker.md) | List of markers. | [optional] |
 | **requests** | [**Array<DistributionWidgetRequest>**](DistributionWidgetRequest.md) | Array of one request object to display in the widget.  See the dedicated [Request JSON schema documentation](https://docs.datadoghq.com/dashboards/graphing_json/request_json)  to learn how to build the `REQUEST_SCHEMA`. |  |
-| **show_legend** | **Boolean** | Whether or not to display the legend on this widget. | [optional] |
+| **show_legend** | **Boolean** | (Deprecated) The widget legend was replaced by a tooltip and sidebar. | [optional] |
 | **time** | [**WidgetTime**](WidgetTime.md) |  | [optional] |
 | **title** | **String** | Title of the widget. | [optional] |
 | **title_align** | [**WidgetTextAlign**](WidgetTextAlign.md) |  | [optional] |
 | **title_size** | **String** | Size of the title. | [optional] |
 | **type** | [**DistributionWidgetDefinitionType**](DistributionWidgetDefinitionType.md) |  | [default to 'distribution'] |
+| **xaxis** | [**DistributionWidgetXAxis**](DistributionWidgetXAxis.md) |  | [optional] |
+| **yaxis** | [**DistributionWidgetYAxis**](DistributionWidgetYAxis.md) |  | [optional] |
 
 ## Example
 
@@ -20,13 +23,16 @@ require 'datadog_api_client/v1'
 
 instance = DatadogAPIClient::V1::DistributionWidgetDefinition.new(
   legend_size: null,
+  markers: null,
   requests: [{"q":"host:X tags:Y"}],
   show_legend: null,
   time: null,
   title: null,
   title_align: null,
   title_size: null,
-  type: null
+  type: null,
+  xaxis: null,
+  yaxis: null
 )
 ```
 

data/docs/v1/DistributionWidgetXAxis.md

@@ -0,0 +1,24 @@
+# DatadogAPIClient::V1::DistributionWidgetXAxis
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **include_zero** | **Boolean** | True includes zero. | [optional] |
+| **max** | **String** | Specifies maximum value to show on the x-axis. It takes a number, percentile (p90 === 90th percentile), or auto for default behavior. | [optional][default to 'auto'] |
+| **min** | **String** | Specifies minimum value to show on the x-axis. It takes a number, percentile (p90 === 90th percentile), or auto for default behavior. | [optional][default to 'auto'] |
+| **scale** | **String** | Specifies the scale type. Possible values are `linear`. | [optional][default to 'linear'] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::DistributionWidgetXAxis.new(
+  include_zero: null,
+  max: null,
+  min: null,
+  scale: null
+)
+```
+

data/docs/v1/DistributionWidgetYAxis.md

@@ -0,0 +1,26 @@
+# DatadogAPIClient::V1::DistributionWidgetYAxis
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **include_zero** | **Boolean** | True includes zero. | [optional] |
+| **label** | **String** | The label of the axis to display on the graph. | [optional] |
+| **max** | **String** | Specifies the maximum value to show on the y-axis. It takes a number, or auto for default behavior. | [optional][default to 'auto'] |
+| **min** | **String** | Specifies minimum value to show on the y-axis. It takes a number, or auto for default behavior. | [optional][default to 'auto'] |
+| **scale** | **String** | Specifies the scale type. Possible values are `linear` or `log`. | [optional][default to 'linear'] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::DistributionWidgetYAxis.new(
+  include_zero: null,
+  label: null,
+  max: null,
+  min: null,
+  scale: null
+)
+```
+

data/docs/v1/EventsAPI.md

@@ -139,7 +139,7 @@ end
 
 Query the event stream
 
-The event stream can be queried and filtered by time, priority, sources and tags.  **Notes**: - If the event you’re querying contains markdown formatting of any kind, you may see characters such as `%`,`\\`,`n` in your output.  - This endpoint returns a maximum of `1000` most recent results. To return additional results, identify the last timestamp of the last result and set that as the `end` query time to paginate the results.
+The event stream can be queried and filtered by time, priority, sources and tags.  **Notes**: - If the event you’re querying contains markdown formatting of any kind, you may see characters such as `%`,`\\`,`n` in your output.  - This endpoint returns a maximum of `1000` most recent results. To return additional results, identify the last timestamp of the last result and set that as the `end` query time to paginate the results. You can also use the page parameter to specify which set of `1000` results to return.
 
 ### Examples
 
@@ -152,7 +152,9 @@ opts = {
   priority: DatadogAPIClient::V1::EventPriority::NORMAL, # EventPriority | Priority of your events, either `low` or `normal`.
   sources: 'sources_example', # String | A comma separated string of sources.
   tags: 'host:host0', # String | A comma separated list indicating what tags, if any, should be used to filter the list of monitors by scope.
-  unaggregated: true # Boolean | Set unaggregated to `true` to return all events within the specified [`start`,`end`] timeframe. Otherwise if an event is aggregated to a parent event with a timestamp outside of the timeframe, it won't be available in the output.
+  unaggregated: true, # Boolean | Set unaggregated to `true` to return all events within the specified [`start`,`end`] timeframe. Otherwise if an event is aggregated to a parent event with a timestamp outside of the timeframe, it won't be available in the output. Aggregated events with `is_aggregate=true` in the response will still be returned unless exclude_aggregate is set to `true.`
+  exclude_aggregate: true, # Boolean | Set `exclude_aggregate` to `true` to only return unaggregated events where `is_aggregate=false` in the response. If the `exclude_aggregate` parameter is set to `true`, then the unaggregated parameter is ignored and will be `true` by default.
+  page: 56 # Integer | By default 1000 results are returned per request. Set page to the number of the page to return with `0` being the first page. The page parameter can only be used when either unaggregated or exclude_aggregate is set to `true.`
 }
 
 begin
@@ -191,7 +193,9 @@ end
 | **priority** | **EventPriority** | Priority of your events, either `low` or `normal`. | [optional] |
 | **sources** | **String** | A comma separated string of sources. | [optional] |
 | **tags** | **String** | A comma separated list indicating what tags, if any, should be used to filter the list of monitors by scope. | [optional] |
-| **unaggregated** | **Boolean** | Set unaggregated to `true` to return all events within the specified [`start`,`end`] timeframe. Otherwise if an event is aggregated to a parent event with a timestamp outside of the timeframe, it won't be available in the output. | [optional] |
+| **unaggregated** | **Boolean** | Set unaggregated to `true` to return all events within the specified [`start`,`end`] timeframe. Otherwise if an event is aggregated to a parent event with a timestamp outside of the timeframe, it won't be available in the output. Aggregated events with `is_aggregate=true` in the response will still be returned unless exclude_aggregate is set to `true.` | [optional] |
+| **exclude_aggregate** | **Boolean** | Set `exclude_aggregate` to `true` to only return unaggregated events where `is_aggregate=false` in the response. If the `exclude_aggregate` parameter is set to `true`, then the unaggregated parameter is ignored and will be `true` by default. | [optional] |
+| **page** | **Integer** | By default 1000 results are returned per request. Set page to the number of the page to return with `0` being the first page. The page parameter can only be used when either unaggregated or exclude_aggregate is set to `true.` | [optional] |
 
 ### Return type
 

data/docs/v1/GroupWidgetDefinition.md

@@ -4,8 +4,12 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
+| **background_color** | **String** | Background color of the group title. | [optional] |
+| **banner_img** | **String** | URL of image to display as a banner for the group. | [optional] |
 | **layout_type** | [**WidgetLayoutType**](WidgetLayoutType.md) |  |  |
+| **show_title** | **Boolean** | Whether to show the title or not. | [optional][default to true] |
 | **title** | **String** | Title of the widget. | [optional] |
+| **title_align** | [**WidgetTextAlign**](WidgetTextAlign.md) |  | [optional] |
 | **type** | [**GroupWidgetDefinitionType**](GroupWidgetDefinitionType.md) |  | [default to 'group'] |
 | **widgets** | [**Array<Widget>**](Widget.md) | List of widget groups. |  |
 
@@ -15,8 +19,12 @@
 require 'datadog_api_client/v1'
 
 instance = DatadogAPIClient::V1::GroupWidgetDefinition.new(
+  background_color: null,
+  banner_img: null,
   layout_type: null,
+  show_title: null,
   title: null,
+  title_align: null,
   type: null,
   widgets: [{"definition":{"requests":{"fill":{"q":"system.cpu.user"}},"type":"hostmap"}}]
 )

data/docs/v1/ImageWidgetDefinition.md

@@ -4,10 +4,15 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
+| **has_background** | **Boolean** | Whether to display a background or not. | [optional][default to true] |
+| **has_border** | **Boolean** | Whether to display a border or not. | [optional][default to true] |
+| **horizontal_align** | [**WidgetHorizontalAlign**](WidgetHorizontalAlign.md) |  | [optional] |
 | **margin** | [**WidgetMargin**](WidgetMargin.md) |  | [optional] |
 | **sizing** | [**WidgetImageSizing**](WidgetImageSizing.md) |  | [optional] |
 | **type** | [**ImageWidgetDefinitionType**](ImageWidgetDefinitionType.md) |  | [default to 'image'] |
 | **url** | **String** | URL of the image. |  |
+| **url_dark_theme** | **String** | URL of the image in dark mode. | [optional] |
+| **vertical_align** | [**WidgetVerticalAlign**](WidgetVerticalAlign.md) |  | [optional] |
 
 ## Example
 
@@ -15,10 +20,15 @@
 require 'datadog_api_client/v1'
 
 instance = DatadogAPIClient::V1::ImageWidgetDefinition.new(
+  has_background: true,
+  has_border: true,
+  horizontal_align: null,
   margin: null,
   sizing: null,
   type: null,
-  url: 
+  url: https://example.com/image.png,
+  url_dark_theme: https://example.com/image-dark-mode.png,
+  vertical_align: null
 )
 ```
 

data/docs/v1/LogsByRetention.md

@@ -0,0 +1,22 @@
+# DatadogAPIClient::V1::LogsByRetention
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **orgs** | [**LogsByRetentionOrgs**](LogsByRetentionOrgs.md) |  | [optional] |
+| **usage** | [**Array<LogsRetentionAggSumUsage>**](LogsRetentionAggSumUsage.md) | Aggregated index logs usage for each retention period with usage. | [optional] |
+| **usage_by_month** | [**LogsByRetentionMonthlyUsage**](LogsByRetentionMonthlyUsage.md) |  | [optional] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::LogsByRetention.new(
+  orgs: null,
+  usage: null,
+  usage_by_month: null
+)
+```
+

data/docs/v1/LogsByRetentionMonthlyUsage.md

@@ -0,0 +1,20 @@
+# DatadogAPIClient::V1::LogsByRetentionMonthlyUsage
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **date** | **String** | The month for the usage. | [optional] |
+| **usage** | [**Array<LogsRetentionSumUsage>**](LogsRetentionSumUsage.md) | Indexed logs usage for each active retention for the month. | [optional] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::LogsByRetentionMonthlyUsage.new(
+  date: null,
+  usage: null
+)
+```
+

data/docs/v1/LogsByRetentionOrgUsage.md

@@ -0,0 +1,18 @@
+# DatadogAPIClient::V1::LogsByRetentionOrgUsage
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **usage** | [**Array<LogsRetentionSumUsage>**](LogsRetentionSumUsage.md) | Indexed logs usage for each active retention for the organization. | [optional] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::LogsByRetentionOrgUsage.new(
+  usage: null
+)
+```
+

data/docs/v1/LogsByRetentionOrgs.md

@@ -0,0 +1,18 @@
+# DatadogAPIClient::V1::LogsByRetentionOrgs
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **usage** | [**Array<LogsByRetentionOrgUsage>**](LogsByRetentionOrgUsage.md) | Indexed logs usage summary for each organization. | [optional] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::LogsByRetentionOrgs.new(
+  usage: null
+)
+```
+

data/docs/v1/LogsRetentionAggSumUsage.md

@@ -0,0 +1,24 @@
+# DatadogAPIClient::V1::LogsRetentionAggSumUsage
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **logs_indexed_logs_usage_agg_sum** | **Integer** | Total indexed logs for this retention period. | [optional] |
+| **logs_live_indexed_logs_usage_agg_sum** | **Integer** | Live indexed logs for this retention period. | [optional] |
+| **logs_rehydrated_indexed_logs_usage_agg_sum** | **Integer** | Rehydrated indexed logs for this retention period. | [optional] |
+| **retention** | **String** | The retention period in days or \"custom\" for all custom retention periods. | [optional] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::LogsRetentionAggSumUsage.new(
+  logs_indexed_logs_usage_agg_sum: null,
+  logs_live_indexed_logs_usage_agg_sum: null,
+  logs_rehydrated_indexed_logs_usage_agg_sum: null,
+  retention: null
+)
+```
+

data/docs/v1/LogsRetentionSumUsage.md

@@ -0,0 +1,24 @@
+# DatadogAPIClient::V1::LogsRetentionSumUsage
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **logs_indexed_logs_usage_sum** | **Integer** | Total indexed logs for this retention period. | [optional] |
+| **logs_live_indexed_logs_usage_sum** | **Integer** | Live indexed logs for this retention period. | [optional] |
+| **logs_rehydrated_indexed_logs_usage_sum** | **Integer** | Rehydrated indexed logs for this retention period. | [optional] |
+| **retention** | **String** | The retention period in days or \"custom\" for all custom retention periods. | [optional] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::LogsRetentionSumUsage.new(
+  logs_indexed_logs_usage_sum: null,
+  logs_live_indexed_logs_usage_sum: null,
+  logs_rehydrated_indexed_logs_usage_sum: null,
+  retention: null
+)
+```
+

data/docs/v1/MonitorsAPI.md

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

data/docs/v1/NoteWidgetDefinition.md

@@ -7,11 +7,13 @@
 | **background_color** | **String** | Background color of the note. | [optional] |
 | **content** | **String** | Content of the note. |  |
 | **font_size** | **String** | Size of the text. | [optional] |
+| **has_padding** | **Boolean** | Whether to add padding or not. | [optional][default to true] |
 | **show_tick** | **Boolean** | Whether to show a tick or not. | [optional] |
 | **text_align** | [**WidgetTextAlign**](WidgetTextAlign.md) |  | [optional] |
 | **tick_edge** | [**WidgetTickEdge**](WidgetTickEdge.md) |  | [optional] |
 | **tick_pos** | **String** | Where to position the tick on an edge. | [optional] |
 | **type** | [**NoteWidgetDefinitionType**](NoteWidgetDefinitionType.md) |  | [default to 'note'] |
+| **vertical_align** | [**WidgetVerticalAlign**](WidgetVerticalAlign.md) |  | [optional] |
 
 ## Example
 
@@ -22,11 +24,13 @@ instance = DatadogAPIClient::V1::NoteWidgetDefinition.new(
   background_color: null,
   content: ,
   font_size: null,
+  has_padding: null,
   show_tick: null,
   text_align: null,
   tick_edge: null,
   tick_pos: null,
-  type: null
+  type: null,
+  vertical_align: null
 )
 ```
 

data/docs/v1/NotebookAbsoluteTime.md

@@ -0,0 +1,22 @@
+# DatadogAPIClient::V1::NotebookAbsoluteTime
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **_end** | **Time** | The end time. |  |
+| **live** | **Boolean** | Indicates whether the timeframe should be shifted to end at the current time. | [optional] |
+| **start** | **Time** | The start time. |  |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::NotebookAbsoluteTime.new(
+  _end: 2021-02-24T20:18:28Z,
+  live: null,
+  start: 2021-02-24T19:18:28Z
+)
+```
+

data/docs/v1/NotebookAuthor.md

@@ -0,0 +1,34 @@
+# DatadogAPIClient::V1::NotebookAuthor
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **created_at** | **Time** | Creation time of the user. | [optional] |
+| **disabled** | **Boolean** | Whether the user is disabled. | [optional] |
+| **email** | **String** | Email of the user. | [optional] |
+| **handle** | **String** | Handle of the user. | [optional] |
+| **icon** | **String** | URL of the user's icon. | [optional] |
+| **name** | **String** | Name of the user. | [optional] |
+| **status** | **String** | Status of the user. | [optional] |
+| **title** | **String** | Title of the user. | [optional] |
+| **verified** | **Boolean** | Whether the user is verified. | [optional] |
+
+## Example
+
+```ruby
+require 'datadog_api_client/v1'
+
+instance = DatadogAPIClient::V1::NotebookAuthor.new(
+  created_at: null,
+  disabled: null,
+  email: null,
+  handle: null,
+  icon: null,
+  name: null,
+  status: null,
+  title: null,
+  verified: null
+)
+```
+