Add notes for Events V1 API DD monitor aggregation key update (#2178)

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": "2025-01-09 21:08:20.412560",
-            "spec_repo_commit": "435429e0"
+            "regenerated": "2025-01-09 22:06:06.242932",
+            "spec_repo_commit": "8d40e082"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-01-09 21:08:20.427708",
-            "spec_repo_commit": "435429e0"
+            "regenerated": "2025-01-09 22:06:06.258111",
+            "spec_repo_commit": "8d40e082"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -36666,10 +36666,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
 

.generator/schemas/v2/openapi.yaml

@@ -48310,10 +48310,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: Manage your Datadog Fastly integration accounts and services directly
     through the Datadog API. See the [Fastly integration page](https://docs.datadoghq.com/integrations/fastly/)

features/v1/events.feature

@@ -3,7 +3,14 @@ Feature: Events
   The Event Management API allows you to programmatically post events 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.
+  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.
 
   Background:
     Given a valid "apiKeyAuth" key in the system

features/v2/events.feature

@@ -3,7 +3,14 @@ Feature: Events
   The Event Management API allows you to programmatically post events 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.
+  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.
 
   Background:
     Given a valid "apiKeyAuth" key in the system