datadog_api_client 2.29.1 → 2.31.0

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

@@ -844,8 +844,15 @@ components:
             Only hosts that match one of the defined tags are imported into Datadog.'
           example: key:value,filter:example
           type: string
-        metrics_config:
-          $ref: '#/components/schemas/AzureAccountMetricsConfig'
+        metrics_enabled:
+          description: Enable Azure metrics for your organization.
+          example: true
+          type: boolean
+        metrics_enabled_default:
+          description: Enable Azure metrics for your organization for resource providers
+            where no resource provider config is specified.
+          example: true
+          type: boolean
         new_client_id:
           description: Your New Azure web application ID.
           example: new1c7f6-1234-5678-9101-3fcbf464test
@@ -860,37 +867,26 @@ components:
             monitored by this app registration.
           example: true
           type: boolean
+        resource_provider_configs:
+          description: Configuration settings applied to resources from the specified
+            Azure resource providers.
+          items:
+            $ref: '#/components/schemas/ResourceProviderConfig'
+          type: array
         tenant_name:
           description: Your Azure Active Directory ID.
           example: testc44-1234-5678-9101-cc00736ftest
           type: string
+        usage_metrics_enabled:
+          description: Enable azure.usage metrics for your organization.
+          example: true
+          type: boolean
       type: object
     AzureAccountListResponse:
       description: Accounts configured for your organization.
       items:
         $ref: '#/components/schemas/AzureAccount'
       type: array
-    AzureAccountMetricsConfig:
-      description: 'Dictionary containing the key `excluded_resource_providers` which
-        has to be a list of Microsoft Azure Resource Provider names.
-
-        This feature is currently being beta tested.
-
-        In order to enable all resource providers for metric collection, pass:
-
-        `metrics_config: {"excluded_resource_providers": []}` (i.e., an empty list
-        for `excluded_resource_providers`).'
-      properties:
-        excluded_resource_providers:
-          description: List of Microsoft Azure Resource Providers to exclude from
-            metric collection.
-          example:
-          - Microsoft.Sql
-          - Microsoft.Cdn
-          items:
-            type: string
-          type: array
-      type: object
     CancelDowntimesByScopeRequest:
       description: Cancel downtimes according to scope.
       properties:
@@ -1038,7 +1034,7 @@ components:
       example: {}
       properties:
         ok:
-          description: An array of of Monitor IDs that can be safely deleted.
+          description: An array of Monitor IDs that can be safely deleted.
           items:
             description: ID of a monitor that can be safely deleted.
             format: int64
@@ -1061,7 +1057,7 @@ components:
       description: An array of service level objective objects.
       properties:
         ok:
-          description: An array of of SLO IDs that can be safely deleted.
+          description: An array of SLO IDs that can be safely deleted.
           items:
             description: An SLO ID.
             type: string
@@ -1213,13 +1209,8 @@ components:
         reflow_type:
           $ref: '#/components/schemas/DashboardReflowType'
         restricted_roles:
-          deprecated: true
-          description: 'A list of role identifiers. Only the author and users associated
+          description: A list of role identifiers. Only the author and users associated
             with at least one of these roles can edit this dashboard.
-
-
-            This property is deprecated; please use the [Restriction Policies API](https://docs.datadoghq.com/api/latest/restriction-policies/)
-            instead to manage write authorization for individual dashboards.'
           items:
             description: A role UUID.
             type: string
@@ -1460,11 +1451,13 @@ components:
       enum:
       - open
       - invite
+      - embed
       nullable: true
       type: string
       x-enum-varnames:
       - OPEN
       - INVITE
+      - EMBED
     DashboardSummary:
       description: Dashboard summary response.
       properties:
@@ -5935,6 +5928,9 @@ components:
 
         Make sure to use an application key created by an admin.'
       properties:
+        description:
+          description: A description of the pipeline.
+          type: string
         filter:
           $ref: '#/components/schemas/LogsFilter'
         id:
@@ -5957,6 +5953,12 @@ components:
           items:
             $ref: '#/components/schemas/LogsProcessor'
           type: array
+        tags:
+          description: A list of tags associated with the pipeline.
+          items:
+            description: A single tag using the format `key:value`.
+            type: string
+          type: array
         type:
           description: Type of pipeline.
           example: pipeline
@@ -5966,7 +5968,7 @@ components:
       - name
       type: object
     LogsPipelineList:
-      description: Array of pipeline ID strings.
+      description: Array of all log pipeline objects configured for the organization.
       items:
         $ref: '#/components/schemas/LogsPipeline'
       type: array
@@ -6049,6 +6051,7 @@ components:
       - $ref: '#/components/schemas/LogsLookupProcessor'
       - $ref: '#/components/schemas/ReferenceTableLogsLookupProcessor'
       - $ref: '#/components/schemas/LogsTraceRemapper'
+      - $ref: '#/components/schemas/LogsSpanRemapper'
     LogsQueryCompute:
       description: Define computation for a log query.
       properties:
@@ -6160,6 +6163,43 @@ components:
       x-enum-varnames:
       - TIME_ASCENDING
       - TIME_DESCENDING
+    LogsSpanRemapper:
+      description: "There are two ways to define correlation between application spans
+        and logs:\n\n  1. Follow the documentation on [how to inject a span ID in
+        the application logs](https://docs.datadoghq.com/tracing/connect_logs_and_traces).\n
+        \ Log integrations automatically handle all remaining setup steps by default.\n\n
+        \ 2. Use the span remapper processor to define a log attribute as its associated
+        span ID."
+      properties:
+        is_enabled:
+          default: false
+          description: Whether or not the processor is enabled.
+          type: boolean
+        name:
+          description: Name of the processor.
+          type: string
+        sources:
+          default:
+          - dd.span_id
+          description: Array of source attributes.
+          items:
+            description: Attribute to extract the span ID from.
+            type: string
+          type: array
+        type:
+          $ref: '#/components/schemas/LogsSpanRemapperType'
+      required:
+      - type
+      type: object
+    LogsSpanRemapperType:
+      default: span-id-remapper
+      description: Type of logs span remapper.
+      enum:
+      - span-id-remapper
+      example: span-id-remapper
+      type: string
+      x-enum-varnames:
+      - SPAN_ID_REMAPPER
     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  -
@@ -6275,7 +6315,7 @@ components:
           - dd.trace_id
           description: Array of source attributes.
           items:
-            description: Attribute to extract the Trace ID from.
+            description: Attribute to extract the trace ID from.
             type: string
           type: array
         type:
@@ -6793,6 +6833,62 @@ components:
       - FIREFOX_LAPTOP_LARGE
       - FIREFOX_TABLET
       - FIREFOX_MOBILE_SMALL
+    MonitorFormulaAndFunctionCostAggregator:
+      description: Aggregation methods for metric queries.
+      enum:
+      - avg
+      - sum
+      - max
+      - min
+      - last
+      - area
+      - l2norm
+      - percentile
+      - stddev
+      example: avg
+      type: string
+      x-enum-varnames:
+      - AVG
+      - SUM
+      - MAX
+      - MIN
+      - LAST
+      - AREA
+      - L2NORM
+      - PERCENTILE
+      - STDDEV
+    MonitorFormulaAndFunctionCostDataSource:
+      description: Data source for cost queries.
+      enum:
+      - metrics
+      - cloud_cost
+      - datadog_usage
+      example: cloud_cost
+      type: string
+      x-enum-varnames:
+      - METRICS
+      - CLOUD_COST
+      - DATADOG_USAGE
+    MonitorFormulaAndFunctionCostQueryDefinition:
+      description: A formula and functions cost query.
+      properties:
+        aggregator:
+          $ref: '#/components/schemas/MonitorFormulaAndFunctionCostAggregator'
+        data_source:
+          $ref: '#/components/schemas/MonitorFormulaAndFunctionCostDataSource'
+        name:
+          description: Name of the query for use in formulas.
+          example: query1
+          type: string
+        query:
+          description: The monitor query.
+          example: sum:all.cost{*}.rollup(sum, 86400)
+          type: string
+      required:
+      - name
+      - data_source
+      - query
+      type: object
     MonitorFormulaAndFunctionEventAggregation:
       description: Aggregation methods for event platform queries.
       enum:
@@ -6943,6 +7039,7 @@ components:
       description: A formula and function query.
       oneOf:
       - $ref: '#/components/schemas/MonitorFormulaAndFunctionEventQueryDefinition'
+      - $ref: '#/components/schemas/MonitorFormulaAndFunctionCostQueryDefinition'
     MonitorGroupSearchResponse:
       description: The response of a monitor group search.
       example:
@@ -7342,7 +7439,7 @@ components:
       properties:
         day_starts:
           description: The time of the day at which a one day cumulative evaluation
-            window starts. Must be defined in UTC time in `HH:mm` format.
+            window starts.
           example: 04:00
           type: string
         hour_starts:
@@ -7361,6 +7458,11 @@ components:
           maximum: 1
           minimum: 1
           type: integer
+        timezone:
+          description: The timezone of the time of the day of the cumulative evaluation
+            window start.
+          example: Europe/Paris
+          type: string
       type: object
     MonitorOverallStates:
       description: The different states your monitor can be in.
@@ -7449,6 +7551,9 @@ components:
           - handle: jane@datadoghq.com
             name: Jane Doe
           org_id: 1234
+          quality_issues:
+          - broken_at_handle
+          - noisy_monitor
           scopes:
           - '!availability-zone:us-east-1c'
           - name:cassandra
@@ -7548,6 +7653,14 @@ components:
           format: int64
           readOnly: true
           type: integer
+        quality_issues:
+          description: Quality issues detected with the monitor.
+          items:
+            description: A quality issue detected with the monitor.
+            readOnly: true
+            type: string
+          readOnly: true
+          type: array
         query:
           description: The monitor query.
           example: avg(last_5m):sum:system.net.bytes_rcvd{host:host0} > 100
@@ -7764,6 +7877,7 @@ components:
       - error-tracking alert
       - database-monitoring alert
       - network-performance alert
+      - cost alert
       example: query alert
       type: string
       x-enum-varnames:
@@ -7785,6 +7899,7 @@ components:
       - ERROR_TRACKING_ALERT
       - DATABASE_MONITORING_ALERT
       - NETWORK_PERFORMANCE_ALERT
+      - COST_ALERT
     MonitorUpdateRequest:
       description: Object describing a monitor update request.
       properties:
@@ -7839,9 +7954,10 @@ components:
             be pulled from the [Roles API](https://docs.datadoghq.com/api/latest/roles/#list-roles)
             and are located in the `data.id` field. Editing a monitor includes any
             updates to the monitor configuration, monitor deletion, and muting of
-            the monitor for any amount of time. `restricted_roles` is the successor
-            of `locked`. For more information about `locked` and `restricted_roles`,
-            see the [monitor options docs](https://docs.datadoghq.com/monitors/guide/monitor_api_options/#permissions-options).
+            the monitor for any amount of time. You can use the [Restriction Policies
+            API](https://docs.datadoghq.com/api/latest/restriction-policies/) to manage
+            write authorization for individual monitors by teams and users, in addition
+            to roles.
           items:
             description: A role UUID.
             type: string
@@ -9667,6 +9783,62 @@ components:
       items:
         $ref: '#/components/schemas/NotifyEndType'
       type: array
+    NumberFormatUnit:
+      description: Number format unit.
+      oneOf:
+      - $ref: '#/components/schemas/NumberFormatUnitCanonical'
+      - $ref: '#/components/schemas/NumberFormatUnitCustom'
+    NumberFormatUnitCanonical:
+      description: Canonical unit.
+      properties:
+        per_unit_name:
+          description: The name of the unit per item.
+          example: bytes
+          type: string
+        type:
+          $ref: '#/components/schemas/NumberFormatUnitScaleType'
+        unit_name:
+          description: The name of the unit.
+          example: bytes
+          type: string
+      type: object
+    NumberFormatUnitCustom:
+      description: Custom unit.
+      properties:
+        label:
+          description: The label for the custom unit.
+          maxLength: 12
+          minLength: 1
+          type: string
+        type:
+          $ref: '#/components/schemas/NumberFormatUnitCustomType'
+      type: object
+    NumberFormatUnitCustomType:
+      description: The type of custom unit.
+      enum:
+      - custom_unit_label
+      type: string
+      x-enum-varnames:
+      - CUSTOM_UNIT_LABEL
+    NumberFormatUnitScale:
+      description: The definition of `NumberFormatUnitScale` object.
+      nullable: true
+      properties:
+        type:
+          $ref: '#/components/schemas/NumberFormatUnitScaleType'
+        unit_name:
+          description: The name of the unit.
+          example: bytes
+          type: string
+      type: object
+    NumberFormatUnitScaleType:
+      description: The type of unit scale.
+      enum:
+      - canonical_unit
+      example: canonical_unit
+      type: string
+      x-enum-varnames:
+      - CANONICAL_UNIT
     OnMissingDataOption:
       description: 'Controls how groups or monitors are treated if an evaluation does
         not return any data points.
@@ -10209,6 +10381,19 @@ components:
       - lookup_enrichment_table
       - type
       type: object
+    ResourceProviderConfig:
+      description: Configuration settings applied to resources from the specified
+        Azure resource provider.
+      properties:
+        metrics_enabled:
+          description: Collect metrics for resources from this provider.
+          example: true
+          type: boolean
+        namespace:
+          description: The provider namespace to apply this configuration to.
+          example: Microsoft.Compute
+          type: string
+      type: object
     ResponseMetaAttributes:
       description: Object describing meta attributes of response.
       properties:
@@ -10443,7 +10628,7 @@ components:
       description: A list of  SLO correction objects.
       properties:
         data:
-          description: The list of of SLO corrections objects.
+          description: The list of SLO corrections objects.
           items:
             $ref: '#/components/schemas/SLOCorrection'
           type: array
@@ -12880,7 +13065,7 @@ components:
       properties:
         author:
           $ref: '#/components/schemas/SharedDashboardAuthor'
-        created_at:
+        created:
           description: Date the dashboard was shared.
           format: date-time
           readOnly: true
@@ -12891,6 +13076,20 @@ components:
           type: string
         dashboard_type:
           $ref: '#/components/schemas/DashboardType'
+        embeddable_domains:
+          description: The `SharedDashboard` `embeddable_domains`.
+          example:
+          - https://domain.atlassian.net/
+          - http://myserver.com/
+          items:
+            description: The allowlisted referrers for an EMBED shared dashboard.
+            type: string
+          type: array
+        expiration:
+          description: The time when an OPEN shared dashboard becomes publicly unavailable.
+          format: date-time
+          nullable: true
+          type: string
         global_time:
           $ref: '#/components/schemas/DashboardGlobalTime'
         global_time_selectable_enabled:
@@ -12898,6 +13097,23 @@ components:
             setting for the shared dashboard.
           nullable: true
           type: boolean
+        invitees:
+          description: The `SharedDashboard` `invitees`.
+          example:
+          - access_expiration: '2030-01-01T12:00:00.00Z'
+            email: test@datadoghq.com
+          - access_expiration: null
+            email: test2@datadoghq.com
+          items:
+            $ref: '#/components/schemas/SharedDashboardInviteesItems'
+          type: array
+        last_accessed:
+          description: The last time the shared dashboard was accessed. Null if never
+            accessed.
+          format: date-time
+          nullable: true
+          readOnly: true
+          type: string
         public_url:
           description: URL of the shared dashboard.
           readOnly: true
@@ -12917,6 +13133,7 @@ components:
           nullable: true
           type: array
         share_list:
+          deprecated: true
           description: List of email addresses that can receive an invitation to access
             to the shared dashboard.
           example:
@@ -12930,10 +13147,17 @@ components:
           type: array
         share_type:
           $ref: '#/components/schemas/DashboardShareType'
+        status:
+          $ref: '#/components/schemas/SharedDashboardStatus'
+        title:
+          description: Title of the shared dashboard.
+          type: string
         token:
           description: A unique token assigned to the shared dashboard.
           readOnly: true
           type: string
+        viewing_preferences:
+          $ref: '#/components/schemas/ViewingPreferences'
       required:
       - dashboard_id
       - dashboard_type
@@ -12953,6 +13177,27 @@ components:
           type: string
       readOnly: true
       type: object
+    SharedDashboardInviteesItems:
+      description: The allowlisted invitees for an INVITE-only shared dashboard.
+      properties:
+        access_expiration:
+          description: Time of the invitee expiration. Null means the invite will
+            not expire.
+          format: date-time
+          nullable: true
+          type: string
+        created_at:
+          description: Time that the invitee was created.
+          format: date-time
+          readOnly: true
+          type: string
+        email:
+          description: Email of the invitee.
+          example: test@datadoghq.com
+          type: string
+      required:
+      - email
+      type: object
     SharedDashboardInvites:
       description: Invitations data and metadata that exists for a shared dashboard
         returned by the API.
@@ -13069,6 +13314,17 @@ components:
           format: int64
           type: integer
       type: object
+    SharedDashboardStatus:
+      description: Active means the dashboard is publicly available. Paused means
+        the dashboard is not publicly available.
+      enum:
+      - active
+      - paused
+      example: active
+      type: string
+      x-enum-varnames:
+      - ACTIVE
+      - PAUSED
     SharedDashboardUpdateRequest:
       description: Update a shared dashboard's settings.
       example:
@@ -13079,6 +13335,20 @@ components:
         - test2@datadoghq.com
         share_type: invite
       properties:
+        embeddable_domains:
+          description: The `SharedDashboard` `embeddable_domains`.
+          example:
+          - https://domain.atlassian.net/
+          - http://myserver.com/
+          items:
+            description: The allowlisted referrers for an EMBED shared dashboard.
+            type: string
+          type: array
+        expiration:
+          description: The time when an OPEN shared dashboard becomes publicly unavailable.
+          format: date-time
+          nullable: true
+          type: string
         global_time:
           $ref: '#/components/schemas/SharedDashboardUpdateRequestGlobalTime'
         global_time_selectable_enabled:
@@ -13086,6 +13356,16 @@ components:
             setting for the shared dashboard.
           nullable: true
           type: boolean
+        invitees:
+          description: The `SharedDashboard` `invitees`.
+          example:
+          - access_expiration: '2030-01-01T12:00:00.00Z'
+            email: test@datadoghq.com
+          - access_expiration: null
+            email: test2@datadoghq.com
+          items:
+            $ref: '#/components/schemas/SharedDashboardInviteesItems'
+          type: array
         selectable_template_vars:
           description: List of objects representing template variables on the shared
             dashboard which can have selectable values.
@@ -13101,6 +13381,7 @@ components:
           nullable: true
           type: array
         share_list:
+          deprecated: true
           description: List of email addresses that can be given access to the shared
             dashboard.
           example:
@@ -13114,8 +13395,13 @@ components:
           type: array
         share_type:
           $ref: '#/components/schemas/DashboardShareType'
-      required:
-      - global_time
+        status:
+          $ref: '#/components/schemas/SharedDashboardStatus'
+        title:
+          description: Title of the shared dashboard.
+          type: string
+        viewing_preferences:
+          $ref: '#/components/schemas/ViewingPreferences'
       type: object
     SharedDashboardUpdateRequestGlobalTime:
       description: Timeframe setting for the shared dashboard.
@@ -13758,6 +14044,9 @@ components:
           items:
             $ref: '#/components/schemas/SyntheticsParsingOptions'
           type: array
+        extractedValuesFromScript:
+          description: Generate variables using JavaScript.
+          type: string
         isCritical:
           description: 'Determines whether or not to consider the entire test as failed
             if this step fails.
@@ -14915,7 +15204,6 @@ components:
       - element
       - email
       - global
-      - javascript
       - text
       example: text
       type: string
@@ -14923,7 +15211,6 @@ components:
       - ELEMENT
       - EMAIL
       - GLOBAL
-      - JAVASCRIPT
       - TEXT
     SyntheticsCIBatchMetadata:
       description: Metadata for the Synthetic tests run.
@@ -15025,7 +15312,7 @@ components:
       description: Object describing the synthetics tests to trigger.
       properties:
         tests:
-          description: Individual synthetics test.
+          description: List of Synthetic tests with overrides.
           items:
             $ref: '#/components/schemas/SyntheticsCITest'
           type: array
@@ -15653,8 +15940,7 @@ components:
       description: User locator to find the element.
       properties:
         failTestOnCannotLocate:
-          description: Whether if the the test should fail if the element cannot be
-            found.
+          description: Whether if the test should fail if the element cannot be found.
           type: boolean
         values:
           description: Values of the user locator.
@@ -16265,6 +16551,9 @@ components:
         params:
           description: The parameters of the step.
           type: object
+        public_id:
+          description: The public ID of the step.
+          type: string
         timeout:
           description: The time before declaring a step failed.
           format: int64
@@ -17107,7 +17396,7 @@ components:
       description: Object describing the Synthetic tests to trigger.
       properties:
         tests:
-          description: Individual Synthetic test.
+          description: List of Synthetic tests.
           items:
             $ref: '#/components/schemas/SyntheticsTriggerTest'
           type: array
@@ -17267,11 +17556,13 @@ components:
       enum:
       - number
       - bar
+      - trend
       example: number
       type: string
       x-enum-varnames:
       - NUMBER
       - BAR
+      - TREND
     TableWidgetDefinition:
       description: The table visualization is available on timeboards and screenboards.
         It displays columns of metrics grouped by tag key.
@@ -19697,7 +19988,8 @@ components:
           format: int64
           type: integer
         avg_profiled_fargate_tasks:
-          description: The average profiled task count for Fargate Profiling.
+          description: The average total count for Fargate Container Profiler over
+            all hours in the current date for all organizations.
           format: int64
           type: integer
         aws_host_top99p:
@@ -19956,6 +20248,73 @@ components:
             over all hours in the current date for all organizations.
           format: int64
           type: integer
+        eph_infra_host_agent_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts with the
+            Datadog Agent over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_alibaba_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on Alibaba
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_aws_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on AWS
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_azure_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on Azure
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_ent_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts for Enterprise
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_gcp_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on GCP
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_heroku_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on Heroku
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_only_aas_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts with only
+            Azure App Services over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_only_vsphere_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts with only
+            vSphere over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_opentelemetry_apm_sum:
+          description: Shows the sum of all ephemeral APM hosts reported by the Datadog
+            exporter for the OpenTelemetry Collector over all hours in the current
+            date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_opentelemetry_sum:
+          description: Shows the sum of all ephemeral hosts reported by the Datadog
+            exporter for the OpenTelemetry Collector over all hours in the current
+            date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_pro_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts for Pro
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_proplus_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts for Pro
+            Plus over all hours in the current date for the given org.
+          format: int64
+          type: integer
         error_tracking_error_events_sum:
           description: Shows the sum of all Error Tracking error events over all hours
             in the current date for the given org.
@@ -19971,6 +20330,16 @@ components:
             hours in the current date for the given org.
           format: int64
           type: integer
+        fargate_container_profiler_profiling_fargate_avg:
+          description: The average number of Profiling Fargate tasks over all hours
+            in the current date for all organizations.
+          format: int64
+          type: integer
+        fargate_container_profiler_profiling_fargate_eks_avg:
+          description: The average number of Profiling Fargate Elastic Kubernetes
+            Service tasks over all hours in the current date for all organizations.
+          format: int64
+          type: integer
         fargate_tasks_count_avg:
           description: Shows the high-watermark of all Fargate tasks over all hours
             in the current date for all organizations.
@@ -20184,7 +20553,7 @@ components:
           type: integer
         profiling_host_top99p:
           description: Shows the 99th percentile of all profiled hosts over all hours
-            in the current date for all organizations.
+            within the current date for all organizations.
           format: int64
           type: integer
         rum_browser_and_mobile_session_count:
@@ -20273,10 +20642,25 @@ components:
           type: integer
         rum_mobile_lite_session_count_roku_sum:
           description: Shows the sum of all mobile RUM lite sessions on Roku over
-            all hours in the current date for all organizations (To be introduced
+            all hours within the current date for all organizations (To be introduced
             on October 1st, 2024).
           format: int64
           type: integer
+        rum_mobile_replay_session_count_android_sum:
+          description: Shows the sum of all mobile RUM replay sessions on Android
+            over all hours within the current date for the given org.
+          format: int64
+          type: integer
+        rum_mobile_replay_session_count_ios_sum:
+          description: Shows the sum of all mobile RUM replay sessions on iOS over
+            all hours within the current date for the given org.
+          format: int64
+          type: integer
+        rum_mobile_replay_session_count_reactnative_sum:
+          description: Shows the sum of all mobile RUM replay sessions on React Native
+            over all hours within the current date for the given org.
+          format: int64
+          type: integer
         rum_replay_session_count_sum:
           description: Shows the sum of all RUM Session Replay counts over all hours
             in the current date for all organizations (To be introduced on October
@@ -20468,7 +20852,8 @@ components:
           format: int64
           type: integer
         avg_profiled_fargate_tasks:
-          description: The average profiled task count for Fargate Profiling.
+          description: The average total count for Fargate Container Profiler over
+            all hours in the current month for the given org.
           format: int64
           type: integer
         aws_host_top99p:
@@ -20733,6 +21118,73 @@ components:
             queries over all hours in the current month for the given org.
           format: int64
           type: integer
+        eph_infra_host_agent_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts with the
+            Datadog Agent over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_alibaba_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on Alibaba
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_aws_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on AWS
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_azure_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on Azure
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_ent_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts for Enterprise
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_gcp_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on GCP
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_heroku_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on Heroku
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_only_aas_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts with only
+            Azure App Services over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_only_vsphere_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts with only
+            vSphere over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_opentelemetry_apm_sum:
+          description: Shows the sum of all ephemeral APM hosts reported by the Datadog
+            exporter for the OpenTelemetry Collector over all hours in the current
+            date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_opentelemetry_sum:
+          description: Shows the sum of all ephemeral hosts reported by the Datadog
+            exporter for the OpenTelemetry Collector over all hours in the current
+            date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_pro_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts for Pro
+            over all hours in the current date for the given org.
+          format: int64
+          type: integer
+        eph_infra_host_proplus_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts for Pro
+            Plus over all hours in the current date for the given org.
+          format: int64
+          type: integer
         error_tracking_error_events_sum:
           description: Shows the sum of all Error Tracking error events over all hours
             in the current date for the given org.
@@ -20748,6 +21200,16 @@ components:
             hours in the current date for the given org.
           format: int64
           type: integer
+        fargate_container_profiler_profiling_fargate_avg:
+          description: The average number of Profiling Fargate tasks over all hours
+            in the current month for the given org.
+          format: int64
+          type: integer
+        fargate_container_profiler_profiling_fargate_eks_avg:
+          description: The average number of Profiling Fargate Elastic Kubernetes
+            Service tasks over all hours in the current month for the given org.
+          format: int64
+          type: integer
         fargate_tasks_count_avg:
           description: The average task count for Fargate.
           format: int64
@@ -20959,7 +21421,7 @@ components:
           type: integer
         profiling_host_top99p:
           description: Shows the 99th percentile of all profiled hosts over all hours
-            in the current date for the given org.
+            within the current date for the given org.
           format: int64
           type: integer
         public_id:
@@ -21058,6 +21520,21 @@ components:
             1st, 2024).
           format: int64
           type: integer
+        rum_mobile_replay_session_count_android_sum:
+          description: Shows the sum of all mobile RUM replay sessions on Android
+            over all hours within the current date for the given org.
+          format: int64
+          type: integer
+        rum_mobile_replay_session_count_ios_sum:
+          description: Shows the sum of all mobile RUM replay sessions on iOS over
+            all hours within the current date for the given org.
+          format: int64
+          type: integer
+        rum_mobile_replay_session_count_reactnative_sum:
+          description: Shows the sum of all mobile RUM replay sessions on React Native
+            over all hours within the current date for the given org.
+          format: int64
+          type: integer
         rum_replay_session_count_sum:
           description: Shows the sum of all RUM Session Replay counts over all hours
             in the current date for the given org (To be introduced on October 1st,
@@ -21243,8 +21720,8 @@ components:
           format: int64
           type: integer
         avg_profiled_fargate_tasks_sum:
-          description: Shows the average of all profiled Fargate tasks over all hours
-            in the current month for all organizations.
+          description: The average total count for Fargate Container Profiler over
+            all hours in the current month for all organizations.
           format: int64
           type: integer
         aws_host_top99p_sum:
@@ -21453,9 +21930,8 @@ components:
           format: int64
           type: integer
         cspm_container_hwm_sum:
-          description: Shows the sum of the the high-water marks of Cloud Security
-            Management Pro containers over all hours in the current month for all
-            organizations.
+          description: Shows the sum of the high-water marks of Cloud Security Management
+            Pro containers over all hours in the current month for all organizations.
           format: int64
           type: integer
         cspm_gcp_host_top99p_sum:
@@ -21517,6 +21993,73 @@ components:
           description: Shows the last date of usage in the current month for all organizations.
           format: date-time
           type: string
+        eph_infra_host_agent_agg_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts with the
+            Datadog Agent over all hours in the current month for all organizations.
+          format: int64
+          type: integer
+        eph_infra_host_alibaba_agg_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on Alibaba
+            over all hours in the current month for all organizations.
+          format: int64
+          type: integer
+        eph_infra_host_aws_agg_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on AWS
+            over all hours in the current month for all organizations.
+          format: int64
+          type: integer
+        eph_infra_host_azure_agg_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on Azure
+            over all hours in the current month for all organizations.
+          format: int64
+          type: integer
+        eph_infra_host_ent_agg_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts for Enterprise
+            over all hours in the current month for all organizations.
+          format: int64
+          type: integer
+        eph_infra_host_gcp_agg_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on GCP
+            over all hours in the current month for all organizations.
+          format: int64
+          type: integer
+        eph_infra_host_heroku_agg_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts on Heroku
+            over all hours in the current month for all organizations.
+          format: int64
+          type: integer
+        eph_infra_host_only_aas_agg_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts with only
+            Azure App Services over all hours in the current month for all organizations.
+          format: int64
+          type: integer
+        eph_infra_host_only_vsphere_agg_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts with only
+            vSphere over all hours in the current month for all organizations.
+          format: int64
+          type: integer
+        eph_infra_host_opentelemetry_agg_sum:
+          description: Shows the sum of all ephemeral hosts reported by the Datadog
+            exporter for the OpenTelemetry Collector over all hours in the current
+            month for all organizations.
+          format: int64
+          type: integer
+        eph_infra_host_opentelemetry_apm_agg_sum:
+          description: Shows the sum of all ephemeral APM hosts reported by the Datadog
+            exporter for the OpenTelemetry Collector over all hours in the current
+            month for all organizations.
+          format: int64
+          type: integer
+        eph_infra_host_pro_agg_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts for Pro
+            over all hours in the current month for all organizations.
+          format: int64
+          type: integer
+        eph_infra_host_proplus_agg_sum:
+          description: Shows the sum of all ephemeral infrastructure hosts for Pro
+            Plus over all hours in the current month for all organizations.
+          format: int64
+          type: integer
         error_tracking_error_events_agg_sum:
           description: Shows the sum of all Error Tracking error events over all hours
             in the current month for all organizations.
@@ -21532,6 +22075,16 @@ components:
             hours in the current month for all organizations.
           format: int64
           type: integer
+        fargate_container_profiler_profiling_fargate_avg_sum:
+          description: The average number of Profiling Fargate tasks over all hours
+            in the current month for all organizations.
+          format: int64
+          type: integer
+        fargate_container_profiler_profiling_fargate_eks_avg_sum:
+          description: The average number of Profiling Fargate Elastic Kubernetes
+            Service tasks over all hours in the current month for all organizations.
+          format: int64
+          type: integer
         fargate_tasks_count_avg_sum:
           description: Shows the average of all Fargate tasks over all hours in the
             current month for all organizations.
@@ -21599,8 +22152,8 @@ components:
           format: int64
           type: integer
         incident_management_monthly_active_users_hwm_sum:
-          description: Shows sum of the the high-water marks of incident management
-            monthly active users in the current month for all organizations.
+          description: Shows sum of the high-water marks of incident management monthly
+            active users in the current month for all organizations.
           format: int64
           type: integer
         indexed_events_count_agg_sum:
@@ -21631,8 +22184,8 @@ components:
           format: int64
           type: integer
         last_updated:
-          description: Shows the the most recent hour in the current month for all
-            organizations for which all usages were calculated.
+          description: Shows the most recent hour in the current month for all organizations
+            for which all usages were calculated.
           format: date-time
           type: string
         live_indexed_events_agg_sum:
@@ -21869,10 +22422,25 @@ components:
           type: integer
         rum_mobile_lite_session_count_roku_agg_sum:
           description: Shows the sum of all mobile RUM lite sessions on Roku over
-            all hours in the current month for all organizations (To be introduced
+            all hours within the current month for all organizations (To be introduced
             on October 1st, 2024).
           format: int64
           type: integer
+        rum_mobile_replay_session_count_android_agg_sum:
+          description: Shows the sum of all mobile RUM replay sessions on Android
+            over all hours within the current month for all organizations.
+          format: int64
+          type: integer
+        rum_mobile_replay_session_count_ios_agg_sum:
+          description: Shows the sum of all mobile RUM replay sessions on iOS over
+            all hours within the current month for all organizations.
+          format: int64
+          type: integer
+        rum_mobile_replay_session_count_reactnative_agg_sum:
+          description: Shows the sum of all mobile RUM replay sessions on React Native
+            over all hours within the current month for all organizations.
+          format: int64
+          type: integer
         rum_replay_session_count_agg_sum:
           description: Shows the sum of all RUM Session Replay counts over all hours
             in the current month for all organizations (To be introduced on October
@@ -22261,8 +22829,31 @@ components:
     Version:
       description: Version of the updated signal. If server side version is higher,
         update will be rejected.
+      example: 0
       format: int64
       type: integer
+    ViewingPreferences:
+      description: The viewing preferences for a shared dashboard.
+      properties:
+        high_density:
+          description: Whether the widgets on the shared dashboard should be displayed
+            with high density.
+          type: boolean
+        theme:
+          $ref: '#/components/schemas/ViewingPreferencesTheme'
+      type: object
+    ViewingPreferencesTheme:
+      description: The theme of the shared dashboard view. "system" follows your system's
+        default viewing theme.
+      enum:
+      - system
+      - light
+      - dark
+      type: string
+      x-enum-varnames:
+      - SYSTEM
+      - LIGHT
+      - DARK
     WebhooksIntegration:
       description: Datadog-Webhooks integration.
       properties:
@@ -22682,6 +23273,8 @@ components:
           type: string
         cell_display_mode:
           $ref: '#/components/schemas/TableWidgetCellDisplayMode'
+        cell_display_mode_options:
+          $ref: '#/components/schemas/WidgetFormulaCellDisplayModeOptions'
         conditional_formats:
           description: List of conditional formats.
           items:
@@ -22693,11 +23286,44 @@ components:
           type: string
         limit:
           $ref: '#/components/schemas/WidgetFormulaLimit'
+        number_format:
+          $ref: '#/components/schemas/WidgetNumberFormat'
         style:
           $ref: '#/components/schemas/WidgetFormulaStyle'
       required:
       - formula
       type: object
+    WidgetFormulaCellDisplayModeOptions:
+      description: Cell display mode options for the widget formula. (only if `cell_display_mode`
+        is set to `trend`).
+      properties:
+        trend_type:
+          $ref: '#/components/schemas/WidgetFormulaCellDisplayModeOptionsTrendType'
+        y_scale:
+          $ref: '#/components/schemas/WidgetFormulaCellDisplayModeOptionsYScale'
+      type: object
+    WidgetFormulaCellDisplayModeOptionsTrendType:
+      description: Trend type for the cell display mode options.
+      enum:
+      - area
+      - line
+      - bars
+      example: area
+      type: string
+      x-enum-varnames:
+      - AREA
+      - LINE
+      - BARS
+    WidgetFormulaCellDisplayModeOptionsYScale:
+      description: Y scale for the cell display mode options.
+      enum:
+      - shared
+      - independent
+      example: shared
+      type: string
+      x-enum-varnames:
+      - SHARED
+      - INDEPENDENT
     WidgetFormulaLimit:
       description: Options for limiting results returned.
       properties:
@@ -23112,6 +23738,14 @@ components:
       x-enum-varnames:
       - HOST
       - CONTAINER
+    WidgetNumberFormat:
+      description: Number format options for the widget.
+      properties:
+        unit:
+          $ref: '#/components/schemas/NumberFormatUnit'
+        unit_scale:
+          $ref: '#/components/schemas/NumberFormatUnitScale'
+      type: object
     WidgetOrderBy:
       description: What to order by.
       enum:
@@ -23358,12 +23992,18 @@ components:
             continuous_profiler_pgo_read: Read and query Continuous Profiler data
               for Profile-Guided Optimization (PGO).
             create_webhooks: Create webhooks integrations.
+            dashboards_embed_share: Create, modify, and delete shared dashboards with
+              share type 'embed'.
+            dashboards_invite_share: Create, modify, and delete shared dashboards
+              with share type 'invite'.
             dashboards_public_share: Generate public and authenticated links to share
               dashboards or embeddable graphs externally.
             dashboards_read: View dashboards.
             dashboards_write: Create and change dashboards.
             data_scanner_read: View Data Scanner configurations.
             data_scanner_write: Edit Data Scanner configurations.
+            embeddable_graphs_share: Generate public links to share embeddable graphs
+              externally.
             events_read: Read Events data.
             hosts_read: List hosts and their attributes.
             incident_notification_settings_write: Configure Incidents Notification
@@ -23382,10 +24022,15 @@ components:
               configuring allowed login methods, creating child orgs, subscribing
               & unsubscribing from apps in the marketplace, and enabling & disabling
               Remote Configuration for the entire organization.
+            security_comments_read: Read comments of vulnerabilities.
             security_monitoring_filters_read: Read Security Filters.
             security_monitoring_filters_write: Create, edit, and delete Security Filters.
             security_monitoring_findings_read: View a list of findings that include
               both misconfigurations and identity risks.
+            security_monitoring_notification_profiles_read: View Rule Security Notification
+              rules.
+            security_monitoring_notification_profiles_write: Create, edit, and delete
+              Security Notification rules.
             security_monitoring_rules_read: Read Detection Rules.
             security_monitoring_rules_write: Create and edit Detection Rules.
             security_monitoring_signals_read: View Security Signals.
@@ -23413,7 +24058,7 @@ components:
               Access Manage permission.
             teams_read: Read Teams data. A User with this permission can view Team
               names, metadata, and which Users are on each Team.
-            test_visibility_read: View Test Visibility.
+            test_optimization_read: View Test Optimization.
             timeseries_query: Query Timeseries data.
             usage_read: View your organization's usage and usage attribution.
             user_access_invite: Invite other users to your organization.
@@ -23452,8 +24097,6 @@ components:
       x-auth-id-alias: appKeyAuth
       x-env-name: DD_APP_KEY
     bearerAuth:
-      in: header
-      name: Authorization
       scheme: bearer
       type: http
       x-env-name: DD_BEARER_TOKEN
@@ -27997,8 +28640,9 @@ paths:
       tags:
       - Logs Indexes
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     put:
       description: 'This endpoint updates the index order of your organization.
 
@@ -28070,8 +28714,9 @@ paths:
       tags:
       - Logs Indexes
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     post:
       description: Creates a new index. Returns the Index object passed in the request
         body when the request is successful.
@@ -28113,6 +28758,43 @@ paths:
         permissions:
         - logs_modify_indexes
   /api/v1/logs/config/indexes/{name}:
+    delete:
+      description: 'Delete an existing index from your organization. Index deletions
+        are permanent and cannot be reverted.
+
+        You cannot recreate an index with the same name as deleted ones.'
+      operationId: DeleteLogsIndex
+      parameters:
+      - description: Name of the log index.
+        in: path
+        name: name
+        required: true
+        schema:
+          type: string
+      responses:
+        '200':
+          description: OK
+        '403':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Forbidden
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LogsAPIErrorResponse'
+          description: Not Found
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      summary: Delete an index
+      tags:
+      - Logs Indexes
+      x-permission:
+        operator: OR
+        permissions:
+        - logs_modify_indexes
     get:
       description: Get one log index from your organization. This endpoint takes no
         JSON arguments.
@@ -28148,6 +28830,10 @@ paths:
       summary: Get an index
       tags:
       - Logs Indexes
+      x-permission:
+        operator: OR
+        permissions:
+        - logs_read_config
     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
@@ -28222,8 +28908,9 @@ paths:
       tags:
       - Logs Pipelines
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     put:
       description: 'Update the order of your pipelines. Since logs are processed sequentially,
         reordering a pipeline may change
@@ -28304,8 +28991,9 @@ paths:
       tags:
       - Logs Pipelines
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     post:
       description: Create a pipeline in your organization.
       operationId: CreateLogsPipeline
@@ -28419,8 +29107,9 @@ paths:
       tags:
       - Logs Pipelines
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     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
@@ -28633,13 +29322,13 @@ paths:
         - metrics_metadata_write
   /api/v1/monitor:
     get:
-      description: Get details about the specified monitor from your organization.
+      description: Get all monitors from your organization.
       operationId: ListMonitors
       parameters:
       - description: 'When specified, shows additional information about the group
           states.
 
-          Choose one or more from `all`, `alert`, `warn`, and `no data`.'
+          Choose one or more from `all`, `alert`, `warn`, and `no data` (`no%20data`).'
         in: query
         name: group_states
         required: false
@@ -28716,6 +29405,7 @@ paths:
           content:
             application/json:
               schema:
+                description: An array of monitor objects.
                 items:
                   $ref: '#/components/schemas/Monitor'
                 type: array
@@ -28739,7 +29429,7 @@ paths:
         appKeyAuth: []
       - AuthZ:
         - monitors_read
-      summary: Get all monitor details
+      summary: Get all monitors
       tags:
       - Monitors
       x-pagination:
@@ -28750,399 +29440,150 @@ paths:
         permissions:
         - monitors_read
     post:
-      description: 'Create a monitor using the specified options.
-
-
-        #### Monitor Types
-
-
-        The type of monitor chosen from:
-
-
-        - anomaly: `query alert`
-
-        - APM: `query alert` or `trace-analytics alert`
-
-        - composite: `composite`
-
-        - custom: `service check`
-
-        - forecast: `query alert`
-
-        - host: `service check`
-
-        - integration: `query alert` or `service check`
-
-        - live process: `process alert`
-
-        - logs: `log alert`
-
-        - metric: `query alert`
-
-        - network: `service check`
-
-        - outlier: `query alert`
-
-        - process: `service check`
-
-        - rum: `rum alert`
-
-        - SLO: `slo alert`
-
-        - watchdog: `event-v2 alert`
-
-        - event-v2: `event-v2 alert`
-
-        - audit: `audit alert`
-
-        - error-tracking: `error-tracking alert`
-
-        - database-monitoring: `database-monitoring alert`
-
-        - network-performance: `network-performance alert`
-
-        - cloud cost: `cost alert`
-
-
-        **Notes**:
-
-        - Synthetic monitors are created through the Synthetics API. See the [Synthetics
-        API](https://docs.datadoghq.com/api/latest/synthetics/) documentation for
-        more information.
-
-        - Log monitors require an unscoped App Key.
-
-
-        #### Query Types
-
-
-        ##### Metric Alert Query
-
-
-        Example: `time_aggr(time_window):space_aggr:metric{tags} [by {key}] operator
-        #`
-
-
-        - `time_aggr`: avg, sum, max, min, change, or pct_change
-
-        - `time_window`: `last_#m` (with `#` between 1 and 10080 depending on the
-        monitor type) or `last_#h`(with `#` between 1 and 168 depending on the monitor
-        type) or `last_1d`, or `last_1w`
-
-        - `space_aggr`: avg, sum, min, or max
-
-        - `tags`: one or more tags (comma-separated), or *
-
-        - `key`: a ''key'' in key:value tag syntax; defines a separate alert for each
-        tag in the group (multi-alert)
-
-        - `operator`: <, <=, >, >=, ==, or !=
-
-        - `#`: an integer or decimal number used to set the threshold
-
-
-        If you are using the `_change_` or `_pct_change_` time aggregator, instead
-        use `change_aggr(time_aggr(time_window),
-
-        timeshift):space_aggr:metric{tags} [by {key}] operator #` with:
-
-
-        - `change_aggr` change, pct_change
-
-        - `time_aggr` avg, sum, max, min [Learn more](https://docs.datadoghq.com/monitors/create/types/#define-the-conditions)
-
-        - `time_window` last\_#m (between 1 and 2880 depending on the monitor type),
-        last\_#h (between 1 and 48 depending on the monitor type), or last_#d (1 or
-        2)
-
-        - `timeshift` #m_ago (5, 10, 15, or 30), #h_ago (1, 2, or 4), or 1d_ago
-
-
-        Use this to create an outlier monitor using the following query:
-
-        `avg(last_30m):outliers(avg:system.cpu.user{role:es-events-data} by {host},
-        ''dbscan'', 7) > 0`
-
-
-        ##### Service Check Query
-
-
-        Example: `"check".over(tags).last(count).by(group).count_by_status()`
-
-
-        - `check` name of the check, for example `datadog.agent.up`
-
-        - `tags` one or more quoted tags (comma-separated), or "*". for example: `.over("env:prod",
-        "role:db")`; `over` cannot be blank.
-
-        - `count` must be at greater than or equal to your max threshold (defined
-        in the `options`). It is limited to 100.
-
-        For example, if you''ve specified to notify on 1 critical, 3 ok, and 2 warn
-        statuses, `count` should be at least 3.
-
-        - `group` must be specified for check monitors. Per-check grouping is already
-        explicitly known for some service checks.
-
-        For example, Postgres integration monitors are tagged by `db`, `host`, and
-        `port`, and Network monitors by `host`, `instance`, and `url`. See [Service
-        Checks](https://docs.datadoghq.com/api/latest/service-checks/) documentation
-        for more information.
-
-
-        ##### Event Alert Query
-
-
-        **Note:** The Event Alert Query has been replaced by the Event V2 Alert Query.
-        For more information, see the [Event Migration guide](https://docs.datadoghq.com/service_management/events/guides/migrating_to_new_events_features/).
-
-
-        ##### Event V2 Alert Query
-
-
-        Example: `events(query).rollup(rollup_method[, measure]).last(time_window)
-        operator #`
-
-
-        - `query` The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).
-
-        - `rollup_method` The stats roll-up method - supports `count`, `avg` and `cardinality`.
-
-        - `measure` For `avg` and cardinality `rollup_method` - specify the measure
-        or the facet name you want to use.
-
-        - `time_window` #m (between 1 and 2880), #h (between 1 and 48).
-
-        - `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.
-
-        - `#` an integer or decimal number used to set the threshold.
-
-
-        ##### Process Alert Query
-
-
-        Example: `processes(search).over(tags).rollup(''count'').last(timeframe) operator
-        #`
-
-
-        - `search` free text search string for querying processes.
-
-        Matching processes match results on the [Live Processes](https://docs.datadoghq.com/infrastructure/process/?tab=linuxwindows)
-        page.
-
-        - `tags` one or more tags (comma-separated)
-
-        - `timeframe` the timeframe to roll up the counts. Examples: 10m, 4h. Supported
-        timeframes: s, m, h and d
-
-        - `operator` <, <=, >, >=, ==, or !=
-
-        - `#` an integer or decimal number used to set the threshold
-
-
-        ##### Logs Alert Query
-
-
-        Example: `logs(query).index(index_name).rollup(rollup_method[, measure]).last(time_window)
-        operator #`
-
-
-        - `query` The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).
-
-        - `index_name` For multi-index organizations, the log index in which the request
-        is performed.
-
-        - `rollup_method` The stats roll-up method - supports `count`, `avg` and `cardinality`.
-
-        - `measure` For `avg` and cardinality `rollup_method` - specify the measure
-        or the facet name you want to use.
-
-        - `time_window` #m (between 1 and 2880), #h (between 1 and 48).
-
-        - `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.
-
-        - `#` an integer or decimal number used to set the threshold.
-
-
-        ##### Composite Query
-
-
-        Example: `12345 && 67890`, where `12345` and `67890` are the IDs of non-composite
-        monitors
-
-
-        * `name` [*required*, *default* = **dynamic, based on query**]: The name of
-        the alert.
-
-        * `message` [*required*, *default* = **dynamic, based on query**]: A message
-        to include with notifications for this monitor.
-
-        Email notifications can be sent to specific users by using the same ''@username''
-        notation as events.
-
-        * `tags` [*optional*, *default* = **empty list**]: A list of tags to associate
-        with your monitor.
-
-        When getting all monitor details via the API, use the `monitor_tags` argument
-        to filter results by these tags.
-
-        It is only available via the API and isn''t visible or editable in the Datadog
-        UI.
-
-
-        ##### SLO Alert Query
-
-
-        Example: `error_budget("slo_id").over("time_window") operator #`
-
-
-        - `slo_id`: The alphanumeric SLO ID of the SLO you are configuring the alert
-        for.
-
-        - `time_window`: The time window of the SLO target you wish to alert on. Valid
-        options: `7d`, `30d`, `90d`.
-
-        - `operator`: `>=` or `>`
-
-
-        ##### Audit Alert Query
-
-
-        Example: `audits(query).rollup(rollup_method[, measure]).last(time_window)
-        operator #`
-
-
-        - `query` The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).
-
-        - `rollup_method` The stats roll-up method - supports `count`, `avg` and `cardinality`.
-
-        - `measure` For `avg` and cardinality `rollup_method` - specify the measure
-        or the facet name you want to use.
-
-        - `time_window` #m (between 1 and 2880), #h (between 1 and 48).
-
-        - `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.
-
-        - `#` an integer or decimal number used to set the threshold.
-
-
-        ##### CI Pipelines Alert Query
-
-
-        Example: `ci-pipelines(query).rollup(rollup_method[, measure]).last(time_window)
-        operator #`
-
-
-        - `query` The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).
-
-        - `rollup_method` The stats roll-up method - supports `count`, `avg`, and
-        `cardinality`.
-
-        - `measure` For `avg` and cardinality `rollup_method` - specify the measure
-        or the facet name you want to use.
-
-        - `time_window` #m (between 1 and 2880), #h (between 1 and 48).
-
-        - `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.
-
-        - `#` an integer or decimal number used to set the threshold.
-
-
-        ##### 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.
-
-
-        ##### Error Tracking Alert Query
-
-
-        "New issue" example: `error-tracking(query).source(issue_source).new().rollup(rollup_method[,
-        measure]).by(group_by).last(time_window) operator #`
-
-        "High impact issue" example: `error-tracking(query).source(issue_source).impact().rollup(rollup_method[,
-        measure]).by(group_by).last(time_window) operator #`
-
-
-        - `query` The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).
-
-        - `issue_source` The issue source - supports `all`, `browser`, `mobile` and
-        `backend` and defaults to `all` if omitted.
-
-        - `rollup_method` The stats roll-up method - supports `count`, `avg`, and
-        `cardinality` and defaults to `count` if omitted.
-
-        - `measure` For `avg` and cardinality `rollup_method` - specify the measure
-        or the facet name you want to use.
-
-        - `group by` Comma-separated list of attributes to group by - should contain
-        at least `issue.id`.
-
-        - `time_window` #m (between 1 and 2880), #h (between 1 and 48).
-
-        - `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.
-
-        - `#` an integer or decimal number used to set the threshold.
-
-
-        **Database Monitoring Alert Query**
-
-
-        Example: `database-monitoring(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.
-
-
-        **Network Performance Alert Query**
-
-
-        Example: `network-performance(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.'
+      description: "Create a monitor using the specified options.\n\n#### Monitor
+        Types\n\nThe type of monitor chosen from:\n\n- anomaly: `query alert`\n- APM:
+        `query alert` or `trace-analytics alert`\n- composite: `composite`\n- custom:
+        `service check`\n- forecast: `query alert`\n- host: `service check`\n- integration:
+        `query alert` or `service check`\n- live process: `process alert`\n- logs:
+        `log alert`\n- metric: `query alert`\n- network: `service check`\n- outlier:
+        `query alert`\n- process: `service check`\n- rum: `rum alert`\n- SLO: `slo
+        alert`\n- watchdog: `event-v2 alert`\n- event-v2: `event-v2 alert`\n- audit:
+        `audit alert`\n- error-tracking: `error-tracking alert`\n- database-monitoring:
+        `database-monitoring alert`\n- network-performance: `network-performance alert`\n-
+        cloud cost: `cost alert`\n\n**Notes**:\n- Synthetic monitors are created through
+        the Synthetics API. See the [Synthetics API](https://docs.datadoghq.com/api/latest/synthetics/)
+        documentation for more information.\n- Log monitors require an unscoped App
+        Key.\n\n#### Query Types\n\n##### Metric Alert Query\n\nExample: `time_aggr(time_window):space_aggr:metric{tags}
+        [by {key}] operator #`\n\n- `time_aggr`: avg, sum, max, min, change, or pct_change\n-
+        `time_window`: `last_#m` (with `#` between 1 and 10080 depending on the monitor
+        type) or `last_#h`(with `#` between 1 and 168 depending on the monitor type)
+        or `last_1d`, or `last_1w`\n- `space_aggr`: avg, sum, min, or max\n- `tags`:
+        one or more tags (comma-separated), or *\n- `key`: a 'key' in key:value tag
+        syntax; defines a separate alert for each tag in the group (multi-alert)\n-
+        `operator`: <, <=, >, >=, ==, or !=\n- `#`: an integer or decimal number used
+        to set the threshold\n\nIf you are using the `_change_` or `_pct_change_`
+        time aggregator, instead use `change_aggr(time_aggr(time_window),\ntimeshift):space_aggr:metric{tags}
+        [by {key}] operator #` with:\n\n- `change_aggr` change, pct_change\n- `time_aggr`
+        avg, sum, max, min [Learn more](https://docs.datadoghq.com/monitors/create/types/#define-the-conditions)\n-
+        `time_window` last\\_#m (between 1 and 2880 depending on the monitor type),
+        last\\_#h (between 1 and 48 depending on the monitor type), or last_#d (1
+        or 2)\n- `timeshift` #m_ago (5, 10, 15, or 30), #h_ago (1, 2, or 4), or 1d_ago\n\nUse
+        this to create an outlier monitor using the following query:\n`avg(last_30m):outliers(avg:system.cpu.user{role:es-events-data}
+        by {host}, 'dbscan', 7) > 0`\n\n##### Service Check Query\n\nExample: `\"check\".over(tags).last(count).by(group).count_by_status()`\n\n-
+        `check` name of the check, for example `datadog.agent.up`\n- `tags` one or
+        more quoted tags (comma-separated), or \"*\". for example: `.over(\"env:prod\",
+        \"role:db\")`; `over` cannot be blank.\n- `count` must be at greater than
+        or equal to your max threshold (defined in the `options`). It is limited to
+        100.\nFor example, if you've specified to notify on 1 critical, 3 ok, and
+        2 warn statuses, `count` should be at least 3.\n- `group` must be specified
+        for check monitors. Per-check grouping is already explicitly known for some
+        service checks.\nFor example, Postgres integration monitors are tagged by
+        `db`, `host`, and `port`, and Network monitors by `host`, `instance`, and
+        `url`. See [Service Checks](https://docs.datadoghq.com/api/latest/service-checks/)
+        documentation for more information.\n\n##### Event Alert Query\n\n**Note:**
+        The Event Alert Query has been replaced by the Event V2 Alert Query. For more
+        information, see the [Event Migration guide](https://docs.datadoghq.com/service_management/events/guides/migrating_to_new_events_features/).\n\n#####
+        Event V2 Alert Query\n\nExample: `events(query).rollup(rollup_method[, measure]).last(time_window)
+        operator #`\n\n- `query` The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).\n-
+        `rollup_method` The stats roll-up method - supports `count`, `avg` and `cardinality`.\n-
+        `measure` For `avg` and cardinality `rollup_method` - specify the measure
+        or the facet name you want to use.\n- `time_window` #m (between 1 and 2880),
+        #h (between 1 and 48).\n- `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.\n-
+        `#` an integer or decimal number used to set the threshold.\n\n##### Process
+        Alert Query\n\nExample: `processes(search).over(tags).rollup('count').last(timeframe)
+        operator #`\n\n- `search` free text search string for querying processes.\nMatching
+        processes match results on the [Live Processes](https://docs.datadoghq.com/infrastructure/process/?tab=linuxwindows)
+        page.\n- `tags` one or more tags (comma-separated)\n- `timeframe` the timeframe
+        to roll up the counts. Examples: 10m, 4h. Supported timeframes: s, m, h and
+        d\n- `operator` <, <=, >, >=, ==, or !=\n- `#` an integer or decimal number
+        used to set the threshold\n\n##### Logs Alert Query\n\nExample: `logs(query).index(index_name).rollup(rollup_method[,
+        measure]).last(time_window) operator #`\n\n- `query` The search query - following
+        the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).\n-
+        `index_name` For multi-index organizations, the log index in which the request
+        is performed.\n- `rollup_method` The stats roll-up method - supports `count`,
+        `avg` and `cardinality`.\n- `measure` For `avg` and cardinality `rollup_method`
+        - specify the measure or the facet name you want to use.\n- `time_window`
+        #m (between 1 and 2880), #h (between 1 and 48).\n- `operator` `<`, `<=`, `>`,
+        `>=`, `==`, or `!=`.\n- `#` an integer or decimal number used to set the threshold.\n\n#####
+        Composite Query\n\nExample: `12345 && 67890`, where `12345` and `67890` are
+        the IDs of non-composite monitors\n\n* `name` [*required*, *default* = **dynamic,
+        based on query**]: The name of the alert.\n* `message` [*required*, *default*
+        = **dynamic, based on query**]: A message to include with notifications for
+        this monitor.\nEmail notifications can be sent to specific users by using
+        the same '@username' notation as events.\n* `tags` [*optional*, *default*
+        = **empty list**]: A list of tags to associate with your monitor.\nWhen getting
+        all monitor details via the API, use the `monitor_tags` argument to filter
+        results by these tags.\nIt is only available via the API and isn't visible
+        or editable in the Datadog UI.\n\n##### SLO Alert Query\n\nExample: `error_budget(\"slo_id\").over(\"time_window\")
+        operator #`\n\n- `slo_id`: The alphanumeric SLO ID of the SLO you are configuring
+        the alert for.\n- `time_window`: The time window of the SLO target you wish
+        to alert on. Valid options: `7d`, `30d`, `90d`.\n- `operator`: `>=` or `>`\n\n#####
+        Audit Alert Query\n\nExample: `audits(query).rollup(rollup_method[, measure]).last(time_window)
+        operator #`\n\n- `query` The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).\n-
+        `rollup_method` The stats roll-up method - supports `count`, `avg` and `cardinality`.\n-
+        `measure` For `avg` and cardinality `rollup_method` - specify the measure
+        or the facet name you want to use.\n- `time_window` #m (between 1 and 2880),
+        #h (between 1 and 48).\n- `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.\n-
+        `#` an integer or decimal number used to set the threshold.\n\n##### CI Pipelines
+        Alert Query\n\nExample: `ci-pipelines(query).rollup(rollup_method[, measure]).last(time_window)
+        operator #`\n\n- `query` The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).\n-
+        `rollup_method` The stats roll-up method - supports `count`, `avg`, and `cardinality`.\n-
+        `measure` For `avg` and cardinality `rollup_method` - specify the measure
+        or the facet name you want to use.\n- `time_window` #m (between 1 and 2880),
+        #h (between 1 and 48).\n- `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.\n-
+        `#` an integer or decimal number used to set the threshold.\n\n##### CI Tests
+        Alert Query\n\nExample: `ci-tests(query).rollup(rollup_method[, measure]).last(time_window)
+        operator #`\n\n- `query` The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).\n-
+        `rollup_method` The stats roll-up method - supports `count`, `avg`, and `cardinality`.\n-
+        `measure` For `avg` and cardinality `rollup_method` - specify the measure
+        or the facet name you want to use.\n- `time_window` #m (between 1 and 2880),
+        #h (between 1 and 48).\n- `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.\n-
+        `#` an integer or decimal number used to set the threshold.\n\n##### Error
+        Tracking Alert Query\n\n\"New issue\" example: `error-tracking(query).source(issue_source).new().rollup(rollup_method[,
+        measure]).by(group_by).last(time_window) operator #`\n\"High impact issue\"
+        example: `error-tracking(query).source(issue_source).impact().rollup(rollup_method[,
+        measure]).by(group_by).last(time_window) operator #`\n\n- `query` The search
+        query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).\n-
+        `issue_source` The issue source - supports `all`, `browser`, `mobile` and
+        `backend` and defaults to `all` if omitted.\n- `rollup_method` The stats roll-up
+        method - supports `count`, `avg`, and `cardinality` and defaults to `count`
+        if omitted.\n- `measure` For `avg` and cardinality `rollup_method` - specify
+        the measure or the facet name you want to use.\n- `group by` Comma-separated
+        list of attributes to group by - should contain at least `issue.id`.\n- `time_window`
+        #m (between 1 and 2880), #h (between 1 and 48).\n- `operator` `<`, `<=`, `>`,
+        `>=`, `==`, or `!=`.\n- `#` an integer or decimal number used to set the threshold.\n\n**Database
+        Monitoring Alert Query**\n\nExample: `database-monitoring(query).rollup(rollup_method[,
+        measure]).last(time_window) operator #`\n\n- `query` The search query - following
+        the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).\n-
+        `rollup_method` The stats roll-up method - supports `count`, `avg`, and `cardinality`.\n-
+        `measure` For `avg` and cardinality `rollup_method` - specify the measure
+        or the facet name you want to use.\n- `time_window` #m (between 1 and 2880),
+        #h (between 1 and 48).\n- `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.\n-
+        `#` an integer or decimal number used to set the threshold.\n\n**Network Performance
+        Alert Query**\n\nExample: `network-performance(query).rollup(rollup_method[,
+        measure]).last(time_window) operator #`\n\n- `query` The search query - following
+        the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).\n-
+        `rollup_method` The stats roll-up method - supports `count`, `avg`, and `cardinality`.\n-
+        `measure` For `avg` and cardinality `rollup_method` - specify the measure
+        or the facet name you want to use.\n- `time_window` #m (between 1 and 2880),
+        #h (between 1 and 48).\n- `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.\n-
+        `#` an integer or decimal number used to set the threshold.\n\n**Cost Alert
+        Query**\n\nExample: `formula(query).timeframe_type(time_window).function(parameter)
+        operator #`\n\n- `query` The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).\n-
+        `timeframe_type` The timeframe type to evaluate the cost\n        - for `forecast`
+        supports `current`\n        - for `change`, `anomaly`, `threshold` supports
+        `last`\n- `time_window` - supports daily roll-up e.g. `7d`\n- `function` -
+        [optional, defaults to `threshold` monitor if omitted] supports `change`,
+        `anomaly`, `forecast`\n- `parameter` Specify the parameter of the type\n    -
+        for `change`:\n        - supports `relative`, `absolute`\n        - [optional]
+        supports `#`, where `#` is an integer or decimal number used to set the threshold\n
+        \   - for `anomaly`:\n        - supports `direction=both`, `direction=above`,
+        `direction=below`\n        - [optional] supports `threshold=#`, where `#`
+        is an integer or decimal number used to set the threshold\n- `operator`\n
+        \   - for `threshold` supports `<`, `<=`, `>`, `>=`, `==`, or `!=`\n    -
+        for `change` supports `>`, `<`\n    - for `anomaly` supports `>=`\n    - for
+        `forecast` supports `>`\n- `#` an integer or decimal number used to set the
+        threshold."
       operationId: CreateMonitor
       requestBody:
         content:
@@ -36425,10 +36866,17 @@ tags:
     end times, prevent all alerting related to specified Datadog tags.'
   name: Downtimes
 - description: 'The Event Management API allows you to programmatically post events
-    to the Events Explorer
+    to the Events Explorer and fetch events from the Events Explorer. See the [Event
+    Management page](https://docs.datadoghq.com/service_management/events/) for more
+    information.
 
-    and fetch events from the Events Explorer. See the [Event Management page](https://docs.datadoghq.com/service_management/events/)
-    for more information.'
+
+    **Update to Datadog monitor events `aggregation_key` starting March 1, 2025:**
+    The Datadog monitor events `aggregation_key` is unique to each Monitor ID. Starting
+    March 1st, this key will also include Monitor Group, making it unique per *Monitor
+    ID and Monitor Group*. If you''re using monitor events `aggregation_key` in dashboard
+    queries or the Event API, you must migrate to use `@monitor.id`. Reach out to
+    [support](https://www.datadoghq.com/support/) if you have any question.'
   name: Events
 - description: 'Configure your Datadog-Google Cloud Platform (GCP) integration directly
 
@@ -36457,10 +36905,7 @@ tags:
 - description: Search your logs and send them to your Datadog platform over HTTP.
     See the [Log Management page](https://docs.datadoghq.com/logs/) for more information.
   name: Logs
-- description: 'Manage configuration of [log indexes](https://docs.datadoghq.com/logs/indexes/).
-
-    You need an API and non-scoped application key with Admin rights to interact with
-    these endpoints.'
+- description: Manage configuration of [log indexes](https://docs.datadoghq.com/logs/indexes/).
   externalDocs:
     description: Find out more at
     url: https://docs.datadoghq.com/logs/indexes/
@@ -36470,14 +36915,12 @@ tags:
     page](https://app.datadoghq.com/logs/pipelines)\n  for a list of the pipelines
     and processors currently configured in web UI.\n\n- Additional API-related information
     about processors can be found in the\n  [processors documentation](https://docs.datadoghq.com/logs/log_configuration/processors/?tab=api#lookup-processor).\n\n-
-    For more information about Pipelines, see the\n  [pipeline documentation](https://docs.datadoghq.com/logs/log_configuration/pipelines).\n\n**Notes:**\n\nThese
-    endpoints are only available for admin users.\nMake sure to use an application
-    key created by an admin with no applied scopes.\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."
+    For more information about Pipelines, see the\n  [pipeline documentation](https://docs.datadoghq.com/logs/log_configuration/pipelines).\n\n**Notes:**\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/log_configuration