David, I agree you -- what development work is required? SNMP <> JMX bridges are available from various third parties. A minimal bridge is provided in the Sun JRE [1]. log4j message formats are highly configurable [2] to conform to the expectations of almost any conceivable downstream log file collection and analysis package.
Thanks, -John [1] http://docs.oracle.com/javase/6/docs/technotes/guides/management/snmp.html [2] http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html On Jan 8, 2013, at 10:48 AM, David Nalley <[email protected]> wrote: > On Tue, Jan 8, 2013 at 10:46 AM, Ram Ganesh <[email protected]> wrote: >>> -----Original Message----- >>> From: Chip Childers [mailto:[email protected]] >>> Sent: 04 January 2013 00:13 >>> To: [email protected] >>> Subject: Re: [DISCUSS] Syslog enhancements >>> >>> I think that Ram and Hari are talking about CloudStack system "events" >>> (call this set 1). The log4j conversation is around log messages being >>> sent through the logger (call this set 2). >>> >>> If we assume that (2) is a superset of (1), then IMO there is no >>> reason to do something different from the log4j syslog appender. On >>> the other hand, if there is a portion of set (1) that is not included >>> in set (2), then I actually think we have a logging problem to fix. >> >> Sorry for getting back late on this. The intent of this enhancement is to >> send out system events in multiple(configured) formats. SNMP and Syslogs are >> two formats. Users can choose the format of their interest based on their >> existing element management infrastructure. Currently in CloudStack I guess >> not all system events are logged into the log file. >> >> > > As verbose as our logs are, there are still things missing from them?? :) > > --David
