Hi Lahiru,
As promised here are my thoughts about what I'd like to achieve from the
project I defined for your GSoC work.
So, currently we provide some JMX calls which expose various attributes in
the Qpid Java broker. We have users who are interested in these attributes,
but there's currently no simple way for them to get access to them. They can
view them on the management console (assuming they can get it working :-),
they can attach some other monitoring GUI or proprietary application.
For some of our JMX props, they can be set up to log alerts to the broker
log - which can again be monitored.
However, it would be really useful if they could simply use a CLI tool to
extract the information they're looking for.
I had envisaged it taking a really simple form:
- a shell script (bash or .bat) to call the CLI tool, probably simply
wrapping a java call, which will run as a daemon (or service)
- a config/properties file or command line options to specify:
- the JMX attribute to extract
- the frequency with which to extract it, in minutes (i.e. an
elapsed time between extraction like 5 minutes)
- a path into which to record the output
- an option for the output format (see my proposal info about
formatting etc) like csv, tab-delimited, html etc. This might be
better done
as optional export into another tool ?
- the properties/config should be extensible so that new attributes
implemented in the broker can easily be added
So, when a user wants to get useful management information from the broker
(but not using a GUI) they can simply create a props file and voila !
What do you think ? Does this make sense to you ok ?
I'll reply to your email about issues shortly, in a separate email.
Hth,
Thanks & Regards,
Marnie
