Jolokia and Jmx4Perl will go on tour this autumn. Roland Huss will talk about both projects in November at Devoxx, Antwerp, which is the biggest independent Java community conference in the world and at the Open Source Monitoring Conference, Nuremberg.
The summer break is over and Jolokia is one step closer to
1.0. Germans might reasonably argue, ‘ehm, what summer do you talk
about ?’ but at least 0.95 is now a fact and introduces two new
features. Very cool features, IMO.
Hand in hand, Jolokia and Jmx4Perl started their countdown for their first major version, scheduled late this summer.
While Jolokia got some minor enhancements, Jmx4Perl now finally got rid of any Java code, relying now completely on a Jolokia agent.
Let’s welcome the new kid on the labs.consol block: Jolokia.
Jmx4Perl 0.72 has been released which is a pure bug-fix release.
|Tags:||check_jmx4perl, jmx, Jmx4Perl|
This is the first announcement about my new toy osgish [os-gish], a shell for
The first developer version jmx4perl 0.55_1 with OSGi support has been pushed to CPAN.
Jmx4perl 0.51 has been released.
Glassfish Enterprise Server v3 has been released yesterday and it brings some exciting news related to monitoring. Here are some links to the new monitoring features of v3.
In its standalone mode, Mule provides a simple to use interface for custom agents to plug in. This blog post is about the new jmx4perl mule agent which can be used with
jmx4perl and the Nagios check
In our series of articles about configuring remote JMX access for the jmx4perl proxy mode, this article tackles how to enable JMX remoting for Weblogic Server 9 and 10. It is not specific to jmx4perl and explains several different setups and possible problems.
jmx4perl knows since some time how to restrict access to the agent (and soon proxy) servlet based on various criteria. However, this feature is unfortunately not yet well documented and a little bit hidden. This blog describes the nifty details and future roadmap.
As described in the last post jmx4perl can be operated in a so called agentless mode. For this to work, the target java server must be prepared for accepting remote JMX connections as described in JSR-160.
Unfortunately, this setup is not really standardized and specific to the Java JDK in use and the application server itself. In this post we concentrate on how to setup JMX remoting for JBoss.
Big news around: jmx4perl supports now an agentless mode in which the target platform can be monitored without installing the j4p agent servlet. This works by using
j4p.war as a JMX Proxy, which translates our JSON/HTTP protocol on the frontside to JSR-160 JMX remote requests on the backend and vice versa.