RubyGems - datadog_api_client - Versions diffs - 2.29.1 → 2.30.0 - Mend

datadog_api_client 2.29.1 → 2.30.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (325) hide show

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

@@ -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:
@@ -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
@@ -5935,6 +5926,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 +5951,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 +5966,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
@@ -6793,6 +6793,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 +6999,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:
@@ -7764,6 +7821,7 @@ components:
       - error-tracking alert
       - database-monitoring alert
       - network-performance alert
+      - cost alert
       example: query alert
       type: string
       x-enum-varnames:
@@ -7785,6 +7843,7 @@ components:
       - ERROR_TRACKING_ALERT
       - DATABASE_MONITORING_ALERT
       - NETWORK_PERFORMANCE_ALERT
+      - COST_ALERT
     MonitorUpdateRequest:
       description: Object describing a monitor update request.
       properties:
@@ -7839,9 +7898,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
@@ -10209,6 +10269,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:
@@ -16265,6 +16338,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
@@ -19697,7 +19773,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 +20033,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 +20115,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 +20338,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 +20427,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 +20637,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 +20903,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 +20985,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 +21206,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 +21305,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 +21505,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:
@@ -21517,6 +21779,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 +21861,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.
@@ -21869,10 +22208,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,6 +22615,7 @@ components:
     Version:
       description: Version of the updated signal. If server side version is higher,
         update will be rejected.
+      example: 0
       format: int64
       type: integer
     WebhooksIntegration:
@@ -23358,12 +23713,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 +23743,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 +23779,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 +23818,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 +28361,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 +28435,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.
@@ -28148,6 +28514,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 +28592,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 +28675,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 +28791,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,7 +29006,7 @@ 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
@@ -28716,6 +29089,7 @@ paths:
           content:
             application/json:
               schema:
+                description: An array of monitor objects.
                 items:
                   $ref: '#/components/schemas/Monitor'
                 type: array
@@ -28739,7 +29113,7 @@ paths:
         appKeyAuth: []
       - AuthZ:
         - monitors_read
-      summary: Get all monitor details
+      summary: Get all monitors
       tags:
       - Monitors
       x-pagination:
@@ -28750,399 +29124,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 +36550,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 +36589,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 +36599,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