Alex Boten

In the long term, the collector should be configurable through the same configuration as the OpenTelemetry Configuration schema provides, would the right way to configure this be to have an...

> Here the collector has an opportunity to distinguish its own (diagnostic) logs from the logs it collects from applications. @tonglil maybe I'm misunderstanding what is being said here, but...

Assigned the issue to you @danielbdias

Added this component to the Collector SIG agenda as a vendor proposed component, the next maintainer on the [rotating sponsor](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#rotating-sponsors) list should pick this up. cc @crobert-1

Some thoughts: - should `BuildInfo` be in this package? since its more directly tied to the service running, it might make more sense to move it to that package -...

Note that there's also an OTEP that has specific metrics that may require a rename later on https://github.com/open-telemetry/oteps/pull/238, but adding a prefix would still be useful in the short term.

> My vote is to NOT do this, and to if needed use relevant names for the meter that produces these metrics. @bogdandrutu As an end-user, wouldn't this potentially cause...

As discussed on the SIG call on 6-Mar-2024, the concensus that prefixes were better in the short term to be consistent. Additionally, using `_` instead of `/` will allow both...

@evan-bradley ptal at the check failure

@bogdandrutu are you in favour of keeping the short form or the long form scope name? or both? > here is probably just otelcol? I guess it depends on how...