[syslog-ng]Syslog-ng Reliability

Michael Renner m.renner@inode.at
Mon, 15 Apr 2002 17:42:46 +0200


At 10:35 15.04.2002 -0400, you wrote:
>Well, I got syslog-ng setup and running. Runs great. I have to say, this is
>a realy nice way of doing logging. Major kudos to developers.

Full ack.

>a few questions:
>
>1. How reliable is network server operation of Syslog-ng under heavy load? I
>am running remote servers using tcp() and anticipate a lot of throughput.
>Will syslog-ng not drop stuff like syslogd does?

Should be more reliable than udp, syslog-ng barfed (major data corruption) 
when i tried to send a 100kb file via splogger (qmail stdin-to-syslog 
program) at once to syslog-ng via udp (lots of corrupted entries), but i 
have to admit that the syslog protocol shouldn't be used to transfer 
plaintext files :)

>2. log_fifo_size(100) is this in bytes or kbytes or what? Is this a memory
>buffer before a write is done?

http://www.balabit.hu/static/syslog-ng/reference/x564.html

log_fifo_size() number The number of lines fitting to the output queue

Afaik messages are kept in memory until they exceed log_fifo_size; then 
they're written out in single write()'s.

>3. I didn't find the documentation in the man page for variables like $YEAR,
>$MONTH, $HOST, etc. Where is the list of these?

http://www.balabit.hu/static/syslog-ng/reference/x324.html


>4. Any idea when compress(on) function will be implemented?

This question can only answer bazsi, but a cronjob gzipping all the 
logfiles every night does the trick for me.


mfg/best regards

-- 

Michael Renner
Junior System Engineer

Inode Telekommunikationsdienstleistungs GmbH - http://www.inode.at
support@inode.at, Tel.: 05 9999-0, Fax.: 05 9999-2699