It was not my intention to provide direct SNMP access to these stats in the near term. I thought about using JNDI but would rather focus more on the JMX approach and wait until JNDI is a part of the Container / James architecture before going that way. At that point SNMP access is avaialable to anyone using an SNMP Agent from Sun, AdventNet, iReasoning etc. Using JMX I was also thinking of providing a command line tool a la vmstat / iostat but I guess that could be done with RemoteManager.
Steve > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: Friday, December 05, 2003 10:13 AM > To: James Developers List > Subject: RE: Monitoring > > > > The Monitor service would be exposed via JMX (automatically > thanks to > > Phoenix and hopefully Merlin). > > > The monitor service configuration would allow declaration of groups > > and act as a factory for other components that wish to be monitored. > > My suggestion would be to use JNDI for this purpose, and to > have a JNDI context containing the metrics. > > ../metrics/protocols/SMTP/.. > > An SNMP service would expose an SNMP protocol view of the > information in the metrics context. A component would get > its metrics context and interact with the beans that we'll > probably store there. So long as we have a suitably common > interface, the rest is automagic. > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
