On Tue, Jan 8, 2013 at 12:12 PM, Ram Ganesh <[email protected]> wrote: >> -----Original Message----- >> From: Alex Huang [mailto:[email protected]] >> Sent: 08 January 2013 22:10 >> To: [email protected] >> Subject: RE: [DISCUSS] Syslog enhancements >> >> Ram and Hari, >> >> I continue to have trouble with this feature. What I'm used to seeing >> in syslogs are not the things that are being described here. They're >> usually some log level of an application. If there are system events >> that are not logged to our own logs, why not log them to our own logs >> and use the log4j syslogappender to filter them and send them to >> syslog. Why write something else? >> >> Do you have any use cases where system events should not be logged into >> CloudStack's logs? > > I do not think so. I think it is just the legacy code. We need to > ensure that those events also get logged into the log files. Will take the > log4j syslogappender path then > > Thanks, > Ram >
So does this obviate the need for the Syslog feature itself? Can we just make this a docs bug to document how to configure log4j? --David
