Version 4.11 of syslog-ng will feature a brand-new Kafka source. While it is being tested and reviewed, we are working on reducing the number of open issues. What should be fixed next?
Two weeks ago, I wrote about testing the upcoming syslog-ng 4.11 release: https://www.syslog-ng.com/community/b/blog/posts/call-for-testing-syslog-ng-4-11-is-coming Testing and reviewing the Kafka source, the focus of the upcoming 4.11 release, happened to be a larger task than expected, so testing of the development branch is still very welcome. While waiting for the Kafka source, we started reducing the number of open issues on GitHub: https://github.com/syslog-ng/syslog-ng/issues
We have already resolved a number of issues based on our own priorities. However, we are also curious about what issues we should be working on based on your priorities. Let us know which particular open issues cause you the most headache, and how. Knowing the details helps us both in prioritization and resolving the issue.
Before pressing +1 or providing details to open issues, make sure that the issue is not yet fixed. This is why I linked 4.11 testing earlier. It might be fixed even if the issue is not yet closed. Feedback on the Kafka source is also welcome!
-
If you have questions or comments related to syslog-ng, do not hesitate to contact us. You can reach us by email or even chat with us. For a list of possibilities, check our GitHub page under the “Community” section at https://github.com/syslog-ng/syslog-ng. On Twitter, I am available as @PCzanik, on Mastodon as @Pczanik@fosstodon.org.