Re: Maven artifacts for RHQ 4.0.1
On Thu, Jun 30, 2011 at 09:06, Heiko W.Rupp <hrupp(a)redhat.com> wrote:
Hey,
Am 30.06.2011 um 08:59 schrieb Andreas Veithen:
> I'm able to build the custom plugin against the 4.0.1 libs now. Thanks, Ian.
Wanna tell a bit more what you are doing?
Sure. We are using RHQ as a platform to monitor our WebSphere
environment (see also my previous mail on the dev list). Since the
support for WebSphere in RHQ is almost non existent, I have developed
a custom plugin for this. Right now we have the following features
working:
* Collection of PMI statistics from applications (response times,
request counts, etc.), data sources, J2C connection factories
(including JMS), SIBus destinations and thread pools.
* Resource discovery based on the persistent WebSphere configuration
(using a connection to the deployment manager).
* The plugin internally uses WebSphere APIs (which themselves are
mostly based on standard JMX APIs), but provides a compatibility layer
for EMS based plugins. This allows us to reuse the existing support
for JVM statistics in RHQ. We also tested this with another custom EMS
based plugin, but not yet with the existing Hibernate plugin.
* Remote capture of log events (i.e. log messages written to
SystemOut.log). This either uses a component (RasLoggingService)
available out of the box in WebSphere or a custom component that in
addition allows to link these log events to individual application
components (servlets or enterprise beans).
* Experimental support for retrieving statistics from DB2 and linking
them to data sources defined in WebSphere.
I started working on that plugin shortly before the 4.0 release, and
we are still using RHQ 3.0 right now (the plugin builds fine against
the 4.0 libraries but deployment fails). We are successfully using the
solution to monitor our WebSphere acceptance and production
environments, primarily in order to identify and investigate
performance issues. That is why the features of our plugin primarily
focus on collecting metrics, and to a lesser extent on support for
operations and configurations, which means that they are somewhat
orthogonal to the features (managing application configurations and
patching libraries) discussed about a month ago on the dev list.
Andreas