The loggly() destination sends log messages to the Loggly Logging-as-a-Service provider. You can send log messages over TCP, or encrypted with TLS.
loggly(token());
To use the loggly() destination, the only mandatory parameter is your user token. The following example sends every log from the system() source to your Loggly account.
log { source { system(); }; destination { loggly(token("<USER-TOKEN-AS-PROVIDED-BY-LOGGLY>")); }; };
The following example uses TLS encryption. Before using it, download the CA certificate of Loggly and copy it to your hosts (for example, into the /etc/ssl/certs/ directory.
log { destination { loggly(token("<USER-TOKEN-AS-PROVIDED-BY-LOGGLY>") port(6514) tls(peer-verify(required-trusted) ca-dir('/etc/ssl/certs')) ); }; };
The following example parses the access logs of an Apache webserver from a file and sends them to Loggly in JSON format.
log { source { file("/var/log/apache2/access.log" flags(no-parse)); }; parser { apache-accesslog-parser(); }; destination { loggly(token("<USER-TOKEN-AS-PROVIDED-BY-LOGGLY>") tag(apache) template("$(format-json .apache.* timestamp=${ISODATE})")); }; }
To use the loggly() driver, the scl.conf file must be included in your syslog-ng OSE configuration:
@include "scl.conf"
The loggly() driver is actually a reusable configuration snippet configured to send log messages using the tcp() driver using a template. For details on using or writing such configuration snippets, see Reusing configuration blocks. You can find the source of this configuration snippet on GitHub.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center