-
Notifications
You must be signed in to change notification settings - Fork 2.2k
feat(tag_cardinality_limit transform): Add exact_fingerprint mode for lower memory usage #25640
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
Open
ArunPiduguDD
wants to merge
4
commits into
vectordotdev:master
Choose a base branch
from
ArunPiduguDD:feat/tag-cardinality-exact-fingerprint
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
317f3e5
feat(tag_cardinality_limit transform): add exact_fingerprint mode for…
ArunPiduguDD a3756c1
Add suggested changes (test refactor + fps rename + use derive)
ArunPiduguDD 430f037
cargo fmt
ArunPiduguDD c6c12d6
Merge branch 'master' into feat/tag-cardinality-exact-fingerprint
pront File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
7 changes: 7 additions & 0 deletions
7
changelog.d/tag_cardinality_limit_fingerprint_mode.feature.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| The `tag_cardinality_limit` transform now supports `mode: exact_fingerprint`, a new storage | ||
| mode that can reduce memory usage for high-cardinality tag values compared to | ||
| `mode: exact`. Instead of storing the full tag-value strings, only a 64 bit fingerprint hash of | ||
| each value is kept. The trade-off is that throughput is slightly impacted due to extra hashing | ||
| operations, and there is technically a (unlikely) chance of collisions at very high cardinalities | ||
|
|
||
| authors: ArunPiduguDD |
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
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
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
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
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -66,6 +66,13 @@ generated: components: transforms: tag_cardinality_limit: configuration: { | |||||
| This mode has higher memory requirements than `probabilistic`, but never falsely outputs | ||||||
| metrics with new tags after the limit has been hit. | ||||||
| """ | ||||||
| exact_fingerprint: """ | ||||||
| This mode operates similarly to `exact` mode except it tracks cardinality using 64-bit hash fingerprints | ||||||
| of tag values instead of the original strings. This leads to lower memory requirements in most | ||||||
| scenarios (assuming average tag value size is greater than 8 bytes) at the cost of slightly | ||||||
| reduced throughput due to extra hashing operations and a very small chance of collisions at | ||||||
| very high cardinalities | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
| """ | ||||||
| probabilistic: """ | ||||||
| Tracks cardinality probabilistically. | ||||||
|
|
||||||
|
|
@@ -126,7 +133,8 @@ generated: components: transforms: tag_cardinality_limit: configuration: { | |||||
| description: "Controls the approach taken for tracking tag cardinality." | ||||||
| required: true | ||||||
| type: string: enum: { | ||||||
| exact: "Tracks cardinality exactly. See `Mode::Exact` for details." | ||||||
| exact: "Tracks cardinality exactly. See `Mode::Exact` for details." | ||||||
| exact_fingerprint: "Tracks cardinality using 64-bit hash fingerprints. See `Mode::ExactFingerprint` for details." | ||||||
| excluded: """ | ||||||
| Skip cardinality tracking for this metric. All tag values pass through and nothing is | ||||||
| limited. Other fields in this per-metric configuration are ignored when this is selected. | ||||||
|
|
||||||
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Would there be any value in pre-computing
BuildHasherDefault::<SeaHasher>::default()whenFingerprintStorageis created? You might want to seed it differently for each storage unit to avoid known-seed collision attacks.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.
Hm, what is a scenario where we would need to guard against known-seed collision attacks in Vector?
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.
The path would be being able to synthetically cause a collision with attacker-controlled data. In this case that would cause an undercount, allowing through a higher cardinality than otherwise IIUC, which amounts to a DoS attack due to service costs. Having an unknown seed makes that much harder, particularly if Vector is used in a cluster where every node has different seeds. The question then is if this is concerning.
FWIW microbenchmarks confirm that the setup of the hasher is free for this use.