Pablo Baeyens

@marcalff Thanks for the link! This is not an environment variable though, I am not sure I see the relation

> By this logic, the collector YAML config you reference is unrelated theMeterConfig.disabled, since YAML config != programmatic config 😉. I think the fact of the matter is that programmatic...

> Isn't the case for the collector that all usages of enabled are false by default so the user has to explicitly enable them? If so then Collector also follows...

> From my perspective, having different conventions for different configuration interfaces (env vars vs. programmatic) is a bad design We are not just building the specification, we are also building...

We discussed this on the Specification SIG meeting on 2025-01-07. Some arguments raised (other than the ones already raised on this thread): - On the 'default should be false' convention...

I filed #4351 which is one of the approaches discussed yesterday. I am not sure if this would need a sponsor or if I should file a separate issue for...

> This is a very one-side summary of the meeting conversation. It should be noted for readers here there were dissenting views to many of these points that are not...

I spent a bit of time writing down the usages of enabled and disabled on the Collector components and the OpenTelemetry declarative configuration. # Collector usage ## Usages of `enabled`...

We discussed this again towards the second half of the 2025-10-21 specification meeting. @MrAlias mentioned (correct me if I misunderstood) that there were user reports of confusion when not following...

I edited the [original comment](https://github.com/open-telemetry/opentelemetry-specification/issues/4344#issue-2744483026) to make a summary of the current positions around this topic, their current usages and the main arguments that I am aware of that have...