The io.github.nomisRev.kafka.publisher.KafkaPublisher interface in this library exposes metrics() function to get metrics from the underlying org.apache.kafka.clients.producer.KafkaProducer.
Unfortunately, the io.github.nomisRev.kafka.receiver.KafkaReceiver interface does not expose anything similar to obtain metrics.
This is a feature request to make it possible to obtain metrics from the underlying org.apache.kafka.clients.consumer.KafkaConsumer. As for now, I don't even see any workaround to get consumer metrics, because KafkaConsumer gets created on each receive() call and is very well encapsulated.
There are different extensions on org.apache.kafka.clients.consumer.*-types (including raw KafkaConsumer) in Consumer.kt and I could probably refactor current code to use them, but all of them are marked as deprecated with a recommendation to use io.github.nomisRev.kafka.receiver.KafkaReceiver instead.
I guess that receive() method on KafkaReceiver should rather return some advanced combined type, which has both traits: 1) the Flow itself + 2) other interfaces with additional capabilities (for example, for accessing metrics)
Hello
The
io.github.nomisRev.kafka.publisher.KafkaPublisherinterface in this library exposesmetrics()function to get metrics from the underlyingorg.apache.kafka.clients.producer.KafkaProducer. Unfortunately, theio.github.nomisRev.kafka.receiver.KafkaReceiverinterface does not expose anything similar to obtain metrics.This is a feature request to make it possible to obtain metrics from the underlying
org.apache.kafka.clients.consumer.KafkaConsumer. As for now, I don't even see any workaround to get consumer metrics, becauseKafkaConsumergets created on eachreceive()call and is very well encapsulated.There are different extensions on
org.apache.kafka.clients.consumer.*-types (including rawKafkaConsumer) inConsumer.ktand I could probably refactor current code to use them, but all of them are marked as deprecated with a recommendation to useio.github.nomisRev.kafka.receiver.KafkaReceiverinstead.I guess that
receive()method onKafkaReceivershould rather return some advanced combined type, which has both traits: 1) theFlowitself + 2) other interfaces with additional capabilities (for example, for accessing metrics)