Update docs for monitor types having left beta (#1700)

Co-authored-by: ci.datadog-api-spec <[email protected]>

Author: api-clients-generation-pipeline[bot]

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2023-10-05 15:54:41.516135",
-            "spec_repo_commit": "432a5a71"
+            "regenerated": "2023-10-05 18:57:55.441668",
+            "spec_repo_commit": "faa2c8d3"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2023-10-05 15:54:41.542763",
-            "spec_repo_commit": "432a5a71"
+            "regenerated": "2023-10-05 18:57:55.456179",
+            "spec_repo_commit": "faa2c8d3"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -25694,37 +25694,8 @@ paths:
         ##### Event Alert Query
 
 
-        Example: `events(''sources:nagios status:error,warning priority:normal tags:
-        "string query"'').rollup("count").last("1h")"`
-
-
-        - `event`, the event query string:
-
-        - `string_query` free text query to match against event title and text.
-
-        - `sources` event sources (comma-separated).
-
-        - `status` event statuses (comma-separated). Valid options: error, warn, and
-        info.
-
-        - `priority` event priorities (comma-separated). Valid options: low, normal,
-        all.
-
-        - `host` event reporting host (comma-separated).
-
-        - `tags` event tags (comma-separated).
-
-        - `excluded_tags` excluded event tags (comma-separated).
-
-        - `rollup` the stats roll-up method. `count` is the only supported method
-        now.
-
-        - `last` the timeframe to roll up the counts. Examples: 45m, 4h. Supported
-        timeframes: m, h and d. This value should not exceed 48 hours.
-
-
-        **NOTE** The Event Alert Query is being deprecated and replaced by the Event
-        V2 Alert Query. For more information, see the [Event Migration guide](https://docs.datadoghq.com/events/guides/migrating_to_new_events_features/).
+        **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
@@ -25856,10 +25827,6 @@ paths:
         - `#` an integer or decimal number used to set the threshold.
 
 
-        **NOTE** Only available on US1-FED and in closed beta on US1, EU, AP1, US3,
-        and US5.
-
-
         ##### CI Pipelines Alert Query
 
 
@@ -25882,9 +25849,6 @@ paths:
         - `#` an integer or decimal number used to set the threshold.
 
 
-        **NOTE** CI Pipeline monitors are in alpha on US1, EU, AP1, US3, and US5.
-
-
         ##### CI Tests Alert Query
 
 
@@ -25907,10 +25871,6 @@ paths:
         - `#` an integer or decimal number used to set the threshold.
 
 
-        **NOTE** CI Test monitors are available only in closed beta on US1, EU, AP1,
-        US3, and US5.
-
-
         ##### Error Tracking Alert Query
 
 

src/datadog_api_client/v1/api/monitors_api.py

@@ -437,20 +437,7 @@ def create_monitor(
 
         **Event Alert Query**
 
-        Example: ``events('sources:nagios status:error,warning priority:normal tags: "string query"').rollup("count").last("1h")"``
-
-        * ``event`` , the event query string:
-        * ``string_query`` free text query to match against event title and text.
-        * ``sources`` event sources (comma-separated).
-        * ``status`` event statuses (comma-separated). Valid options: error, warn, and info.
-        * ``priority`` event priorities (comma-separated). Valid options: low, normal, all.
-        * ``host`` event reporting host (comma-separated).
-        * ``tags`` event tags (comma-separated).
-        * ``excluded_tags`` excluded event tags (comma-separated).
-        * ``rollup`` the stats roll-up method. ``count`` is the only supported method now.
-        * ``last`` the timeframe to roll up the counts. Examples: 45m, 4h. Supported timeframes: m, h and d. This value should not exceed 48 hours.
-
-        **NOTE** The Event Alert Query is being deprecated and replaced by the Event V2 Alert Query. For more information, see the `Event Migration guide <https://docs.datadoghq.com/events/guides/migrating_to_new_events_features/>`_.
+        **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**
 
@@ -516,8 +503,6 @@ def create_monitor(
         * ``operator`` ``<`` , ``<=`` , ``>`` , ``>=`` , ``==`` , or ``!=``.
         * ``#`` an integer or decimal number used to set the threshold.
 
-        **NOTE** Only available on US1-FED and in closed beta on US1, EU, AP1, US3, and US5.
-
         **CI Pipelines Alert Query**
 
         Example: ``ci-pipelines(query).rollup(rollup_method[, measure]).last(time_window) operator #``
@@ -529,8 +514,6 @@ def create_monitor(
         * ``operator`` ``<`` , ``<=`` , ``>`` , ``>=`` , ``==`` , or ``!=``.
         * ``#`` an integer or decimal number used to set the threshold.
 
-        **NOTE** CI Pipeline monitors are in alpha on US1, EU, AP1, US3, and US5.
-
         **CI Tests Alert Query**
 
         Example: ``ci-tests(query).rollup(rollup_method[, measure]).last(time_window) operator #``
@@ -542,8 +525,6 @@ def create_monitor(
         * ``operator`` ``<`` , ``<=`` , ``>`` , ``>=`` , ``==`` , or ``!=``.
         * ``#`` an integer or decimal number used to set the threshold.
 
-        **NOTE** CI Test monitors are available only in closed beta on US1, EU, AP1, US3, and US5.
-
         **Error Tracking Alert Query**
 
         Example(RUM): ``error-tracking-rum(query).rollup(rollup_method[, measure]).last(time_window) operator #``