fix(agent): tune download throughput histogram buckets#602
Merged
Conversation
sambhav-jain-16
approved these changes
Apr 22, 2026
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
2 participants
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.
kraken-agent's throughput histogram does not have enough granularity in the <1MB/s range. This means that for blobs in the <5MB size range the throughput metric is always the same, as it's hitting the bottom bucket (0-1MB/s). This PR fixes that by changing the distribution of granularity in the histogram's buckets.
versiontag of those metrics10GiB+size tag value to10GiBplus, as some metrics libraries/databases/ingestion pipelines cannot handle the+character.100MiB-1GBrange by changing it to1GiBfrom1GB.