Add support for TCP/TLS
fanwar opened this issue · comments
Would like to be able to also send logs via TCP/TLS, not just UDP. Is there any reason that this is not currently supported by this library?
The main reason why we didn't do it was because it would require more careful implementation to ensure that the thread that submits the logs does not block the thread calling the logger at any point (and also does not use up an unbounded amount of memory).
It definitely would be doable, it just requires some care.
@fanwar: here's more on that, including some detailed explanations: https://github.com/papertrail/remote_syslog_logger/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20tcp
Thanks for your response ... looks like adding this support in the short term is going to be difficult. We are trying to get TLS-based logging from a docker/kubernetes environment and have had trouble with other solutions pushing to papertrail (eg. logspout). Will keep searching for a working way to do this integration.
@fanwar I'd be curious to hear more about your experiences with logspout (and any other TLS senders usable from Docker) @ support at papertrailapp dawt com. My gut reaction is that the easiest route might be https://github.com/papertrail/remote_syslog2 on the host, pointed at a directory exposed to guests with docker run -v (more). It's the option that Papertrail covers here.
Anyway, if you're comfortable sharing details about your environment and what you saw in email, I'd like to hear it.
Thanks Troy, will email you shortly with more details. Would love to get some help on this.