[DOCS-15597] MongoDB Kafka Connector - Explain How To Better Track Connector Log Messages Created: 31/Aug/22  Updated: 15/Sep/22  Resolved: 15/Sep/22

Status: Closed
Project: Documentation
Component/s: Kafka
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Diego Rodriguez (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: kafka-documentation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Related
related to KAFKA-310 Add connector id to all log messages Closed
Participants:
Days since reply: 1 year, 23 weeks ago
Epic Link: DOCSP-11739

 Description   

Hi Team,

If Kafka Connect is running multiple MongoDB connectors it might not be clear which Connector is generating the log message and thus making debugging log messages very tricky.

The above can be improved by configuring Connector Context Logging (see KIP-449 and KAFKA-3816).

As such, I propose that we add to our Troubleshooting section a heading that says "Improving Connector Logging" and explain the following:

If Kafka Connect is running multiple MongoDB Connectors (or any other type of Kafka Connectors) it might not be clear which Connector is generating a given log message making troubleshooting more complicated.

When the above happens we recommend adding the following line (or un-comment it if already present) to file $KAFKA_HOME/config/connect-log4j.properties:

connect.log.pattern=[%d] %p %X{connector.context}%m (%c:%L)%n

Regards
Diego


Generated at Thu Feb 08 08:13:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.