Open GoogleCodeExporter opened 8 years ago
Currently, it's not possible.
To implement this, configuration should be simple (properties file perhaps).
Original comment by evernat@free.fr
on 20 Feb 2014 at 8:40
Evernat, do You find it usefull?
If it's simple, will You try to add it in next release ?
Original comment by jjaku...@gmail.com
on 21 Feb 2014 at 10:19
useful? yes.
next release? yes, if you contribute and test the code
Original comment by evernat@free.fr
on 22 Feb 2014 at 9:29
[deleted comment]
"you contribute" means I implement and test it and send a patch,
or you do the implementation and I test it ?
Original comment by jjaku...@gmail.com
on 23 Feb 2014 at 9:54
You can implement, test and send a patch.
Original comment by evernat@free.fr
on 23 Feb 2014 at 9:56
Issue 445 has been merged into this issue.
Original comment by evernat@free.fr
on 23 Nov 2014 at 10:31
This sounds like a great idea.
Ideally, it should support more than "one graph per method in the JMX bean".
It should support more dynamic data.
For example, if I make a JMX bean that exposes JBoss Infinispan cache
statistics, I want to have statistics per cache (name). This is just one
example of "dynamic" data, that cannot be known at application startup time.
But for the JBoss Infinispan cache case, it might be that Javamelody should get
"native" support for that, like it has for ehcache. I might look into how much
work that would be.
Original comment by alf.hoge...@gmail.com
on 9 Jan 2015 at 6:35
I did implement the collect custom JMX bean statistics feature in a basic
version that fits my needs. It can only add new graphs by numeric attributes in
JMX beans.
See:
https://github.com/evernat/javamelody/pull/2
https://groups.google.com/forum/#!topic/javamelody/hA8Z5EfFMTY
In my opinion the requested "statistics per cache" feature is not easy to
implement and needs more time to create a proper concept. But my implementation
is very extensible. I think the bigest problem is how to translate the value of
the JMX bean into multiple different counters.
The easyiest solution for the enhanced JMX feature would be to implement a
feature for Map<String, Numeric> attributes. The implementation could be
changed to create a graph for every entry in the map.
But does this fit all of our needs or is it just a workaround? As soon as we
need more flexibility we have to deal with some kind of scripting language. For
example JavaScript or Beanshell could be integrated to transform the JMX bean
values to the appropriate information that can be visualized.
Original comment by sascha...@googlemail.com
on 11 Apr 2015 at 10:23
The JavaMelody project has moved. Follow this issue at
https://github.com/javamelody/javamelody/issues/384
Original comment by evernat@free.fr
on 12 Jul 2015 at 10:17
Original issue reported on code.google.com by
jjaku...@gmail.com
on 20 Feb 2014 at 10:10