Puppet users - Oct 2010 - Prefixing syslog messages with client names

Hi.


 The puppetmaster is set up to log to syslog, which is working fine. The
downside is that most of the log entries created by the puppetmaster does
not indicate which puppet client that message if from. So basically I have
lots and lots of syslog entries created by the puppetmaster, but no way of
telling which client it references.

Is there any way to have the puppet master prefix each syslog message with
the name of the client the log message is for?

I''m running puppet version 0.25.4.


Best regards
Kenneth

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Tue, Oct 12, 2010 at 02:27:51PM +0200, Kenneth Holter
wrote:
> Hi.
> 
> 
>  The puppetmaster is set up to log to syslog, which is working fine. The
> downside is that most of the log entries created by the puppetmaster does
> not indicate which puppet client that message if from. So basically I have
> lots and lots of syslog entries created by the puppetmaster, but no way of
> telling which client it references.
Just to be clear, you are having your puppet clients tell the
puppestmaster what they are doing and then the master is logging that?  
> 
> Is there any way to have the puppet master prefix each syslog message with
> the name of the client the log message is for?
I think it is better to have puppet clients logging to local syslog.
You can always configure your syslog daemon to replicate this to another
host (rsyslog or syslog-ng will both do this for you quite easily) or
have logwatch track it.  The benefits of this are a) log redundancy,
b) you get to see what the client is doing even when the puppetmaster is
down (or not visible to the client) and c) less load on the puppetmaster
(logging can become a significant extra load if you have a large
network).

-- 
Bruce

Explota!: miles de lemmings no pueden estar equivocados.

On Tue, Oct 12, 2010 at 6:37 PM, Bruce Richardson
<itsbruce@workshy.org>wrote:
> On Tue, Oct 12, 2010 at 02:27:51PM +0200, Kenneth Holter wrote:
> > Hi.
> >
> >
> >  The puppetmaster is set up to log to syslog, which is working fine.
The
> > downside is that most of the log entries created by the puppetmaster
does
> > not indicate which puppet client that message if from. So basically I
> have
> > lots and lots of syslog entries created by the puppetmaster, but no
way
> of
> > telling which client it references.
>
> Just to be clear, you are having your puppet clients tell the
> puppestmaster what they are doing and then the master is logging that?
>
> >
> > Is there any way to have the puppet master prefix each syslog message
> with
> > the name of the client the log message is for?
>
> I think it is better to have puppet clients logging to local syslog.
> You can always configure your syslog daemon to replicate this to another
> host (rsyslog or syslog-ng will both do this for you quite easily) or
> have logwatch track it.  The benefits of this are a) log redundancy,
> b) you get to see what the client is doing even when the puppetmaster is
> down (or not visible to the client) and c) less load on the puppetmaster
> (logging can become a significant extra load if you have a large
> network).
>
> --
> Bruce
>
> Explota!: miles de lemmings no pueden estar equivocados.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAky0XYYACgkQtkVqYTMBSwFu3QCdGuZauN7HtTk5dfVo8bYN3NeN
> 5aUAn2ww1FAr4+WIokQhDwcCAhzbyHUT
> =3vTw
> -----END PGP SIGNATURE-----
>
>
Thanks for these pointers, Bruce !

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Thanks for great advice. The puppet clients are logging to the master, but I
agree that it would be better for them to log to syslog. I''ve got an
rsyslog
master up and running, which all my linux servers log to, so I''ll make
use
of that to extract the puppet related messages.


- Kenneth

On Tue, Oct 12, 2010 at 3:07 PM, Bruce Richardson
<itsbruce@workshy.org>wrote:
> On Tue, Oct 12, 2010 at 02:27:51PM +0200, Kenneth Holter wrote:
> > Hi.
> >
> >
> >  The puppetmaster is set up to log to syslog, which is working fine.
The
> > downside is that most of the log entries created by the puppetmaster
does
> > not indicate which puppet client that message if from. So basically I
> have
> > lots and lots of syslog entries created by the puppetmaster, but no
way
> of
> > telling which client it references.
>
> Just to be clear, you are having your puppet clients tell the
> puppestmaster what they are doing and then the master is logging that?
>
> >
> > Is there any way to have the puppet master prefix each syslog message
> with
> > the name of the client the log message is for?
>
> I think it is better to have puppet clients logging to local syslog.
> You can always configure your syslog daemon to replicate this to another
> host (rsyslog or syslog-ng will both do this for you quite easily) or
> have logwatch track it.  The benefits of this are a) log redundancy,
> b) you get to see what the client is doing even when the puppetmaster is
> down (or not visible to the client) and c) less load on the puppetmaster
> (logging can become a significant extra load if you have a large
> network).
>
> --
> Bruce
>
> Explota!: miles de lemmings no pueden estar equivocados.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAky0XYYACgkQtkVqYTMBSwFu3QCdGuZauN7HtTk5dfVo8bYN3NeN
> 5aUAn2ww1FAr4+WIokQhDwcCAhzbyHUT
> =3vTw
> -----END PGP SIGNATURE-----
>
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.