KIP-1017: Leverage the health check endpoint for Kafka Connect #654
Description
Issue submitter TODO list
- I've searched for an already existing issues here
- I'm running a supported version of the application which is listed here and the feature is not present there
Is your proposal related to a problem?
When Kafka Connect is not rechargeable, the UI does not make it clear that the Kafka Connect cluster may be offline/unavailable. If we try to connect to a Kafka Connect instance that is not available, it fails and it does not make it clear that the cluster is not reachable.
Just like we have the option to know if a Kafka Cluster is offline/not reachable, we should have a similar option for Kafka Connect
Describe the feature you're interested in
With KIP-1017 the REST endpoint, GET /health was added to the Kafka Connect REST API. If the worker is healthy, the response will have a 200 status code and if it is unhealthy it will show a 500 status code.
Describe alternatives you've considered
- Manually check the status of the connect cluster externally and/or inspect the logs of the Kafka UI