remote_syslog2

This blog post is factually incorrect. Papertrail and Loggly both strongly recommend and support syslog over TLS. For example, https://documentation.solarwinds.com/en/Success_Center/paper... covers how to setup encrypted logging. That page is linked to as part of the standard setup doc and it's in the sidebar, immediately beneath the simplest possible setup instructions. This blog post says "Of course, they support TLS and have advanced/optional instructions for configuring that but after decades of experience in software and devops we know the power of defaults," which is at best a mischaracterization. Also, the sender maintained by Papertrail, remote_syslog2, both defaults to encryption (https://github.com/papertrail/remote_syslog2/blob/master/exa...) and makes it a single config option, which isn't true of most other senders.

Disclaimer: I work for both Papertrail and Loggly's parent company: SolarWinds. For general purpose logging - we deploy Papertrail's remote_syslog2 https://github.com/papertrail/remote_syslog2 - which is more or less set it and forget it setup. e.g. specify which text files I want to aggregate, and then watch them flow into the live tail viewer. For logging in more limited environments (can't sudo or apt-get install), we use Loggly's http API (https://www.loggly.com/docs/http-endpoint/). Also, Loggly's JSON support allows us to answer questions like: "how many signup events failed since the last deployment". Or "What is the most common signup error". Bonus! If you're looking for trace-level reporting and integrating that with your logs, check out the AppOptics and Loggly integration: https://www.loggly.com/blog/announcing-appoptics-loggly