From users-return-27109-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Mon Apr 04 20:01:46 2011 Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 63883 invoked from network); 4 Apr 2011 20:01:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Apr 2011 20:01:46 -0000 Received: (qmail 72107 invoked by uid 500); 4 Apr 2011 20:01:45 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 72027 invoked by uid 500); 4 Apr 2011 20:01:45 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 71979 invoked by uid 99); 4 Apr 2011 20:01:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Apr 2011 20:01:45 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Mike.Kitchin@tideworks.com designates 64.18.3.40 as permitted sender) Received: from [64.18.3.40] (HELO exprod8og120.obsmtp.com) (64.18.3.40) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Apr 2011 20:01:39 +0000 Received: from tideworks.com ([12.129.5.185]) (using TLSv1) by exprod8ob120.postini.com ([64.18.7.12]) with SMTP ID DSNKTZojjZF6i5W5gOA94HaNdnF6tT25KGI1@postini.com; Mon, 04 Apr 2011 13:01:19 PDT Received: from LWEXMB02.usa.int ([fe80::5404:e877:ded1:373e]) by LWEXHUB02.usa.int ([::1]) with mapi id 14.01.0218.012; Mon, 4 Apr 2011 12:57:15 -0700 From: "Mike J. Kitchin" To: "users@activemq.apache.org" Subject: Best way to remotely monitor AMQ 5.x installation via .NET? Thread-Topic: Best way to remotely monitor AMQ 5.x installation via .NET? Thread-Index: AcvzAn34fdbz7RFUR0+FRH9+R8ZUOA== Date: Mon, 4 Apr 2011 19:57:14 +0000 Message-ID: <87936EAF7CFD504B80F2AA68845673031337F5@LWEXMB02.usa.int> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.17.2.115] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Hi there, We use AMQ extensively in our enterprise to integrate our C++ and C# applic= ations (CMS & NMS API's, respectively) and would like to integrate runtime = monitoring of the broker into an existing, web-based monitoring mechanism b= uilt into one of our applications.=20 This mechanism already integrates a fair amount of information from across = our products but is, nonetheless, .NET based. After experimenting with what= AMQ advisory messages and JMX can provide, I've concluded the JMX MBean-ho= sted information already available in AMQ would be the best source of proce= ss utilization- and stability-type information, but haven't found a.NET cli= ent for JMX, presumably because standards JMX connectors are RMI-based. The best option, therefore, seems to be some sort of RESTFul JMX bridge or = the like that I can then proxy from our monitoring mechanism. Is there any = collective experience with these sorts of add-ons to AMQ and, if so, which = sounds like the most straightforward and trouble-free approach? Please let me know if I may provide any additional information. Thanks. -Regards, MjK - - - - - "Here lies Zeke, second-fastest draw in Cripple Creek." - Epitaph (Cripple Creek, CO) Michael J. Kitchin (Senior Software Engineer) Tideworks Technology http://www.tideworks.com