On 8/26/14 10:34 AM, Mike Reed wrote:
Hello all,
I've recently been looking into various methods for configuring
meaningful logging from my puppet 3.6 master/agent nodes. I've
typically gone the route of grep'ing through syslog on both
master/agents and I'd like something a little more robust and user
friendly for other who may not be hip on going through hundreds of lines
of syslog information in addition to a simpler design.
I've recently been playing with an agent's puppet.conf and simply trying
to set the logdir using this with no success at all (permissions have
been changed to allow puppet to write to that directory):
[agent]
logdir= /var/log/puppet
I've also tested syslog facility configurations but after some time, it
seemed like having to modify multiple configuration files to get puppet
logging consistent, seems a bit bulky to me.
I suppose I have two questions:
1. Is there a simple way to push messages to a file other than
/var/log/syslog on an Ubuntu machine?
2. Is there a preferred way in the community by which people aggregate
logs to make troubleshooting nodes issues easier to manage?
Thank you all for your time in advance.
Cheers,
Mike
This is the way I do it,
http://ask.puppetlabs.com/question/432/puppet-and-rsyslog/?answer=439#post-id-439
I thought that the Puppet packages used to install a syslog config, but
maybe I imagined that.
Ramin
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/53FCC85A.9050805%40badapple.net.
For more options, visit https://groups.google.com/d/optout.
