[syslog-ng] Syslog-ng 3.0.2 statistics

[Aaron Robel]

You make a good point. I initially thought the same thing and did some
checking on the bandwidth usage and we aren't saturating any of the links or
even getting close.  I also didn't see any errors or drops on the
interfaces.  The big question for me is how does this all play out in the
virtualized environment could I be running into a limitation there,
rhetorical question.  All of these hosts live physically on the same piece
of hardware and on the same vlan.   I'll keep poking around in that arena to
see if anything turns up. Maybe play with tcp to the archive host, I just
worry about performance implications.

Do you see anything else in my options config that looks amiss?

Thanks for the suggestion Joe.
Hardware stats:
relays:
2 3gig procs
4 gig mem
1 TB disk

archive
4 3 gig procs
6 gig mem
5.5 TB disk

Network bandwidth stats:
relay 01:  in-850KBps out-300KBps (I'm assuming the descrepancy here is due
to the fifo and flush settings.)
relay 02:  in-60KBps out-55KBps
relay 03:  in-nill out-nill

Archive:
network utilization: 600KBps
On Wed, Jun 17, 2009 at 8:58 AM, Fegan, Joe <Joe.Fegan at hp.com> wrote:

>  Knee jerk reaction: are you using udp? You probably know that udp is a
> connection-less, fire-and-forget protocol so if the packet gets lost neither
> the sender nor the intended recipent will know (or care).
>
>  ------------------------------
> *From:* syslog-ng-bounces at lists.balabit.hu [mailto:
> syslog-ng-bounces at lists.balabit.hu] *On Behalf Of *Aaron Robel
> *Sent:* 17 June 2009 16:20
> *To:* syslog-ng at lists.balabit.hu
> *Subject:* [syslog-ng] Syslog-ng 3.0.2 statistics
>
>   Hello,
>
> 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.
>
> I have a 4 server syslog deployment with 3 front end "relay" boxes and 1
> backend archive box all within a virtualized SLES environment.
>
> 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.
>
> 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.
>
> What does stamp, processed, stored, etc.. mean?  I couldn't find any
> detailed documentation about the different statistics.
>
> Why am I getting such a large discrepency between "stamp" and "processed"
> in the log stats?
>
> 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?
>
> Here are my stats in question off my archive box:
> processed='src.udp(s_network#0)=22020892',
> stamp='src.udp(s_network#0)=1245249328'
>
> Here's the global's off the archive box:
> options {
>         time_sleep(10);
>         log_fetch_limit(250);
>         log_fifo_size(2000);
>         use_dns(no);
>         keep_timestamp(yes);
>         dns_cache(no);
>         long_hostnames(off);
>         flush_lines(2000);
>         flush_timeout(200);
>         perm(0644);
>         stats_freq(1800);
>         stats_level(1);
>         time_reopen(10);
>         create_dirs(yes);
>         dir_perm(755);
> };
>  Thanks!
>
>
>
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation:
> http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.campin.net/syslog-ng/faq.html
>
>
>


-- 
Aaron Robel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20090617/6d28f505/attachment.htm