Update Strimzi Metrics Reporter to version 0.3.0#12392
Conversation
995ea0a to
d1f311d
Compare
| 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); |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Thanks for spotting. Removed.
Codecov Report✅ All modified and coverable lines are covered by tests. 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
🚀 New features to boost your workflow:
|
CHANGELOG.md
Outdated
| * 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) |
There was a problem hiding this comment.
Is this really relevant? The user does not configure any of this, or?
There was a problem hiding this comment.
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> |
There was a problem hiding this comment.
Isn't the client part a dependency of the server part? So should we really have both?
There was a problem hiding this comment.
No, you are correct. Refactored
d1f311d to
5ca3e96
Compare
|
/gha run pipeline=regression |
|
⏳ System test verification started: link The following 6 job(s) will be executed:
Tests will start after successful build completion. |
|
@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. |
|
❌ System test verification failed: link |
|
There is one failing test for the metrics-reporter - for the Bridge. but we cannot do anything about it, until new Bridge version is released. |
|
❌ System test verification failed: link |
|
@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. |
|
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. |
|
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. |
|
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. |
|
Fine with me. Thanks. |
|
@OwenCorrigan76 could you please update this PR accordingly? Thanks |
|
Will do @im-konge. Thanks guys |
5ca3e96 to
c9bf55b
Compare
|
/gha run pipeline=regression |
|
⏳ System test verification started: link The following 6 job(s) will be executed:
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> |
There was a problem hiding this comment.
It was released already, so should it be 0.3.0?
| <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> |
|
🎉 System test verification passed: link |
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>
c9bf55b to
aa5a887
Compare
|
/gha run pipeline=regression |
|
⏳ System test verification started: link The following 6 job(s) will be executed:
Tests will start after successful build completion. |
|
|
|
/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 |
Type of change
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