a3ec3ce2b8
* Sync log_dir/log_file/use_syslog usage from upstream in order to use the same logging guidelines for all OS modules in Fuel as well * Add new use_syslog_rfc_format option in addition to use_syslog in order to ensure RFC5424 comliant logging to syslog for all OS services * Add section for handling the deprecated things in OS logging class * Fix remote logs matching for multiline messages (Use octet-framing at sender side) * Simplify matching logic (&~) for remote logs processing * Remove artificial separation for DEBUG and other OS logging cases * Remove unneeded anymore imfile::templates * Remove unneeded anymore python log configs templates for OS and syslog_log_level option used for its log configs as well * Remove artificial logging w/a for Neutron and its imfile templates * Fix ceilometer facility to LOCAL0 and its facility parameter usage * Move Fuel customizations from rsyslog module to openstack * Move custom logging templates and configuration * Move checksum_udp and use rsyslog port as a class var * Keep custom port and escapenewline vars for rsyslog module, * Disable RELP package for syslog module unless it would be used in Fuel * Fix identations... Implemenets step2 for blueprint refactor-logging-puppet-openstack-services Change-Id: Ie20725b9c91584311350a520107a79a4828937bc Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com> |
||
---|---|---|
.. | ||
examples | ||
files | ||
manifests | ||
spec | ||
templates | ||
tests | ||
.project | ||
Modulefile | ||
README.md |
puppet-rsyslog
================
Manage rsyslog client and server via Puppet
REQUIREMENTS
- Puppet >=2.6 if using parameterized classes
- Currently supports Ubuntu >=11.04 & Debian running rsyslog >=4.5
USAGE
Client
Using default values
class { 'rsyslog::client': }
Variables and default values
class { 'rsyslog::client':
log_remote => true,
remote_type => 'tcp',
log_local => false,
log_auth_local => false,
custom_config => undef,
server => 'log',
port => '514',
}
Server
Using default values
class { 'rsyslog::server': }
Variables and default values
class { 'rsyslog::server':
enable_tcp => true,
enable_udp => true,
server_dir => '/srv/log/',
custom_config => undef,
high_precision_timestamps => false,
}
Both can be installed at the same time.
PARAMETERS
The following lists all the class parameters this module accepts.
RSYSLOG::SERVER CLASS PARAMETERS VALUES DESCRIPTION
--------------------------------------------------------------
enable_tcp true,false Enable TCP listener. Defaults to true.
enable_udp true,false Enable UDP listener. Defaults to true.
server_dir STRING Folder where logs will be stored on the server. Defaults to '/srv/log/'
custom_config STRING Specify your own template to use for server config. Defaults to undef. Example usage: custom_config => 'rsyslog/my_config.erb'
high_precision_timestamps true,false Whether or not to use high precision timestamps.
RSYSLOG::CLIENT CLASS PARAMETERS VALUES DESCRIPTION
--------------------------------------------------------------
log_remote true,false Log Remotely. Defaults to true.
remote_type 'tcp','udp' Which protocol to use when logging remotely. Defaults to 'tcp'.
log_local true,false Log locally. Defualts to false.
log_auth_local true,false Just log auth facility locally. Defaults to false.
custom_config STRING Specify your own template to use for client config. Defaults to undef. Example usage: custom_config => 'rsyslog/my_config.erb
server STRING Rsyslog server to log to. Will be used in the client configuration file.
Other notes
Due to a missing feature in current RELP versions (InputRELPServerBindRuleset option), remote logging is using TCP. You can switch between TCP and UDP. As soon as there is a new RELP version which supports setting Rulesets, I will add support for relp back.