[
https://issues.apache.org/jira/browse/KAFKA-18133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940370#comment-17940370
]
oshione gabriel esiemokhai commented on KAFKA-18133:
----------------------------------------------------
Hello, I hope you're doing well. As per the documentation, the 'TARGET' will
always be your SECONDARY cluster. The provided metrics output aligns with the
documentation requirements, so everything looks good. Please let me know if
this answers your question or if you need further clarification.
> Not getting 'target' details for metrics group: kafka.connect.mirror
> --------------------------------------------------------------------
>
> Key: KAFKA-18133
> URL: https://issues.apache.org/jira/browse/KAFKA-18133
> Project: Kafka
> Issue Type: Bug
> Components: connect, mirrormaker
> Affects Versions: 3.6.2
> Reporter: MANOJ KUMAR GHOSH
> Priority: Major
>
> Using 7.6.3-ce, I have a Mirrormaker cluster with multiple connectors. The
> problem is related to metrics where the metrics group: 'kafka.connect.mirror'
> is used to get the metrics 'replication-latency-ms-avg', as per
> documentation:
> [https://kafka.apache.org/documentation/#georeplication-monitoring|https://kafka.apache.org/documentation/#georeplication-monitoring,][;|https://kafka.apache.org/documentation/#georeplication-monitoring,]
> it should come along below details:
> * {{target}}
> * {{topic}}
> * {{{}partition{}}}{{{}{}}}
> But, I am not getting 'target' details irrespective of setting the target
> alias in the connector config.
> Below is a sample of the metrics output that I am getting-
> {{}}
> {code:java}
> kafka.connect.mirror,topic=aggr_test
> RecordCount=354.0,RecordAgeMs=98.0,RecordAgeMsMin=98.0,RecordAgeMsMax=273.0,RecordAgeMsAvg=156.33333333333334,ReplicationLatencyMs=103.0,ReplicationLatencyMsMin=103.0,ReplicationLatencyMax=278.0,ReplicationLatencyAvg=161.66666666666666,ByteRate=25.139806812404675,partition=59
> {code}
> Not sure if this is a known issue or if something is wrong on my end. Please
> suggest
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
