Message Logging to Loggly works on port 514 but not with 6514!?

[mail-2]

<MessageLogging name="final-logging">
    <DisplayName>final logging</DisplayName>
    <Syslog>
        <Message>[0fd...279@41058 tag="{organization.name}.{apiproxy.name}.{environment.name}"] test</Message>
        <Host>logs-01.loggly.com</Host>
        <Port>514</Port>
        <Protocol>TCP</Protocol>
        <FormatMessage>true</FormatMessage>
    </Syslog>
    <logLevel>INFO</logLevel>
</MessageLogging>

Above policy successfully logs to Loggly.

But I'd like to use a TLS encrypted channel which is supposedly available on port 6514. [1]

But if I replace above Port 514 with 6514 then nothing is logged.

Any ideas?

1: https://documentation.solarwinds.com/en/Success_Center/loggly/Content/admin/streaming-syslog-without...

[ssvaidyanathan · Accepted solution]

@Raffael2020

Please include

<SSLInfo>
  <Enabled>true</Enabled>
</SSLInfo>

This is required for the SSL. Please refer to this doc

[mail-2]

Thanks!

I noticed that for many (actually almost all) features/policies the plain-HTTP connection is presented as the default case. I'd suggest a one-eighty in this regard and present TLS as the default mode and proactively discourage unencrypted communication.

[ssvaidyanathan]

Agree - feel free to post a doc feedback on this. We have seen our Private cloud customer use this within their on-premises. Again we recommend to use TLS there too. Pls drop a doc feedback