datadog_api_client 1.1.0 → 1.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 966d9a971a8b59a89c3146c840524dfa0681c78a89c79010cc6c49ac432c051e
-  data.tar.gz: c080a88ce308169979c2341d257ae48bcba252ca6c1d6d6f057e0c24d902d0ab
+  metadata.gz: 16a8c0052c39f7c2e4839e49adc639faa2ec6fbcbe7181fd29cf9e0c50eca672
+  data.tar.gz: fcb145b61dff944737763e2ad718645cc60cf7516f62469e865392de1f86b6ea
 SHA512:
-  metadata.gz: 917343d9d3726e7d10ee74e9927130e1b3180aba3f2c2221e8da966a80ec765dbf397a482381e5dca8963230777fc612013d4ee2159b272d001602e65511f0fc
-  data.tar.gz: c4fb4d110cc1481ad2324a096cedb1eb7e0668a7da0641efaf3a69449416ea883d4fa74c0043c61fa96398f8229c3b40100762caa961b892a416cae0fb9f036b
+  metadata.gz: 9db95256744c03eb24972bb4615899430a0de5501b9a76824c93faf86dabd8456328beae4acc76f83d6089d0cc59a831016962be02d108e23ca9722996358fae
+  data.tar.gz: c69015b38aacc8879bb943bc0ac63ce284a47d6e19b2babe949d1af45d0db5128f46101e4815a5aa3b11ddc1434f200a33b279edae1aeed1cbbdb8e9fedd4443

data/.apigentools-info

@@ -3,14 +3,14 @@
     "info_version": "2",
     "spec_versions": {
         "v1": {
-            "apigentools_version": "1.4.1.dev8",
-            "regenerated": "2021-06-07 11:36:45.335016",
-            "spec_repo_commit": "cb48df5"
+            "apigentools_version": "1.4.1.dev11",
+            "regenerated": "2021-07-14 09:07:16.506440",
+            "spec_repo_commit": "f0a4221"
         },
         "v2": {
-            "apigentools_version": "1.4.1.dev8",
-            "regenerated": "2021-06-07 11:37:41.263441",
-            "spec_repo_commit": "cb48df5"
+            "apigentools_version": "1.4.1.dev11",
+            "regenerated": "2021-07-14 09:08:07.251643",
+            "spec_repo_commit": "f0a4221"
         }
     }
 }

data/.generator/templates/api_doc.mustache

@@ -19,9 +19,7 @@ All URIs are relative to *{{basePath}}*
 
 > {{#returnType}}{{#returnTypeIsPrimitive}}{{returnType}}{{/returnTypeIsPrimitive}}{{^returnTypeIsPrimitive}}<{{{returnType}}}>{{/returnTypeIsPrimitive}} {{/returnType}}{{operationId}}{{#hasParams}}({{#requiredParams}}{{{paramName}}}{{^-last}}, {{/-last}}{{/requiredParams}}{{#optionalParams}}{{#-last}}{{#hasRequiredParams}}, {{/hasRequiredParams}}opts{{/-last}}{{/optionalParams}}){{/hasParams}}
 
-{{{summary}}}{{#notes}}
-
-{{{notes}}}{{/notes}}
+{{#notes}}{{{unescapedNotes}}}{{/notes}}
 
 ### Examples
 

data/.generator/templates/base_object.mustache

@@ -55,6 +55,9 @@
       when :Object
         # generic object (usually a Hash), return directly
         value
+      when :Array
+        # generic array, return directly
+        value
       when /\AArray<(?<inner_type>.+)>\z/
         inner_type = Regexp.last_match[:inner_type]
         value.map { |v| _deserialize(inner_type, v) }

data/.github/workflows/approved_status.yml

@@ -0,0 +1,35 @@
+name: Send PR Approval Status
+
+on:
+  pull_request:
+    branches:
+      - master
+    types: ["review_requested", "synchronize", "opened", "reopened"]
+  pull_request_review:
+    types:
+      - submitted
+      - dismissed
+
+jobs:
+  send_status:
+    runs-on: ubuntu-latest
+    if: >
+      github.event.pull_request.draft == false &&
+      !contains(github.event.pull_request.labels.*.name, 'ci/skip') &&
+      !contains(github.event.pull_request.head.ref, 'datadog-api-spec/test/') &&
+      contains(github.event.pull_request.head.ref, 'datadog-api-spec/generated/')
+    steps:
+      - name: Get GitHub App token
+        id: get_token
+        uses: tibdex/github-app-token@v1.3.0
+        with:
+          app_id: ${{ secrets.PIPELINE_GITHUB_APP_ID }}
+          private_key: ${{ secrets.PIPELINE_GITHUB_APP_PRIVATE_KEY }}
+          repository: DataDog/datadog-api-spec
+      - name: Checkout code
+        uses: actions/checkout@v2
+      - name: Post PR review status check
+        uses: DataDog/github-actions/post-review-status@v1.0.0
+        with:
+          github-token: ${{ steps.get_token.outputs.token }}
+          repo: datadog-api-spec

data/.github/workflows/test.yml

@@ -14,30 +14,30 @@ jobs:
     runs-on: ubuntu-latest
     if: false == startsWith(github.event.pull_request.head.ref, 'datadog-api-spec/generated/') && !contains(github.event.pull_request.labels.*.name, 'ci/skip/pre-commit')
     steps:
-    - uses: actions/checkout@v1
-    - uses: actions/setup-python@v1
-    - name: Install pre-commit
-      run: python -m pip install pre-commit
-    - name: set PY
-      run: echo "PY=$(python -c 'import hashlib, sys;print(hashlib.sha256(sys.version.encode()+sys.executable.encode()).hexdigest())')" >> $GITHUB_ENV
-    - uses: actions/cache@v1
-      with:
-        path: ~/.cache/pre-commit
-        key: pre-commit|${{ env.PY }}|${{ hashFiles('.pre-commit-config.yaml') }}
-    - name: Run pre-commit
-      run: pre-commit run --all-files --source ${{ github.event.pull_request.base.sha }} --origin ${{ github.event.pull_request.head.sha }} --show-diff-on-failure --color=always
+      - uses: actions/checkout@v1
+      - uses: actions/setup-python@v1
+      - name: Install pre-commit
+        run: python -m pip install pre-commit
+      - name: set PY
+        run: echo "PY=$(python -c 'import hashlib, sys;print(hashlib.sha256(sys.version.encode()+sys.executable.encode()).hexdigest())')" >> $GITHUB_ENV
+      - uses: actions/cache@v1
+        with:
+          path: ~/.cache/pre-commit
+          key: pre-commit|${{ env.PY }}|${{ hashFiles('.pre-commit-config.yaml') }}
+      - name: Run pre-commit
+        run: pre-commit run --from-ref ${{ github.event.pull_request.base.sha }} --to-ref ${{ github.event.pull_request.head.sha }} --show-diff-on-failure --color=always
 
   test:
     strategy:
       matrix:
-        ruby-version: ['2.5', '2.6', '2.7']
+        ruby-version: ["2.5", "2.6", "2.7"]
         platform: [ubuntu-latest, macos-latest] # , windows-latest]
         # test only latest version on macos and windows
         exclude:
           - platform: macos-latest
-            ruby-version: '2.5'
+            ruby-version: "2.5"
           - platform: macos-latest
-            ruby-version: '2.6'
+            ruby-version: "2.6"
           # - platform: windows-latest
           #   ruby-version: '2.5'
           # - platform: windows-latest
@@ -45,12 +45,35 @@ jobs:
     runs-on: ${{ matrix.platform }}
     if: github.event.pull_request.draft == false && !contains(github.event.pull_request.labels.*.name, 'ci/skip') && !contains(github.event.pull_request.head.ref, 'datadog-api-spec/test/')
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby ${{ matrix.ruby-version }}
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby-version }}
-        bundler-cache: true
-    - name: Test
-      run: ./run-tests.sh
-      shell: bash
+      - uses: actions/checkout@v2
+      - name: Set up Ruby ${{ matrix.ruby-version }}
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby-version }}
+          bundler-cache: true
+      - name: Test
+        run: ./run-tests.sh
+        shell: bash
+
+  report:
+    runs-on: ubuntu-latest
+    if: always() && github.event_name == 'pull_request' && contains(github.event.pull_request.head.ref, 'datadog-api-spec/generated/')
+    needs: test
+    steps:
+      - name: Get GitHub App token
+        if: github.event_name == 'pull_request'
+        id: get_token
+        uses: tibdex/github-app-token@v1.3.0
+        with:
+          app_id: ${{ secrets.PIPELINE_GITHUB_APP_ID }}
+          private_key: ${{ secrets.PIPELINE_GITHUB_APP_PRIVATE_KEY }}
+          repository: DataDog/datadog-api-spec
+      - name: Checkout code
+        uses: actions/checkout@v2
+      - name: Post status check
+        uses: DataDog/github-actions/post-status-check@v1.0.0
+        with:
+          github-token: ${{ steps.get_token.outputs.token }}
+          repo: datadog-api-spec
+          status: ${{ needs.test.result }}
+          context: unit

data/.github/workflows/test_integration.yml

@@ -31,57 +31,57 @@ jobs:
           DD_HOSTNAME: "none"
           DD_INSIDE_CI: "true"
     steps:
-    - name: Get GitHub App token
-      if: github.event_name == 'pull_request'
-      id: get_token
-      uses: tibdex/github-app-token@v1.3.0
-      with:
-        app_id: ${{ secrets.PIPELINE_GITHUB_APP_ID }}
-        private_key: ${{ secrets.PIPELINE_GITHUB_APP_PRIVATE_KEY }}
-        repository: DataDog/datadog-api-spec
-    - name: Checkout code
-      uses: actions/checkout@v2
-    - name: Post pending status check
-      if: github.event_name == 'pull_request'
-      uses: actions/github-script@v4.0.2
-      with:
-        github-token: ${{ steps.get_token.outputs.token }}
-        script: |
-          const script = require('.github/workflows/scripts/test_integration.js')
-          await script.post_status_check(github, context, "pending")
-    - name: Set up Ruby 2.7
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.7
-        bundler-cache: true
-    - name: Install deps
-      run: bundle install
-    - name: Run integration tests
-      run: ./run-tests.sh
-      shell: bash
-      env:
-        CI: "true"
-        DD_AGENT_HOST: localhost
-        DD_ENV: prod
-        DD_SERVICE: datadog-api-client-ruby
-        DD_TAGS: "team:integration-tools-and-libraries"
-        DD_TEST_CLIENT_API_KEY: ${{ secrets.DD_CLIENT_API_KEY }}
-        DD_TEST_CLIENT_APP_KEY: ${{ secrets.DD_CLIENT_APP_KEY }}
-        DD_TRACE_ANALYTICS_ENABLED: "true"
-        RECORD: "none"
-    - name: Post failure status check
-      if: failure() && github.event_name == 'pull_request'
-      uses: actions/github-script@v4.0.2
-      with:
-        github-token: ${{ steps.get_token.outputs.token }}
-        script: |
-          const script = require('./.github/workflows/scripts/test_integration.js')
-          await script.post_status_check(github, context, "failure")
-    - name: Post success status check
-      if: "!failure() && github.event_name == 'pull_request'"
-      uses: actions/github-script@v4.0.2
-      with:
-        github-token: ${{ steps.get_token.outputs.token }}
-        script: |
-          const script = require('./.github/workflows/scripts/test_integration.js')
-          await script.post_status_check(github, context, "success")
+      - name: Get GitHub App token
+        if: github.event_name == 'pull_request'
+        id: get_token
+        uses: tibdex/github-app-token@v1.3.0
+        with:
+          app_id: ${{ secrets.PIPELINE_GITHUB_APP_ID }}
+          private_key: ${{ secrets.PIPELINE_GITHUB_APP_PRIVATE_KEY }}
+          repository: DataDog/datadog-api-spec
+      - name: Checkout code
+        uses: actions/checkout@v2
+      - name: Post pending status check
+        if: github.event_name == 'pull_request' && contains(github.event.pull_request.head.ref, 'datadog-api-spec/generated/')
+        uses: DataDog/github-actions/post-status-check@v1.0.0
+        with:
+          github-token: ${{ steps.get_token.outputs.token }}
+          repo: datadog-api-spec
+          status: pending
+          context: integration
+      - name: Set up Ruby 2.7
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.7
+          bundler-cache: true
+      - name: Install deps
+        run: bundle install
+      - name: Run integration tests
+        run: ./run-tests.sh
+        shell: bash
+        env:
+          CI: "true"
+          DD_AGENT_HOST: localhost
+          DD_ENV: prod
+          DD_SERVICE: datadog-api-client-ruby
+          DD_TAGS: "team:integration-tools-and-libraries"
+          DD_TEST_CLIENT_API_KEY: ${{ secrets.DD_CLIENT_API_KEY }}
+          DD_TEST_CLIENT_APP_KEY: ${{ secrets.DD_CLIENT_APP_KEY }}
+          DD_TRACE_ANALYTICS_ENABLED: "true"
+          RECORD: "none"
+      - name: Post failure status check
+        if: failure() && github.event_name == 'pull_request' && contains(github.event.pull_request.head.ref, 'datadog-api-spec/generated/')
+        uses: DataDog/github-actions/post-status-check@v1.0.0
+        with:
+          github-token: ${{ steps.get_token.outputs.token }}
+          repo: datadog-api-spec
+          status: failure
+          context: integration
+      - name: Post success status check
+        if: "!failure() && github.event_name == 'pull_request' && contains(github.event.pull_request.head.ref, 'datadog-api-spec/generated/')"
+        uses: DataDog/github-actions/post-status-check@v1.0.0
+        with:
+          github-token: ${{ steps.get_token.outputs.token }}
+          repo: datadog-api-spec
+          status: success
+          context: integration

data/.openapi-generator/FILES

@@ -266,7 +266,6 @@ docs/SecurityFilterAttributes.md
 docs/SecurityFilterCreateAttributes.md
 docs/SecurityFilterCreateData.md
 docs/SecurityFilterCreateRequest.md
-docs/SecurityFilterDeleteResponse.md
 docs/SecurityFilterExclusionFilter.md
 docs/SecurityFilterExclusionFilterResponse.md
 docs/SecurityFilterFilteredDataType.md
@@ -605,7 +604,6 @@ lib/datadog_api_client/v2/models/security_filter_attributes.rb
 lib/datadog_api_client/v2/models/security_filter_create_attributes.rb
 lib/datadog_api_client/v2/models/security_filter_create_data.rb
 lib/datadog_api_client/v2/models/security_filter_create_request.rb
-lib/datadog_api_client/v2/models/security_filter_delete_response.rb
 lib/datadog_api_client/v2/models/security_filter_exclusion_filter.rb
 lib/datadog_api_client/v2/models/security_filter_exclusion_filter_response.rb
 lib/datadog_api_client/v2/models/security_filter_filtered_data_type.rb
@@ -939,7 +937,6 @@ spec/models/security_filter_attributes_spec.rb
 spec/models/security_filter_create_attributes_spec.rb
 spec/models/security_filter_create_data_spec.rb
 spec/models/security_filter_create_request_spec.rb
-spec/models/security_filter_delete_response_spec.rb
 spec/models/security_filter_exclusion_filter_response_spec.rb
 spec/models/security_filter_exclusion_filter_spec.rb
 spec/models/security_filter_filtered_data_type_spec.rb

data/CHANGELOG.md

@@ -1,5 +1,25 @@
 # CHANGELOG
 
+## v1.2.0 / 2021-07-15
+
+* [Added] Add `allow_insecure` option for multistep steps in Synthetics. See [#426](https://github.com/DataDog/datadog-api-client-ruby/pull/426).
+* [Added] Add support for ` GET /api/v2/application_keys/{app_key_id}`. See [#416](https://github.com/DataDog/datadog-api-client-ruby/pull/416).
+* [Added] Add `meta` property with pagination info to SLOCorrectionList endpoint response. See [#414](https://github.com/DataDog/datadog-api-client-ruby/pull/414).
+* [Added] Add support for `treemap` widget. See [#409](https://github.com/DataDog/datadog-api-client-ruby/pull/409).
+* [Added] Add missing properties `query_index` and `tag_set` to `MetricsQueryMetadata`. See [#385](https://github.com/DataDog/datadog-api-client-ruby/pull/385).
+* [Added] Add missing fields `hasExtendedTitle`, `type`, `version` and `updateAuthorId` for Security Monitoring Rule endpoints. See [#398](https://github.com/DataDog/datadog-api-client-ruby/pull/398).
+* [Added] Dashboard RBAC role support. See [#395](https://github.com/DataDog/datadog-api-client-ruby/pull/395).
+* [Added] Add missing fields in usage billable summary keys. See [#393](https://github.com/DataDog/datadog-api-client-ruby/pull/393).
+* [Added] [Synthetics] Add monitor name and priority options. See [#388](https://github.com/DataDog/datadog-api-client-ruby/pull/388).
+* [Fixed] Fix `status` property name for browser error status in Synthetics. See [#428](https://github.com/DataDog/datadog-api-client-ruby/pull/428).
+* [Fixed] Remove US only constraint for AWS tag filtering. See [#405](https://github.com/DataDog/datadog-api-client-ruby/pull/405).
+* [Fixed] Add BDD tests to synthetics. See [#404](https://github.com/DataDog/datadog-api-client-ruby/pull/404).
+* [Fixed] Handle null in query metrics unit. See [#401](https://github.com/DataDog/datadog-api-client-ruby/pull/401).
+* [Changed] Add separate schema for deleting AWS account. See [#425](https://github.com/DataDog/datadog-api-client-ruby/pull/425).
+* [Changed] Specify format of `report_id` parameter. See [#422](https://github.com/DataDog/datadog-api-client-ruby/pull/422).
+* [Changed] Remove Synthetics tick interval enum. See [#403](https://github.com/DataDog/datadog-api-client-ruby/pull/403).
+* [Removed] Remove deprecated endpoints `/api/v1/usage/traces` and `/api/v1/usage/tracing-without-limits`. See [#430](https://github.com/DataDog/datadog-api-client-ruby/pull/430).
+
 ## 1.1.0 / 2021-06-08
 
 * [Added] Add CWS to usage metering endpoint. See [#376](https://github.com/DataDog/datadog-api-client-ruby/pull/376).

data/data/v1/openapi.yaml

@@ -131,6 +131,22 @@ components:
           description: AWS external_id.
           type: string
       type: object
+    AWSAccountDeleteRequest:
+      description: List of AWS accounts to delete.
+      properties:
+        access_key_id:
+          description: Your AWS access key ID. Only required if your AWS account is
+            a GovCloud or China account.
+          type: string
+        account_id:
+          description: Your AWS Account ID without dashes.
+          example: '1234567'
+          type: string
+        role_name:
+          description: Your Datadog role delegation name.
+          example: DatadogAWSIntegrationRole
+          type: string
+      type: object
     AWSAccountListResponse:
       description: List of enabled AWS accounts.
       properties:
@@ -652,9 +668,9 @@ components:
             $ref: '#/components/schemas/WidgetCustomLink'
           type: array
         requests:
-          description: "Array of one request object to display in the widget.\n\n\
-            See the dedicated [Request JSON schema documentation](https://docs.datadoghq.com/dashboards/graphing_json/request_json)\n\
-            \ to learn how to build the `REQUEST_SCHEMA`."
+          description: "Array of one request object to display in the widget.\n\nSee
+            the dedicated [Request JSON schema documentation](https://docs.datadoghq.com/dashboards/graphing_json/request_json)\n
+            to learn how to build the `REQUEST_SCHEMA`."
           example:
           - q/apm_query/log_query: <METRIC_1>{<SCOPE_1>}
           items:
@@ -847,9 +863,9 @@ components:
       readOnly: true
       type: object
     Dashboard:
-      description: "A dashboard is Datadog\u2019s tool for visually tracking, analyzing,\
-        \ and displaying\nkey performance metrics, which enable you to monitor the\
-        \ health of your infrastructure."
+      description: "A dashboard is Datadog\u2019s tool for visually tracking, analyzing,
+        and displaying\nkey performance metrics, which enable you to monitor the health
+        of your infrastructure."
       properties:
         author_handle:
           description: Identifier of the dashboard author.
@@ -893,6 +909,15 @@ components:
           type: array
         reflow_type:
           $ref: '#/components/schemas/DashboardReflowType'
+        restricted_roles:
+          description: A list of role identifiers. Only the author and users associated
+            with at least one of these roles can edit this dashboard. Overrides the
+            `is_read_only` property if both are present. **This feature is currently
+            in beta.**
+          items:
+            description: A role UUID.
+            type: string
+          type: array
         template_variable_presets:
           description: Array of template variables saved views.
           items:
@@ -1114,9 +1139,9 @@ components:
       readOnly: true
       type: object
     DistributionWidgetDefinition:
-      description: "The Distribution visualization is another way of showing metrics\n\
-        aggregated across one or several tags, such as hosts.\nUnlike the heat map,\
-        \ a distribution graph\u2019s x-axis is quantity rather than time."
+      description: "The Distribution visualization is another way of showing metrics\naggregated
+        across one or several tags, such as hosts.\nUnlike the heat map, a distribution
+        graph\u2019s x-axis is quantity rather than time."
       properties:
         legend_size:
           deprecated: true
@@ -1129,9 +1154,9 @@ components:
             $ref: '#/components/schemas/WidgetMarker'
           type: array
         requests:
-          description: "Array of one request object to display in the widget.\n\n\
-            See the dedicated [Request JSON schema documentation](https://docs.datadoghq.com/dashboards/graphing_json/request_json)\n\
-            \ to learn how to build the `REQUEST_SCHEMA`."
+          description: "Array of one request object to display in the widget.\n\nSee
+            the dedicated [Request JSON schema documentation](https://docs.datadoghq.com/dashboards/graphing_json/request_json)\n
+            to learn how to build the `REQUEST_SCHEMA`."
           example:
           - q: host:X tags:Y
           items:
@@ -2493,7 +2518,7 @@ components:
           type: integer
         message:
           description: Error message.
-          example: ''
+          example: Your browser sent an invalid request.
           type: string
       required:
       - code
@@ -3392,22 +3417,22 @@ components:
           $ref: '#/components/schemas/LogsAPIError'
       type: object
     LogsArithmeticProcessor:
-      description: "Use the Arithmetic Processor to add a new attribute (without spaces\
-        \ or special characters\nin the new attribute name) to a log with the result\
-        \ of the provided formula.\nThis enables you to remap different time attributes\
-        \ with different units into a single attribute,\nor to compute operations\
-        \ on attributes within the same log.\n\nThe formula can use parentheses and\
-        \ the basic arithmetic operators `-`, `+`, `*`, `/`.\n\nBy default, the calculation\
-        \ is skipped if an attribute is missing.\nSelect \u201CReplace missing attribute\
-        \ by 0\u201D to automatically populate\nmissing attribute values with 0 to\
-        \ ensure that the calculation is done.\nAn attribute is missing if it is not\
-        \ found in the log attributes,\nor if it cannot be converted to a number.\n\
-        \n*Notes*:\n\n- The operator `-` needs to be space split in the formula as\
-        \ it can also be contained in attribute names.\n- If the target attribute\
-        \ already exists, it is overwritten by the result of the formula.\n- Results\
-        \ are rounded up to the 9th decimal. For example, if the result of the formula\
-        \ is `0.1234567891`,\n  the actual value stored for the attribute is `0.123456789`.\n\
-        - If you need to scale a unit of measure,\n  see [Scale Filter](https://docs.datadoghq.com/logs/processing/parsing/?tab=filter#matcher-and-filter)."
+      description: "Use the Arithmetic Processor to add a new attribute (without spaces
+        or special characters\nin the new attribute name) to a log with the result
+        of the provided formula.\nThis enables you to remap different time attributes
+        with different units into a single attribute,\nor to compute operations on
+        attributes within the same log.\n\nThe formula can use parentheses and the
+        basic arithmetic operators `-`, `+`, `*`, `/`.\n\nBy default, the calculation
+        is skipped if an attribute is missing.\nSelect \u201CReplace missing attribute
+        by 0\u201D to automatically populate\nmissing attribute values with 0 to ensure
+        that the calculation is done.\nAn attribute is missing if it is not found
+        in the log attributes,\nor if it cannot be converted to a number.\n\n*Notes*:\n\n-
+        The operator `-` needs to be space split in the formula as it can also be
+        contained in attribute names.\n- If the target attribute already exists, it
+        is overwritten by the result of the formula.\n- Results are rounded up to
+        the 9th decimal. For example, if the result of the formula is `0.1234567891`,\n
+        \ the actual value stored for the attribute is `0.123456789`.\n- If you need
+        to scale a unit of measure,\n  see [Scale Filter](https://docs.datadoghq.com/logs/processing/parsing/?tab=filter#matcher-and-filter)."
       properties:
         expression:
           description: Arithmetic operation between one or more log attributes.
@@ -3560,17 +3585,17 @@ components:
           type: array
       type: object
     LogsCategoryProcessor:
-      description: "Use the Category Processor to add a new attribute (without spaces\
-        \ or special characters in the new attribute name)\nto a log matching a provided\
-        \ search query. Use categories to create groups for an analytical view.\n\
-        For example, URL groups, machine groups, environments, and response time buckets.\n\
-        \n**Notes**:\n\n- The syntax of the query is the one of Logs Explorer search\
-        \ bar.\n  The query can be done on any log attribute or tag, whether it is\
-        \ a facet or not.\n  Wildcards can also be used inside your query.\n- Once\
-        \ the log has matched one of the Processor queries, it stops.\n  Make sure\
-        \ they are properly ordered in case a log could match several queries.\n-\
-        \ The names of the categories must be unique.\n- Once defined in the Category\
-        \ Processor, you can map categories to log status using the Log Status Remapper."
+      description: "Use the Category Processor to add a new attribute (without spaces
+        or special characters in the new attribute name)\nto a log matching a provided
+        search query. Use categories to create groups for an analytical view.\nFor
+        example, URL groups, machine groups, environments, and response time buckets.\n\n**Notes**:\n\n-
+        The syntax of the query is the one of Logs Explorer search bar.\n  The query
+        can be done on any log attribute or tag, whether it is a facet or not.\n  Wildcards
+        can also be used inside your query.\n- Once the log has matched one of the
+        Processor queries, it stops.\n  Make sure they are properly ordered in case
+        a log could match several queries.\n- The names of the categories must be
+        unique.\n- Once defined in the Category Processor, you can map categories
+        to log status using the Log Status Remapper."
       properties:
         categories:
           description: 'Array of filters to match or not a log and their
@@ -3618,17 +3643,17 @@ components:
       x-enum-varnames:
       - CATEGORY_PROCESSOR
     LogsDateRemapper:
-      description: "As Datadog receives logs, it timestamps them using the value(s)\
-        \ from any of these default attributes.\n\n  - `timestamp`\n  - `date`\n \
-        \ - `_timestamp`\n  - `Timestamp`\n  - `eventTime`\n  - `published_date`\n\
-        \n  If your logs put their dates in an attribute not in this list,\n  use\
-        \ the log date Remapper Processor to define their date attribute as the official\
-        \ log timestamp.\n  The recognized date formats are ISO8601, UNIX (the milliseconds\
-        \ EPOCH format), and RFC3164.\n\n  **Note:** If your logs don\u2019t contain\
-        \ any of the default attributes\n  and you haven\u2019t defined your own date\
-        \ attribute, Datadog timestamps\n  the logs with the date it received them.\n\
-        \n  If multiple log date remapper processors can be applied to a given log,\n\
-        \  only the first one (according to the pipelines order) is taken into account."
+      description: "As Datadog receives logs, it timestamps them using the value(s)
+        from any of these default attributes.\n\n  - `timestamp`\n  - `date`\n  -
+        `_timestamp`\n  - `Timestamp`\n  - `eventTime`\n  - `published_date`\n\n  If
+        your logs put their dates in an attribute not in this list,\n  use the log
+        date Remapper Processor to define their date attribute as the official log
+        timestamp.\n  The recognized date formats are ISO8601, UNIX (the milliseconds
+        EPOCH format), and RFC3164.\n\n  **Note:** If your logs don\u2019t contain
+        any of the default attributes\n  and you haven\u2019t defined your own date
+        attribute, Datadog timestamps\n  the logs with the date it received them.\n\n
+        \ If multiple log date remapper processors can be applied to a given log,\n
+        \ only the first one (according to the pipelines order) is taken into account."
       properties:
         is_enabled:
           default: false
@@ -4368,21 +4393,20 @@ components:
       - TIME_ASCENDING
       - TIME_DESCENDING
     LogsStatusRemapper:
-      description: "Use this Processor if you want to assign some attributes as the\
-        \ official status.\n\nEach incoming status value is mapped as follows.\n\n\
-        \  - Integers from 0 to 7 map to the Syslog severity standards\n  - Strings\
-        \ beginning with `emerg` or f (case-insensitive) map to `emerg` (0)\n  - Strings\
-        \ beginning with `a` (case-insensitive) map to `alert` (1)\n  - Strings beginning\
-        \ with `c` (case-insensitive) map to `critical` (2)\n  - Strings beginning\
-        \ with `err` (case-insensitive) map to `error` (3)\n  - Strings beginning\
-        \ with `w` (case-insensitive) map to `warning` (4)\n  - Strings beginning\
-        \ with `n` (case-insensitive) map to `notice` (5)\n  - Strings beginning with\
-        \ `i` (case-insensitive) map to `info` (6)\n  - Strings beginning with `d`,\
-        \ `trace` or `verbose` (case-insensitive) map to `debug` (7)\n  - Strings\
-        \ beginning with `o` or matching `OK` or `Success` (case-insensitive) map\
-        \ to OK\n  - All others map to `info` (6)\n\n  **Note:** If multiple log status\
-        \ remapper processors can be applied to a given log,\n  only the first one\
-        \ (according to the pipelines order) is taken into account."
+      description: "Use this Processor if you want to assign some attributes as the
+        official status.\n\nEach incoming status value is mapped as follows.\n\n  -
+        Integers from 0 to 7 map to the Syslog severity standards\n  - Strings beginning
+        with `emerg` or f (case-insensitive) map to `emerg` (0)\n  - Strings beginning
+        with `a` (case-insensitive) map to `alert` (1)\n  - Strings beginning with
+        `c` (case-insensitive) map to `critical` (2)\n  - Strings beginning with `err`
+        (case-insensitive) map to `error` (3)\n  - Strings beginning with `w` (case-insensitive)
+        map to `warning` (4)\n  - Strings beginning with `n` (case-insensitive) map
+        to `notice` (5)\n  - Strings beginning with `i` (case-insensitive) map to
+        `info` (6)\n  - Strings beginning with `d`, `trace` or `verbose` (case-insensitive)
+        map to `debug` (7)\n  - Strings beginning with `o` or matching `OK` or `Success`
+        (case-insensitive) map to OK\n  - All others map to `info` (6)\n\n  **Note:**
+        If multiple log status remapper processors can be applied to a given log,\n
+        \ only the first one (according to the pipelines order) is taken into account."
       properties:
         is_enabled:
           default: false
@@ -4414,17 +4438,16 @@ components:
       x-enum-varnames:
       - STATUS_REMAPPER
     LogsStringBuilderProcessor:
-      description: "Use the string builder processor to add a new attribute (without\
-        \ spaces or special characters)\nto a log with the result of the provided\
-        \ template.\nThis enables aggregation of different attributes or raw strings\
-        \ into a single attribute.\n\nThe template is defined by both raw text and\
-        \ blocks with the syntax `%{attribute_path}`.\n\n**Notes**:\n\n- The processor\
-        \ only accepts attributes with values or an array of values in the blocks.\n\
-        - If an attribute cannot be used (object or array of object),\n  it is replaced\
-        \ by an empty string or the entire operation is skipped depending on your\
-        \ selection.\n- If the target attribute already exists, it is overwritten\
-        \ by the result of the template.\n- Results of the template cannot exceed\
-        \ 256 characters."
+      description: "Use the string builder processor to add a new attribute (without
+        spaces or special characters)\nto a log with the result of the provided template.\nThis
+        enables aggregation of different attributes or raw strings into a single attribute.\n\nThe
+        template is defined by both raw text and blocks with the syntax `%{attribute_path}`.\n\n**Notes**:\n\n-
+        The processor only accepts attributes with values or an array of values in
+        the blocks.\n- If an attribute cannot be used (object or array of object),\n
+        \ it is replaced by an empty string or the entire operation is skipped depending
+        on your selection.\n- If the target attribute already exists, it is overwritten
+        by the result of the template.\n- Results of the template cannot exceed 256
+        characters."
       properties:
         is_enabled:
           default: false
@@ -4465,12 +4488,12 @@ components:
       x-enum-varnames:
       - STRING_BUILDER_PROCESSOR
     LogsTraceRemapper:
-      description: "There are two ways to improve correlation between application\
-        \ traces and logs.\n\n  1. Follow the documentation on [how to inject a trace\
-        \ ID in the application logs](https://docs.datadoghq.com/tracing/connect_logs_and_traces)\n\
-        \  and by default log integrations take care of all the rest of the setup.\n\
-        \n  2. Use the Trace remapper processor to define a log attribute as its associated\
-        \ trace ID."
+      description: "There are two ways to improve correlation between application
+        traces and logs.\n\n  1. Follow the documentation on [how to inject a trace
+        ID in the application logs](https://docs.datadoghq.com/tracing/connect_logs_and_traces)\n
+        \ and by default log integrations take care of all the rest of the setup.\n\n
+        \ 2. Use the Trace remapper processor to define a log attribute as its associated
+        trace ID."
       properties:
         is_enabled:
           default: false
@@ -4718,6 +4741,11 @@ components:
             $ref: '#/components/schemas/Point'
           readOnly: true
           type: array
+        query_index:
+          description: The index of the series' query within the request.
+          format: int64
+          readOnly: true
+          type: integer
         scope:
           description: Metric scope, comma separated list of tags.
           example: host:foo,env:test
@@ -4728,6 +4756,13 @@ components:
           format: int64
           readOnly: true
           type: integer
+        tag_set:
+          description: Unique tags identifying this series.
+          items:
+            description: Unique tags identifying this series.
+            type: string
+          readOnly: true
+          type: array
         unit:
           description: 'Detailed information about the metric unit.
 
@@ -4795,6 +4830,7 @@ components:
     MetricsQueryUnit:
       description: Object containing the metric unit family, scale factor, name, and
         short name.
+      nullable: true
       properties:
         family:
           description: Unit family, allows for conversion between units of the same
@@ -5136,17 +5172,17 @@ components:
           type: boolean
         renotify_interval:
           default: none
-          description: "The number of minutes after the last notification before a\
-            \ monitor re-notifies on the current status.\nIt only re-notifies if it\u2019\
-            s not resolved."
+          description: "The number of minutes after the last notification before a
+            monitor re-notifies on the current status.\nIt only re-notifies if it\u2019s
+            not resolved."
           format: int64
           nullable: true
           type: integer
         require_full_window:
-          description: "A Boolean indicating whether this monitor needs a full window\
-            \ of data before it\u2019s evaluated.\nWe highly recommend you set this\
-            \ to `false` for sparse metrics,\notherwise some evaluations are skipped.\
-            \ Default is false."
+          description: "A Boolean indicating whether this monitor needs a full window
+            of data before it\u2019s evaluated.\nWe highly recommend you set this
+            to `false` for sparse metrics,\notherwise some evaluations are skipped.
+            Default is false."
           type: boolean
         silenced:
           additionalProperties:
@@ -6590,6 +6626,18 @@ components:
       required:
       - service_name
       type: object
+    Pagination:
+      description: Pagination object.
+      properties:
+        total_count:
+          description: Total count.
+          format: int64
+          type: integer
+        total_filtered_count:
+          description: Total count of elements matched by the filter.
+          format: int64
+          type: integer
+      type: object
     Point:
       description: Array of timeseries points.
       example:
@@ -6743,6 +6791,12 @@ components:
         security_query:
           $ref: '#/components/schemas/LogQueryDefinition'
       type: object
+    ResponseMetaAttributes:
+      description: Object describing meta attributes of response.
+      properties:
+        page:
+          $ref: '#/components/schemas/Pagination'
+      type: object
     SLOBulkDelete:
       additionalProperties:
         description: An array of all SLO timeframes.
@@ -6900,6 +6954,8 @@ components:
           items:
             $ref: '#/components/schemas/SLOCorrection'
           type: array
+        meta:
+          $ref: '#/components/schemas/ResponseMetaAttributes'
       type: object
     SLOCorrectionResponse:
       description: The response object of an SLO correction
@@ -7114,7 +7170,14 @@ components:
 
                 If a metric query only has one unit object, the second array element
                 is null.'
-              example: '[{"family":"bytes","scale_factor":1.0,"name":"byte","short_name":"B","plural":"bytes","id":2},null]'
+              example:
+              - family: bytes
+                id: 2
+                name: byte
+                plural: bytes
+                scale_factor: 1.0
+                short_name: B
+              - null
               items:
                 $ref: '#/components/schemas/SLOHistoryMetricsSeriesMetadataUnit'
               nullable: true
@@ -7578,11 +7641,13 @@ components:
       - 7d
       - 30d
       - 90d
+      - custom
       type: string
       x-enum-varnames:
       - SEVEN_DAYS
       - THIRTY_DAYS
       - NINETY_DAYS
+      - CUSTOM
     SLOType:
       description: The type of the service level objective.
       enum:
@@ -8477,7 +8542,6 @@ components:
               type: string
             targetValue:
               description: The path target value to compare to.
-              type: object
           type: object
         type:
           $ref: '#/components/schemas/SyntheticsAssertionType'
@@ -8593,7 +8657,7 @@ components:
           description: Name of the error.
           example: ''
           type: string
-        statusCode:
+        status:
           description: Status Code of the error.
           format: int64
           type: integer
@@ -9778,6 +9842,10 @@ components:
             an alert.'
           format: int64
           type: integer
+        monitor_name:
+          description: The monitor name is used for the alert title as well as for
+            all monitor dashboard widgets and SLOs.
+          type: string
         monitor_options:
           description: 'Object containing the options for a Synthetic test as a monitor
 
@@ -9793,13 +9861,23 @@ components:
               minimum: 0
               type: integer
           type: object
+        monitor_priority:
+          description: Integer from 1 (high) to 5 (low) indicating alert severity.
+          format: int32
+          maximum: 5
+          minimum: 1
+          type: integer
         noScreenshot:
           description: Prevents saving screenshots of the steps.
           type: boolean
         retry:
           $ref: '#/components/schemas/SyntheticsTestOptionsRetry'
         tick_every:
-          $ref: '#/components/schemas/SyntheticsTickInterval'
+          description: The frequency at which to run the Synthetic test (in seconds).
+          format: int64
+          maximum: 604800
+          minimum: 30
+          type: integer
       type: object
     SyntheticsTestOptionsRetry:
       description: Object describing the retry strategy to apply to a Synthetic test.
@@ -9849,6 +9927,10 @@ components:
     SyntheticsTestRequest:
       description: Object describing the Synthetic test request.
       properties:
+        allow_insecure:
+          description: Allows loading insecure content for an HTTP request in a multistep
+            test step.
+          type: boolean
         basicAuth:
           $ref: '#/components/schemas/SyntheticsBasicAuth'
         body:
@@ -9921,32 +10003,6 @@ components:
           description: Date of update of the certificate or key, ISO format.
           type: string
       type: object
-    SyntheticsTickInterval:
-      description: The frequency at which to run the Synthetic test (in seconds).
-      enum:
-      - 30
-      - 60
-      - 300
-      - 900
-      - 1800
-      - 3600
-      - 21600
-      - 43200
-      - 86400
-      - 604800
-      format: int64
-      type: integer
-      x-enum-varnames:
-      - THIRTY_SECONDS
-      - MINUTE
-      - FIVE_MINUTES
-      - FIFTEEN_MINUTES
-      - THIRTY_MINUTES
-      - HOUR
-      - SIX_HOURS
-      - TWELVE_HOURS
-      - DAY
-      - WEEK
     SyntheticsTiming:
       description: 'Object containing all metrics and their values collected for a
         Synthetic API test.
@@ -10458,6 +10514,87 @@ components:
         style:
           $ref: '#/components/schemas/WidgetRequestStyle'
       type: object
+    TreeMapColorBy:
+      default: user
+      description: The attribute used to determine color in the widget.
+      enum:
+      - user
+      example: user
+      type: string
+      x-enum-varnames:
+      - USER
+    TreeMapGroupBy:
+      description: The attribute used to group elements in the widget.
+      enum:
+      - user
+      - family
+      - process
+      example: user
+      type: string
+      x-enum-varnames:
+      - USER
+      - FAMILY
+      - PROCESS
+    TreeMapSizeBy:
+      description: The attribute used to determine size in the widget.
+      enum:
+      - pct_cpu
+      - pct_mem
+      example: pct_cpu
+      type: string
+      x-enum-varnames:
+      - PCT_CPU
+      - PCT_MEM
+    TreeMapWidgetDefinition:
+      description: "The treemap visualization found on the Host Dashboards comes from
+        the output of `ps auxww`. This is not continuously run on your hosts. Instead,
+        it\u2019s run once on Agent start/restart. The treemap is only supported for
+        process data on a single host dashboard \u2014 this may not be reused in other
+        dashboards or for other metrics."
+      properties:
+        color_by:
+          $ref: '#/components/schemas/TreeMapColorBy'
+        group_by:
+          $ref: '#/components/schemas/TreeMapGroupBy'
+        requests:
+          description: List of top list widget requests.
+          example:
+          - q: system.load.1
+          items:
+            $ref: '#/components/schemas/TreeMapWidgetRequest'
+          maxItems: 1
+          minItems: 1
+          type: array
+        size_by:
+          $ref: '#/components/schemas/TreeMapSizeBy'
+        title:
+          description: Title of your widget.
+          type: string
+        type:
+          $ref: '#/components/schemas/TreeMapWidgetDefinitionType'
+      required:
+      - type
+      - requests
+      - size_by
+      - color_by
+      - group_by
+      type: object
+    TreeMapWidgetDefinitionType:
+      default: treemap
+      description: Type of the treemap widget.
+      enum:
+      - treemap
+      example: treemap
+      type: string
+      x-enum-varnames:
+      - TREEMAP
+    TreeMapWidgetRequest:
+      description: An updated treemap widget.
+      properties:
+        q:
+          description: The widget metrics query.
+          type: string
+      type: object
     UsageAnalyzedLogsHour:
       description: The number of analyzed logs for each hour for a given organization.
       properties:
@@ -10924,14 +11061,40 @@ components:
           $ref: '#/components/schemas/UsageBillableSummaryBody'
         lambda_function_average:
           $ref: '#/components/schemas/UsageBillableSummaryBody'
+        logs_indexed_15day_sum:
+          $ref: '#/components/schemas/UsageBillableSummaryBody'
+        logs_indexed_180day_sum:
+          $ref: '#/components/schemas/UsageBillableSummaryBody'
+        logs_indexed_30day_sum:
+          $ref: '#/components/schemas/UsageBillableSummaryBody'
+        logs_indexed_3day_sum:
+          $ref: '#/components/schemas/UsageBillableSummaryBody'
+        logs_indexed_45day_sum:
+          $ref: '#/components/schemas/UsageBillableSummaryBody'
+        logs_indexed_60day_sum:
+          $ref: '#/components/schemas/UsageBillableSummaryBody'
+        logs_indexed_7day_sum:
+          $ref: '#/components/schemas/UsageBillableSummaryBody'
+        logs_indexed_90day_sum:
+          $ref: '#/components/schemas/UsageBillableSummaryBody'
+        logs_indexed_custom_retention_sum:
+          $ref: '#/components/schemas/UsageBillableSummaryBody'
         logs_indexed_sum:
           $ref: '#/components/schemas/UsageBillableSummaryBody'
         logs_ingested_sum:
           $ref: '#/components/schemas/UsageBillableSummaryBody'
+        network_device_top99p:
+          $ref: '#/components/schemas/UsageBillableSummaryBody'
         npm_flow_sum:
           $ref: '#/components/schemas/UsageBillableSummaryBody'
+        npm_host_sum:
+          $ref: '#/components/schemas/UsageBillableSummaryBody'
         npm_host_top99p:
           $ref: '#/components/schemas/UsageBillableSummaryBody'
+        prof_container_sum:
+          $ref: '#/components/schemas/UsageBillableSummaryBody'
+        prof_host_top99p:
+          $ref: '#/components/schemas/UsageBillableSummaryBody'
         rum_sum:
           $ref: '#/components/schemas/UsageBillableSummaryBody'
         serverless_invocation_sum:
@@ -10959,13 +11122,13 @@ components:
         hour.
       properties:
         cws_container_count:
-          description: "The total number of Cloud Workload Security container hours\
-            \ from the start of the given hour\u2019s month until the given hour."
+          description: "The total number of Cloud Workload Security container hours
+            from the start of the given hour\u2019s month until the given hour."
           format: int64
           type: integer
         cws_host_count:
-          description: "The total number of Cloud Workload Security host hours from\
-            \ the start of the given hour\u2019s month until the given hour."
+          description: "The total number of Cloud Workload Security host hours from
+            the start of the given hour\u2019s month until the given hour."
           format: int64
           type: integer
         hour:
@@ -12508,52 +12671,6 @@ components:
             $ref: '#/components/schemas/UsageTopAvgMetricsHour'
           type: array
       type: object
-    UsageTraceHour:
-      description: The hours of trace usage.
-      properties:
-        hour:
-          description: The hour for the usage.
-          format: date-time
-          type: string
-        indexed_events_count:
-          description: Contains the number of Indexed Spans indexed.
-          format: int64
-          type: integer
-      type: object
-    UsageTraceResponse:
-      description: A response containing trace usage.
-      properties:
-        usage:
-          description: Array with the number of hourly traces indexed for a given
-            organization.
-          items:
-            $ref: '#/components/schemas/UsageTraceHour'
-          type: array
-      type: object
-    UsageTracingWithoutLimitsHour:
-      description: Tracing without limits usage for a given organization for a given
-        hour.
-      properties:
-        hour:
-          description: The hour for the usage.
-          format: date-time
-          type: string
-        ingested_events_bytes:
-          description: Contains the total number of bytes ingested during a given
-            hour.
-          format: int64
-          type: integer
-      type: object
-    UsageTracingWithoutLimitsResponse:
-      description: Response containing the tracing without limits usage for each hour
-        for a given organization.
-      properties:
-        usage:
-          description: Get hourly usage for tracing without limits.
-          items:
-            $ref: '#/components/schemas/UsageTracingWithoutLimitsHour'
-          type: array
-      type: object
     User:
       description: Create, edit, and disable users.
       properties:
@@ -12611,11 +12728,11 @@ components:
           $ref: '#/components/schemas/User'
       type: object
     Widget:
-      description: "Information about widget.\n\n**Note**: The `layout` property is\
-        \ required for widgets in dashboards with `free` `layout_type`.\n      For\
-        \ the **new dashboard layout**, the `layout` property depends on the `reflow_type`\
-        \ of the dashboard.\n      - If `reflow_type` is `fixed`, `layout` is required.\n\
-        \      - If `reflow_type` is `auto`, `layout` should not be set."
+      description: "Information about widget.\n\n**Note**: The `layout` property is
+        required for widgets in dashboards with `free` `layout_type`.\n      For the
+        **new dashboard layout**, the `layout` property depends on the `reflow_type`
+        of the dashboard.\n      - If `reflow_type` is `fixed`, `layout` is required.\n
+        \     - If `reflow_type` is `auto`, `layout` should not be set."
       properties:
         definition:
           $ref: '#/components/schemas/WidgetDefinition'
@@ -12801,6 +12918,7 @@ components:
       - $ref: '#/components/schemas/TableWidgetDefinition'
       - $ref: '#/components/schemas/TimeseriesWidgetDefinition'
       - $ref: '#/components/schemas/ToplistWidgetDefinition'
+      - $ref: '#/components/schemas/TreeMapWidgetDefinition'
       type: object
     WidgetDisplayType:
       description: Type of display to use for the request.
@@ -13053,9 +13171,9 @@ components:
         graphs.
       properties:
         display_type:
-          description: "Combination of:\n  - A severity error, warning, ok, or info\n\
-            \  - A line type: dashed, solid, or bold\nIn this case of a Distribution\
-            \ widget, this can be set to be `x_axis_percentile`.\n"
+          description: "Combination of:\n  - A severity error, warning, ok, or info\n
+            \ - A line type: dashed, solid, or bold\nIn this case of a Distribution
+            widget, this can be set to be `x_axis_percentile`.\n"
           example: error dashed
           type: string
         label:
@@ -13911,7 +14029,7 @@ paths:
       description: Get specified daily custom reports.
       operationId: GetSpecifiedDailyCustomReports
       parameters:
-      - description: The specified ID to search results for.
+      - description: Date of the report in the format `YYYY-MM-DD`.
         in: path
         name: report_id
         required: true
@@ -14577,14 +14695,14 @@ paths:
         type: idempotent
   /api/v1/events:
     get:
-      description: "The event stream can be queried and filtered by time, priority,\
-        \ sources and tags.\n\n**Notes**:\n- If the event you\u2019re querying contains\
-        \ markdown formatting of any kind,\nyou may see characters such as `%`,`\\\
-        `,`n` in your output.\n\n- This endpoint returns a maximum of `1000` most\
-        \ recent results. To return additional results,\nidentify the last timestamp\
-        \ of the last result and set that as the `end` query time to\npaginate the\
-        \ results. You can also use the page parameter to specify which set of `1000`\
-        \ results to return."
+      description: "The event stream can be queried and filtered by time, priority,
+        sources and tags.\n\n**Notes**:\n- If the event you\u2019re querying contains
+        markdown formatting of any kind,\nyou may see characters such as `%`,`\\`,`n`
+        in your output.\n\n- This endpoint returns a maximum of `1000` most recent
+        results. To return additional results,\nidentify the last timestamp of the
+        last result and set that as the `end` query time to\npaginate the results.
+        You can also use the page parameter to specify which set of `1000` results
+        to return."
       operationId: ListEvents
       parameters:
       - description: POSIX timestamp.
@@ -14717,9 +14835,9 @@ paths:
         type: safe
   /api/v1/events/{event_id}:
     get:
-      description: "This endpoint allows you to query for event details.\n\n**Note**:\
-        \ If the event you\u2019re querying contains markdown formatting of any kind,\n\
-        you may see characters such as `%`,`\\`,`n` in your output."
+      description: "This endpoint allows you to query for event details.\n\n**Note**:
+        If the event you\u2019re querying contains markdown formatting of any kind,\nyou
+        may see characters such as `%`,`\\`,`n` in your output."
       operationId: GetEvent
       parameters:
       - description: The ID of the event.
@@ -15051,7 +15169,7 @@ paths:
         content:
           application/json:
             schema:
-              $ref: '#/components/schemas/AWSAccount'
+              $ref: '#/components/schemas/AWSAccountDeleteRequest'
         description: AWS request object
         required: true
       responses:
@@ -15311,33 +15429,6 @@ paths:
               schema:
                 $ref: '#/components/schemas/APIErrorResponse'
           description: Authentication Error
-      servers:
-      - url: https://{subdomain}.{site}
-        variables:
-          site:
-            default: datadoghq.com
-            description: The regional site for our customers.
-            enum:
-            - datadoghq.com
-          subdomain:
-            default: api
-            description: The subdomain where the API is deployed.
-      - url: '{protocol}://{name}'
-        variables:
-          name:
-            default: api.datadoghq.com
-            description: Full site DNS name.
-          protocol:
-            default: https
-            description: The protocol for accessing the API.
-      - url: https://{subdomain}.{site}
-        variables:
-          site:
-            default: datadoghq.com
-            description: Any Datadog deployment.
-          subdomain:
-            default: api
-            description: The subdomain where the API is deployed.
       summary: Delete a tag filtering entry
       tags:
       - AWS Integration
@@ -15374,33 +15465,6 @@ paths:
               schema:
                 $ref: '#/components/schemas/APIErrorResponse'
           description: Authentication Error
-      servers:
-      - url: https://{subdomain}.{site}
-        variables:
-          site:
-            default: datadoghq.com
-            description: The regional site for our customers.
-            enum:
-            - datadoghq.com
-          subdomain:
-            default: api
-            description: The subdomain where the API is deployed.
-      - url: '{protocol}://{name}'
-        variables:
-          name:
-            default: api.datadoghq.com
-            description: Full site DNS name.
-          protocol:
-            default: https
-            description: The protocol for accessing the API.
-      - url: https://{subdomain}.{site}
-        variables:
-          site:
-            default: datadoghq.com
-            description: Any Datadog deployment.
-          subdomain:
-            default: api
-            description: The subdomain where the API is deployed.
       summary: Get all AWS tag filters
       tags:
       - AWS Integration
@@ -15441,33 +15505,6 @@ paths:
               schema:
                 $ref: '#/components/schemas/APIErrorResponse'
           description: Authentication Error
-      servers:
-      - url: https://{subdomain}.{site}
-        variables:
-          site:
-            default: datadoghq.com
-            description: The regional site for our customers.
-            enum:
-            - datadoghq.com
-          subdomain:
-            default: api
-            description: The subdomain where the API is deployed.
-      - url: '{protocol}://{name}'
-        variables:
-          name:
-            default: api.datadoghq.com
-            description: Full site DNS name.
-          protocol:
-            default: https
-            description: The protocol for accessing the API.
-      - url: https://{subdomain}.{site}
-        variables:
-          site:
-            default: datadoghq.com
-            description: Any Datadog deployment.
-          subdomain:
-            default: api
-            description: The subdomain where the API is deployed.
       summary: Set an AWS tag filter
       tags:
       - AWS Integration
@@ -15491,7 +15528,7 @@ paths:
 
           For more information about your AWS account Role name,
 
-          see the [Datadog AWS integration configuration info](https://github.com/DataDog/documentation/blob/master/integrations/amazon_web_services/#installation).'
+          see the [Datadog AWS integration configuration info](https://docs.datadoghq.com/integrations/amazon_web_services/#setup).'
         required: true
       responses:
         '200':
@@ -15770,14 +15807,13 @@ paths:
         type: unsafe
   /api/v1/integration/aws/logs/services_async:
     post:
-      description: "Test if permissions are present to add log-forwarding triggers\
-        \ for the\ngiven services and AWS account. Input is the same as for `EnableAWSLogServices`.\n\
-        Done async, so can be repeatedly polled in a non-blocking fashion until\n\
-        the async request completes.\n\n- Returns a status of `created` when it's\
-        \ checking if the permissions exists\n  in the AWS account.\n- Returns a status\
-        \ of `waiting` while checking.\n- Returns a status of `checked and ok` if\
-        \ the Lambda exists.\n- Returns a status of `error` if the Lambda does not\
-        \ exist."
+      description: "Test if permissions are present to add log-forwarding triggers
+        for the\ngiven services and AWS account. Input is the same as for `EnableAWSLogServices`.\nDone
+        async, so can be repeatedly polled in a non-blocking fashion until\nthe async
+        request completes.\n\n- Returns a status of `created` when it's checking if
+        the permissions exists\n  in the AWS account.\n- Returns a status of `waiting`
+        while checking.\n- Returns a status of `checked and ok` if the Lambda exists.\n-
+        Returns a status of `error` if the Lambda does not exist."
       operationId: CheckAWSLogsServicesAsync
       requestBody:
         content:
@@ -16729,10 +16765,10 @@ paths:
       x-undo:
         type: safe
     put:
-      description: "Update an index as identified by its name.\nReturns the Index\
-        \ object passed in the request body when the request is successful.\n\nUsing\
-        \ the `PUT` method updates your index\u2019s configuration by **replacing**\n\
-        your current configuration with the new one sent to your Datadog organization."
+      description: "Update an index as identified by its name.\nReturns the Index
+        object passed in the request body when the request is successful.\n\nUsing
+        the `PUT` method updates your index\u2019s configuration by **replacing**\nyour
+        current configuration with the new one sent to your Datadog organization."
       operationId: UpdateLogsIndex
       parameters:
       - description: Name of the log index.
@@ -16994,10 +17030,10 @@ paths:
       x-undo:
         type: safe
     put:
-      description: "Update a given pipeline configuration to change it\u2019s processors\
-        \ or their order.\n\n**Note**: Using this method updates your pipeline configuration\
-        \ by **replacing**\nyour current configuration with the new one sent to your\
-        \ Datadog organization."
+      description: "Update a given pipeline configuration to change it\u2019s processors
+        or their order.\n\n**Note**: Using this method updates your pipeline configuration
+        by **replacing**\nyour current configuration with the new one sent to your
+        Datadog organization."
       operationId: UpdateLogsPipeline
       parameters:
       - description: ID of the pipeline to delete.
@@ -17459,7 +17495,7 @@ paths:
         - **`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).
+        - **`time_window`** #m (between 1 and 2880), #h (between 1 and 48).
 
         - **`operator`** `<`, `<=`, `>`, `>=`, `==`, or `!=`.
 
@@ -17509,7 +17545,7 @@ paths:
         - **`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 `!=`.
 
@@ -18114,7 +18150,7 @@ paths:
       description: Get specified monthly custom reports.
       operationId: GetSpecifiedMonthlyCustomReports
       parameters:
-      - description: The specified ID to search results for.
+      - description: Date of the report in the format `YYYY-MM-DD`.
         in: path
         name: report_id
         required: true
@@ -18815,22 +18851,23 @@ paths:
         type: safe
   /api/v1/series:
     post:
-      description: "The metrics end-point allows you to post time-series data that\
-        \ can be graphed on Datadog\u2019s dashboards.\nThe maximum payload size is\
-        \ 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- 20 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."
+      description: "The metrics end-point allows you to post time-series data that
+        can be graphed on Datadog\u2019s dashboards.\nThe maximum payload size is
+        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- 20 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."
       operationId: SubmitMetrics
       requestBody:
         content:
           application/json:
             examples:
               dynamic-points:
-                description: TODO.
+                description: "Post time-series data that can be graphed on Datadog\u2019s
+                  dashboards."
                 summary: Dynamic Points
                 value:
                   series:
@@ -18918,6 +18955,20 @@ paths:
         required: false
         schema:
           type: string
+      - description: The number of SLOs to return in the response.
+        in: query
+        name: limit
+        required: false
+        schema:
+          format: int64
+          type: integer
+      - description: The specific offset to use as the beginning of the returned response.
+        in: query
+        name: offset
+        required: false
+        schema:
+          format: int64
+          type: integer
       responses:
         '200':
           content:
@@ -18986,11 +19037,11 @@ paths:
         slo:
           parameters:
           - name: body
-            value: "{\n  \"type\": \"metric\",\n  \"name\": \"{{ unique }}\",\n  \"\
-              thresholds\": [{\n    \"timeframe\": \"7d\",\n    \"target\": 95.0,\n\
-              \    \"warning\": 98.0\n  }],\n  \"query\": {\n    \"numerator\": \"\
-              sum:httpservice.hits{code:2xx}.as_count()\",\n    \"denominator\": \"\
-              sum:httpservice.hits{!code:3xx}.as_count()\"\n  }\n}"
+            value: "{\n  \"type\": \"metric\",\n  \"name\": \"{{ unique }}\",\n  \"thresholds\":
+              [{\n    \"timeframe\": \"7d\",\n    \"target\": 95.0,\n    \"warning\":
+              98.0\n  }],\n  \"query\": {\n    \"numerator\": \"sum:httpservice.hits{code:2xx}.as_count()\",\n
+              \   \"denominator\": \"sum:httpservice.hits{!code:3xx}.as_count()\"\n
+              \ }\n}"
           step: there is a valid "slo" in the system
       x-menu-order: 1
       x-undo:
@@ -19160,11 +19211,11 @@ paths:
         correction:
           parameters:
           - name: body
-            value: "{\n  \"data\": {\n    \"attributes\": {\n      \"slo_id\": \"\
-              {{ slo.data[0].id }}\",\n      \"start\": {{ now_ts }},\n      \"end\"\
-              : {{ hour_later_ts }},\n      \"category\": \"Other\",\n      \"timezone\"\
-              : \"UTC\",\n      \"description\": \"Test Correction\"\n     },\n  \
-              \   \"type\": \"correction\"\n  }\n}"
+            value: "{\n  \"data\": {\n    \"attributes\": {\n      \"slo_id\": \"{{
+              slo.data[0].id }}\",\n      \"start\": {{ timestamp(\"now\") }},\n      \"end\":
+              {{ timestamp(\"now + 1h\") }},\n      \"category\": \"Other\",\n      \"timezone\":
+              \"UTC\",\n      \"description\": \"Test Correction\"\n     },\n     \"type\":
+              \"correction\"\n  }\n}"
           step: there is a valid "correction" for "slo"
       x-menu-order: 1
       x-undo:
@@ -19448,12 +19499,12 @@ paths:
         type: idempotent
   /api/v1/slo/{slo_id}/history:
     get:
-      description: "Get a specific SLO\u2019s history, regardless of its SLO type.\n\
-        \nThe detailed history data is structured according to the source data type.\n\
-        For example, metric data is included for event SLOs that use\nthe metric source,\
-        \ and monitor SLO types include the monitor transition history.\n\n**Note:**\
-        \ There are different response formats for event based and time based SLOs.\n\
-        Examples of both are shown."
+      description: "Get a specific SLO\u2019s history, regardless of its SLO type.\n\nThe
+        detailed history data is structured according to the source data type.\nFor
+        example, metric data is included for event SLOs that use\nthe metric source,
+        and monitor SLO types include the monitor transition history.\n\n**Note:**
+        There are different response formats for event based and time based SLOs.\nExamples
+        of both are shown."
       operationId: GetSLOHistory
       parameters:
       - description: The ID of the service level objective object.
@@ -19477,7 +19528,7 @@ paths:
           format: int64
           type: integer
       - description: The SLO target. If `target` is passed in, the response will include
-          the error budget that remains.
+          the remaining error budget and a timeframe value of `custom`.
         in: query
         name: target
         schema:
@@ -19752,8 +19803,10 @@ paths:
       x-codegen-request-body-name: body
       x-menu-order: 1
       x-undo:
-        operationId: TODO
-        parameters: []
+        operationId: DeleteTests
+        parameters:
+        - name: body
+          template: '{"public_ids": ["{{ public_id }}"]}'
         type: unsafe
   /api/v1/synthetics/tests/api/{public_id}:
     get:
@@ -22122,108 +22175,6 @@ paths:
       x-menu-order: 5
       x-undo:
         type: safe
-  /api/v1/usage/traces:
-    get:
-      deprecated: true
-      description: 'Get hourly usage for trace search.
-
-
-        **Note** This endpoint has been renamed to `/api/v1/usage/indexed-spans`.'
-      operationId: GetUsageTrace
-      parameters:
-      - description: 'Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh]
-          for usage beginning at this hour.'
-        in: query
-        name: start_hr
-        required: true
-        schema:
-          format: date-time
-          type: string
-      - description: 'Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh]
-          for usage ending **before** this hour.'
-        in: query
-        name: end_hr
-        required: false
-        schema:
-          format: date-time
-          type: string
-      responses:
-        '200':
-          content:
-            application/json;datetime-format=rfc3339:
-              schema:
-                $ref: '#/components/schemas/UsageTraceResponse'
-          description: OK
-        '400':
-          content:
-            application/json;datetime-format=rfc3339:
-              schema:
-                $ref: '#/components/schemas/APIErrorResponse'
-          description: Bad Request
-        '403':
-          content:
-            application/json;datetime-format=rfc3339:
-              schema:
-                $ref: '#/components/schemas/APIErrorResponse'
-          description: Forbidden - User is not authorized
-      summary: Get hourly usage for Trace Search
-      tags:
-      - Usage Metering
-      x-menu-order: 6
-      x-undo:
-        type: safe
-  /api/v1/usage/tracing-without-limits:
-    get:
-      deprecated: true
-      description: 'Get hourly usage for tracing without limits.
-
-
-        **Note** This endpoint has been renamed to `/api/v1/usage/ingested-spans`.'
-      operationId: GetTracingWithoutLimits
-      parameters:
-      - description: 'Datetime in ISO-8601 format, UTC, precise to hour: `[YYYY-MM-DDThh]`
-          for usage beginning at this hour.'
-        in: query
-        name: start_hr
-        required: true
-        schema:
-          format: date-time
-          type: string
-      - description: 'Datetime in ISO-8601 format, UTC, precise to hour: `[YYYY-MM-DDThh]`
-          for usage ending
-
-          **before** this hour.'
-        in: query
-        name: end_hr
-        required: false
-        schema:
-          format: date-time
-          type: string
-      responses:
-        '200':
-          content:
-            application/json;datetime-format=rfc3339:
-              schema:
-                $ref: '#/components/schemas/UsageTracingWithoutLimitsResponse'
-          description: OK
-        '400':
-          content:
-            application/json;datetime-format=rfc3339:
-              schema:
-                $ref: '#/components/schemas/APIErrorResponse'
-          description: Bad Request
-        '403':
-          content:
-            application/json;datetime-format=rfc3339:
-              schema:
-                $ref: '#/components/schemas/APIErrorResponse'
-          description: Forbidden - User is not authorized
-      summary: Get hourly usage for tracing without limits
-      tags:
-      - Usage Metering
-      x-menu-order: 25
-      x-undo:
-        type: safe
   /api/v1/user:
     get:
       description: List all users for your organization.
@@ -22672,14 +22623,13 @@ tags:
   externalDocs:
     url: https://docs.datadoghq.com/api/?lang=bash#integration-aws-logs
   name: AWS Logs Integration
-- description: "All requests to Datadog\u2019s API must be authenticated.\nRequests\
-    \ that write data require reporting access and require an `API key`.\nRequests\
-    \ that read data require full access and also require an `application key`.\n\n\
-    **Note:** All Datadog API clients are configured by default to consume Datadog\
-    \ US site APIs.\nIf you are on the Datadog EU site, set the environment variable\
-    \ `DATADOG_HOST` to\n`https://api.datadoghq.eu` or override this value directly\
-    \ when creating your client.\n\n[Manage your account\u2019s API and application\
-    \ keys](https://app.datadoghq.com/account/settings#api)."
+- description: "All requests to Datadog\u2019s API must be authenticated.\nRequests
+    that write data require reporting access and require an `API key`.\nRequests that
+    read data require full access and also require an `application key`.\n\n**Note:**
+    All Datadog API clients are configured by default to consume Datadog US site APIs.\nIf
+    you are on the Datadog EU site, set the environment variable `DATADOG_HOST` to\n`https://api.datadoghq.eu`
+    or override this value directly when creating your client.\n\n[Manage your account\u2019s
+    API and application keys](https://app.datadoghq.com/account/settings#api)."
   name: Authentication
 - description: 'Configure your Datadog-Azure integration directly through the Datadog
     API.
@@ -22747,39 +22697,37 @@ tags:
     description: Find out more at
     url: https://docs.datadoghq.com/logs/indexes/
   name: Logs Indexes
-- description: "Pipelines and processors operate on incoming logs, parsing\nand transforming\
-    \ them into structured attributes for easier querying.\n\n- See the [pipelines\
-    \ configuration page](https://app.datadoghq.com/logs/pipelines)\n  for a list\
-    \ of the pipelines and processors currently configured in our UI.\n\n- Additional\
-    \ API-related information about processors can be found in the\n  [processors\
-    \ documentation](https://docs.datadoghq.com/logs/processing/processors/?tab=api#lookup-processor).\n\
-    \n- For more information about Pipelines, see the\n  [pipeline documentation](https://docs.datadoghq.com/logs/processing).\n\
-    \n**Notes:**\n\nThese endpoints are only available for admin users.\nMake sure\
-    \ to use an application key created by an admin.\n\n**Grok parsing rules may effect\
-    \ JSON output and require\nreturned data to be configured before using in a request.**\n\
-    For example, if you are using the data returned from a\nrequest for another request\
-    \ body, and have a parsing rule\nthat uses a regex pattern like `\\s` for spaces,\
-    \ you will\nneed to configure all escaped spaces as `%{space}` to use\nin the\
-    \ body data."
+- description: "Pipelines and processors operate on incoming logs, parsing\nand transforming
+    them into structured attributes for easier querying.\n\n- See the [pipelines configuration
+    page](https://app.datadoghq.com/logs/pipelines)\n  for a list of the pipelines
+    and processors currently configured in our UI.\n\n- Additional API-related information
+    about processors can be found in the\n  [processors documentation](https://docs.datadoghq.com/logs/processing/processors/?tab=api#lookup-processor).\n\n-
+    For more information about Pipelines, see the\n  [pipeline documentation](https://docs.datadoghq.com/logs/processing).\n\n**Notes:**\n\nThese
+    endpoints are only available for admin users.\nMake sure to use an application
+    key created by an admin.\n\n**Grok parsing rules may effect JSON output and require\nreturned
+    data to be configured before using in a request.**\nFor example, if you are using
+    the data returned from a\nrequest for another request body, and have a parsing
+    rule\nthat uses a regex pattern like `\\s` for spaces, you will\nneed to configure
+    all escaped spaces as `%{space}` to use\nin the body data."
   externalDocs:
     description: Find out more at
     url: https://docs.datadoghq.com/logs/processing/
   name: Logs Pipelines
-- description: "The metrics endpoint allows you to:\n\n- Post metrics data so it can\
-    \ be graphed on Datadog\u2019s dashboards\n- Query metrics from any time period\n\
-    - Modify tag configurations for metrics\n- View tags and volumes for metrics\n\
-    \n**Note**: A graph can only contain a set number of points\nand as the timeframe\
-    \ over which a metric is viewed increases,\naggregation between points occurs\
-    \ to stay below that set number.\n\nThe Post, Patch, and Delete `manage_tags`\
-    \ API methods can only be performed by\na user who has the `Manage Tags for Metrics`\
-    \ permission."
+- description: "The metrics endpoint allows you to:\n\n- Post metrics data so it can
+    be graphed on Datadog\u2019s dashboards\n- Query metrics from any time period\n-
+    Modify tag configurations for metrics\n- View tags and volumes for metrics\n\n**Note**:
+    A graph can only contain a set number of points\nand as the timeframe over which
+    a metric is viewed increases,\naggregation between points occurs to stay below
+    that set number.\n\nThe Post, Patch, and Delete `manage_tags` API methods can
+    only be performed by\na user who has the `Manage Tags for Metrics` permission."
   name: Metrics
 - description: '[Monitors](https://docs.datadoghq.com/monitors) allow you to watch
-    a metric or check that you care about,
+    a metric or check that you care about and
+
+    notifies your team when a defined threshold has exceeded.
 
-    notifying your team when some defined threshold is exceeded.
 
-    Refer to the Creating Monitors page for more information on creating monitors.'
+    For more information, see [Creating Monitors](https://docs.datadoghq.com/monitors/monitor_types/).'
   externalDocs:
     description: Find out more at
     url: https://docs.datadoghq.com/monitors/monitor_types/
@@ -22837,11 +22785,11 @@ tags:
 
     [5]: https://docs.datadoghq.com/developers/service_checks/'
   name: Service Checks
-- description: "SLO Status Corrections allow you to prevent specific time periods\
-    \ from negatively impacting\nyour SLO\u2019s status and error budget. You can\
-    \ use Status Corrections for various purposes, such\nas removing planned maintenance\
-    \ windows, non-business hours, or other time periods that do\nnot correspond to\
-    \ genuine issues."
+- description: "SLO Status Corrections allow you to prevent specific time periods
+    from negatively impacting\nyour SLO\u2019s status and error budget. You can use
+    Status Corrections for various purposes, such\nas removing planned maintenance
+    windows, non-business hours, or other time periods that do\nnot correspond to
+    genuine issues."
   name: Service Level Objective Corrections
 - description: '[Service Level Objectives](https://docs.datadoghq.com/monitors/service_level_objectives/#configuration)
 
@@ -22865,12 +22813,12 @@ tags:
   name: Slack Integration
 - description: Take graph snapshots using the API.
   name: Snapshots
-- description: "Datadog Synthetics uses simulated user requests and browser rendering\
-    \ to help you ensure uptime,\nidentify regional issues, and track your application\
-    \ performance. Datadog Synthetics tests come in\ntwo different flavors, [API tests](https://docs.datadoghq.com/synthetics/api_tests/?tab=httptest)\n\
-    and [browser tests](https://docs.datadoghq.com/synthetics/browser_tests). You\
-    \ can use Datadog\u2019s API to\nmanage both test types programmatically.\n\n\
-    For more information about Synthetics, see the [Synthetics overview](https://docs.datadoghq.com/synthetics/)."
+- description: "Datadog Synthetics uses simulated user requests and browser rendering
+    to help you ensure uptime,\nidentify regional issues, and track your application
+    performance. Datadog Synthetics tests come in\ntwo different flavors, [API tests](https://docs.datadoghq.com/synthetics/api_tests/?tab=httptest)\nand
+    [browser tests](https://docs.datadoghq.com/synthetics/browser_tests). You can
+    use Datadog\u2019s API to\nmanage both test types programmatically.\n\nFor more
+    information about Synthetics, see the [Synthetics overview](https://docs.datadoghq.com/synthetics/)."
   name: Synthetics
 - description: 'The tag endpoint allows you to assign tags to hosts,