Tyler Yahn
Tyler Yahn
Blocked by the metric SDK having a working example in the new_sdk/main branch Removed in https://github.com/open-telemetry/opentelemetry-go/pull/2802
The [current implementation](https://github.com/open-telemetry/opentelemetry-go/pull/3045) of the cumulative histogram copies both it's bounds and bucket counts every time Aggregation is called. These copies mean that new slices are allocated for each call...
~Blocked by https://github.com/open-telemetry/opentelemetry-go/issues/2800~
~Blocked by https://github.com/open-telemetry/opentelemetry-go/issues/2800~
Blocked by the metric SDK having a working example in the new_sdk/main branch Removed in https://github.com/open-telemetry/opentelemetry-go/pull/2802
The cumulative sum `Aggregator` will never forget a sum for an attribute set, even if that set if never updated again. This means that an unbounded amount of memory will...
> > After looking at the output, a few things stick out. Some of these are easy to tell what's wrong, but some less so: In the ResourceMetrics test: resources...
Complete the `sdk/metric/metrictest` package. - [ ] Create a testing framework to end-to-end test the SDK - Needs to be extensible. When new aggregators or interfaces are added the SDK...
> It looks like there's a lot of logic baked into the Sum aggregator that could be treated at at higher level in the SDK, to me. I'm referring mostly...