currently we have in epel8 version 3.23.1. would be great to have at least 3.37.1 as there is a neat feature, which makes life easier for admins: https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.37/administration-guide/78#TOPIC-1829213 Renaming message fields If you want to change the name of a field of a message, you can use rename() rewrite rules. This can be also achieved via using set() and unset() but those require extra conditions and two operation instead of one. The rename() rewrite rule uses positional arguments and they are both required. It supports condition rewrite. For more information, see Conditional rewrites. yours josef
While I fully agree, EPEL has the policy of version lock. Just for this reason, I also have syslog-ng packages in Copr. This blog describes how to use versioned package repositories: https://www.syslog-ng.com/community/b/blog/posts/installing-latest-syslog-ng-on-rhel-and-other-rpm-distributions And this one a repo, which is updated on each new syslog-ng release after some delay: https://www.syslog-ng.com/community/b/blog/posts/introducing-the-syslog-ng-stable-rpm-repositories
thanks for the very fast suggestion on using copr. sadly we cannot use copr-repos in our environment. maybe we could get a permission from EPEL Steering Committee?