Blog

Users report that syslog over UDP loses 30-40% of their messages. Learn why messages are dropped and how you can solve or at least mitigate the problems.

Users report that syslog over UDP loses 30-40% of their messages. Learn why messages are dropped and how you can solve or at least mitigate the problems.

Version 4.1 with its new metrics system brings syslog-ng closer to the cloud-native ecosystem and the modern observability supply chain.

Axoflow is happy to announce that our flavored syslog-ng container images are available for download.

Logs have been my passion for over two decades now. As a 3rd-year university student, I started an Open Source project to fix the “syslogd” problem. syslogd was the standard solution at that time to collect, deliver and aggregate system and device logs. The new project was named “syslog, the next generation” or syslog-ng for short. Well, 25 years on and we are now launching Axoflow – where we are bringing to market a long-overdue capability for the burgeoning Observability space that we anticipate will have similar impact!

Open source tools have been used to implement data collection to feed SIEM and other security systems for decades. We at Axoflow feel that these existing deployments of open source technologies play an important role in the future data supply chains as well.

Log data as collected from operating systems, appliances, and applications is extremely unstructured. You can't imagine how much so. Unless you are an analyst working with logs or you have a past where you were "grepping" data in log files, you are probably not aware of the infinite variety of formats and lack of standardization. If this is the case, you likely have a less-than-complete understanding of the story logs can tell – be it security incidents, IT operations irregularities, and a myriad of other business insights.