Für alle Freunde des leichtgewichtigen JMX Monitorings findet sich in der neuesten Ausgabe des Perl Magazins eine Vorstellung von jmx4perl. In dem 9-seitigen Artikel wird JMX im Allgemeinen, die jxm4perl (bzw. Jolokia) Agenten und die Programmierung mit JMX::Jmx4Perl beleuchtet.
Die Ausgabe lässt sich online für 6 € inkl. Versandkosten bestellen. Fragen zu dem Artikel bzw. jmx4perl im Allgemeinen beantworte ich in den Kommentaren hier gerne.
OMD, the new star on the open monitoring scene, has been released in version 0.44 two weeks ago with a lot of enhancements and new addons.
This post explains why a dedicated Tomcat Connector reserved for the jmx4perl agent is a useful thing.
Jmx4Perl reaches is next evolution step, with a bunch of new features. The most important news are a new JDK 6 based JVM agent which allows monitoring of arbitrary Java applications (not only servlet containers) and the support for bulk read requests.
Jmx4Perl's next release 0.60 is out in the wild.
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 check_jmx4perl.
mode. Luckily, since version 0.36 it knows about configuration files which are the topic of this post.
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.