Surface errors from Connect workers

[ybyzek]

Is your feature request related to a problem? Please describe.
Users have no visibility into connect worker status and errors in ksqldb

Describe the solution you'd like
Need to surface connect worker (not connector task) status and errors to ksqldb

[agavra]

@ybyzek - I believe this was fixed by #3289 it will show the trace if there is some error message (NOTE that you need to DESCRIBE CONNECTOR to get this information)

[ybyzek]

@agavra for clarification, will it show the trace if there is an error message for the connect worker or connector? The need is for both.

[agavra]

both 😄 the output will contain the trace for the connector in the top level and the trace for each task in the table below

You can see the test here: https://github.com/confluentinc/ksql/blob/master/ksql-cli/src/test/java/io/confluent/ksql/cli/console/ConsoleTest.java#L633 (I mock the trace for both)

[ybyzek]

@agavra If no connector has been submitted, but the connect worker has failed, how does it get surfaced? Wouldn't DESCRIBE CONNECTOR be blank?

[agavra]

oh now I understand.. I thought the distinction was between task and connector. You are right, if the connect worker fails this is only shown in the logs

[ybyzek]

Right, so a few levels to reporting. IIUC

• task: addressed by feat: include error message in DESCRIBE CONNECTOR (MINOR) #3289
• connector: addressed by feat: include error message in DESCRIBE CONNECTOR (MINOR) #3289
• connect worker: unaddressed...needs to be resolved by this GH issue