Rod Cordova created KAFKA-7586:
----------------------------------
Summary: Connector status endpoint HTTP response codes
Key: KAFKA-7586
URL: https://issues.apache.org/jira/browse/KAFKA-7586
Project: Kafka
Issue Type: Improvement
Components: KafkaConnect
Affects Versions: 1.1.1
Reporter: Rod Cordova
It appears that the HTTP response code for the status endpoint is always
200/OK. It would be extremely helpful if the response code was NOT 200/OK if
there are FAILED connector states or task states. Having to parse the response
body JSON in order to determine actual health adds unnecessary burden on the
upstream client doing the health check.
Based on the existing documentation you can see that even though there is a
FAILED worker task the HTTP response code is 200/OK
([https://docs.confluent.io/current/connect/references/restapi.html#get--connectors-(string-name)-status])
We run these connectors in Docker containers and have resorted to Docker health
checks (calling a simple script to parse the JSON status response body) but
would much prefer to leverage the HTTP response code as that is the lowest
common denominator supported by most proxies/load balancers etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
