Hi, You can define multiple destinations and route traffic based on $MSEC or $RCPTID thereby load balancing traffic. The destination IP/port can be the same for all of these destinations, as long as you use the persist-name() option (which defaults to a name that contains IP/port, and cannot collide). We even had an SCL macro somewhere to wrap this nicely into a simple destination driver. load-balancer() or something. The point is that we can easily create something that looks like a destination driver and wraps this routing complexity away. On Thu, Jun 8, 2023, 13:05 Steve Bernacki <steve@copacetic.net> wrote:
Hello,
We have a syslog TCP destination that receives logs from many different destinations. During peak log volume times, this destination begins to back up and queue. We've found that if we define multiple destinations for the same IP/port and route logs through these multiple destinations, the destination is able to handle these peak log volume times much better.
Our current solution of having a destination for each source is pretty kludgy. Is there a way to define a TCP destination and specify to open, say, 10 connections to the destination and load balance the traffic over those 10 connections?
Thanks. Steve
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq