Stefan is doing some amazing work here and I think you might be interested. This is an example for server monitoring in a dashboard.
[Update: Source Code now with Garbacollector]
Sometimes it is necessary to tackle down CLM performance issues. To monitor the OS resources like CPU, IO, Memory etc. is not really helpful, because Java is like a black box for an OS like LINUX. With JMX you can look “behind the scene”.
Sometimes it is necessary to tackle down CLM performance issues. To monitor the OS resources like CPU, IO, Memory etc. is not really helpful, because Java is like a black box for an OS like LINUX. With JMX you can look “behind the scene”.
You can monitor the Heap, Threads, Memory and other things from a CLM Tomcat Server. With the help of some JMX settings you can access this information with jconsole. jconsole is include in every Java JDK (not JRE) since 1.5.
But JMX has some disadvantages:
- Only Java
- Problems with firewalls. Especially Productive CLM server are in a protected environment, so it is nearly impossible to get access with your jconsole.
- “All or nothing” protection
Today we will create a Open Social Widget that will show the amount of running Threads, Heapsize, CCM Requests and Garbage Collector with the help of JMX…
View original post 105 more words
![[Update: Source Code now with Garbacollector]](http://rtcpractise.files.wordpress.com/2014/04/screen-shot-2014-04-06-at-20-01-48.png){kind=link}