Insider 2018-09: SCL; Splunk .conf18; failover; human readable numbers; webinars;

Dear syslog-ng users,

This is the 69th issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news.



Creating your first block for the syslog-ng configuration library (SCL)

The syslog-ng configuration library (SCL) is a collection of ready-to-use configuration snippets that hide away the complexity of the specifics of your log processing pipeline. If you already reuse parts of your configuration on different machines, it is not rocket science to turn these parts into blocks, making your configuration files a lot simpler. And if they are not site-specific, you can even help other syslog-ng users by submitting them to be included in SCL, and distributed in the official syslog-ng releases.

syslog-ng at Splunk .conf18

Going to Splunk .conf18? See a demo, meet with us (Booth #M49) and talk to syslog-ng creator, Balázs Scheidler. He will also give a talk on 02 October, 2:15 - 3:00 p.m. about simplifying complex log data ingestion with syslog-ng:

Client-side failover and failback using syslog-ng

When you have multiple syslog servers collecting logs, syslog-ng, on the client side, can fail over to secondary servers if the primary one becomes unavailable. It can also fail back to the primary server soon after it is back online – if configured so. Using client-side failover lowers the risk of message loss and makes the maintenance of servers easier.

Human readable numbers in syslog-ng

Writing an extra zero at the wrong place in a configuration file can result in a filled-up partition and data loss. This is where human readable numbers in syslog-ng can help: using kilo / mega / giga instead of writing many-digit numbers can save you lots of debugging and headache.


You can watch our past webinars:

Or register for our upcoming syslog-ng webinars:

Your feedback and news, or tips about the next issue are welcome.