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
A client may have the need to expose its health to the rest of the system (Kubernetes) and so client needs a way to know if the parallel consumer connection to the broker has been lost. It later needs to be informed if the connection has been re-established.
@fowlerp-qlik are there mechanisms from the Kafka clients for this that you want exposed? Have you looked at available JMX metrics from the raw clients?
@fowlerp-qlik do you specifically want to be informed of connection state changes, or is it enough to have the state exposed through metrics / health check?
I've also just realised that AK consumer doesn't actually expose this either. We will be adding metrics very soon, let's see if that will be enough. Otherwise, we can also implement some active health check system like starting an admin client and interrogating the cluster about something.
A client may have the need to expose its health to the rest of the system (Kubernetes) and so client needs a way to know if the parallel consumer connection to the broker has been lost. It later needs to be informed if the connection has been re-established.
Related:
The text was updated successfully, but these errors were encountered: