CCDAK · Question #215
You have a Connect cluster with multiple connectors deployed. One connector is not working as expected. You need to find logs related to that specific connector to investigate the origin of the issue.
The correct answer is B. Modify the 'log4j.properties' file to add a dedicated log appender for the connector.. To isolate logs for a specific connector, you can modify the log4j.properties file to add a dedicated log appender for that connector's class or logger name. This allows you to route logs from the connector to a separate file, making troubleshooting easier without affecting other
Question
You have a Connect cluster with multiple connectors deployed. One connector is not working as expected. You need to find logs related to that specific connector to investigate the origin of the issue. How can you find the connector's logs?
Options
- AModify the 'log4j.properties' file to enable connector context.
- BModify the 'log4j.properties' file to add a dedicated log appender for the connector.
- CChange the log level to DEBUG to have connector context information in logs.
- DMake no change, there is no way to find the logs other than by stopping all the other connectors.
How the community answered
(27 responses)- A4% (1)
- B74% (20)
- C7% (2)
- D15% (4)
Explanation
To isolate logs for a specific connector, you can modify the log4j.properties file to add a dedicated log appender for that connector's class or logger name. This allows you to route logs from the connector to a separate file, making troubleshooting easier without affecting other connectors.
Topics
Community Discussion
No community discussion yet for this question.