Zookeeper metrics port registration#183
Open
kamilchociej wants to merge 2 commits intodatastax:mainfrom
Open
Conversation
Author
|
There is a workaround for that issue. You can register Pod Monitor on "client" port and reconfigure scraping using relabelings: |
pgier
approved these changes
Dec 23, 2025
|
Should this one be merged? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Zookeeper container is currently not configured to register the metrics port, which prevents the creation of a PodMonitor for monitoring Zookeeper metrics. This issue is a critical blocker, as it limits the ability to scrape and collect metrics from the Zookeeper pods effectively.
This PR addresses the problem by ensuring that the Zookeeper container properly exposes and registers the metrics port, enabling the integration with Prometheus via a PodMonitor.