From 987ec860ff2df8a88aed5b1ba5417fcfd0158467 Mon Sep 17 00:00:00 2001 From: "api-clients-generation-pipeline[bot]" <54105614+api-clients-generation-pipeline[bot]@users.noreply.github.com> Date: Fri, 10 Jan 2025 13:48:49 +0000 Subject: [PATCH] Add notes for Events V1 API DD monitor aggregation key update (#2864) Co-authored-by: ci.datadog-api-spec --- .apigentools-info | 8 ++++---- .generator/schemas/v1/openapi.yaml | 13 ++++++++++--- .generator/schemas/v2/openapi.yaml | 13 ++++++++++--- tests/scenarios/features/v1/events.feature | 9 ++++++++- tests/scenarios/features/v2/events.feature | 9 ++++++++- 5 files changed, 40 insertions(+), 12 deletions(-) diff --git a/.apigentools-info b/.apigentools-info index 40a72e1e0a7..7f264faf311 100644 --- a/.apigentools-info +++ b/.apigentools-info @@ -4,13 +4,13 @@ "spec_versions": { "v1": { "apigentools_version": "1.6.6", - "regenerated": "2025-01-09 21:08:20.268969", - "spec_repo_commit": "435429e0" + "regenerated": "2025-01-09 22:06:11.503685", + "spec_repo_commit": "8d40e082" }, "v2": { "apigentools_version": "1.6.6", - "regenerated": "2025-01-09 21:08:20.283894", - "spec_repo_commit": "435429e0" + "regenerated": "2025-01-09 22:06:11.519399", + "spec_repo_commit": "8d40e082" } } } \ No newline at end of file diff --git a/.generator/schemas/v1/openapi.yaml b/.generator/schemas/v1/openapi.yaml index c2af523e94c..09a4d845e5f 100644 --- a/.generator/schemas/v1/openapi.yaml +++ b/.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 diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml index fadab8d3ec6..7e519f92653 100644 --- a/.generator/schemas/v2/openapi.yaml +++ b/.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/) diff --git a/tests/scenarios/features/v1/events.feature b/tests/scenarios/features/v1/events.feature index 3005fc756fb..e1b7d8a0fd6 100644 --- a/tests/scenarios/features/v1/events.feature +++ b/tests/scenarios/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 diff --git a/tests/scenarios/features/v2/events.feature b/tests/scenarios/features/v2/events.feature index eada249fd88..61310eb2c6f 100644 --- a/tests/scenarios/features/v2/events.feature +++ b/tests/scenarios/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