JMX instrumentation + hudson plugin for jets3t

[Doug MacEachern-3]

Hi All,

Looking to get some feedback on a proof-of-concept patch that adds some
JMX instrumentation to the jets3t library..
MBeans include counters for bucket/object operations (GET, PUT, DELETE,
etc.) and counters for service error codes
(http://docs.amazonwebservices.com/AmazonS3/2006-03-01/index.html?ErrorC
odeList.html).  I created a git mirror of the jets3t cvs repo using:
http://gist.github.com/55379

You can checkout and view the jmx changes using:
% git clone git://github.com/hyperic/jets3t.git
% git branch --track jmx origin/jmx
% git checkout jmx
% git diff master..jmx

You can also browse the changes via:
New classes:
http://github.com/hyperic/jets3t/commit/f58920a265906130edfa55989e0a27aa
0db8fc81
Integrated:
http://github.com/hyperic/jets3t/commit/b2cc31dafa1cf3137573f08f6653b3f7
db5f1e55

And see it in action using cockpit or any jets3t app by adding the
system property: -Dcom.sun.management.jmxremote

The object and bucket MBeans are disabled by default, to enable add:
-Ds3service.object.mx=true -Ds3service.bucket.mx=true

We're currently using it with a plugin to copy Hudson
(https://hudson.dev.java.net/) build artifacts to s3 via jets3t:
http://github.com/dougm/hudson-s3
And monitoring the MBeans attributes via Hyperic HQ
(http://www.hyperic.com/) and collectd (http://www.collectd.org/) with
jcollectd (http://support.hyperic.com/display/hypcomm/jcollectd).

Any interest in having this folded into the jets3t mainline?  I know
jets3t still supports Java 1.4, so there'd be another change required to
compile against mx4j or similar when using 1.4 runtimes.  Otherwise the
code itself should still work with 1.4.  Thoughts?

Thanks,
-Doug



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[James Murty-3]

Hi Doug,

Sorry I've taken so long to get back to you on this, I've just moved overseas and have been busy dealing with everything that entails.

I don't mind the idea of folding some JMX instrumentation into JetS3t proper, though I will have to research whether there are any ways of doing it without adding more library requirements to build the library. I'm reluctant to add more library dependencies.

I'll have a closer look at your code in the next few days and think about what it would mean to add this support to JetS3t.

James

---
http://www.jamesmurty.com

On Sat, Feb 21, 2009 at 1:53 PM, Doug MacEachern <Doug.MacEachern@...> wrote:

Hi All,

Looking to get some feedback on a proof-of-concept patch that adds some
JMX instrumentation to the jets3t library..
MBeans include counters for bucket/object operations (GET, PUT, DELETE,
etc.) and counters for service error codes
(http://docs.amazonwebservices.com/AmazonS3/2006-03-01/index.html?ErrorC
odeList.html).  I created a git mirror of the jets3t cvs repo using:
http://gist.github.com/55379

You can checkout and view the jmx changes using:
% git clone git://github.com/hyperic/jets3t.git
% git branch --track jmx origin/jmx
% git checkout jmx
% git diff master..jmx

You can also browse the changes via:
New classes:
http://github.com/hyperic/jets3t/commit/f58920a265906130edfa55989e0a27aa
0db8fc81
Integrated:
http://github.com/hyperic/jets3t/commit/b2cc31dafa1cf3137573f08f6653b3f7
db5f1e55

And see it in action using cockpit or any jets3t app by adding the
system property: -Dcom.sun.management.jmxremote

The object and bucket MBeans are disabled by default, to enable add:
-Ds3service.object.mx=true -Ds3service.bucket.mx=true

We're currently using it with a plugin to copy Hudson
(https://hudson.dev.java.net/) build artifacts to s3 via jets3t:
http://github.com/dougm/hudson-s3
And monitoring the MBeans attributes via Hyperic HQ
(http://www.hyperic.com/) and collectd (http://www.collectd.org/) with
jcollectd (http://support.hyperic.com/display/hypcomm/jcollectd).

Any interest in having this folded into the jets3t mainline?  I know
jets3t still supports Java 1.4, so there'd be another change required to
compile against mx4j or similar when using 1.4 runtimes.  Otherwise the
code itself should still work with 1.4.  Thoughts?

Thanks,
-Doug



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...