Eduard Mielieshkin

Hi @trask. My bad, the error confused me and it's not related to the main problem. > shouldn't cause any other issues That's what I thought too, but the main...

While I'm trying to solve a higher priority problem via the CET, I tried to print the OpenTelemetry logs bypassing your configuration: https://github.com/microsoft/ApplicationInsights-Java/blob/80f6eafba12454c9b59cc6f9e474e15d3c33c4fd/agent/agent-tooling/src/main/java/com/microsoft/applicationinsights/agent/internal/init/LoggingLevelConfigurator.java#L72-L76 and found that if the `loggerLevel` value...

Keep digging deeper into it. TL;DR The problem occurs when the logger name starts with `io.opentelemetry.sdk.metrics` but no deeper then `io.opentelemetry.sdk.metrics.internal`. I get a list of configured loggers Code block...

Hi @trask. I've consolidated the shared files (LoggingLevelConfigurator.java and the [application's ones](https://github.com/microsoft/ApplicationInsights-Java/issues/3524#issuecomment-1916779056)) in the [progxaker/reproduce-trace-issues](https://github.com/progxaker/reproduce-trace-issues/) repository. P.S. I tested the workaround for v3.4.19, but it doesn't work for v3.5.0.

As for v3.5.0, the problem occurs not only with the TRACE log level, but also with DEBUG.

Hi @trask. I hope you're doing well. Sorry for the long delay, been busy implementing OpenTelemetry (Python) into a project. **TL;DR:** The problem is reproduced when setting the `JAVA_TOOL_OPTIONS` variable...

https://github.com/progxaker/reproduce-trace-issues/#windows

Hello team. Is there any ETA, issues/internal tickets or updates?

Hello. Are there any updates?