Bogdan Drutu
Bogdan Drutu
@dashpole would be good if you drive this to resolution, see https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/7134 which you also need :)
@swiatekm-sumo I am a bit reluctant because: ``` For example, we could: Retry transient consumer errors Reject incoming data if there's backpressure - could be via a timeout or by...
Does it worth the complicated process since we don't have the conflict problem in this repo?
I think that it "breaking" is very minimal, and is part of an API that we don't expect users to use publicly `component.Config` object, which is public just because of...
@jpkrohling we already expose "MeterProvider" in the CreateParams (I know is a no-op) so components can start using that (will be some time until we will enable them though).
Also cannot reproduce. Closing, if anyone else can reproduce please reopen, may have been just a configuration issue on @tigrannajaryan 's machine? ```shell go test -race -run TestNewDefaultConfig -count 10000...
@jpkrohling the list of "requirements" can be embedded in the code. Something like the "AuthExtension" can have a "Requirements()" API that tells the HTTP/GRPC what infos are required?
@jpkrohling maybe can use "Host" as the intermediary, components can "record their needs"? Not sold necessary on the "Host" but you can come up with a solution :)
Look at this https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver