Skip to content

Fix histogram overflow bucket accounting - #333

Closed
xiaoxichen wants to merge 1 commit into
dev/v14.xfrom
fix/histogram-overflow-bucket
Closed

xiaoxichen wants to merge 1 commit into
dev/v14.xfrom
fix/histogram-overflow-bucket

Conversation

@xiaoxichen

Copy link
Copy Markdown
Contributor

Histogram observations above the largest configured boundary use the implicit overflow bucket at index boundaries.size(). RCU and thread-buffer aggregation previously omitted that slot during merge, leaving the sum updated while count and the Prometheus +Inf bucket were too low. The atomic implementation discarded these observations entirely.

Account for the implicit overflow bucket in every implementation, validate that configured boundaries fit the fixed histogram storage, and cover below-boundary, exact-boundary, and overflow observations across all backends and Prometheus output.

Histogram observations above the largest configured boundary use the implicit overflow bucket at index
boundaries.size(). RCU and thread-buffer aggregation previously omitted that slot during merge, leaving the sum
updated while count and the Prometheus +Inf bucket were too low. The atomic implementation discarded these
observations entirely.

Account for the implicit overflow bucket in every implementation, validate that configured boundaries fit the fixed
histogram storage, and cover below-boundary, exact-boundary, and overflow observations across all backends and
Prometheus output.
@xiaoxichen
xiaoxichen force-pushed the fix/histogram-overflow-bucket branch from 797f05d to 2640c9f Compare September 6, 2026 07:10
@xiaoxichen xiaoxichen closed this Sep 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant