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

Balazs Scheidler bazsi at balabit.hu
Fri Apr 6 11:19:26 CEST 2007

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?
> If so, does it work with UDP or only TCP?
> I have seen the log_fifo_size() option, but don't easily see how this
> would limit the amount of bandwidth used (seems like it is designed to
> provide a larger output buffer  for slow links, but does not actually
> limit the bandwidth used by NG)
> I am also looking at the flow-control flag, but again it is not clear
> how to use it to limit the bandwidth.
> 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. This way if a service started generating an excessive amount of
> log data (e.g. if a daemon were put into debug mode) it would help
> prevent the log server from choking the network trying to send all the
> packets (it would be especially nice if you could configure how large an
> output buffer were available, so if you wanted to deal with *bursty*
> services, you could limit them to a small amount of bandwidth, but
> provide them with a larger output buffer so you would be less likely to
> drop messages.

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.


More information about the syslog-ng mailing list