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.
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.