Merged
Conversation
Closed
and rely on metric staleness alerts instead for exporter liveness. This reverts commit 74a5177.
Contributor
Author
|
Gotcha: |
and we might not need liveness if we have alerts for stale metrics. This reverts commit f1e6e96.
This was referenced Feb 2, 2018
may be impacting the producer clients, losing messages or causing back-pressure in the application.
This is most often a “site down” type of problem and will need to be addressed immediately.”
Excerpt from: Neha Narkhede, Gwen Shapira, and Todd Palino. ”Kafka: The Definitive Guide”.
We now export kafka_controller_kafkacontroller_value{name="OfflinePartitionsCount",} and friends.
See #140 for why.
Contributor
Author
|
Time to merge. Feels quite robust now; you can't really live without it in cases like #116. Noteworthy:
|
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.
... only to brokers, and using
kubectl patchto keep this optional. The JMX containers consume significant memory (100-200 MB per pod) so you'll only want them if you have Prometheus. For other uses of JMX, like the interactive use cases that the spec seems designed for, see #96.This PR replaces #49 (which is still a valid addon for tags <3.1) and #93. Zookeeper metrics is excluded in this PR though, because I hope #125 includes what we need from there.
Both memory limits and liveness probe is experimental right now. We're running them in QA now to see how low we can go. See #49 (comment) for history.
We'll keep an eye on the
jmx_scrape_duration_secondsmetric now, and OOMKilled events. Once again see #49 for history.@yacut Do you have better config still, than the one I copied to this PR?