Logcat logs can't be disabled via configuration

[almozavr]

Despite configuration

ElasticApmConfiguration.builder().setLibraryLoggingPolicy(LoggingPolicy.disabled())

Logcat shows the logs, e.g.:

LoggingSpanExporter      I  'ViewDestroyed' : 5bacf... 0db9... INTERNAL [tracer: io.opentelemetry.lifecycle:] ...

[LikeTheSalad]

Thanks for letting us know, @almozavr

The log you've pointed out is sent by OTel Android, so that's why our agent's config doesn't affect it. However, I agree it isn't ideal, so I will mark this issue for the 1.0.0 refactor to ensure it doesn't happen there.

[almozavr]

I wonder if there is some kind of flag or resource attr OTel accepts to turn it off meanwhile? 🤔 For now quite a destructive way to "shut it down" is proguard :(

-assumenosideeffects class java.util.logging.Logger
{
  public void log(...);
}

[LikeTheSalad]

I see. I couldn't find a config in OTel to disable their logs, and they're also using JUL which I'd say isn't as flexible as other frameworks such as slf4j for example, so there doesn't seem to be too many options, unfortunately. Having said that, the one thing I did find was that calling LogManager.getLogManager().reset() could do the trick (it would disable all logs that are sent using JUL, if I understood correctly), I haven't tried it though.

[almozavr]

Thanks for the research! As far as I understand they still work on the global debug config which is expected (I hope) to be used for the logging purpose as well open-telemetry/opentelemetry-android#668

[LikeTheSalad]

Thanks for the research! As far as I understand they still work on the global debug config which is expected (I hope) to be used for the logging purpose as well open-telemetry/opentelemetry-android#668

It's a feature I'd like to have there too, so if it's still not there by the time I'm done with the Elastic agent 1.0.0 changes and other OTel Android priorities, I can work on it then.