[Bug] MM2 should have its own default Strimzi Metrics configuration (#12180)#12277
Conversation
scholzj
left a comment
There was a problem hiding this comment.
Thanks for the PR. I left few comments - but it looks good otherwise.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #12277 +/- ##
=========================================
Coverage 74.79% 74.80%
- Complexity 6626 6631 +5
=========================================
Files 376 376
Lines 25345 25351 +6
Branches 3402 3402
=========================================
+ Hits 18957 18964 +7
Misses 4998 4998
+ Partials 1390 1389 -1
🚀 New features to boost your workflow:
|
e2bad14 to
2504004
Compare
|
Hi @scholzj |
|
/gha run pipeline=regression |
|
⏳ System test verification started: link The following 6 job(s) will be executed:
Tests will start after successful build completion. |
|
🎉 System test verification passed: link |
scholzj
left a comment
There was a problem hiding this comment.
One nit about the formatting. But looks good to me otherwise. Thanks.
| /** | ||
| * Default Strimzi Metrics Reporter allowlist for Kafka Connect. | ||
| * Check example dashboard compatibility in case of changes to existing regexes. | ||
| */ |
There was a problem hiding this comment.
I think this indentation change should not be here?
There was a problem hiding this comment.
Thank you for pointing it out. It is addressed in the new commit
…trimzi#12180 This commit fixes the issue where Kafka Connect and MirrorMaker 2 shared the same default Strimzi Metrics configuration, incorrectly exposing MM2 connector metrics in Kafka Connect's default metrics configuration. Changes: - Removed MM2-specific metrics (mirrorcheckpointconnector, mirrorsourceconnector) from Kafka Connect's DEFAULT_METRICS_ALLOW_LIST - Created DEFAULT_MIRROR_MAKER_2_METRICS_ALLOW_LIST for MirrorMaker 2 with both Connect and MM2-specific metrics - Added getDefaultMetricsAllowList() method for extensibility - Added comprehensive unit tests for both components Signed-off-by: Azeez Syed <syedazeez337@gmail.com>
2504004 to
10c6c2a
Compare
ppatierno
left a comment
There was a problem hiding this comment.
LGTM. Thanks for the contribution!
This PR fixes GitHub issue #12180 by giving MirrorMaker 2 its own default Strimzi Metrics configuration, separating it from Kafka Connect's configuration.
Problem
Previously, Kafka Connect and MirrorMaker 2 shared the same default metrics configuration, which incorrectly exposed MM2 connector metrics in Kafka Connect's default metrics configuration:
These MM2-specific metrics were appearing in Kafka Connect deployments even when MirrorMaker 2 wasn't being used.
Solution
Code Changes
Testing
All tests pass:
✅ Kafka Connect doesn't include MM2 metrics
✅ MirrorMaker 2 includes both Connect and MM2 metrics
✅ All existing tests still pass