Totally worth it.So without loggly [or equivalent] is the script "as is" useful for us noobs?
I set it up to work with a free loggly account mostly out of curiosity and proof of concept. One day I will get around to making it useful or trying one of the alternatives (like, um, the other "scribe"), perhaps in a jail on my NAS getting fed by other devices.
I have pixelserv-tls set at log level 2 because I can collect statistics from it. But it generates thousands of messages as a byproduct, and once tabulated, are useless. So using syslog-ng to pull those to one file means the collecting process only operates on that file, and then logrotate deletes the older messages automatically. Presto.
I have syslog-ng pulling out the skynet messages for essentially the same process for its statistics, including the tons of messages from the last hour until they get destroyed. Presto.
I have syslog-ng sending openvpn messages to its own file, because sometimes I want to see those messages, and generally don't want to see all the refused connections as someone trolls the ports.
What I have left is a webgui log that has mostly routine messages but is much easier to scan. Scribe leaves you just with handling configurations you might want to set up, or try, in syslog-ng.d and a companion logrotate in logrotate.d . But the @cmkelley has done all the heavy lifting (and the light lifting too) evidenced by over 500 messages in this thread.