Repository navigation
Conversation
…/jlambatl/vector into transform_aggregate_distribution
pront
reviewed
Oct 13, 2025
…improve the documentation that is generated for the distribution aggregation mode in the configuration parameter
Contributor
Author
|
I've pushed up a commit that should resolve the comments/feedback provided. It's hard to find the balance between being too verbose and not providing enough clarity. |
Member
|
Starting to look good, will wait for a review from @vectordotdev/documentation. |
rtrieu
previously approved these changes
Oct 14, 2025
pront
reviewed
Oct 24, 2025
Contributor
Author
|
@pront The update looks good to me; it's also nice to see the improved tests. Thankyou. |
pront
enabled auto-merge
October 29, 2025 13:35
…transform_aggregate_distribution
auto-merge was automatically disabled
November 5, 2025 22:49
Head branch was pushed to by a user without write access
Contributor
Author
|
@pront I've fixed the Clippy error that was failing in CI and pushed up the changes. |
pront
enabled auto-merge
November 6, 2025 15:40
Contributor
Author
|
@vectordotdev/vector Is there anything outstanding with this PR? |
auto-merge was automatically disabled
April 15, 2026 01:37
Head branch was pushed to by a user without write access
Contributor
Author
|
I have resolved the merge conflicts... |
…gate module Re-apply the `distribution` aggregation mode on top of the split `transforms/aggregate/` module layout and the new event-time aggregation. - Add `AggregationMode::Distribution` / `InnerMode::Distribution` and handle it in both the system-time and event-time paths via a shared `distribution_from_entries` helper. - Pass incremental metrics through unchanged, consistent with the other modes that aggregate absolute metrics (Latest, Diff, Max, Min, Mean, Stdev). - Only store absolute metrics that can yield samples (gauge, set, distribution, aggregated histogram). Other absolute types are ignored, so an empty distribution is never emitted and no event-time bucket is created. - Port the existing Distribution tests and add coverage for incremental passthrough, unsupported absolute types and event-time bucketing. - Update the aggregate component docs.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This change adds a new AggregateMode
distributionthat aggregates individual metrics into a distribution. This doesn't reduce the accuracy of the metrics; instead, it reduces the volume of payloads being emitted from Vector by reducing the overhead of duplicate tags and other fields in exchange for a single larger payload.This pattern suits real-time analytics databases, where histograms and other statistical functions can be calculated on the fly. It reduces the need to manually codify histogram buckets, which can become an onerous task on systems dealing with large metric volumes.
The distribution is sorted in the current implementation. I have been unsure whether that is a good idea, but I'm happy to change that based on your feedback.
closes: #24001
Vector configuration
How did you test this PR?
I have added many different unit tests that cover the primary aggregation types, histograms, distributions, etc.
Change Type
Is this a breaking change?
Does this PR include user-facing changes?
no-changeloglabel to this PR.Notes
N/A