Skip to content

Commit 18fb9f0

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit 618968b6 of spec repo
1 parent 081efd5 commit 18fb9f0

File tree

5 files changed

+40
-12
lines changed

5 files changed

+40
-12
lines changed

.apigentools-info

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@
44
"spec_versions": {
55
"v1": {
66
"apigentools_version": "1.6.6",
7-
"regenerated": "2025-01-09 20:03:43.350349",
8-
"spec_repo_commit": "07ed2f56"
7+
"regenerated": "2025-01-09 21:10:19.112773",
8+
"spec_repo_commit": "618968b6"
99
},
1010
"v2": {
1111
"apigentools_version": "1.6.6",
12-
"regenerated": "2025-01-09 20:03:43.365124",
13-
"spec_repo_commit": "07ed2f56"
12+
"regenerated": "2025-01-09 21:10:19.128238",
13+
"spec_repo_commit": "618968b6"
1414
}
1515
}
1616
}

.generator/schemas/v1/openapi.yaml

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -36665,10 +36665,17 @@ tags:
3666536665
end times, prevent all alerting related to specified Datadog tags.'
3666636666
name: Downtimes
3666736667
- description: 'The Event Management API allows you to programmatically post events
36668-
to the Events Explorer
36668+
to the Events Explorer and fetch events from the Events Explorer. See the [Event
36669+
Management page](https://docs.datadoghq.com/service_management/events/) for more
36670+
information.
3666936671

36670-
and fetch events from the Events Explorer. See the [Event Management page](https://docs.datadoghq.com/service_management/events/)
36671-
for more information.'
36672+
36673+
**Update to Datadog monitor events `aggregation_key` starting March 1, 2025:**
36674+
The Datadog monitor events `aggregation_key` is unique to each Monitor ID. Starting
36675+
March 1st, this key will also include Monitor Group, making it unique per *Monitor
36676+
ID and Monitor Group*. If you''re using monitor events `aggregation_key` in dashboard
36677+
queries or the Event API, you must migrate to use `@monitor.id`. Reach out to
36678+
[support](https://www.datadoghq.com/support/) if you have any question.'
3667236679
name: Events
3667336680
- description: 'Configure your Datadog-Google Cloud Platform (GCP) integration directly
3667436681

.generator/schemas/v2/openapi.yaml

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -48310,10 +48310,17 @@ tags:
4831048310
end times, prevent all alerting related to specified Datadog tags.'
4831148311
name: Downtimes
4831248312
- description: 'The Event Management API allows you to programmatically post events
48313-
to the Events Explorer
48313+
to the Events Explorer and fetch events from the Events Explorer. See the [Event
48314+
Management page](https://docs.datadoghq.com/service_management/events/) for more
48315+
information.
4831448316

48315-
and fetch events from the Events Explorer. See the [Event Management page](https://docs.datadoghq.com/service_management/events/)
48316-
for more information.'
48317+
48318+
**Update to Datadog monitor events `aggregation_key` starting March 1, 2025:**
48319+
The Datadog monitor events `aggregation_key` is unique to each Monitor ID. Starting
48320+
March 1st, this key will also include Monitor Group, making it unique per *Monitor
48321+
ID and Monitor Group*. If you''re using monitor events `aggregation_key` in dashboard
48322+
queries or the Event API, you must migrate to use `@monitor.id`. Reach out to
48323+
[support](https://www.datadoghq.com/support/) if you have any question.'
4831748324
name: Events
4831848325
- description: Manage your Datadog Fastly integration accounts and services directly
4831948326
through the Datadog API. See the [Fastly integration page](https://docs.datadoghq.com/integrations/fastly/)

features/v1/events.feature

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,14 @@ Feature: Events
33
The Event Management API allows you to programmatically post events to the
44
Events Explorer and fetch events from the Events Explorer. See the [Event
55
Management page](https://docs.datadoghq.com/service_management/events/)
6-
for more information.
6+
for more information. **Update to Datadog monitor events
7+
`aggregation_key` starting March 1, 2025:** The Datadog monitor events
8+
`aggregation_key` is unique to each Monitor ID. Starting March 1st, this
9+
key will also include Monitor Group, making it unique per *Monitor ID and
10+
Monitor Group*. If you're using monitor events `aggregation_key` in
11+
dashboard queries or the Event API, you must migrate to use `@monitor.id`.
12+
Reach out to [support](https://www.datadoghq.com/support/) if you have any
13+
question.
714

815
Background:
916
Given a valid "apiKeyAuth" key in the system

features/v2/events.feature

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,14 @@ Feature: Events
33
The Event Management API allows you to programmatically post events to the
44
Events Explorer and fetch events from the Events Explorer. See the [Event
55
Management page](https://docs.datadoghq.com/service_management/events/)
6-
for more information.
6+
for more information. **Update to Datadog monitor events
7+
`aggregation_key` starting March 1, 2025:** The Datadog monitor events
8+
`aggregation_key` is unique to each Monitor ID. Starting March 1st, this
9+
key will also include Monitor Group, making it unique per *Monitor ID and
10+
Monitor Group*. If you're using monitor events `aggregation_key` in
11+
dashboard queries or the Event API, you must migrate to use `@monitor.id`.
12+
Reach out to [support](https://www.datadoghq.com/support/) if you have any
13+
question.
714

815
Background:
916
Given a valid "apiKeyAuth" key in the system

0 commit comments

Comments
 (0)