You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Status

Current state: Draft

Discussion thread: TBD

JIRA: KAFKA-14740

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

MirrorSourceConnector registers a few metrics to track the mirroring of records from the source to the target cluster. Its metrics have the "target", "topic", "partition" tags. By default, with DefaultReplicationPolicy, the topic name contains the source cluster alias as its prefix, for example source.topic. However as it's part of the topic tag it's oftentimes not easily usable in monitoring tools. In addition, with IdentityReplicationPolicy the source cluster alias does not appear in the metrics at all.

Public Interfaces

A new tag, source, will be added to all metrics registered by MirrorSourceConnector. It will contain the source cluster alias. For example:
kafka.connect.mirror:type=MirrorSourceConnector,source=one,target=two,topic=newtopic,partition=0

Proposed Changes

Update MirrorSourceMetrics to have a new tag, source, and set it to the source cluster alias.

Compatibility, Deprecation, and Migration Plan

  • What impact (if any) will there be on existing users?
  • If we are changing behavior how will we phase out the older behavior?
  • If we need special migration tools, describe them here.
  • When will we remove the existing behavior?

Test Plan

Describe in few sentences how the KIP will be tested. We are mostly interested in system tests (since unit-tests are specific to implementation details). How will we know that the implementation works as expected? How will we know nothing broke?

Rejected Alternatives

If there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other way.

  • No labels