search

ryomasaber / javamelody

Automatically exported from code.google.com/p/javamelody
0 stars 0 forks source link

Expose javamelody metrics via jmx #435

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Can't access javamelody metrics via jmx
2.
3.

What is the expected output? What do you see instead?
Expose javamelody metrics via jmx

What version of the product are you using? On what application server, JDK,
operating system?
tomcat

Please provide any additional information below.

Original issue reported on code.google.com by tomer...@gmail.com on 14 Sep 2014 at 1:56

GoogleCodeExporter commented 8 years ago 
What is your use case?
Why do you want to use jmx instead of the external api?
https://code.google.com/p/javamelody/wiki/ExternalAPI#PNG_and_lastValue

Original comment by evernat@free.fr on 14 Sep 2014 at 7:50

GoogleCodeExporter commented 8 years ago 
An external monitoring system which knows to poll jmx only is monitoring my
tomcat

Original comment by tomer...@gmail.com on 15 Sep 2014 at 3:39

GoogleCodeExporter commented 8 years ago 
1) Which external monitoring system? Nagios?

2) Is it a system written in java which polls jmx itself, or does it start java 
each time it wants to retrieve jmx value(s)?

Original comment by evernat@free.fr on 15 Sep 2014 at 7:42

GoogleCodeExporter commented 8 years ago 
1. Custom in-house system (not developed anymore).

2.  Its actually polling jmx values based on configuration.

Original comment by tomer...@gmail.com on 15 Sep 2014 at 9:01

GoogleCodeExporter commented 8 years ago 
ok i guess for now i can workaround this by exposing in my tomcat jmx with a 
"bridge" to 
https://code.google.com/p/javamelody/wiki/ExternalAPI#PNG_and_lastValue and 
thus the external monitoring system would be able to watch it. this resolves it.
thanks

Original comment by tomer...@gmail.com on 15 Sep 2014 at 3:26

GoogleCodeExporter commented 8 years ago 
It's ok.
Given your comment, I will resolve this as done.

If you wish to create a new "clean" issue for "Expose metrics via jmx" with a 
bit more general use case, you are welcome.
I may set a low priority to that issue, but it can exist anyway.

Original comment by evernat@free.fr on 15 Sep 2014 at 10:22