datadog_api_client 1.9.0 → 1.10.0

data/.generator/schemas/v1/openapi.yaml

@@ -4,6 +4,13 @@ components:
   headers: {}
   links: {}
   parameters:
+    SignalID:
+      description: The ID of the signal.
+      in: path
+      name: signal_id
+      required: true
+      schema:
+        type: string
     SlackAccountNamePathParameter:
       description: Your Slack account name.
       in: path
@@ -360,6 +367,23 @@ components:
       - ADMIN
       - READ_ONLY
       - ERROR
+    AddSignalToIncidentRequest:
+      description: Attributes describing which incident to add the signal to.
+      properties:
+        add_to_signal_timeline:
+          description: Whether to post the signal on the incident timeline.
+          type: boolean
+        incident_id:
+          description: Public ID attribute of the incident to which the signal will
+            be added.
+          example: 2066
+          format: int64
+          type: integer
+        version:
+          $ref: '#/components/schemas/Version'
+      required:
+      - incident_id
+      type: object
     AgentCheck:
       description: Array of strings.
       example:
@@ -1499,6 +1523,11 @@ components:
             description: A monitor tag.
             type: string
           type: array
+        mute_first_recovery_notification:
+          description: If the first recovery notification during a downtime should
+            be muted.
+          example: false
+          type: boolean
         parent_id:
           description: ID of the parent Downtime.
           example: 123
@@ -1628,6 +1657,11 @@ components:
             description: A monitor tag.
             type: string
           type: array
+        mute_first_recovery_notification:
+          description: If the first recovery notification during a downtime should
+            be muted.
+          example: false
+          type: boolean
         parent_id:
           description: ID of the parent Downtime.
           example: 123
@@ -1783,7 +1817,7 @@ components:
           description: 'The type of event being posted. Option examples include nagios,
             hudson, jenkins, my_apps, chef, puppet, git, bitbucket, etc.
 
-            A complete list of source attribute values [available here](https://docs.datadoghq.com/integrations/faq/list-of-api-source-attribute-value).'
+            The list of standard source attribute values [available here](https://docs.datadoghq.com/integrations/faq/list-of-api-source-attribute-value).'
           type: string
         tags:
           description: A list of tags to apply to the event.
@@ -2887,6 +2921,9 @@ components:
       - message
       type: object
     HTTPLogItem:
+      additionalProperties:
+        description: Additional log attributes.
+        type: string
       description: Logs that are sent over HTTP.
       properties:
         ddsource:
@@ -4298,7 +4335,7 @@ components:
         categories:
           description: 'Array of filters to match or not a log and their
 
-            corresponding `name`to assign a custom value to the log.'
+            corresponding `name` to assign a custom value to the log.'
           example: []
           items:
             $ref: '#/components/schemas/LogsCategoryProcessorCategory'
@@ -5084,7 +5121,7 @@ components:
       x-enum-varnames:
       - SERVICE_REMAPPER
     LogsSort:
-      description: Time-ascending `asc` or time-descending `desc`results.
+      description: Time-ascending `asc` or time-descending `desc` results.
       enum:
       - asc
       - desc
@@ -5801,11 +5838,13 @@ components:
       enum:
       - rum
       - ci_pipelines
+      - ci_tests
       example: rum
       type: string
       x-enum-varnames:
       - RUM
       - CI_PIPELINES
+      - CI_TESTS
     MonitorFormulaAndFunctionQueryDefinition:
       description: A formula and function query.
       oneOf:
@@ -6059,7 +6098,8 @@ components:
           type: boolean
         silenced:
           additionalProperties:
-            description: ID of the downtime applied to the monitor.
+            description: UTC epoch timestamp in seconds when the downtime for the
+              group expires.
             format: int64
             nullable: true
             type: integer
@@ -6499,6 +6539,7 @@ components:
       - event-v2 alert
       - audit alert
       - ci-pipelines alert
+      - ci-tests alert
       - error-tracking alert
       example: query alert
       type: string
@@ -6517,6 +6558,7 @@ components:
       - EVENT_V2_ALERT
       - AUDIT_ALERT
       - CI_PIPELINES_ALERT
+      - CI_TESTS_ALERT
       - ERROR_TRACKING_ALERT
     MonitorUpdateRequest:
       description: Object describing a monitor update request.
@@ -6641,7 +6683,7 @@ components:
         metadata:
           $ref: '#/components/schemas/MonthlyUsageAttributionMetadata'
         usage:
-          description: Get Usage Summary by tag(s).
+          description: Get usage summary by tag(s).
           items:
             $ref: '#/components/schemas/MonthlyUsageAttributionBody'
           type: array
@@ -8195,7 +8237,7 @@ components:
           example: FREQ=DAILY;INTERVAL=10;COUNT=5
           type: string
         slo_id:
-          description: ID of the SLO that this correction will be applied to.
+          description: ID of the SLO that this correction applies to.
           example: sloId
           type: string
         start:
@@ -8236,7 +8278,7 @@ components:
         category:
           $ref: '#/components/schemas/SLOCorrectionCategory'
         created_at:
-          description: The epoch timestamp of when the correction was created at
+          description: The epoch timestamp of when the correction was created at.
           format: int64
           type: integer
         creator:
@@ -8256,7 +8298,7 @@ components:
           format: int64
           type: integer
         modified_at:
-          description: The epoch timestamp of when the correction was modified at
+          description: The epoch timestamp of when the correction was modified at.
           format: int64
           type: integer
         modifier:
@@ -8265,12 +8307,12 @@ components:
           description: 'The recurrence rules as defined in the iCalendar RFC 5545.
             The supported rules for SLO corrections
 
-            are `FREQ`, `INTERVAL`, `COUNT` and `UNTIL`.'
+            are `FREQ`, `INTERVAL`, `COUNT`, and `UNTIL`.'
           example: FREQ=DAILY;INTERVAL=10;COUNT=5
           nullable: true
           type: string
         slo_id:
-          description: ID of the SLO that this correction will be applied to.
+          description: ID of the SLO that this correction applies to.
           type: string
         start:
           description: Starting time of the correction in epoch seconds.
@@ -8341,7 +8383,7 @@ components:
           description: 'The recurrence rules as defined in the iCalendar RFC 5545.
             The supported rules for SLO corrections
 
-            are `FREQ`, `INTERVAL`, `COUNT` and `UNTIL`.'
+            are `FREQ`, `INTERVAL`, `COUNT`, and `UNTIL`.'
           example: FREQ=DAILY;INTERVAL=10;COUNT=5
           type: string
         start:
@@ -9340,8 +9382,9 @@ components:
             type: string
           type: array
         type:
-          default: gauge
-          description: The type of the metric either `count`, `gauge`, or `rate`.
+          default: ''
+          description: The type of the metric. Valid types are "",`count`, `gauge`,
+            and `rate`.
           example: rate
           type: string
       required:
@@ -9747,6 +9790,59 @@ components:
       type: string
       x-enum-varnames:
       - TRACE_SERVICE
+    SignalArchiveReason:
+      description: Reason why a signal has been archived.
+      enum:
+      - none
+      - false_positive
+      - testing_or_maintenance
+      - other
+      type: string
+      x-enum-varnames:
+      - NONE
+      - FALSE_POSITIVE
+      - TESTING_OR_MAINTENANCE
+      - OTHER
+    SignalAssigneeUpdateRequest:
+      description: Attributes describing an assignee update operation over a security
+        signal.
+      properties:
+        assignee:
+          description: The UUID of the user being assigned. Use empty string to return
+            signal to unassigned.
+          example: 773b045d-ccf8-4808-bd3b-955ef6a8c940
+          type: string
+        version:
+          $ref: '#/components/schemas/Version'
+      required:
+      - assignee
+      type: object
+    SignalStateUpdateRequest:
+      description: Attributes describing the change of state for a given state.
+      properties:
+        archiveComment:
+          description: Optional comment to explain why a signal is being archived.
+          type: string
+        archiveReason:
+          $ref: '#/components/schemas/SignalArchiveReason'
+        state:
+          $ref: '#/components/schemas/SignalTriageState'
+        version:
+          $ref: '#/components/schemas/Version'
+      required:
+      - state
+      type: object
+    SignalTriageState:
+      description: The new triage state of the signal.
+      enum:
+      - open
+      - archived
+      - under_review
+      type: string
+      x-enum-varnames:
+      - OPEN
+      - ARCHIVED
+      - UNDER_REVIEW
     SlackIntegrationChannel:
       description: The Slack channel configuration.
       properties:
@@ -9795,6 +9891,13 @@ components:
       items:
         $ref: '#/components/schemas/SlackIntegrationChannel'
       type: array
+    SuccessfulSignalUpdateResponse:
+      description: Updated signal data following a successfully performed update.
+      properties:
+        status:
+          description: Status of the response.
+          type: string
+      type: object
     SunburstWidgetDefinition:
       description: Sunbursts are spot on to highlight how groups contribute to the
         total of a query.
@@ -10350,6 +10453,8 @@ components:
       - packetsReceived
       - networkHop
       - receivedMessage
+      - grpcHealthcheckStatus
+      - connection
       example: statusCode
       type: string
       x-enum-varnames:
@@ -10368,6 +10473,8 @@ components:
       - PACKETS_RECEIVED
       - NETWORK_HOP
       - RECEIVED_MESSAGE
+      - GRPC_HEALTHCHECK_STATUS
+      - CONNECTION
     SyntheticsBasicAuth:
       description: Object to handle basic authentication when performing the test.
       oneOf:
@@ -10853,6 +10960,50 @@ components:
           format: int64
           type: integer
       type: object
+    SyntheticsBrowserTestRumSettings:
+      description: 'The RUM data collection settings for the Synthetic browser test.
+
+        **Note:** There are 3 ways to format RUM settings:
+
+
+        `{ isEnabled: false }`
+
+        RUM data is not collected.
+
+
+        `{ isEnabled: true }`
+
+        RUM data is collected from the Synthetic test''s default application.
+
+
+        `{ isEnabled: true, applicationId: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+        clientTokenId: 12345 }`
+
+        RUM data is collected using the specified application.'
+      example:
+        applicationId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
+        clientTokenId: 12345
+        isEnabled: true
+      properties:
+        applicationId:
+          description: RUM application ID used to collect RUM data for the browser
+            test.
+          example: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
+          type: string
+        clientTokenId:
+          description: RUM application API key ID used to collect RUM data for the
+            browser test.
+          example: 12345
+          format: int64
+          type: integer
+          x-secret: true
+        isEnabled:
+          description: Determines whether RUM data is collected during test runs.
+          example: true
+          type: boolean
+      required:
+      - isEnabled
+      type: object
     SyntheticsBrowserTestType:
       default: browser
       description: Type of the Synthetic test, `browser`.
@@ -11827,7 +11978,7 @@ components:
     SyntheticsTestDetailsSubType:
       description: 'The subtype of the Synthetic API test, `http`, `ssl`, `tcp`,
 
-        `dns`, `icmp`, `udp`, `websocket` or `multi`.'
+        `dns`, `icmp`, `udp`, `websocket`, `grpc` or `multi`.'
       enum:
       - http
       - ssl
@@ -11837,6 +11988,7 @@ components:
       - icmp
       - udp
       - websocket
+      - grpc
       example: http
       type: string
       x-enum-varnames:
@@ -11848,6 +12000,7 @@ components:
       - ICMP
       - UDP
       - WEBSOCKET
+      - GRPC
     SyntheticsTestDetailsType:
       description: Type of the Synthetic test, either `api` or `browser`.
       enum:
@@ -11874,6 +12027,12 @@ components:
         type: string
       description: Headers to include when performing the test.
       type: object
+    SyntheticsTestMetadata:
+      additionalProperties:
+        description: A single Metadatum.
+        type: string
+      description: Metadata to include when performing the gRPC test.
+      type: object
     SyntheticsTestMonitorStatus:
       description: 'The status of your Synthetic monitor.
 
@@ -11948,6 +12107,8 @@ components:
           $ref: '#/components/schemas/SyntheticsRestrictedRoles'
         retry:
           $ref: '#/components/schemas/SyntheticsTestOptionsRetry'
+        rumSettings:
+          $ref: '#/components/schemas/SyntheticsBrowserTestRumSettings'
         tick_every:
           description: The frequency at which to run the Synthetic test (in seconds).
           format: int64
@@ -12049,6 +12210,8 @@ components:
         message:
           description: Message to send for UDP or WebSocket tests.
           type: string
+        metadata:
+          $ref: '#/components/schemas/SyntheticsTestMetadata'
         method:
           $ref: '#/components/schemas/HTTPMethod'
         noSavingResponseBody:
@@ -12077,6 +12240,9 @@ components:
 
             the same IP address and TCP port number.'
           type: string
+        service:
+          description: gRPC service on which you want to perform the healthcheck.
+          type: string
         shouldTrackHops:
           description: Turns on a traceroute probe to discover all gateways along
             the path to the host destination.
@@ -12907,7 +13073,7 @@ components:
         metadata:
           $ref: '#/components/schemas/UsageAttributionMetadata'
         usage:
-          description: Get Usage Summary by tag(s).
+          description: Get usage summary by tag(s).
           items:
             $ref: '#/components/schemas/UsageAttributionBody'
           type: array
@@ -14171,16 +14337,25 @@ components:
         session_count:
           description: Contains the number of browser RUM Lite Sessions.
           format: int64
+          nullable: true
           type: integer
         session_count_android:
           description: Contains the number of mobile RUM Sessions on Android (data
             available beginning December 1, 2020).
           format: int64
+          nullable: true
           type: integer
         session_count_ios:
           description: Contains the number of mobile RUM Sessions on iOS (data available
             beginning December 1, 2020).
           format: int64
+          nullable: true
+          type: integer
+        session_count_reactnative:
+          description: Contains the number of mobile RUM Sessions on React Native
+            (data available beginning May 1, 2022).
+          format: int64
+          nullable: true
           type: integer
       type: object
     UsageRumSessionsResponse:
@@ -14593,6 +14768,11 @@ components:
             in the current date for all organizations.
           format: int64
           type: integer
+        mobile_rum_session_count_reactnative_sum:
+          description: Shows the sum of all mobile RUM Sessions on React Native over
+            all hours in the current date for all organizations.
+          format: int64
+          type: integer
         mobile_rum_session_count_sum:
           description: Shows the sum of all mobile RUM Sessions over all hours in
             the current date for all organizations
@@ -14912,6 +15092,11 @@ components:
             in the current date for the given org.
           format: int64
           type: integer
+        mobile_rum_session_count_reactnative_sum:
+          description: Shows the sum of all mobile RUM Sessions on React Native over
+            all hours in the current date for the given org.
+          format: int64
+          type: integer
         mobile_rum_session_count_sum:
           description: Shows the sum of all mobile RUM Sessions over all hours in
             the current date for the given org.
@@ -15266,6 +15451,11 @@ components:
             in the current months for all organizations.
           format: int64
           type: integer
+        mobile_rum_session_count_reactnative_agg_sum:
+          description: Shows the sum of all mobile RUM Sessions on React Native over
+            all hours in the current months for all organizations.
+          format: int64
+          type: integer
         mobile_rum_units_agg_sum:
           description: Shows the sum of all mobile RUM units over all hours in the
             current months for all organizations.
@@ -15628,6 +15818,11 @@ components:
         user:
           $ref: '#/components/schemas/User'
       type: object
+    Version:
+      description: Version of the updated signal. If server side version is higher,
+        update will be rejected.
+      format: int64
+      type: integer
     WebhooksIntegration:
       description: Datadog-Webhooks integration.
       properties:
@@ -16547,6 +16742,8 @@ components:
               downtimes.
             monitors_read: View monitors.
             monitors_write: Edit, mute, and delete individual monitors.
+            security_monitoring_signals_read: View Security Signals.
+            security_monitoring_signals_write: Modify Security Signals.
             synthetics_global_variable_read: View, search, and use in tests the list
               of global variables available for Synthetics.
             synthetics_global_variable_write: Create, edit, and delete global variables
@@ -17110,6 +17307,7 @@ paths:
         type: safe
   /api/v1/daily_custom_reports:
     get:
+      deprecated: true
       description: Get daily custom reports.
       operationId: GetDailyCustomReports
       parameters:
@@ -17175,6 +17373,7 @@ paths:
         If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v1/daily_custom_reports/{report_id}:
     get:
+      deprecated: true
       description: Get specified daily custom reports.
       operationId: GetSpecifiedDailyCustomReports
       parameters:
@@ -21386,19 +21585,19 @@ paths:
         Example: `"check".over(tags).last(count).by(group).count_by_status()`
 
 
-        - **`check`** name of the check, for example `datadog.agent.up`
+        - `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.
+        - `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
+        - `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.
+        - `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
@@ -21413,28 +21612,28 @@ paths:
         "string query"'').rollup("count").last("1h")"`
 
 
-        - **`event`**, the event query string:
+        - `event`, the event query string:
 
-        - **`string_query`** free text query to match against event title and text.
+        - `string_query` free text query to match against event title and text.
 
-        - **`sources`** event sources (comma-separated).
+        - `sources` event sources (comma-separated).
 
-        - **`status`** event statuses (comma-separated). Valid options: error, warn,
-        and info.
+        - `status` event statuses (comma-separated). Valid options: error, warn, and
+        info.
 
-        - **`priority`** event priorities (comma-separated). Valid options: low, normal,
+        - `priority` event priorities (comma-separated). Valid options: low, normal,
         all.
 
-        - **`host`** event reporting host (comma-separated).
+        - `host` event reporting host (comma-separated).
 
-        - **`tags`** event tags (comma-separated).
+        - `tags` event tags (comma-separated).
 
-        - **`excluded_tags`** excluded event tags (comma-separated).
+        - `excluded_tags` excluded event tags (comma-separated).
 
-        - **`rollup`** the stats roll-up method. `count` is the only supported method
+        - `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
+        - `last` the timeframe to roll up the counts. Examples: 45m, 4h. Supported
         timeframes: m, h and d. This value should not exceed 48 hours.
 
 
@@ -21449,19 +21648,18 @@ paths:
         operator #`
 
 
-        - **`query`** The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).
+        - `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`.
+        - `rollup_method` The stats roll-up method - supports `count`, `avg` and `cardinality`.
 
-        - **`measure`** For `avg` and cardinality `rollup_method` - specify the measure
+        - `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).
+        - `time_window` #m (between 1 and 2880), #h (between 1 and 48).
 
-        - **`operator`** `<`, `<=`, `>`, `>=`, `==`, or `!=`.
+        - `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.
 
-        - **`#`** an integer or decimal number used to set the threshold.
+        - `#` an integer or decimal number used to set the threshold.
 
 
         **Process Alert Query**
@@ -21471,19 +21669,19 @@ paths:
         #`
 
 
-        - **`search`** free text search string for querying processes.
+        - `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)
+        - `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
+        - `timeframe` the timeframe to roll up the counts. Examples: 10m, 4h. Supported
+        timeframes: s, m, h and d
 
-        - **`operator`** <, <=, >, >=, ==, or !=
+        - `operator` <, <=, >, >=, ==, or !=
 
-        - **`#`** an integer or decimal number used to set the threshold
+        - `#` an integer or decimal number used to set the threshold
 
 
         **Logs Alert Query**
@@ -21493,22 +21691,21 @@ paths:
         operator #`
 
 
-        - **`query`** The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).
+        - `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.
+        - `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`.
+        - `rollup_method` The stats roll-up method - supports `count`, `avg` and `cardinality`.
 
-        - **`measure`** For `avg` and cardinality `rollup_method` - specify the measure
+        - `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).
+        - `time_window` #m (between 1 and 2880), #h (between 1 and 48).
 
-        - **`operator`** `<`, `<=`, `>`, `>=`, `==`, or `!=`.
+        - `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.
 
-        - **`#`** an integer or decimal number used to set the threshold.
+        - `#` an integer or decimal number used to set the threshold.
 
 
         **Composite Query**
@@ -21518,16 +21715,16 @@ paths:
         monitors
 
 
-        * **`name`** [*required*, *default* = **dynamic, based on query**]: The name
-        of the alert.
+        * `name` [*required*, *default* = **dynamic, based on query**]: The name of
+        the alert.
 
-        * **`message`** [*required*, *default* = **dynamic, based on query**]: A message
+        * `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
+        * `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
@@ -21543,13 +21740,13 @@ paths:
         Example: `error_budget("slo_id").over("time_window") operator #`
 
 
-        - **`slo_id`**: The alphanumeric SLO ID of the SLO you are configuring the
-        alert for.
+        - `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`.
+        - `time_window`: The time window of the SLO target you wish to alert on. Valid
+        options: `7d`, `30d`, `90d`.
 
-        - **`operator`**: `>=` or `>`
+        - `operator`: `>=` or `>`
 
 
         **Audit Alert Query**
@@ -21559,19 +21756,18 @@ paths:
         operator #`
 
 
-        - **`query`** The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).
+        - `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`.
+        - `rollup_method` The stats roll-up method - supports `count`, `avg` and `cardinality`.
 
-        - **`measure`** For `avg` and cardinality `rollup_method` - specify the measure
+        - `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).
+        - `time_window` #m (between 1 and 2880), #h (between 1 and 48).
 
-        - **`operator`** `<`, `<=`, `>`, `>=`, `==`, or `!=`.
+        - `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.
 
-        - **`#`** an integer or decimal number used to set the threshold.
+        - `#` 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
@@ -21585,24 +21781,50 @@ paths:
         operator #`
 
 
-        - **`query`** The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).
+        - `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`.
+        - `rollup_method` The stats roll-up method - supports `count`, `avg`, and
+        `cardinality`.
 
-        - **`measure`** For `avg` and cardinality `rollup_method` - specify the measure
+        - `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).
+        - `time_window` #m (between 1 and 2880), #h (between 1 and 48).
 
-        - **`operator`** `<`, `<=`, `>`, `>=`, `==`, or `!=`.
+        - `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.
 
-        - **`#`** an integer or decimal number used to set the threshold.
+        - `#` an integer or decimal number used to set the threshold.
 
 
         **NOTE** CI Pipeline monitors are in alpha on US1, EU, US3 and US5.
 
 
+        **CI Tests Alert Query**
+
+
+        Example: `ci-tests(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** CI Test monitors are available only in closed beta on US1, EU, US3
+        and US5.
+
+
         **Error Tracking Alert Query**
 
 
@@ -21613,19 +21835,19 @@ paths:
         measure]).last(time_window) operator #`
 
 
-        - **`query`** The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).
+        - `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`.
+        - `rollup_method` The stats roll-up method - supports `count`, `avg`, and
+        `cardinality`.
 
-        - **`measure`** For `avg` and cardinality `rollup_method` - specify the measure
+        - `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).
+        - `time_window` #m (between 1 and 2880), #h (between 1 and 48).
 
-        - **`operator`** `<`, `<=`, `>`, `>=`, `==`, or `!=`.
+        - `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.
 
-        - **`#`** an integer or decimal number used to set the threshold.'
+        - `#` an integer or decimal number used to set the threshold.'
       operationId: CreateMonitor
       requestBody:
         content:
@@ -22257,6 +22479,7 @@ paths:
         type: idempotent
   /api/v1/monthly_custom_reports:
     get:
+      deprecated: true
       description: Get monthly custom reports.
       operationId: GetMonthlyCustomReports
       parameters:
@@ -22322,6 +22545,7 @@ paths:
         If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v1/monthly_custom_reports/{report_id}:
     get:
+      deprecated: true
       description: Get specified monthly custom reports.
       operationId: GetSpecifiedMonthlyCustomReports
       parameters:
@@ -23088,6 +23312,161 @@ paths:
       x-menu-order: 4
       x-undo:
         type: safe
+  /api/v1/security_analytics/signals/{signal_id}/add_to_incident:
+    patch:
+      description: Add a security signal to an incident. This makes it possible to
+        search for signals by incident within the signal explorer and to view the
+        signals on the incident timeline.
+      operationId: AddSecurityMonitoringSignalToIncident
+      parameters:
+      - $ref: '#/components/parameters/SignalID'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AddSignalToIncidentRequest'
+        description: Attributes describing the signal update.
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/SuccessfulSignalUpdateResponse'
+          description: OK
+        '400':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Bad Request
+        '403':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Forbidden
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Not Found
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - AuthZ:
+        - security_monitoring_signals_write
+        apiKeyAuth: []
+        appKeyAuth: []
+      summary: Add a security signal to an incident
+      tags:
+      - Security Monitoring
+      x-codegen-request-body-name: body
+      x-undo:
+        type: idempotent
+  /api/v1/security_analytics/signals/{signal_id}/assignee:
+    patch:
+      description: Modify the triage assignee of a security signal.
+      operationId: EditSecurityMonitoringSignalAssignee
+      parameters:
+      - $ref: '#/components/parameters/SignalID'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/SignalAssigneeUpdateRequest'
+        description: Attributes describing the signal update.
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/SuccessfulSignalUpdateResponse'
+          description: OK
+        '400':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Bad Request
+        '403':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Forbidden
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Not Found
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - AuthZ:
+        - security_monitoring_signals_write
+        apiKeyAuth: []
+        appKeyAuth: []
+      summary: Modify the triage assignee of a security signal
+      tags:
+      - Security Monitoring
+      x-codegen-request-body-name: body
+      x-undo:
+        type: idempotent
+  /api/v1/security_analytics/signals/{signal_id}/state:
+    patch:
+      description: Change the triage state of a security signal.
+      operationId: EditSecurityMonitoringSignalState
+      parameters:
+      - $ref: '#/components/parameters/SignalID'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/SignalStateUpdateRequest'
+        description: Attributes describing the signal update.
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/SuccessfulSignalUpdateResponse'
+          description: OK
+        '400':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Bad Request
+        '403':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Forbidden
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Not Found
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - AuthZ:
+        - security_monitoring_signals_write
+        apiKeyAuth: []
+        appKeyAuth: []
+      summary: Change the triage state of a security signal
+      tags:
+      - Security Monitoring
+      x-codegen-request-body-name: body
+      x-undo:
+        type: idempotent
   /api/v1/series:
     post:
       description: "The metrics end-point allows you to post time-series data that
@@ -23095,7 +23474,7 @@ paths:
         3.2 megabytes (3200000 bytes). Compressed payloads must have a decompressed
         size of less than 62 megabytes (62914560 bytes).\n\nIf you\u2019re submitting
         metrics directly to the Datadog API without using DogStatsD, expect:\n\n-
-        64 bits for the timestamp\n- 32 bits for the value\n- 40 bytes for the metric
+        64 bits for the timestamp\n- 64 bits for the value\n- 40 bytes for the metric
         names\n- 50 bytes for the timeseries\n- The full payload is approximately
         100 bytes. However, with the DogStatsD API,\ncompression is applied, which
         reduces the payload size."
@@ -23428,9 +23807,6 @@ paths:
       x-menu-order: 2
       x-undo:
         type: safe
-      x-unstable: '**Note**: This endpoint is in public beta.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
     post:
       description: Create an SLO Correction.
       operationId: CreateSLOCorrection
@@ -23489,9 +23865,6 @@ paths:
         - name: slo_correction_id
           source: data.id
         type: unsafe
-      x-unstable: '**Note**: This endpoint is in public beta.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v1/slo/correction/{slo_correction_id}:
     delete:
       description: Permanently delete the specified SLO correction object.
@@ -23526,9 +23899,6 @@ paths:
       x-menu-order: 5
       x-undo:
         type: idempotent
-      x-unstable: '**Note**: This endpoint is in public beta.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
     get:
       description: Get an SLO correction.
       operationId: GetSLOCorrection
@@ -23566,11 +23936,8 @@ paths:
       x-menu-order: 3
       x-undo:
         type: safe
-      x-unstable: '**Note**: This endpoint is in public beta.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
     patch:
-      description: Update the specified SLO correction object object.
+      description: Update the specified SLO correction object.
       operationId: UpdateSLOCorrection
       parameters:
       - description: The ID of the SLO correction object.
@@ -23620,9 +23987,6 @@ paths:
       x-menu-order: 4
       x-undo:
         type: idempotent
-      x-unstable: '**Note**: This endpoint is in public beta.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v1/slo/{slo_id}:
     delete:
       description: 'Permanently delete the specified service level objective object.
@@ -23826,9 +24190,6 @@ paths:
       x-menu-order: 6
       x-undo:
         type: safe
-      x-unstable: '**Note**: This endpoint is in public beta.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v1/slo/{slo_id}/history:
     get:
       description: "Get a specific SLO\u2019s history, regardless of its SLO type.\n\nThe
@@ -23954,7 +24315,7 @@ paths:
       summary: Get details of batch
       tags:
       - Synthetics
-      x-menu-order: 27
+      x-menu-order: 15
       x-undo:
         type: safe
   /api/v1/synthetics/locations:
@@ -23980,7 +24341,7 @@ paths:
       summary: Get all locations (public and private)
       tags:
       - Synthetics
-      x-menu-order: 24
+      x-menu-order: 25
       x-undo:
         type: safe
   /api/v1/synthetics/private-locations:
@@ -24024,7 +24385,7 @@ paths:
       tags:
       - Synthetics
       x-codegen-request-body-name: body
-      x-menu-order: 21
+      x-menu-order: 22
       x-undo:
         operationId: DeletePrivateLocation
         parameters:
@@ -24063,7 +24424,7 @@ paths:
       summary: Delete a private location
       tags:
       - Synthetics
-      x-menu-order: 25
+      x-menu-order: 26
       x-undo:
         type: idempotent
     get:
@@ -24101,7 +24462,7 @@ paths:
       summary: Get a private location
       tags:
       - Synthetics
-      x-menu-order: 22
+      x-menu-order: 23
       x-undo:
         type: safe
     put:
@@ -24147,7 +24508,7 @@ paths:
       tags:
       - Synthetics
       x-codegen-request-body-name: body
-      x-menu-order: 23
+      x-menu-order: 24
       x-undo:
         type: idempotent
   /api/v1/synthetics/tests:
@@ -24824,7 +25185,7 @@ paths:
       tags:
       - Synthetics
       x-codegen-request-body-name: body
-      x-menu-order: 15
+      x-menu-order: 16
       x-undo:
         type: idempotent
   /api/v1/synthetics/tests/trigger:
@@ -24952,7 +25313,7 @@ paths:
       summary: Get a test configuration
       tags:
       - Synthetics
-      x-menu-order: 26
+      x-menu-order: 27
       x-undo:
         type: safe
   /api/v1/synthetics/tests/{public_id}/results:
@@ -25161,7 +25522,7 @@ paths:
       summary: Get all global variables
       tags:
       - Synthetics
-      x-menu-order: 16
+      x-menu-order: 17
       x-undo:
         type: safe
     post:
@@ -25204,7 +25565,7 @@ paths:
       tags:
       - Synthetics
       x-codegen-request-body-name: body
-      x-menu-order: 17
+      x-menu-order: 18
       x-undo:
         operationId: DeleteGlobalVariable
         parameters:
@@ -25253,7 +25614,7 @@ paths:
       summary: Delete a global variable
       tags:
       - Synthetics
-      x-menu-order: 20
+      x-menu-order: 21
       x-undo:
         type: idempotent
     get:
@@ -25345,7 +25706,7 @@ paths:
       tags:
       - Synthetics
       x-codegen-request-body-name: body
-      x-menu-order: 18
+      x-menu-order: 20
       x-undo:
         type: idempotent
   /api/v1/tags/hosts:
@@ -25660,7 +26021,8 @@ paths:
         type: safe
   /api/v1/usage/attribution:
     get:
-      description: Get Usage Attribution.
+      deprecated: true
+      description: Get usage attribution.
       operationId: GetUsageAttribution
       parameters:
       - description: 'Datetime in ISO-8601 format, UTC, precise to month: `[YYYY-MM]`
@@ -25743,7 +26105,7 @@ paths:
         appKeyAuth: []
       - AuthZ:
         - usage_read
-      summary: Get Usage Attribution
+      summary: Get usage attribution
       tags:
       - Usage Metering
       x-menu-order: 29
@@ -25919,8 +26281,7 @@ paths:
         type: safe
   /api/v1/usage/ci-app:
     get:
-      description: Get hourly usage for CI Visibility (Tests, Pipeline, Combo, and
-        Spans).
+      description: Get hourly usage for CI Visibility (Tests, Pipeline, and Spans).
       operationId: GetUsageCIApp
       parameters:
       - description: 'Datetime in ISO-8601 format, UTC, precise to hour: `[YYYY-MM-DDThh]`
@@ -26270,7 +26631,7 @@ paths:
         type: safe
   /api/v1/usage/hourly-attribution:
     get:
-      description: "Get Hourly Usage Attribution.\n\nThis API endpoint is paginated.
+      description: "Get hourly usage attribution.\n\nThis API endpoint is paginated.
         To make sure you receive all records, check if the value of `next_record_id`
         is\nset in the response. If it is, make another request and pass `next_record_id`
         as a parameter.\nPseudo code example:\n\n```\nresponse := GetHourlyUsageAttribution(start_month)\ncursor
@@ -26345,7 +26706,7 @@ paths:
         appKeyAuth: []
       - AuthZ:
         - usage_read
-      summary: Get Hourly Usage Attribution
+      summary: Get hourly usage attribution
       tags:
       - Usage Metering
       x-menu-order: 30
@@ -26770,7 +27131,7 @@ paths:
         type: safe
   /api/v1/usage/monthly-attribution:
     get:
-      description: "Get Monthly Usage Attribution.\n\nThis API endpoint is paginated.
+      description: "Get monthly usage attribution.\n\nThis API endpoint is paginated.
         To make sure you receive all records, check if the value of `next_record_id`
         is\nset in the response. If it is, make another request and pass `next_record_id`
         as a parameter.\nPseudo code example:\n\n```\nresponse := GetMonthlyUsageAttribution(start_month)\ncursor
@@ -26858,7 +27219,7 @@ paths:
         appKeyAuth: []
       - AuthZ:
         - usage_read
-      summary: Get Monthly Usage Attribution
+      summary: Get monthly usage attribution
       tags:
       - Usage Metering
       x-given:
@@ -28342,6 +28703,10 @@ tags:
   externalDocs:
     url: https://docs.datadoghq.com/api/?lang=bash#integration-pagerduty
   name: PagerDuty Integration
+- description: 'Detection rules for generating signals and listing of generated
+
+    signals.'
+  name: Security Monitoring
 - description: 'The service check endpoint allows you to post check statuses for use
     with monitors.