On Thu, 10 Jul 2014, Leam Hall wrote:
Hey guys, I appreciate the responses.
Let me clarify a couple of points. In this case I'm both consumer and
producer of the open source project. The scripts are small and tend to be run
monthly, or so, and ensure security settings are in place.
One of the things I'm really interested in is not locking anyone in to a post
processing method. Some might use logger, some might use Assimilation, some
might just prefer syslog. While I personally like the idea of directly
feeding a CMDB other consumers might want something totally different.
So the output should be verbose enough to be used over large systems, slurped
into some other system, and yet concise enough to to require lots of
programming to clean it up. I can easily see a post processing script to take
the output and "do stuff" with it.
Make sense? The short form is that I'm an open source developer trying to not
lock everyone into doing things the way I do.
if you use syslog, it handles hostname and timestamps for you so your apps don't
need to, if you just write to a log file, then you need to use a file per app
(or worry about concurrancy issues)
I am in the "throw it at syslog" camp. you aren't locking the user down to any
particular software (there are quite a few syslog daemons out there), and once
it's in syslog, it can be put anywhere else it needs to go (individual files,
remote machines, databases, etc)
David Lang
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
