Feature request or enhancement

Right now, we do not have any way to know the delay between when the records got committed and when the records went into Kafka. The commit SCN and the LSN provides the exact time when the records were exactly committed into the database. This information has to be translated into a timestamp and exposed as a JMX metrics.

Even though this can be achieved through the Kafka transformation option but connecting to the database for each messages cause delay in performance. Since, source connector already have this information needed for building this timestamp its best if we can achieve the same using the JMX metrics.

Which use case/requirement will be addressed by the proposed feature?

With this enhancement we can seamlessly know the delay the source connectors took to identify the committed records and pushed into the Kafka. We can directly use the Jolokia to query the metrics needed to achieve the functionality.

Implementation ideas (optional)

• Take the COMMIT SCN and COMMIT LSN from source connectors
• Use the SCN_TO_TIMESTAMP(<COMMIT SCN>) and sys.fn_cdc_map_lsn_to_time(<COMMIT LSN>) to arrive at the timestamp.
• Translate these dates to UTC as database server timestamps will be different compared to Kafka.
• Add the metrics commit_ts with this EPOCH timestamp and expose the JMX metrics.