scholzj commented on issue #1341:
URL: 
https://github.com/apache/camel-kafka-connector/issues/1341#issuecomment-1054590077


   No, that is not really how Kafka Connect works. Kafka Connect provides one 
or more worker nodes on which one or more connectors and their tasks are 
scheduled. There is an abstraction layer in place which abstracts the connector 
from directly using Kafka. So it cannot get the underlying Connect errors like 
this. Also, as I said -> the connector and connect lifecycles are decoupled. So 
single connector failing does not necessarily mean anything for the state of 
other connectors or of the Connect cluster. (If you want a direct link between 
the connector state and the pod state, perhaps other ways to use Camel might be 
better.)
   
   Connect can provide bunch of other metrics. For the problem like above, the 
count of connections from the Connect cluster might be useful. There are also 
metrics with connector and task states which you can use. If you use Strimzi, 
you can check the metrics examples and the Grafana Dashboards.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to