[KAFKA-243] Log Associated Connector Name with "Resume Token Not Found" Message Created: 09/Aug/21 Updated: 27/Oct/23 Resolved: 10/Aug/21 |
|
| Status: | Closed |
| Project: | Kafka Connector |
| Component/s: | Source |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Unknown |
| Reporter: | Diego Rodriguez (Inactive) | Assignee: | Ross Lawley |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | internal-user | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Case: | (copied to CRM) |
| Documentation Changes: | Not Needed |
| Description |
|
Hi Team! Although the message for the "Resume Token Not Found" error has been greatly improved thanks to KAFKA-91, it is still not easy to identify which connector throws the exception:
Understanding that one Source Connector opens a single Change Stream to the source MongoDB Cluster, would it be possible to include the Source Connector name within the error message? This would allow for easier discovery of the affected Connector, specially in distributed environments where several other Connectors might be running. Eventually, logging the associated Source (or Sink) Connector name would be appreciated for any other errors where identifying the associated Connector might be otherwise complicated and painful. Thanks |
| Comments |
| Comment by Ross Lawley [ 10/Aug/21 ] | |||||
|
Hi diego.rodriguez, I believe this functionality is already available via Kafka & Logging configuration:
Source: Kafka Connect Improvements in Apache Kafka 2.3 As such I'm closing this ticket as "Works as Designed". If you feel our documentation would benefit from including this configuration, then please open a DOCSP ticket. Ross |