Peter Czanik<p>Version 4 of <a href="https://fosstodon.org/tags/syslog_ng" class="mention hashtag" rel="tag">#<span>syslog_ng</span></a> works perfectly well in version 3 <a href="https://fosstodon.org/tags/compatibility" class="mention hashtag" rel="tag">#<span>compatibility</span></a> mode. However, if you want to use the syslog-ng 4 features, you need to be aware of some significant <a href="https://fosstodon.org/tags/changes" class="mention hashtag" rel="tag">#<span>changes</span></a>. If you have a simple configuration, like those in <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="tag">#<span>Linux</span></a> distributions, then simply rewriting the version string is most likely enough. However, if you use <a href="https://fosstodon.org/tags/PatternDB" class="mention hashtag" rel="tag">#<span>PatternDB</span></a> or <a href="https://fosstodon.org/tags/JSON" class="mention hashtag" rel="tag">#<span>JSON</span></a> parsing, any <a href="https://fosstodon.org/tags/Python" class="mention hashtag" rel="tag">#<span>Python</span></a> code, or an <a href="https://fosstodon.org/tags/Elasticsearch" class="mention hashtag" rel="tag">#<span>Elasticsearch</span></a>, or <a href="https://fosstodon.org/tags/MongoDB" class="mention hashtag" rel="tag">#<span>MongoDB</span></a> destination, you have to be aware of the changes.<br /><a href="https://www.syslog-ng.com/community/b/blog/posts/upgrade-problems-from-syslog-ng-3-to-4" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://www.</span><span class="ellipsis">syslog-ng.com/community/b/blog</span><span class="invisible">/posts/upgrade-problems-from-syslog-ng-3-to-4</span></a></p>