Skip to content
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 Jolokia #450

Closed
wants to merge 14 commits into from
Closed

Add Jolokia #450

wants to merge 14 commits into from

Conversation

ngvlongit1
Copy link

Add Jilokia HTTP Server to monitoring metric of kafka

@sscaling
Copy link
Collaborator

Thanks for the PR, however - I don't think we're interested in adding jolokia to the project at this time as it is outside the core Apache Kafka offerings (which is what this image packages). It also seems a fairly inactive project judging by the github repo: https://github.com/rhuss/jolokia

I'll leave the PR open for a bit to allow for further comment, but I suspect it's easier just to mount the JAR and configure KAFKA_OPTS or make a new image with wurstmeister/kafka as the base with your specific extras included.

@ngvlongit1
Copy link
Author

Thanks for the review.
I think Jolokia is useful for monitoring. Mount JAR to images and set execute for file is not secure.
Do you know why my PR is failed on Travis? I did not edit any case of test.

@sscaling
Copy link
Collaborator

I think Jolokia is useful for monitoring

This is subjective and adds an additional component to maintain. It is not critical to running Kafka which is why I don't think it's universally required.

Do you know why my PR is failed on Travis?

Looks related to #451 - I have raised #452 as a work-around

Fix kafkacat to version 5.0.0 image (wurstmeister#452)
@ngvlongit1
Copy link
Author

Do you know why my PR is failed on Travis?

Looks related to #451 - I have raised #452 as a work-around

Thanks

@alvarolmedo
Copy link

+1

@alvarolmedo
Copy link

Jolokia is active, exists commits in the last month.
I've created the PR #503 to integrate with jolokia's version 1.6.1 based in this PR of @ngvlongit1.

@sscaling
Copy link
Collaborator

sscaling commented Jun 5, 2019

Thanks @alvarolmedo - but my comments still stand. This is not a universal solution - and not something that we want to maintain at this point in time.

@sscaling sscaling closed this Jun 5, 2019
@ebuildy
Copy link

ebuildy commented Apr 19, 2020

Jolikia is very famous project to monitor JVM application. About Kafka, we use elastic-beat https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-module-kafka.html.

As Docker build principle, all Jolikia related stuff should come at the end of the Dockerfile.

What about to create a tag suffit such as "with-jolikia" ?

@ebuildy
Copy link

ebuildy commented Apr 19, 2020

Or maybe, a simple wiki post, or a Dockerfile example such as :

FROM wurstmeister/kafka:1.0.0

ENV KAFKA_JOLOKIA_PORT=7777

RUN TRG="$KAFKA_HOME/libs/jolokia-jvm-1.6.0-agent.jar" && \
    wget "http://search.maven.org/remotecontent?filepath=org/jolokia/jolokia-jvm/1.6.0/jolokia-jvm-1.6.0-agent.jar" -O ${TRG} && \
    chmod a+x ${TRG}

ENV KAFKA_OPTS="-javaagent:$KAFKA_HOME/libs/jolokia-jvm-1.6.0-agent.jar=port=$KAFKA_JOLOKIA_PORT,host=0.0.0.0 $KAFKA_OPTS"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants