Skip to content

Update Strimzi Metrics Reporter to version 0.3.0#12392

Merged
scholzj merged 4 commits intostrimzi:mainfrom
OwenCorrigan76:test_SMR-0.3.0
Mar 6, 2026
Merged

Update Strimzi Metrics Reporter to version 0.3.0#12392
scholzj merged 4 commits intostrimzi:mainfrom
OwenCorrigan76:test_SMR-0.3.0

Conversation

@OwenCorrigan76
Copy link
Contributor

@OwenCorrigan76 OwenCorrigan76 commented Feb 5, 2026

Type of change

  • Enhancement / new feature

Description

Current Strimzi is using Srimzi Metrics Reporter 0.2.0. This PR updates the version to 0.3.0-rc1 in the kafka-thirdparty-libs directories and updates the code base to use Strimzi Metrtics Reporter 0.3.0-rc1.

Checklist

  • Write tests
  • Make sure all tests pass
  • Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
  • Update CHANGELOG.md

@OwenCorrigan76 OwenCorrigan76 added this to the 0.51.0 milestone Feb 5, 2026
configMap.put("metric.reporters", StrimziMetricsReporterConfig.KAFKA_CLASS);
configMap.put("kafka.metrics.reporters", StrimziMetricsReporterConfig.YAMMER_CLASS);
configMap.put("metric.reporters", StrimziMetricsReporterConfig.CLIENT_CLASS);
configMap.put("kafka.metrics.reporters", StrimziMetricsReporterConfig.SERVER_YAMMER_CLASS);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kafka.metrics.reporters is not a Connect configuration. I'm not sure what this test is doing but this should not need to be set.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for spotting. Removed.

@codecov
Copy link

codecov bot commented Feb 5, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.01%. Comparing base (568706e) to head (aa5a887).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #12392      +/-   ##
============================================
+ Coverage     74.99%   75.01%   +0.01%     
+ Complexity     6651     6650       -1     
============================================
  Files           373      373              
  Lines         25367    25367              
  Branches       3376     3376              
============================================
+ Hits          19025    19029       +4     
+ Misses         4956     4948       -8     
- Partials       1386     1390       +4     
Files with missing lines Coverage Δ
...cluster/model/KafkaBrokerConfigurationBuilder.java 92.97% <100.00%> (ø)
...luster/model/KafkaConnectConfigurationBuilder.java 94.29% <100.00%> (ø)
...tor/cluster/model/KafkaMirrorMaker2Connectors.java 90.71% <100.00%> (ø)

... and 6 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

CHANGELOG.md Outdated
Comment on lines +6 to +10
* Update Strimzi Metrics Reporter to version 0.3.0.
This version splits the metrics reporter into separate client and server artifacts with updated class names:
* `io.strimzi.kafka.metrics.prometheus.ClientMetricsReporter` for Kafka clients (Bridge, Connect, MirrorMaker 2)
* `io.strimzi.kafka.metrics.prometheus.ServerKafkaMetricsReporter` for Kafka brokers (Kafka metrics)
* `io.strimzi.kafka.metrics.prometheus.ServerYammerMetricsReporter` for Kafka brokers (Yammer metrics)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this really relevant? The user does not configure any of this, or?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess not, as the user does not configure this. Removed

<dependency>
<groupId>io.strimzi</groupId>
<artifactId>metrics-reporter</artifactId>
<artifactId>client-metrics-reporter</artifactId>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't the client part a dependency of the server part? So should we really have both?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, you are correct. Refactored

@im-konge
Copy link
Member

im-konge commented Feb 6, 2026

/gha run pipeline=regression

@github-actions
Copy link

github-actions bot commented Feb 6, 2026

⏳ System test verification started: link

The following 6 job(s) will be executed:

  • regression-brokers-and-security-amd64 (oracle-vm-8cpu-32gb-x86-64)
  • regression-operators-amd64 (oracle-vm-8cpu-32gb-x86-64)
  • regression-operands-amd64 (oracle-vm-8cpu-32gb-x86-64)
  • regression-brokers-and-security-arm64 (oracle-vm-8cpu-32gb-arm64)
  • regression-operators-arm64 (oracle-vm-8cpu-32gb-arm64)
  • regression-operands-arm64 (oracle-vm-8cpu-32gb-arm64)

Tests will start after successful build completion.

@im-konge
Copy link
Member

im-konge commented Feb 6, 2026

@OwenCorrigan76 as the 0.3.0 is still not released and this PR is testing the RC1, I would move it to draft for now. Once the metrics-reporter is released, it should be opened for review.

@im-konge im-konge marked this pull request as draft February 6, 2026 15:19
@github-actions
Copy link

github-actions bot commented Feb 6, 2026

❌ System test verification failed: link

@im-konge
Copy link
Member

im-konge commented Feb 6, 2026

There is one failing test for the metrics-reporter - for the Bridge.

Error:  Errors: 
Error:  io.strimzi.systemtest.metrics.StrimziMetricsReporterST.testKafkaBridgeMetrics
Error:    Run 1: StrimziMetricsReporterST.testKafkaBridgeMetrics:230 » Runtime
Error:    Run 2: StrimziMetricsReporterST.testKafkaBridgeMetrics:230 » Runtime

but we cannot do anything about it, until new Bridge version is released.
I think that we even cannot merge this PR once metrics-reporter 0.3.0 is officially released -> at least until we have new version of Bridge.

@github-actions
Copy link

github-actions bot commented Feb 6, 2026

❌ System test verification failed: link

@im-konge
Copy link
Member

@strimzi/maintainers @OwenCorrigan76 what are we going to do with this PR? Should we split it into two PRs where in first we will cover everything except Bridge and in the second one we will cover Bridge? I think we should move this forward in some way.

@ppatierno
Copy link
Member

From my perspective I would like to release the new bridge 0.34.0 with the 0.3.0 metrics reporter support, so I think this is still valid?

@im-konge
Copy link
Member

From my perspective I would like to release the new bridge 0.34.0 with the 0.3.0 metrics reporter support, so I think this is still valid?

It is valid, but the question is if we should split it. If you will run the tests with new Bridge that has metrics-reporter 0.3.0, I think that the tests will anyway fail for the metrics-reporter, as the configuration is different.
That's why I said that we should split it into two implementation, where the Bridge part will be covered in PR updating Bridge to newer version.

@im-konge
Copy link
Member

Or, we can have this PR only and change the Bridge image used in tests to the latest one. But I'm not sure what else it can break and if it's the right thing.

@scholzj scholzj modified the milestones: 0.51.0, 0.52.0 Feb 24, 2026
@im-konge
Copy link
Member

So now when the 0.51.0 release is branched and we have RC1 (RC2 coming soon), we should move this forward. I'm still proposing the same -> removing the Bridge config from this PR, have this bump for everything else and when we have PR with new Bridge, changes needed for the metrics-reporter 0.3.0 will be added as part of it. WDYT @strimzi/maintainers ?

@scholzj
Copy link
Member

scholzj commented Feb 27, 2026

So now when the 0.51.0 release is branched and we have RC1 (RC2 coming soon), we should move this forward. I'm still proposing the same -> removing the Bridge config from this PR, have this bump for everything else and when we have PR with new Bridge, changes needed for the metrics-reporter 0.3.0 will be added as part of it. WDYT @strimzi/maintainers ?

That seems reasonable.

@ppatierno
Copy link
Member

Fine with me. Thanks.

@im-konge
Copy link
Member

@OwenCorrigan76 could you please update this PR accordingly? Thanks

@OwenCorrigan76
Copy link
Contributor Author

Will do @im-konge. Thanks guys

@OwenCorrigan76 OwenCorrigan76 marked this pull request as ready for review March 4, 2026 11:14
@OwenCorrigan76 OwenCorrigan76 requested review from mimaison and scholzj and removed request for mimaison March 4, 2026 11:15
@OwenCorrigan76 OwenCorrigan76 requested review from im-konge, mimaison and scholzj and removed request for im-konge and scholzj March 4, 2026 11:23
@scholzj
Copy link
Member

scholzj commented Mar 4, 2026

/gha run pipeline=regression

@github-actions
Copy link

github-actions bot commented Mar 4, 2026

⏳ System test verification started: link

The following 6 job(s) will be executed:

  • regression-brokers-and-security-amd64 (oracle-vm-8cpu-32gb-x86-64)
  • regression-operators-amd64 (oracle-vm-8cpu-32gb-x86-64)
  • regression-operands-amd64 (oracle-vm-8cpu-32gb-x86-64)
  • regression-brokers-and-security-arm64 (oracle-vm-8cpu-32gb-arm64)
  • regression-operators-arm64 (oracle-vm-8cpu-32gb-arm64)
  • regression-operands-arm64 (oracle-vm-8cpu-32gb-arm64)

Tests will start after successful build completion.

<properties>
<strimzi-oauth.version>0.17.1</strimzi-oauth.version>
<strimzi-metrics-reporter.version>0.2.0</strimzi-metrics-reporter.version>
<strimzi-metrics-reporter.version>0.3.0-rc1</strimzi-metrics-reporter.version>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was released already, so should it be 0.3.0?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @scholzj. Updated

<properties>
<strimzi-oauth.version>0.17.1</strimzi-oauth.version>
<strimzi-metrics-reporter.version>0.2.0</strimzi-metrics-reporter.version>
<strimzi-metrics-reporter.version>0.3.0-rc1</strimzi-metrics-reporter.version>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

@github-actions
Copy link

github-actions bot commented Mar 4, 2026

🎉 System test verification passed: link

ocorriga added 4 commits March 5, 2026 08:03
Signed-off-by: ocorriga <ocorriga@redhat.com>
Signed-off-by: ocorriga <ocorriga@redhat.com>
Signed-off-by: ocorriga <ocorriga@redhat.com>
Signed-off-by: ocorriga <ocorriga@redhat.com>
@im-konge
Copy link
Member

im-konge commented Mar 5, 2026

/gha run pipeline=regression

@github-actions
Copy link

github-actions bot commented Mar 5, 2026

⏳ System test verification started: link

The following 6 job(s) will be executed:

  • regression-brokers-and-security-amd64 (oracle-vm-8cpu-32gb-x86-64)
  • regression-operators-amd64 (oracle-vm-8cpu-32gb-x86-64)
  • regression-operands-amd64 (oracle-vm-8cpu-32gb-x86-64)
  • regression-brokers-and-security-arm64 (oracle-vm-8cpu-32gb-arm64)
  • regression-operators-arm64 (oracle-vm-8cpu-32gb-arm64)
  • regression-operands-arm64 (oracle-vm-8cpu-32gb-arm64)

Tests will start after successful build completion.

@github-actions
Copy link

github-actions bot commented Mar 5, 2026

⚠️ System test verification skipped: link

@im-konge
Copy link
Member

im-konge commented Mar 5, 2026

/gha run pipeline=regression

@github-actions
Copy link

github-actions bot commented Mar 5, 2026

⏳ System test verification started: link

The following 6 job(s) will be executed:

  • regression-brokers-and-security-amd64 (oracle-vm-8cpu-32gb-x86-64)
  • regression-operators-amd64 (oracle-vm-8cpu-32gb-x86-64)
  • regression-operands-amd64 (oracle-vm-8cpu-32gb-x86-64)
  • regression-brokers-and-security-arm64 (oracle-vm-8cpu-32gb-arm64)
  • regression-operators-arm64 (oracle-vm-8cpu-32gb-arm64)
  • regression-operands-arm64 (oracle-vm-8cpu-32gb-arm64)

Tests will start after successful build completion.

@github-actions
Copy link

github-actions bot commented Mar 6, 2026

🎉 System test verification passed: link

@im-konge im-konge requested a review from scholzj March 6, 2026 17:00
@scholzj scholzj merged commit e8f9225 into strimzi:main Mar 6, 2026
32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants