Tomcat Management: Jmx4Perl Makes it Easier - Blogging Techstacks
jeudi 6 mars 2014 à 17:16 Slobberbone, le 06/03/2014 à 17:16
For the intermediate level application server administrator like me, "knowing" that I can manage my tomcat containers remotely using jmx is a lot different than actually writing some useful script that utilizes it. The problem with jmx, in my opinion, is that it's a systems administration technology built into the Java Virtual Machine that is marketed to Developers, not Systems Administrators. Monitoring and Management is probably the last thing on a developer's mind and sometimes I think that the cost in terms of time learning jmx is too high. The payoff in portability from one job to another is probably better than it was having to learn Tcl to write BigIP iRules but probably not much higher. Many sysadmins I've talked to have never heard of it and when they do find out what it is, the need to learn Java first is usually the first barrier that gets thrown up. When you're supporting hundreds of servers and you use a combination of shell scripts and perl scripts most of the time to manage the entire server and not just the VM, learning Java is one of those things that would be nice to learn but who has the time?
While sifting through the keywords reports in this site's google analytics data over this long holiday weekend, I came across Jmx4Perl and I'm really glad I took the time to look it up. Previously, I had heard about JMX4R, which required JRuby and a JVM but all that Jmx4Perl requires is Perl. Installation via 'cpan' is probably the easiest way to do it. Simply open up a cpan shell and then type "install JMX::Jmx4Perl" and you're all set.
(Permalink)
For the intermediate level application server administrator like me, "knowing" that I can manage my tomcat containers remotely using jmx is a lot different than actually writing some useful script that utilizes it. The problem with jmx, in my opinion, is that it's a systems administration technology built into the Java Virtual Machine that is marketed to Developers, not Systems Administrators. Monitoring and Management is probably the last thing on a developer's mind and sometimes I think that the cost in terms of time learning jmx is too high. The payoff in portability from one job to another is probably better than it was having to learn Tcl to write BigIP iRules but probably not much higher. Many sysadmins I've talked to have never heard of it and when they do find out what it is, the need to learn Java first is usually the first barrier that gets thrown up. When you're supporting hundreds of servers and you use a combination of shell scripts and perl scripts most of the time to manage the entire server and not just the VM, learning Java is one of those things that would be nice to learn but who has the time?
While sifting through the keywords reports in this site's google analytics data over this long holiday weekend, I came across Jmx4Perl and I'm really glad I took the time to look it up. Previously, I had heard about JMX4R, which required JRuby and a JVM but all that Jmx4Perl requires is Perl. Installation via 'cpan' is probably the easiest way to do it. Simply open up a cpan shell and then type "install JMX::Jmx4Perl" and you're all set.
(Permalink)