Micrometer registry logs in latest version

Elastic Observability APM
1

Upgrading from 1.34.1 to 1.35.0 of the Java agent, in a Spring Boot application.
During startup, this is logged hundreds of times on multiple threads:

2022-12-06 14:40:47,793 [main] INFO  co.elastic.apm.agent.micrometer.MicrometerMetricsReporter - Not re-registering MeterRegistry as it is already registered from another compound meter registry: io.micrometer.core.instrument.simple.SimpleMeterRegistry@5c2f5dc
2022-12-06 14:40:49,984 [main] INFO  co.elastic.apm.agent.micrometer.MicrometerMetricsReporter - Not re-registering MeterRegistry as it is already registered from another compound meter registry: io.micrometer.core.instrument.simple.SimpleMeterRegistry@5c2f5dc
2022-12-06 14:40:51,407 [Service Thread] INFO  co.elastic.apm.agent.micrometer.MicrometerMetricsReporter - Not re-registering MeterRegistry as it is already registered from another compound meter registry: io.micrometer.core.instrument.simple.SimpleMeterRegistry@5c2f5dc
2022-12-06 14:40:56,710 [lettuce-nioEventLoop-4-1] INFO  co.elastic.apm.agent.micrometer.MicrometerMetricsReporter - Not re-registering MeterRegistry as it is already registered from another compound meter registry: io.micrometer.core.instrument.simple.SimpleMeterRegistry@5c2f5dc
2022-12-06 14:40:57,144 [lettuce-nioEventLoop-4-2] INFO  co.elastic.apm.agent.micrometer.MicrometerMetricsReporter - Not re-registering MeterRegistry as it is already registered from another compound meter registry: io.micrometer.core.instrument.simple.SimpleMeterRegistry@5c2f5dc
2022-12-06 14:40:59,294 [lettuce-nioEventLoop-4-3] INFO  co.elastic.apm.agent.micrometer.MicrometerMetricsReporter - Not re-registering MeterRegistry as it is already registered from another compound meter registry: io.micrometer.core.instrument.simple.SimpleMeterRegistry@5c2f5dc

And then again on a request:

2022-12-06 14:48:25,876 [Service Thread] INFO  co.elastic.apm.agent.micrometer.MicrometerMetricsReporter - Not re-registering MeterRegistry as it is already registered from another compound meter registry: io.micrometer.core.instrument.simple.SimpleMeterRegistry@5c2f5dc
2022-12-06 14:48:26,333 [XNIO-1 task-1] INFO  co.elastic.apm.agent.micrometer.MicrometerMetricsReporter - Not re-registering MeterRegistry as it is already registered from another compound meter registry: io.micrometer.core.instrument.simple.SimpleMeterRegistry@5c2f5dc
2022-12-06 14:48:26,654 [XNIO-1 task-1] INFO  co.elastic.apm.agent.micrometer.MicrometerMetricsReporter - Not re-registering MeterRegistry as it is already registered from another compound meter registry: io.micrometer.core.instrument.simple.SimpleMeterRegistry@5c2f5dc
2022-12-06 14:48:26,870 [XNIO-1 task-1] INFO  co.elastic.apm.agent.micrometer.MicrometerMetricsReporter - Not re-registering MeterRegistry as it is already registered from another compound meter registry: io.micrometer.core.instrument.simple.SimpleMeterRegistry@5c2f5dc

In case it's relevant, I have the following config set:

elastic.apm:
  application_packages: com.example
  disable_send: true
  capture_headers: false
  central_config: false
  enable_log_correlation: true
  environment: test
  service_name: '@project.name@'
  service_version: '@project.version@'
  span_compression_enabled: true
  use_elastic_traceparent_header: false
  use_path_as_transaction_name: true
2

Yes, way too verbose, I'll change that

3

Thanks for reporting this! I created an issue for it.

In the meantime, you can either disable the micrometer instrumentation (config docs) or adjust the log level of the agent.

4

So nothing is wrong, it's just logging at INFO when it should be TRACE?

5

yes, though I'm going for debug, it's useful for debugging when you don't know what's being registered

6

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.