You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default syslog should always use UDP instead of TCP. With TCP the problem is, that if the syslog (logstash) server is unavailable the sending server will start blocking of caching which can be very problematic. This can even crash your whole infrastructure if the logstash server is down for too long.
The text was updated successfully, but these errors were encountered:
There's definitely some different tolerance for loss of logs across implementations... some people seem to want to never lose logs and bring down the service before they lose logs, and some want to drop logs and always keep the service up.
We defaulted to the one that doesn't lose logs, but perhaps we should provide an option?
By default syslog should always use UDP instead of TCP. With TCP the problem is, that if the syslog (logstash) server is unavailable the sending server will start blocking of caching which can be very problematic. This can even crash your whole infrastructure if the logstash server is down for too long.
The text was updated successfully, but these errors were encountered: