Jack Berg

> I think this is simply a better design and the way to go. I've said something to this effect in other comments, but extending LogRecordProcessor with `enabled` and the...

Did a quick peak at the go, rust, cpp, php implementations: - [Go](https://github.com/open-telemetry/opentelemetry-go/blob/main/log/logger.go#L57) - 👍 - [Rust](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry/src/logs/logger.rs#L24C8-L24C21) - has an `event_enabled` method which appears to accept severity and event name...

Sorry for not getting back on this @neugartf. We talked about this in the 10/10/2024 java SIG, just before the 1.43.0 release. Decided it needed more work: - Its not...

> I'll invest some time to get this reproduced on the test app there (opentelemetry-android), though it won't be a proper junit test since we'll need to boot up the...

Thanks for doing that research @neugartf. I have a slight preference to go with @laurit's synchronized approach, because I have a general aversion to implementing `Cloneable` or calling `clone()`. What...

Hey @neugartf - I picked this up in #6841. Take a look and let me know what you think.

Merged #6841 so closing this.

Hi all - moving to the spec repo since this repo is just concerned with the declarative configuration data model. The spec would be the place that would specify any...

> It's basically 2 types of changes: There's a third type of change which is things that can't be configured via declarative config. Consider OTLP proxy configuration, which is available...

I'm not familiar with grpc-xds. Maybe you could sketch out what you have in mind in a draft PR? I should note that our OTLP grpc based exporters don't use...