Hey Andreas,

With the OSGi approach limiting the monitoring at the JVM seems not enough, 
thus implementing a dedicated solution from within the application code itself 
could be a huge win for the Ops folks and I'm sure the Devs would benefit from 
it too.
Granted, unlike having Matterhorn friendly Sys{admin,ops,eng} as yourself 
plugging a tool directly on the JVM or on the existing REST endpoints this will 
require "non-feature" oriented JAVA code writing, a small price to pay IMHO in 
comparison to the potential benefits of JMX based instrumentation. 

Last month Netflix (do I really need to introduce "them"?) announced Servo, 
check it out to see what can be done with JMX

http://techblog.netflix.com/2012/02/announcing-servo.html

Also a quite interesting thesis paper " Resource monitoring and visualization 
of OSGi-based software components" by Tuukka Miettinen albeit a four years old 
one...

http://www.vtt.fi/inf/pdf/publications/2008/P685.pdf

Jaime (the Jaime that Tobias named on his email that keeps advocating for 
built-in pro active monitoring to help the comrades in the Data Centers 
trenches  =) )


On Mar 15, 2012, at 3:34 AM, [email protected] wrote:

> Hi,
> 
> we have been using Cacti/snmp for monitoring the JVM by using
> JAVA_OPTS="-Xms1024m -Xmx1024m -XX:MaxPermSize=256m 
> -Dcom.sun.management.config.file=/home/$MATTERHORN_USER/snmp.properties"
> in the matterhorn startup-skript.
> 
> Sadly this won't work anymore with OpenJDK being used in 1.3+.
> 
> So I'd be very happy to JMX based monitoring installed and what it can do (if 
> I'd be a developer, this would be a +1 ;).
> 
> Do you know of any openjdk-replacement for the -Dcom.sun.management.config 
> switch? I searched the web a little, and it seems openjdk comes without snmp 
> support (why?).
> 
> Regards, Andreas
> 
> Tobias Wunden schrieb am Thu, 15 Mar 2012 betreff "[Opencast Matterhorn]...":
>> Hi all,
>> 
>> those of you who have heard Jaime advocate for improved monitoring 
>> capabilities of Matterhorn have probably been convinced that this is an area 
>> where immediate action is due. And those running Matterhorn in production 
>> will probably agree that even though monitoring can be done using the REST 
>> endpoingt, having better means of accessing Matterhorn metrics might be a 
>> good thing.
>> 
>> Christoph and I have been looking into the technologies used throughout the 
>> field and have come to the conclusion that there are a couple of possible 
>> approaches, but the one that really stands out is using the Java Management 
>> Extension (JMX) [1]. So what is JMX? This was found on the Oracle blog [3]:
>> 
>>      "To make it short, JMX is a technology that lets you implement 
>> management interfaces for Java applications.
>> 
>>      A management interface, as defined by JMX, is composed of named objects 
>> - called MBeans (Management Beans). MBeans are registered with a name (an 
>> ObjectName) in an MBeanServer. To manage (a) resource(s) in your 
>> application, you will write an MBean that defines its management interface, 
>> and then register that MBean in your MBeanServer. The content of the 
>> MBeanServer can then be exposed through various protocols, implemented by 
>> protocol connectors, or protocol adaptors.
>> 
>>      A protocol connector (e.g. the JMX RMI Connector) exposes the MBeans as 
>> they are - so a remote client sees the same model than a local client. A 
>> protocol adaptor (e.g. an SNMP adaptor, or HTML adaptor) performs (or 
>> provides hooks to let you perform) a model mediation - to adapt the model to 
>> what a client of that protocol (e.g. SNMP Manager, or Web Browser) would 
>> expect to see."
>> 
>> People tcan then start building their monitoring needs ontop of the JMX 
>> architecture, which allows for quite a bit of flexibility with the number of 
>> open and commercial tools out there that support the JMX standard.
>> 
>> So our #proposal is to start adding JMX support to Matterhorn and I would 
>> like to get feedback and/or +/- ones on this suggested approach.
>> 
>> Tobias
>> 
>> [1]  
>> http://www.oracle.com/technetwork/java/javase/tech/javamanagement-140525.html
>> [2]  http://openjdk.java.net/tools/svc/jconsole/
>> [3]  https://blogs.oracle.com/jmxetc/entry/what_is_jmx
>> _______________________________________________
>> Matterhorn mailing list
>> [email protected]
>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>> 
>> 
>> To unsubscribe please email
>> [email protected]
>> _______________________________________________
>> 
> 
> -----------------------
> [email protected]
> 01/58801 DW 41523
> mobil: 0664/60 588 4523
> TU Wien
> DVR-Nummer: 0005886
> -----------------------
> _______________________________________________
> Matterhorn mailing list
> [email protected]
> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> 
> 
> To unsubscribe please email
> [email protected]
> _______________________________________________

_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to