-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.
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
Update aggregation key processor documentation to reflect new source inclusion changes #30018
Conversation
…inclusion changes
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
Preview links (active after the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor edit per the style guide
content/en/service_management/events/pipelines_and_processors/aggregation_key.md
Outdated
Show resolved
Hide resolved
…aggregation_key.md Co-authored-by: Bryce Eadie <bryce.eadie@datadoghq.com>
/merge |
View all feedbacks in Devflow UI.
Added to the queue but the mergequeue is not enabled for now.
sam.fraser@datadoghq.com unqueued this merge request |
/merge -c |
View all feedbacks in Devflow UI.
|
/merge |
View all feedbacks in Devflow UI.
Added to the queue but the mergequeue is not enabled for now.
sam.fraser@datadoghq.com unqueued this merge request |
/merge -c |
View all feedbacks in Devflow UI.
|
What does this PR do? What is the motivation?
ECT-3509
An additional line has been added to this documentation to reflect that
@evt.source_id
and@evt.integration_id
are now always included in the aggregation key generation, meaning events with different sources will always have distinct aggregation keys.Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes