Bogdan Drutu

@jpkrohling can you document the motivation? Does not seem to be that useful to produce a standard collector that we already produce and release anyway?

@tigrannajaryan as mentioned in the PR, this is only supported in opencensus, and we try to move away from that. Should we just remove the "otelcol" namespace from metrics for...

I still believe that we should not allow users to change it (not expose this option). We made this decision to have "otelcol" prefix fine, we will not break observability,...

The problem is that, if we add that capability and otel-go does not support we are stuck on opencensus. Without that, we can just go and change all metrics to...

Since we all agree that zpages is a must, let's do that and if we find out that is annoying for this case we can revisit. I feel that we...

@carlosalberto @jmacd @tedsuo can you look into this? @itaybaror can you confirm that this was not a transient error on the backend?

Are you looking for https://github.com/open-telemetry/opentelemetry-collector/blob/main/service/telemetry/config.go#L38?

No answer to the solution, looks like it is resolved.

While responding to your comments I realize that a possible thing is to offer both, do you think that is too confusing? > Dedicated batch processor keeps the batch in...

> The exporters are currently not allowed to mutate data: https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter#data-ownership you know that nobody reads documentation :)) One of them is the signalfx exporter which uses https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/batchperresourceattr/batchperresourceattr.go. Luckily after...