Skip to content

Commit 9546be5

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit e4e37228 of spec repo
1 parent fdc8194 commit 9546be5

File tree

5 files changed

+32
-16
lines changed

5 files changed

+32
-16
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-07 19:53:43.056949",
8-
"spec_repo_commit": "d63fa330"
7+
"regenerated": "2025-01-08 16:17:59.783982",
8+
"spec_repo_commit": "e4e37228"
99
},
1010
"v2": {
1111
"apigentools_version": "1.6.6",
12-
"regenerated": "2025-01-07 19:53:43.071705",
13-
"spec_repo_commit": "d63fa330"
12+
"regenerated": "2025-01-08 16:17:59.798897",
13+
"spec_repo_commit": "e4e37228"
1414
}
1515
}
1616
}

.generator/schemas/v1/openapi.yaml

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -36664,11 +36664,14 @@ tags:
3666436664

3666536665
end times, prevent all alerting related to specified Datadog tags.'
3666636666
name: Downtimes
36667-
- description: 'The Event Management API allows you to programmatically post events
36668-
to the Events Explorer
36669-
36670-
and fetch events from the Events Explorer. See the [Event Management page](https://docs.datadoghq.com/service_management/events/)
36671-
for more information.'
36667+
- description: "The Event Management API allows you to programmatically post events
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.\n\n**Update to the aggregation_key for Datadog monitor events:**
36671+
Currently, the aggregation_key is unique per Monitor ID. Starting March 1st, we
36672+
will update it to be unique per Monitor ID and Monitor Group. If you\u2019re using
36673+
monitor events aggregation_key in dashboard queries or the Event API, please migrate
36674+
to using @monitor.id. Please reach out to support if you have any question."
3667236675
name: Events
3667336676
- description: 'Configure your Datadog-Google Cloud Platform (GCP) integration directly
3667436677

.generator/schemas/v2/openapi.yaml

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -48235,11 +48235,14 @@ tags:
4823548235

4823648236
end times, prevent all alerting related to specified Datadog tags.'
4823748237
name: Downtimes
48238-
- description: 'The Event Management API allows you to programmatically post events
48239-
to the Events Explorer
48240-
48241-
and fetch events from the Events Explorer. See the [Event Management page](https://docs.datadoghq.com/service_management/events/)
48242-
for more information.'
48238+
- description: "The Event Management API allows you to programmatically post events
48239+
to the Events Explorer and fetch events from the Events Explorer. See the [Event
48240+
Management page](https://docs.datadoghq.com/service_management/events/) for more
48241+
information.\n**Update to the aggregation_key for Datadog monitor events:** Currently,
48242+
the aggregation_key is unique per Monitor ID. Starting March 1st, we will update
48243+
it to be unique per Monitor ID and Monitor Group. If you\u2019re using monitor
48244+
events aggregation_key in dashboard queries or the Event API, please migrate to
48245+
using @monitor.id. Please reach out to support if you have any question.\n"
4824348246
name: Events
4824448247
- description: Manage your Datadog Fastly integration accounts and services directly
4824548248
through the Datadog API. See the [Fastly integration page](https://docs.datadoghq.com/integrations/fastly/)

features/v1/events.feature

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,12 @@ 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 the aggregation_key for Datadog monitor
7+
events:** Currently, the aggregation_key is unique per Monitor ID.
8+
Starting March 1st, we will update it to be unique per Monitor ID and
9+
Monitor Group. If you’re using monitor events aggregation_key in dashboard
10+
queries or the Event API, please migrate to using @monitor.id. Please
11+
reach out to support if you have any question.
712

813
Background:
914
Given a valid "apiKeyAuth" key in the system

features/v2/events.feature

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,12 @@ 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 the aggregation_key for Datadog monitor
7+
events:** Currently, the aggregation_key is unique per Monitor ID.
8+
Starting March 1st, we will update it to be unique per Monitor ID and
9+
Monitor Group. If you’re using monitor events aggregation_key in dashboard
10+
queries or the Event API, please migrate to using @monitor.id. Please
11+
reach out to support if you have any question.
712

813
Background:
914
Given a valid "apiKeyAuth" key in the system

0 commit comments

Comments
 (0)