Trask Stalnaker

I think I got it working. Just change `OpenTelemetryAppender.install(openTelemetry)` to `otelAppender.setOpenTelemetry(openTelemetry)`. It seems that `OpenTelemetryAppender.install(openTelemetry)` doesn't work when configuring things dynamically (as opposed to via `log4j2.xml` file). Also, I found...

> To be more accurate, though, the difference seems to be not in static vs. dynamic use, but elsewhere I see different behavior, you can check out my Java repro:...

> Check this out: > > https://github.com/greatvovan/log4j-dynamic-config-example/blob/main/src/main/java/io/opentelemetry/example/logappender/Application2.java#L46-L47 ah, I see, thanks!

btw, not sure if this might be interesting / relevant to follow: https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/12468

@greatvovan just checking if it's ok to close this issue, or if you'd like to leave it open? thanks

Discussed with @lmolkova, we are going to make the following proposal to all languages for the Azure Monitor OpenTelemetry exporters: * Maintain list of specific attributes to exclude, e.g. *...

@FabianMeiswinkel sorry we lost track of this, I've just sent a PR to address it: https://github.com/Azure/azure-sdk-for-java/pull/42460

here's the yaml structure: ``` instrumentation/development: general: http: client: request_captured_headers: response_captured_headers: server: request_captured_headers: response_captured_headers: peer: service_mapping: java: common: controller_telemetry/development: enabled: database: sqlcommenter/development: enabled: statement_sanitizer: enabled: default_enabled: enduser: id: enabled: role:...