-
Notifications
You must be signed in to change notification settings - Fork 7
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
Port integration with Promotheus from amq collection #11
Comments
@rpelisse can I work on it? |
@RanabirChakraborty Please do! |
@RanabirChakraborty Are you anywhere on this topic? if you need any help, maybe ask Guido or @rmarting? |
AFAIK Prometheus export agent is not included in AMQ Streams for RHEL. The monitoring can be done using JMX ports as another JVM process. The documentation describing that is here: https://access.redhat.com/documentation/en-us/red_hat_amq_streams/2.4/html/using_amq_streams_on_rhel/monitoring-str#con-jmx-configuration-options-str Kafka Exporter is the component that exposes some metrics for Prometheus, so we can review it and add as a deployment option. Info: https://access.redhat.com/documentation/en-us/red_hat_amq_streams/2.4/html-single/using_amq_streams_on_rhel/index#assembly-kafka-exporter-str |
@rmarting Given your feedback and the use of JMX instead of Promotheus, I wonder if we should not simply close this. If someone wants to provide integration with Promotheus, we'll be happy to merge it, but I don't think it should be on our priority list. WDYT? |
I agree @rpelisse ! The latest commits allow to declare the JMX properties so they will allow to monitor and get the metrics from Kafka components. As there is no an official way to implement the Prometheus integration, we can close this issue. In the future, a new one can track better that integration. Go ahead and close it! |
Fixed by #93 |
SUMMARY
The amq collection has support for Promotheus that could be easily (hopefully) ported into this one.
ISSUE TYPE
The text was updated successfully, but these errors were encountered: