You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We are seeing duplicated metrics when using OpenTelemetry agent. After doing some analysis it was found its because of the spring-boot-starter-actuator dependency in the application pom file.
We have explicitly set the otel.instrumentation.micrometer.enabled to false but even after that we can see the micrometer related metrics are getting exposed because of this HTTP metrics, runtime metrics etc are exposed twice. One set of time-series with semantics of Otel and another set with micrometer.
Steps to reproduce
Add the below dependency to your pom.xml file
Describe the bug
We are seeing duplicated metrics when using OpenTelemetry agent. After doing some analysis it was found its because of the spring-boot-starter-actuator dependency in the application pom file.
We have explicitly set the otel.instrumentation.micrometer.enabled to false but even after that we can see the micrometer related metrics are getting exposed because of this HTTP metrics, runtime metrics etc are exposed twice. One set of time-series with semantics of Otel and another set with micrometer.
Steps to reproduce
Add the below dependency to your pom.xml file
Set the micrometer instrumentation to disabled
-Dotel.instrumentation.micrometer.enabled=false
What did you expect to see?
OTel should check the instrumentation state set (true/false) and should disable the instrumentation.
What did you see instead?
We are seeing the micrometer metrics getting exposed on top of OTel metrics.
What version are you using?
v.1.24.0 (distro)
Environment
OS: Windows & Linux
Runtime (if different from JDK above): OpenJDK 8,11,17
OS (if different from OS compiled on): Windows & Linux
Additional context
Currently we have set the management.metrics.enable.all=false to forcefully disable the metrics
The text was updated successfully, but these errors were encountered: