-
Notifications
You must be signed in to change notification settings - Fork 734
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 Kafka Prometheus metrics export #128
Commits on Jan 19, 2018
-
Configuration menu - View commit details
-
Copy full SHA for b275895 - Browse repository at this point
Copy the full SHA b275895View commit details -
Configuration menu - View commit details
-
Copy full SHA for d82b419 - Browse repository at this point
Copy the full SHA d82b419View commit details -
Configuration menu - View commit details
-
Copy full SHA for 162902c - Browse repository at this point
Copy the full SHA 162902cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 74a5177 - Browse repository at this point
Copy the full SHA 74a5177View commit details -
This is an optional feature, but belongs to the broker pods,
so let's evaluate kubectl patch to add it
Configuration menu - View commit details
-
Copy full SHA for da113d2 - Browse repository at this point
Copy the full SHA da113d2View commit details -
Evaluates JVM memory limit awareness
Interesting input for #112, for use with broker and zk pods in addition to KAFKA_HEAP_OPTS.
Configuration menu - View commit details
-
Copy full SHA for eaf9ebd - Browse repository at this point
Copy the full SHA eaf9ebdView commit details -
On start the metrics pod gesses that it has ~45%
of the memory limit as "Max. Heap Size (Estimated)" Reducing limits as experiment for #112.
Configuration menu - View commit details
-
Copy full SHA for 66255af - Browse repository at this point
Copy the full SHA 66255afView commit details -
Configuration menu - View commit details
-
Copy full SHA for e05b790 - Browse repository at this point
Copy the full SHA e05b790View commit details -
With 120M you get OOMKilled even on brokers with modest metrics volumes
This reverts commit 66255af.
Configuration menu - View commit details
-
Copy full SHA for f1e6e96 - Browse repository at this point
Copy the full SHA f1e6e96View commit details -
Removes liveness probes, to focus on memory limits,
and rely on metric staleness alerts instead for exporter liveness. This reverts commit 74a5177.
Configuration menu - View commit details
-
Copy full SHA for 0d78e08 - Browse repository at this point
Copy the full SHA 0d78e08View commit details
Commits on Jan 29, 2018
-
It was the liveness probe that killed the metrics container,
and we might not need liveness if we have alerts for stale metrics. This reverts commit f1e6e96.
Configuration menu - View commit details
-
Copy full SHA for cfe434c - Browse repository at this point
Copy the full SHA cfe434cView commit details
Commits on Feb 3, 2018
-
”In a production Kafka cluster, an offline partition
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.
Configuration menu - View commit details
-
Copy full SHA for 152bb19 - Browse repository at this point
Copy the full SHA 152bb19View commit details -
Configuration menu - View commit details
-
Copy full SHA for f022138 - Browse repository at this point
Copy the full SHA f022138View commit details -
Configuration menu - View commit details
-
Copy full SHA for a564ed2 - Browse repository at this point
Copy the full SHA a564ed2View commit details