# Micrometer registry logs in latest version

**URL:** <https://discuss.elastic.co/t/micrometer-registry-logs-in-latest-version/320599>\
**Category:** APM\
**Tags:** java\
**Created:** [December 6, 2022, 2:52pm UTC](https://discuss.elastic.co/t/micrometer-registry-logs-in-latest-version/320599 "2022-12-06T14:52:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![OrangeDog](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/orangedog/32/4630_2.png) [@OrangeDog](https://discuss.elastic.co/u/OrangeDog)\
**Post date:** [December 6, 2022, 2:52pm UTC](https://discuss.elastic.co/t/micrometer-registry-logs-in-latest-version/320599/1 "2022-12-06T14:52:48Z")

</div>

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:

```nohighlight
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:

```nohighlight
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:

```yaml
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

```

---

<div class="post-metadata">

**Author:** ![Jack\_Shirazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_shirazi/32/91641_2.png) [@Jack\_Shirazi](https://discuss.elastic.co/u/Jack_Shirazi)\
**Post date:** [December 6, 2022, 4:07pm UTC](https://discuss.elastic.co/t/micrometer-registry-logs-in-latest-version/320599/2 "2022-12-06T16:07:50Z")

</div>

Yes, way too verbose, I'll change that

---

<div class="post-metadata">

**Author:** ![Jonas\_Kunz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonas_kunz/32/110740_2.png) [@Jonas\_Kunz](https://discuss.elastic.co/u/Jonas_Kunz)\
**Post date:** [December 6, 2022, 4:14pm UTC](https://discuss.elastic.co/t/micrometer-registry-logs-in-latest-version/320599/3 "2022-12-06T16:14:01Z")

</div>

Thanks for reporting this! I created an [issue](https://github.com/elastic/apm-agent-java/issues/2913) for it.

In the meantime, you can either disable the `micrometer` instrumentation ([config docs](https://www.elastic.co/guide/en/apm/agent/java/current/config-core.html#config-disable-instrumentations)) or adjust the [log level of the agent](https://www.elastic.co/guide/en/apm/agent/java/current/config-logging.html#config-log-level).

---

<div class="post-metadata">

**Author:** ![OrangeDog](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/orangedog/32/4630_2.png) [@OrangeDog](https://discuss.elastic.co/u/OrangeDog)\
**Post date:** [December 6, 2022, 4:40pm UTC](https://discuss.elastic.co/t/micrometer-registry-logs-in-latest-version/320599/4 "2022-12-06T16:40:37Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Jack\_Shirazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_shirazi/32/91641_2.png) [@Jack\_Shirazi](https://discuss.elastic.co/u/Jack_Shirazi)\
**Post date:** [December 6, 2022, 4:58pm UTC](https://discuss.elastic.co/t/micrometer-registry-logs-in-latest-version/320599/5 "2022-12-06T16:58:59Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 27, 2022, 12:59pm UTC](https://discuss.elastic.co/t/micrometer-registry-logs-in-latest-version/320599/6 "2022-12-27T12:59:55Z")

</div>

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