Skip to content

Update aggregation key processor documentation to reflect new source inclusion changes #30018

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
+2 −1
Open

Update aggregation key processor documentation to reflect new source inclusion changes #30018

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4eefff5
Update aggregation key processor documentation to reflect new source …
fraseriver Jun 18, 2025
df3e102
Update content/en/service_management/events/pipelines_and_processors/…
fraseriver Jun 18, 2025
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
3 changes: 2 additions & 1 deletion content/en/service_management/events/pipelines_and_processors/aggregation_key.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,10 @@ Use the aggregation key processor to generate a custom aggregation key (`@aggreg

**Notes**:

- Attributes must start with the `@` symbol and follow the path of the standard attribute as it appears in your JSON. For example, `@evt.integration_id`.
- Attributes must start with the `@` symbol and follow the path of the standard attribute as it appears in your JSON. For example, `@evt.category`.
- Tag keys must follow a valid tag key format outlined in [Getting Started with Tags][2].
- A maximum of 5 attributes or tag keys can be added to generate an aggregation key.
- Events originating from different sources or integrations receive distinct aggregation keys.
- By default, existing aggregation keys are overwritten by this processor. Adjust the toggle to configure this behavior.

<div class="alert alert-warning">Aggregation keys are included by default in Datadog Monitor alerts and are not modified by the aggregation key processor. This ensures that monitor alert events retain their original keys and are not overwritten.</div>
Expand Down
Loading