Joshua MacDonald

Similar to the issue here: https://github.com/open-telemetry/opentelemetry-collector/issues/6638. In https://github.com/open-telemetry/otel-arrow/tree/main/collector/netstats, the OTel-Arrow components implements metrics that could be reused by any gRPC receiver or exporter. I would like to see this standardized...

> Non-Goal: Forgetting labels with Synchronous instruments I don't believe we need an explicit operation to forget synchronous instruments. [The Lightstep SDK does this for example.](https://github.com/lightstep/otel-launcher-go/tree/main/lightstep/sdk/metric) as did (roughly speaking)...

This is a reasonable request. See https://github.com/open-telemetry/oteps/pull/250. I expect this functionality will eventually emerge in the probabilisticsamplerprocessor, and that the OpAmp protocol will be used to distributed sampling configurations via...

I will re-open this.

Same as https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/32015#issuecomment-2073301725

Reviewers cc/ @dmitryax @andrzej-stencel, the [corresponding Receiver component](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/32015) has merged. We believe that this code, copied from https://github.com/open-telemetry/otel-arrow/releases/tag/v0.22.0, has already received sufficient review.

@codeboten All generated tests have been re-enabled, I wasn't aware of that mechanism. Nice.

Reviewers: this is a draft until https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/31940 merges.

~`make genotelcontribcol` is un-doing the effect of `make crosslink` and I don't know what to do next.~ (EDIT: the builder configuration has to list replace statements, crosslink won't stick.)

[I support @katiehockman's interpretation that](https://github.com/open-telemetry/opentelemetry-go/issues/3277#issuecomment-1276673807) > An existing API call MAY be extended without incrementing the major version number if the particular language allows to do it in a backward-compatible...