Repository navigation
Hash by ScopeName to prevent double counts #1640
Description
In some instances, we've found that OTEL instrumentation will produce exactly the same ResourceAttributes, ScopeAttributes, and Attributes for a histogram, but with different ScopeNames. This causes histogram calculations to fail because when partitioning ScopeName is not accounted for.
Activity
BilalAtique commentedon Nov 9, 2026
I'd like to take this one. #3598 adds
ScopeNameto the series key (cityHash64(ScopeName, ScopeAttributes, ResourceAttributes, Attributes)) in the gauge, sum, histogram and exponential histogram queries, so two scopes with the same attributes stay two series, also in alerts. Happy to adjust the approach if you had something else in mind.