Tyler Helmuth

@mwear I've added a very rough e2e test in `internal/e2e/status_test.go` that tests that a component that is using sharedcomponent does end up eventually reporting all statuses for each instance and...

@mwear do you feel comfortable enough to move forward with this approach via https://github.com/open-telemetry/opentelemetry-collector/pull/10730?

Ive created https://github.com/open-telemetry/opentelemetry-collector/pull/10777 to complete the transition in core.

@codeboten and I were looking at this for https://github.com/open-telemetry/opentelemetry-collector/issues/10858. The tracing is also consuming a lot of memory. The only thing we've been able to identify is that the ctx...

Also, scaling back the per-statement spans won't help much, as most of the performance hit is from the first, outer span based on our testing.

Unfortunately the cummulativetodelta processor doesn't have metric type as a selection option. It could be made to have that feature.

> Note that this immediately changed the memory consumed by the collector, which is surprising since i didnt change the config: Thanks `init` functions

Is this different than https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-ebpf? You'll need to recruit a SIG member from that repository to help maintain this chart.

Typo, I meant to say sig member

How do those two repos interact? Would they every be installed together?