Hi Paul, On Thu, Apr 5, 2012 at 1:42 PM, Paul Fremantle <[email protected]> wrote:
> Excellent. Is there a way of "automatically" exposing the MBeans, so all > MBeans get exposed? Yes, that's the idea. I just checked in the first cut version of this implementation. It exposes all scalar attributes of all org.apache.synapse MBeans. By default the SNMP support is disabled in Synapse. Adding the following entry to synapse.properties will initialize the SNMP agent: synapse.snmp.enabled=true Synapse SNMP agent supports SNMPv1 and SNMPv2c. By default it runs in SNMPv1 mode which seems to be the most widely used version of SNMP even today. But if needed it can be configured to run in SNMPv2c mode which is also quite popular (Wikipedia states it to be the de-facto SNMP standard). I haven't quite figured out the SNMPv3 API and the security model yet. Therefore I've left it out for the moment. But for someone looking to monitor Synapse using SNMP what we have now is a handful. I have implemented all the obvious nitty-gritty stuff like ability to specify a custom port, ability to specify a custom community string etc. One major thing left is to document the Synapse MIB and add it to our documentation. Thanks, Hiranya > > Paul > > > On Wed, Apr 4, 2012 at 5:12 AM, Hiranya Jayathilaka > <[email protected]>wrote: > >> Hi Folks, >> >> You may have noticed the other mail thread from Alex on OID assignment. >> So we got the OID branch "1.3.6.1.4.1.18060.14". For starters I'm going to >> assign following subbranches: >> >> 1 - ServerManager MBean >> 2- Transport MBeans >> 3 - NHttpConnections MBeans >> 4 - NHTTPLatency MBeans >> 5 - NHTTPS2SLatency MBeans >> >> I'll also add a page to the documentation regarding these assignments. If >> anybody is looking to use an OID for a specific task in Synapse, please >> write to this list first and get the consent. >> >> Thanks, >> Hiranya >> >> >> On Tue, Apr 3, 2012 at 10:00 AM, Hiranya Jayathilaka < >> [email protected]> wrote: >> >>> Hi Devs, >>> >>> I'm in the process of implementing $subject. As the first step I'm going >>> to expose a couple of our MBeans over SNMP. I'm thinking that SNMP support >>> should be disabled by default as most users will not be interested in it. A >>> property in synapse.properties file will activate the SNMP agent. I'm using >>> SNMP4J (licensed under ASL 2.0) as the underlying API. >>> >>> Also I'm not going to worry too much about SNMP security for the first >>> cut implementation. But I'll make it possible to specify a custom community >>> string for the Synapse SNMP agent (default will be 'public'). SNMP4J >>> supports a ton of security options with regard to SNMP. It should be fairly >>> easy to add these stuff in a future iteration. >>> >>> Feedback welcome! >>> >>> Thanks >>> -- >>> Hiranya Jayathilaka >>> Associate Technical Lead; >>> WSO2 Inc.; http://wso2.org >>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>> Blog: http://techfeast-hiranya.blogspot.com >>> >> >> >> >> -- >> Hiranya Jayathilaka >> Associate Technical Lead; >> WSO2 Inc.; http://wso2.org >> E-mail: [email protected]; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [email protected] > > "Oxygenating the Web Service Platform", www.wso2.com > -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
