Open ml-taehoon-choi opened 1 year ago
This might be an input ordering issue. Try adding @AutoConfigureAfter or Import Springs new Metrics autoconfiguration.
Fix:https://github.com/yidongnan/grpc-spring-boot-starter/pull/907
If the constructor injection is causing issues until the update. you can use the following approach:
@Component
class A {
@GrpcClient("test")
private lateinit var stub: TestStub
}
@Component
class A {
private var stub: TestStub
@GrpcClient("test")
fun setStub(stub: TestStub) {
this.stub = stub
}
}
Any update on this issue? As we would prefer to not use the above workaround.
Hey guys, Are there any updates on this? We've just run into the same problem on our project
The bug When I use grpcClient in my server, I cannot see some metrics like jvm, hikari-cp, lettuce and so on from
actuator/metrics
endpoint. But if I comment out the GrpcClientMetricAutoConfiguration importing line, I can see the metrics.Stacktrace and logs x
Steps to Reproduce
kotlin code to reproduce:
dependencies in build.gradle.kts:
application.properties:
When you run the server and access localhost:8080/actuator/metrics, you cannot see jvm. metrics. But if you comment out the GrpcClientMetricAutoConfiguration importing line, you can see jvm. metrics.
The application's environment