Dear syslog-ng users,

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


Creating a central syslog server

Your home network might already contain some devices or systems like a home server, a WiFi router, a media player, or home automation system. Creating a central syslog server to store system logs or syslogs of these systems is considered a best practice.

Learn, how to get started:

Looking for your feedback about syslog-ng

Help us set the direction for syslog-ng by providing your valuable feedback through this short, 9-question survey. Your input will be of great value in determining which features and capabilities to focus our efforts on, going forward.

While this survey can be completed anonymously, we would appreciate if you would share your email address, in case we would need to clarify your response and input.

SNMP traps to Splunk

As we learned at the Splunk .conf18 in October, forwarding SNMP traps to Splunk can be a challenging task. Luckily, using syslog-ng can simplify it for us. All we need to make sure about is that snmptrapd logs traps to a file. The syslog-ng application can read and parse that file and forward the traps to Splunk HEC (HTTP Event Collector).

Send your log messages to Slack

One of the many ways members of a team collaborate is to use Slack. From syslog-ng version 3.19, you can send log messages to Slack. You can receive critical log messages in real-time in your Slack client on your mobile or desktop. Learn how to set up alerting to Slack in just a few minutes.


You can also discuss syslog-ng with me at the following events:


Coming up:

You can also watch our past webinars:

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

Related Content