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
Spring Boot v1.5.x auto configured a MetricRegistry bean, with which developers could add their custom metrics to and were exposed on the actuator /metrics endpoint. This has worked very well for us.
Spring Boot v2 does not appear to auto configure a MetricRegistry bean. So without changes, when you startup you'll get a org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.codahale.metrics.MetricRegistry'.
I don't see references to this change in any of the 2.0.0.M1-M7 release notes, nor migration guide.. Is this just an oversight or did I miss something? I do see references to Micrometer, but nothing saying the previous support is no longer included.
Also, is there a way to manually enable the previous support?
The text was updated successfully, but these errors were encountered:
Spring Boot v1.5.x auto configured a
MetricRegistry
bean, with which developers could add their custom metrics to and were exposed on the actuator/metrics
endpoint. This has worked very well for us.Spring Boot v2 does not appear to auto configure a
MetricRegistry
bean. So without changes, when you startup you'll get aorg.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.codahale.metrics.MetricRegistry'
.I don't see references to this change in any of the 2.0.0.M1-M7 release notes, nor migration guide.. Is this just an oversight or did I miss something? I do see references to Micrometer, but nothing saying the previous support is no longer included.
Also, is there a way to manually enable the previous support?
The text was updated successfully, but these errors were encountered: