[英]Spring Boot Actuator: How to get metrics uptime inside a custom HealthIndicator?
I want to do a custom HealthIndicator that depends on the application uptime.我想做一个取决于应用程序正常运行时间的自定义 HealthIndicator。
@Component
public class HealthActuator implements HealthIndicator {
private final MetricsEndpoint metricsEndpoint;
@Autowired
public HealthActuator(MetricsEndpoint metricsEndpoint) {
this.metricsEndpoint = metricsEndpoint;
}
@Override
public Health health() {
long uptime = (Long) metricsEndpoint.invoke().get("uptime");
// logic with uptime
return Health.up().build();
}
}
But there is an error: a circular dependency between 2 beans in the application context
.但是有一个错误: a circular dependency between 2 beans in the application context
。
I can get uptime metric with a rest call to my endpoint /actuator/health.我可以通过对端点 /actuator/health 的休息调用来获得正常运行时间指标。
But maybe is it possible to do it programmatically?但也许有可能以编程方式做到这一点?
PS Log stacktrace: PS 日志堆栈跟踪:
11-01 14:34:09 WARN org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'healthActuator' defined in file [/Users/serge/projects/bb/bb-imapl/target/classes/bb/imapl/config/HealthActuator.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration$$EnhancerBySpringCGLIB$$2bb06d4a]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'healthActuator': Requested bean is currently in creation: Is there an unresolvable circular reference?
11-01 14:34:09 WARN org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'healthActuator' defined in file [/Users/serge/projects/bb/bb-imapl/target/classes/bb/imapl/config/HealthActuator.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration$$EnhancerBySpringCGLIB$$2bb06d4a]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'healthActuator': Requested bean is currently in creation: Is there an unresolvable circular reference?
11-01 14:34:09 ERROR org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter -
***************************
APPLICATION FAILED TO START
***************************
Description:
There is a circular dependency between 2 beans in the application context:
- healthActuator defined in file [/Users/serge/projects/bb/bb-imapl/target/classes/bb/imapl/config/HealthActuator.class]
- org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration
- healthActuator
11-01 14:34:09 ERROR org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter -
If you do not like setter injection, it should also be possible to work around this with @Lazy
...如果您不喜欢 setter 注入,也应该可以使用@Lazy
解决此@Lazy
...
@Autowired
public HealthActuator(@Lazy MetricsEndpoint metricsEndpoint) {
this.metricsEndpoint = metricsEndpoint;
}
EndpointAutoConfiguration
has a dependency on HealthIndicator
(which you implemented with HealthActuator
). EndpointAutoConfiguration
依赖于HealthIndicator
(您使用HealthActuator
实现)。
So you end up with a circular dependency.所以你最终会得到一个循环依赖。 This happens when 2 beans needs each other to instantiate themselves (through constructor injection).当 2 个 bean 需要彼此实例化自己时(通过构造函数注入),就会发生这种情况。 You can break the cycle by using a setter injection:您可以使用 setter 注入来打破循环:
@Component
public class HealthActuator implements HealthIndicator {
private MetricsEndpoint metricsEndpoint;
@Autowired
private void setMetricsEndpoint(MetricsEndpoint metricsEndpoint) {
this.metricsEndpoint = metricsEndpoint;
}
public HealthActuator() {
}
@Override
public Health health() {
long uptime = (Long) metricsEndpoint.invoke().get("uptime");
// logic with uptime
return Health.up().build();
}
}
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.