-
Notifications
You must be signed in to change notification settings - Fork 125
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
Extract consumer group member_count as a separate metric #103
Comments
Added a new consumer_group_members topic to capture number of members in a consumer group and removed the `member_count` label from consumer_group_info Fixes redpanda-data#103
Added a new consumer_group_members topic to capture number of members in a consumer group and removed the `member_count` label from consumer_group_info Fixes redpanda-data#103
Added a new consumer_group_members topic to capture number of members in a consumer group and removed the `member_count` label from consumer_group_info Fixes redpanda-data#103
Added a new consumer_group_members topic to capture number of members in a consumer group and removed the `member_count` label from consumer_group_info Fixes redpanda-data#103
Added a new consumer_group_members topic to capture number of members in a consumer group and removed the `member_count` label from consumer_group_info Fixes redpanda-data#103
I agree that this makes sense and I'm surprised I haven't done that from the beginning on. Thank you for raising this issue and also filing the PR. I will try to review the PRs in the course of next week. Feel free to ping me in case it takes longer |
Thanks @weeco - sure, take your time. |
Added a new consumer_group_members topic to capture number of members in a consumer group and removed the `member_count` label from consumer_group_info Fixes redpanda-data#103
Technically you are right about the two other metrics, but I think given the stability it's fine to keep them as label as part of the topic info metric. |
Another disadvantage I've see with these numerical labels is when writing alert rules. I couldn't find a way create a prometheus rule that can check say: alert if number of any topic partitions go beyond 1000 |
Added a new consumer_group_members topic to capture number of members in a consumer group and removed the `member_count` label from consumer_group_info Fixes redpanda-data#103
Added a new consumer_group_members topic to capture number of members in a consumer group and removed the `member_count` label from consumer_group_info Fixes redpanda-data#103
Added a new consumer_group_members topic to capture number of members in a consumer group and removed the `member_count` label from consumer_group_info Fixes redpanda-data#103
Added a new consumer_group_members topic to capture number of members in a consumer group and removed the `member_count` label from consumer_group_info Fixes redpanda-data#103
Added a new consumer_group_members topic to capture number of members in a consumer group and removed the `member_count` label from consumer_group_info Fixes redpanda-data#103
Added a new consumer_group_members topic to capture number of members in a consumer group and removed the `member_count` label from consumer_group_info Fixes redpanda-data#103
Currently consumer group member_count is reported as a label in kminion_kafka_consumer_group_info metric.
When there is a high churn in a consumer group with members joining and leaving this leads to a high cardinality in this metric.
Moreover having a separate metric helps in monitoring the number of members in time.
The text was updated successfully, but these errors were encountered: