<div>Hello,</div>
<div> </div>
<div>My apologies in advance, this is my first posting and I'm quite the rook' when it comes to Linux and Syslog-ng. I keep wondering why this is my project.</div>
<div> </div>
<div>I have a 4 server syslog deployment with 3 front end "relay" boxes and 1 backend archive box all within a virtualized SLES environment.</div>
<div> </div>
<div>Recently I noticed that the relay's together are averaging about 2500 messages per second (mps). The majority of the messages are coming from a single relay, about 2000 mps. Yet the archive box is only averaging about 400 mps.</div>
<div> </div>
<div>Since we are running 3.0.2 I decided to turn up the stats_level to (1). I don't see any drops to the about 150 file destinations that I've built.</div>
<div> </div>
<div>What does stamp, processed, stored, etc.. mean? I couldn't find any detailed documentation about the different statistics. </div>
<div> </div>
<div>Why am I getting such a large discrepency between "stamp" and "processed" in the log stats?</div>
<div> </div>
<div>Finally, since I'm sending the email does anyone see an issue with the way I've got the flow control set up in the global options?</div>
<div> </div>
<div>Here are my stats in question off my archive box:</div>
<div>processed='src.udp(s_network#0)=22020892', <br>stamp='src.udp(s_network#0)=1245249328'</div>
<div> </div>
<div>Here's the global's off the archive box:</div>
<div>options {<br> time_sleep(10);<br> log_fetch_limit(250);<br> log_fifo_size(2000);<br> use_dns(no);<br> keep_timestamp(yes);<br> dns_cache(no);<br> long_hostnames(off);<br>
flush_lines(2000);<br> flush_timeout(200);<br> perm(0644);<br> stats_freq(1800);<br> stats_level(1);<br> time_reopen(10);<br> create_dirs(yes);<br> dir_perm(755);<br>
};<br clear="all"></div>
<div></div>
<div>Thanks!</div>
<div> </div>