Why syslog-ng? With syslog-ng, you can collect logs from a wide range of sources, process them in near real-time and deliver them to a wide variety of destinations. syslog-ng allows you to flexibly collect, parse, classify, and correlate logs from across your infrastructure (even from routers, embedded systems) and store or route them to log analysis tools. By integrating with big data tools it is possible to deliver log messages to Kafka and Elasticsearch, even store logs in HDFS. syslog-ng not only supports legacy BSD syslog (RFC3164) and the enhanced RFC5424 protocols but also JavaScript Object Notation (JSON) and journald message formats. Working with unstructured data? That's not a problem: syslog-ng comes with a set of built-in parsers, which you can combine to build very complex things. Even if you need to collect logs from a diverse range of sources, syslog-ng's PatternDB allows you to correlate events together and transform them into a unified format. If you need to store your log messages in a database, you don't need to look any further! We have SQL (MySQL, PostgreSQL,Oracle), MongoDB. We also support inserting messages into Redis. syslog-ng supports the Advanced Message Queuing Protocol (AMQP) and the Simple Text Oriented Messaging Protocol (STOMP) too, with more in the pipeline. syslog-ng supports sending messages to HTTP/REST services natively Want to deliver log messages to new systems, that are not supported by any of the log management systems, then you can easily integrate it with syslog-ng by a few lines of Python code implementing a new destination. Not only destinations could be implemented, but other items of the processing pipeline (e.g.: filter, parser, etc) and not only in Python language but also in Java.