[syslog-ng] Syslog-ng + Consuming syslog alerts via FIFO: Alarms being lost, no logs related anywhere
Richter Vitali Guedes
richter.vitali at icarotech.com
Thu Apr 15 18:18:32 UTC 2021
Thanks for replying.
I really would love to use TCP. But I'm dealing with several legacy
network/telecomm devices, and most of them doesn't support syslog under TCP.
I really need to deal with UDP.
Just applied reusable sockets to the configuration.
More configuration I tried that gave me better results: mem-bug-length
and disk-buf-size : The data loss reached zero.
Got one more doubt: While reading a pipe with cat command, is it normal
to get cat closed while there are messages streams being processed?
Em 09/04/2021 04:08, Fabien Wernli escreveu:
> On Thu, Apr 08, 2021 at 12:25:44PM -0300, Richter Vitali Guedes wrote:
>> How can I fix it? I need to be sure that all data received is forwarded to
>> their destinations, respecting the filters, and without any information
> You should really consider using TCP.
> We switched our 2000 nodes+ a month ago, and it saves us a lot of
> headeaches. It also makes it much easier to monitor, as TCP connections are
> all easily traceable and can be plotted to assess the load-balancer's
> situation for instance.
> If you really want to keep UDP, the advice I could give would be to use
> reusable sockets, which has been implemented quite recently. <https://www.linkedin.com/company/icarotech>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the syslog-ng