Configuration instructions for the syslog-ng add-on can be found on the Syslog-NG Setup page.
Logs are forwarded continuously from all the capsules present on your deployment; so you will see database logs and jmx logs in chronological order. For easier parsing, Compose adds a header to each log message that contains a timestamp, hostname, and process information.
As a result, the raw messages that arrive at your service will vary.
<timestamp> <hostname>: <binary[pid]>: <type info> | <jmx, or ScyllaDB log>
<hostname> : [<customer [email protected]>] <binary[pid]>: <type info> | <jmx or ScyllaDB log>
NB: In addition to just displaying the raw information from syslog-ng, Loggly also applies some parsing by default. It does not recognize the format of our logs, so you may want to implement your own parsing or derived fields to make more effective use of the logs there.
Logentries is no longer available for new deployments or as a new add-on for existing deployments. The format is here for deployments where it is already configured.
<timestamp> <hostname>: <binary[pid]: <type info> | <jmx, or ScyllaDB log>
Updated about a year ago