puppet-rsyslog icon indicating copy to clipboard operation
puppet-rsyslog copied to clipboard

Manage rsyslog through puppet

Results 54 puppet-rsyslog issues
Sort by recently updated
recently updated
newest added

Something to consider to address https://github.com/saz/puppet-rsyslog/issues/262

Allow for a custom override of /var/log/messages. Useful in omitting double logging messages from localx. logging facilities.

The `rsyslog::install`, `rsyslog::config`, and `rsyslog::service` classes are not contained within `rsyslog`. This makes it impossible to create a relationship to the `rsyslog` class and expect the packages, services, and configs...

Hi, i wasn't able to figure out how to configure rsyslog by this module to discard "unwanted" messages. Would it be possible to add a new parameter for this? Thanks!

Needs more information

When not including a trailing slash (`/`) for the `rsyslog::server::server_dir` parameter a lot of stuff behaves quite odd. It would be great if this parameter could be munged - I...

For example, It would be nice If you could block certain log messages directly through puppet/hiera.

Needs more information
Feature

This was removed with the addition of freebsd log style (f1cd4db2), PR #160

When logging locally, Red Hat based (and non-freebsd) servers don't get emergency messages set in the /etc/rsyslog.d/client.conf file. The file ends with only: # Everybody gets emergency messages There is...

1) The default rsyslog.conf (templates/rsyslog.conf.erb) appears to cover _.emerg for everyone, whether or not local logging is enabled, correct? = 7 -%> *.emerg :omusrmsg:_ *.emerg * Those lines are duplicated...

Calling the `rsyslog` class with `package_status => absent` still results in the module installing the config and trying to start the service: ``` Notice: /Stage[main]/Rsyslog::Install/Package[rsyslog]/ensure: removed Info: /Stage[main]/Rsyslog::Install/Package[rsyslog]: Scheduling refresh...

Bug