-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add metrics to monitor the ConsumerGroup replicas changes #3386
Add metrics to monitor the ConsumerGroup replicas changes #3386
Conversation
Understanding how KEDA scales up and down Knative Kafka resources is critical to debugging any performance problem that the autoscaler might introduce, so we need to expose new metrics that record mutations to Knative resources done by KEDA. `kafka_controller_consumer_group_expected_replicas` records number of expected replicas for a given Kafka consumer group resource. `kafka_controller_consumer_group_ready_replicas` records number of ready replicas for a given Kafka consumer group resource. Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
Codecov Report
@@ Coverage Diff @@
## main #3386 +/- ##
=============================================
+ Coverage 58.47% 70.84% +12.37%
- Complexity 0 761 +761
=============================================
Files 91 90 -1
Lines 9245 3077 -6168
Branches 0 265 +265
=============================================
- Hits 5406 2180 -3226
+ Misses 3410 730 -2680
+ Partials 429 167 -262
Flags with carried forward coverage won't be shown. Click here to find out more. |
/retest-required |
4 similar comments
/retest-required |
/retest-required |
/retest-required |
/retest-required |
/test reconciler-tests-namespaced-broker |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Cali0707, pierDipi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest-required |
5 similar comments
/retest-required |
/retest-required |
/retest-required |
/retest-required |
/retest-required |
/test channel-integration-tests-sasl-ssl |
/retest-required |
/test channel-integration-tests-sasl-plain |
/test reconciler-tests-namespaced-broker |
/test upgrade-tests |
/test reconciler-tests |
It merged 🎉 |
…ve-extensions#3386) Understanding how KEDA scales up and down Knative Kafka resources is critical to debugging any performance problem that the autoscaler might introduce, so we need to expose new metrics that record mutations to Knative resources done by KEDA. `kafka_controller_consumer_group_expected_replicas` records number of expected replicas for a given Kafka consumer group resource. `kafka_controller_consumer_group_ready_replicas` records number of ready replicas for a given Kafka consumer group resource. Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
…ve-extensions#3386) (#879) Understanding how KEDA scales up and down Knative Kafka resources is critical to debugging any performance problem that the autoscaler might introduce, so we need to expose new metrics that record mutations to Knative resources done by KEDA. `kafka_controller_consumer_group_expected_replicas` records number of expected replicas for a given Kafka consumer group resource. `kafka_controller_consumer_group_ready_replicas` records number of ready replicas for a given Kafka consumer group resource. Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
Understanding how KEDA scales up and down Knative Kafka
resources is critical to debugging any performance problem
that the autoscaler might introduce, so we need to expose new
metrics that record mutations to Knative resources done by KEDA.
This is the table representation of the new metrics
note: resource in this context means user-facing resources: KafkaSource, Trigger, Subscription; so no internal or generated names should be used.
Part of #1537
Proposed Changes
Release Note
Docs