Monitor Custom JBoss JMX Beans

[jordy_hyperic]

Hi,

We've got several applications (build by external party's) that deliver JMX Beans with internal performance information. We would like to view this information inside hyperic as part of the metric data. Several other monitoring tools discover these beans automaticaly as it's part of the JBoss JMX architecture and they show up inside the JMX Console. How can i get these counters ?

Thanks

Message was edited by: jordy

[Douglas MacEachern]

You can tell HQ to look for other MBeans during auto-discovery by
writing a simple plugin, see:

http://support.hyperic.com/confluence/display/DOCSHQ27/JBoss+Custom
+MBean+Plugin
http://support.hyperic.com/confluence/display/DOCSHQ27/JMX+Plugin

On Jan 16, 2007, at 2:46 AM, jordy wrote:

> Hi,
>
> We've got several applications (build by external party's) that
> deliver JMX Beans with internal performance information. We would
> like to view this information inside hyperic as part of the metric
> data. Several other monitoring tools discover these beans
> automaticaly as it's part of the JBoss JMX architecture and they
> show up inside the JMX Console. How can i get these counters ?
>
> Thanks
>
> Message was edited by: jordy
>

[jordy_hyperic]

This won't be able to auto discover the MX Beans? I'll have to create a XML file containing the list of variables it should monitor ? I tried it and it doesn't look like it's a super easy job.

Too bad, as the tool is pretty complete.

[Douglas MacEachern]

The XML plugin describes the MBean type(s) you wish to monitor,
attributes you want to collect as metrics, operations you want to
expose as control actions and notifications you'd want to capture.
We then auto-discover all instances of the MBean type your plugin
defines based on the ObjectName.
As you've probably seen with JBoss and other app servers, the
MBeanServer tends to have a ton of beans that are meant for internal
use, rather than server+application management from a product such as
HQ. In addition, there isn't a way to disambiguate between which
attributes are meant for configuration and which are meant for
monitoring. Nor is there a way to determine the units or collection
type of a given metric (newer revs of the JMX spec address this I
believe). We don't want to auto-discover *every* MBean in an
MBeanServer otherwise we'd end up with another jmx console. So we
require some molding of MBeans into the HQ world, but it should be
easy once you get the hang of it as it has been for many others.
Happy to help with the plugin if you want to share some details about
the MBean(s) you want to monitor.

On Jan 22, 2007, at 11:38 PM, jordy wrote:

> This won't be able to auto discover the MX Beans? I'll have to
> create a XML file containing the list of variables it should
> monitor ? I tried it and it doesn't look like it's a super easy job.
>
> Too bad, as the tool is pretty complete.
>

[jordy_hyperic]

MBean Name: Domain Name: Sas
service: Information

List of MBean attributes:

Name Type Access Value Description
SasTransactionPerformance
DbTransactionCount
HttpRequestTopPerformance
ActiveSASUsers
ReportingPeriod
DbTransactionTopPerformance
DbTransactionPerformance
HttpRequestCount
SasTransactionCount
HttpRequestPerformance
ErrorCount
WarningCount
SasTransactionTopPerformance

How do I have to create this file and where do I'll have to put it ?

Message was edited by: jordy

[Douglas MacEachern]

Here's a start, to deploy the plugin, see:
http://support.hyperic.com/confluence/display/DOCSHQ27/Plugin+Development+Center#PluginDevelopmentCenter-deployment

Then you'd just add a metric tag for any other MBean attributes you want to collect as monitoring data.