-
Notifications
You must be signed in to change notification settings - Fork 445
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
GUI Monitor #354
Comments
This is your first issue in the repository. Thank you for raising this issue.' first issue |
You need to enable the Jolokia service and then open the file |
Hi, what do you mean with enabling the Jolokia service? |
kafka-monitor/config/xinfra-monitor.properties Lines 82 to 84 in 77f9655
|
@zigarn since the jolokia service needs to run to view the xinfra-monitor web ui I assume the port needed to access the xinfra-monitor ui will be the jolokia port(8778 by default)? I am unable to hit the Can you offer further guidance on how to reach the xinfra-monitor web ui? |
@sean-rossignol : once the jolokia service is enabled in xinfra-monitor, you just open directly in your browser directly the static file |
Thanks for your reply. If no port is specified then the browser will default to one of 80 or 443 and neither of those ports are open on our nodes which run xinfra-monitor at present. So just to confirm, are you stating that one of these ports has to be opened to access the xinfra-mnitor web ui? Is there a way to specify a separate port to access the xinfra-montior web ui through? |
Looks like this web UI is not automatically exposed anymore (#220) and that's why the doc about it disappeared (#315). So, you need to expose yourself the webapp folder through a simple webserver of your choice like nginx, lighttpd, or even a simple Or you can simply open locally this file in your browser (with kafka-monitor/webapp/index.html Lines 203 to 204 in a97a60b
|
Hi,
From this blog https://engineering.linkedin.com/blog/2016/05/open-sourcing-kafka-monitor, seems there is a GUI available for Xinfra Monitor. However, the readme page does not provide detailed steps on how to access such GUI?
The text was updated successfully, but these errors were encountered: