Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .apigentools-info
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,13 @@
"spec_versions": {
"v1": {
"apigentools_version": "1.6.6",
"regenerated": "2025-01-09 21:08:21.064628",
"spec_repo_commit": "435429e0"
"regenerated": "2025-01-09 22:06:12.202192",
"spec_repo_commit": "8d40e082"
},
"v2": {
"apigentools_version": "1.6.6",
"regenerated": "2025-01-09 21:08:21.079610",
"spec_repo_commit": "435429e0"
"regenerated": "2025-01-09 22:06:12.217985",
"spec_repo_commit": "8d40e082"
}
}
}
13 changes: 10 additions & 3 deletions .generator/schemas/v1/openapi.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
13 changes: 10 additions & 3 deletions .generator/schemas/v2/openapi.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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/)
Expand Down
9 changes: 8 additions & 1 deletion features/v1/events.feature
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
9 changes: 8 additions & 1 deletion features/v2/events.feature
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading