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.
Das neueste Release von check_hpasm ermittelt jetzt nicht mehr nur den globalen Status der cpqRack-MIB eines BladeCenters, sondern liest die wichtigsten Tabellen detailliert aus. Aufgerufen mit -v liefert check_hpasm eine Übersicht der verbauten Komponenten samt deren Status. Und so sieht das dann aus:
| Author: | Gerhard Laußer |
|---|---|
| Tags: | Blade, BladeCenter, check_hpasm, cpqRack, hp, Nagios, Plugins |
| Categories: | nagios |
When you have already used jmx4perl you probably have remarked that the
argument list can be quite lengthy, often due to the verbose JMX
URLs. This gets even worse with jmx4perl’s forthcoming proxy
mode. Luckily, since version 0.36 it knows about configuration files which are the topic of this post.
| Author: | Roland Huß |
|---|---|
| Tags: | Config::General, configuration, Jmx4Perl |
| Categories: | jmx4perl |
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.
Statt zwei Wochen hat das Redesign von check_hpasm nun doch zwei Monate gedauert, aber dafür ist das Plugin für künftige Erweiterungen bestens gerüstet. Hinzugekommen ist die Unterstützung der neuen G6-Proliants und die Fähigkeit, auch HP BladeCenter (wenn auch nicht so detailliert) und HP Storage-Systeme überwachen zu können. Es wurden auch ein paar Verbesserungen an der (nicht ganz einfachen) Erkennung der Speichermodule vorgenommen. Bei einigen Anwendern dürften jetzt defekte Riegel ans Tageslicht kommen, deren Zustand sich mit der 3.x-Version nicht feststellen liess.
| Author: | Gerhard Laußer |
|---|---|
| Tags: | check_hpasm, hp, Nagios, proliant |
| Categories: | nagios |
Nagios installations which rely on working external commands should have a check which verifys that external commands are really working. This plugins sends a test command and checks the logfile if that command occurs.
$ check_nagios_external_commands -t 120 -p /usr/local/nagios/var/rw/nagios.cmd \
-l /usr/local/nagios/var/nagios.log
WARNING - command took 23s|command_write=0.85s command_read=22s| Author: | Sven Nierlein |
|---|---|
| Tags: | check_nagios_external_commands, Nagios |
| Categories: | nagios |
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.