Found https://issues.apache.org/jira/browse/FLINK-22766

________________________________
From: Alexey Trenikhun <yen...@msn.com>
Sent: Tuesday, May 25, 2021 3:25 PM
To: Ardhani Narasimha <ardhani.narasi...@razorpay.com>; 陳樺威 
<oscar8492...@gmail.com>; Flink User Mail List <user@flink.apache.org>
Subject: Re: KafkaSource metrics

Looks like when KafkaSource is used instead of FlinkKafkaConsumer, metrics 
listed below are not available. Bug? Work in progress?


Thanks,
Alexey
________________________________
From: Ardhani Narasimha <ardhani.narasi...@razorpay.com>
Sent: Monday, May 24, 2021 9:08 AM
To: 陳樺威 <oscar8492...@gmail.com>
Cc: user <user@flink.apache.org>
Subject: Re: KafkaSource metrics

Use below respectively

flink_taskmanager_job_task_operator_KafkaConsumer_bytes_consumed_rate - 
Consumer rate
flink_taskmanager_job_task_operator_KafkaConsumer_records_lag_max - Consumer lag
flink_taskmanager_job_task_operator_KafkaConsumer_commit_latency_max - commit 
latency

unsure if reactive mode makes any difference.
On Mon, May 24, 2021 at 7:44 PM 陳樺威 
<oscar8492...@gmail.com<mailto:oscar8492...@gmail.com>> wrote:
Hello,

Our team tries to test reactive mode and replace FlinkKafkaConsumer with the 
new KafkaSource.
But we can’t find the KafkaSource metrics list. Does anyone have any idea? In 
our case, we want to know the Kafka consume delay and consume rate.

Thanks,
Oscar

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
IMPORTANT: The contents of this email and any attachments are confidential and 
protected by applicable laws. If you have received this email by mistake, 
please (i) notify the sender immediately; (ii) delete it from your database; 
and (iii) do not disclose the contents to anyone or make copies thereof. 
Razorpay accepts no liability caused due to any inadvertent/ unintentional data 
transmitted through this email.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Reply via email to