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
Is there an existing issue that is already proposing this?
I have searched the existing issues
Is your feature request related to a problem? Please describe it
The Microservice Health Indicator only checks whether a producer can connect to Kafka, but I’m also interested in the state of the consumer. If the consumer has crashed, then I want the health indicator to fail.
unfortunately, implementing this myself I ran into a few issues:
accessing the ServerKafka instance, which contains the consumer, doesn’t seem possible in the context of a health indicator
The usage should be the same as the existing MicroserviceHealthIndicator, though it shouldn’t require instantiating a new instance of ServerKafka, it should use the existing one.
What is the motivation / use case for changing the behavior?
I need to be able to know if the consumer has crashed and include that information in a liveness check.
The text was updated successfully, but these errors were encountered:
My workaround I've found is to move the custom microservice implementation into a module in the application context, add a public method to expose the consumer and then use app.resolve to fetch it to run connectMicroservice:
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
The Microservice Health Indicator only checks whether a producer can connect to Kafka, but I’m also interested in the state of the consumer. If the consumer has crashed, then I want the health indicator to fail.
unfortunately, implementing this myself I ran into a few issues:
Describe the solution you'd like
I’d like the Microservice Health Indicator to also check the status of the Server side, not just the client side.
Teachability, documentation, adoption, migration strategy
The usage should be the same as the existing MicroserviceHealthIndicator, though it shouldn’t require instantiating a new instance of ServerKafka, it should use the existing one.
What is the motivation / use case for changing the behavior?
I need to be able to know if the consumer has crashed and include that information in a liveness check.
The text was updated successfully, but these errors were encountered: