rsyslog
Nov 20, 2008 - 11:36 PM
Professional Support
Custom written rsyslog.conf? Maintenance Contract?

rsyslog professional services


Donate!
Satisfied with rsyslog?

Donate and help keep
the project alive!

Rainer's Blog

Login




 


 Log in Problems?
 New User? Sign Up!

Online
There are 31 unlogged users and 0 registered users online.

You can log-in or register for a user account here.

Announcements
Announcements  :: rsyslogd 1.10.2 released ::
(6748 Reads)  
Posted by rgerhards on Tuesday, September 27, 2005 - 10:26 PM

I am glad to announce rsyslog 1.10.2, the regularly scheduled release. The main improvements are

  • ability to limit the systems rsyslogd accepts messages from
  • new comparison operations for the property-based filters

Of course, there are also some other new features as well as some bug fixes.

I recommend upgrading to 1.10.2 if you are running any release of the development branch. Full details can be found in the change log. Because I was often asked what can be done with new features, I have included some lines from the sample configuration file after my signature. I hope they are useful.

As always, feedback is deeply appreciated.
Rainer

-- excerpt from sample.conf --

# We limit who can send us messages:
$AllowedSender UDP, 192.0.2.0/24, 10.0.0.1
# all machines in 192.0.2 as well as 10.0.0.1
$AllowedSender TCP, 10.0.0.1 # for TCP, we allow only 10.0.0.1
# remove the AllowedSender directives if you do not want to limit
# who can send rsyslogd messages (not recommended)

# We also support property-based filters, which allow for nice
# things. Let's for example assume that you receive a lot of
# nonsense messages with "ID-4711" in the message text. You know
# that you will never need these messages. So you simply discard them
:msg, contains, "ID-4711" ~

# or you would like to store messages from a specific host to
# a different file:
:FROMHOST, isequal,"myhost.example.com" /var/log/myhost.log

# everyting that does not contain "error" should also be
# discarded
:msg, !contains, "error" ~
# and the rest go to a seperate file
*.* /var/log/error
# (keep in mind that the two directives shown immediately
# above must be kept in that order to actually work)

# you can also execute a script. Let's assume, for example, you need
# to execute "turn-diesel-generator-on" when "power failed" is contained
# in a message... ;)
:msg, contains, "power failed" ^turn-diesel-generator-on
# (The script is passed the syslog message as first and only paramter.
# Other parameters can currently not be specified.)

Send this story to someone  Printer-friendly page
Only logged in users are allowed to comment. register/log in
 RSyslog Sponsors
 
Functionality looking for Sponsors

for sponsor

 Search
 
Google

 Last Forum Posts
 · Compiled version of rsyslog for RHEL3.0 ...
Hi,I'm trying to install rsyslog (we require the PRI information ...
· Re: %HOSTNAME% or %FROMHOST% not really ...
Ah, excellent. Sorry, I overlooked that the function was overhaul ...
· Re: Quieting console output with imklog ...
Oh, let me add: rsyslog can work on a much finer granularity, for ...
· Re: Quieting console output with imklog ...
If I understand you correctly, you want to discard some messages ...
· Quieting console output with imklog
Hello,How do I tell imklog to squelch info notices to the console ...
· Re: %HOSTNAME% or %FROMHOST% not really ...
Hi Rainer,There was enough of a difference in the code that the p ...
· Re: problems with ommail setup in rsyslo ...
Please see the ommail doc:http://www.rsyslog.com/doc-ommail.htmlT ...
· problems with ommail setup in rsyslog.co ...
Hi, I dont seem to be able to get ommail mail alerts to work pro ...

:: Syndication: ::
Page created in 0.090008020401 seconds.