-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Syslog has UDP but not TCP support #627
Comments
@derekchan why do you need TCP instead of UDP? Any problem with the UDP handler? I don't think there would be a problem to have a tcp handler, but I guess there is not reason to have one :). |
Logging via TCP is not really a great idea IMO because you slow down the app with network delays quite a bit just to guarantee log delivery which is usually not critical. If log delivery is critical I think dumping to disk or redis and then having another process streaming the data via TCP to the log server is a lot more efficient. |
The problem with UDP syslog is that the log messages can come in out of order, especially if they're sent very close together. |
Yes, that's true, but then again there are many ways to reliably ship logs off a system, using TCP in the logger is not one of the good ones IMO. |
There is a SyslogUdpHandler, but no TCP implementation. Is there some special reason for this?
I can take a stab at implementing it, if the reason is only because nobody has ever requested.
The text was updated successfully, but these errors were encountered: