[ http://issues.apache.org/jira/browse/QPID-29?page=all ]
Bhupendra Bhardwaj resolved QPID-29.
------------------------------------
Fix Version/s: M1
Resolution: Fixed
-If monitoring is only to see if the Qpid process is up or down, then there is
nothing to be done in Qpid implementation.
- For monitoring the logs, the Qpid will need to use Tivoli log4j appender.
That is adding another appender in log4j config file.
> Provide support for using Qpid JMX with Tivoli for application monitoring
> -------------------------------------------------------------------------
>
> Key: QPID-29
> URL: http://issues.apache.org/jira/browse/QPID-29
> Project: Qpid
> Issue Type: New Feature
> Environment: All
> Reporter: Marnie McCormack
> Assigned To: Bhupendra Bhardwaj
> Fix For: M1
>
>
> As part of an end user integration task we need to ensure that Qpid broker
> instances can be monitored using Tivoli.
> I think that since Tivoli provide a JMX container that this should be fairly
> straightforward but request that some analysis is completed to ensure that it
> would be fairly simple for an Tivoli administrator to connect to and use the
> Qpid JMX interfaces.
> A quick set of instructions about how to do this would be useful once the
> analysis is complete.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
