[syslog-ng] syslog-ng 2 and bandwidth limiting

[Jim Hendrick]

Thanks for the response. I am not familiar enough with the overall
architecture to know where to look to implement something like this (nor
have I written any significant code in several years).

Does the message flow create a separate network connection for each
'destination' or would it be at the 'log' level?

Does it maintain a separate buffer (queue) at the destination level or log
level?


I was thinking that one feature that would probably make this more useful
would be an internal (or local) alert message related to bandwidth.
Something like if the bandwidth exceeds the cap for a given destination send
an alert message (once per time interval).

That way you would know (downstream) that log messages were (possibly) being
lost, or at least that a bandwidth condition had been reached.

Thoughts?

And thanks again for the reply!

Jim



> -----Original Message-----
> From: syslog-ng-bounces at lists.balabit.hu 
> [mailto:syslog-ng-bounces at lists.balabit.hu] On Behalf Of 
> Balazs Scheidler
> Sent: Friday, April 06, 2007 5:19 AM
> To: Syslog-ng users' and developers' mailing list
> Subject: Re: [syslog-ng] syslog-ng 2 and bandwidth limiting
> 
> 
> On Thu, 2007-04-05 at 12:07 -0400, jrhendri at maine.rr.com wrote:
> > Hi,
> >   Is there a way to limit the bandwidth of an ng server?
> > Ideally I would like something that would allow NG to be 
> limited to a 
> > specific amount of bandwidth (packets/sec or kb/s, etc.) 
> for each log 
> > path. 


> syslog-ng has no such feature currently. albeit it would not 
> be difficult to implement, at least on a per-destination 
> basis. On a per-application basis, this would be a bit more complex.
> 
> 
> -- 
> Bazsi
> 
> _______________________________________________
> syslog-ng maillist  -  syslog-ng at lists.balabit.hu 
> https://lists.balabit.hu/mailman/listinfo/sysl> og-ng
> 
> Frequently asked questions at 
> http://www.campin.net/syslog-ng/faq.html
>