*rsyslog* rebased to version 8.24.0
The *rsyslog* utility has been rebased to upstream version 8.24.0, which includes numerous enhancements, new features and bug fixes. Notable improvements include:
* A new core engine has been implemented, offering faster message processing.
* Speed and stability when handling data in the JSON format have been improved.
* The RainerScript configuration format has been selected as default and improved with more options.
* A new *mmexternal* module for manipulation of messages inside *rsyslog* using external applications has been added.
* The *omprog* module has received improvements for better communication with external binaries.
* Modules *imrelp* and *omrelp* now support encrypted transmission using the TLS protocol.
* The *imuxsock* module now supports rule sets for individual sockets, which override the global rule set.
* When the *imuxsock* module is used, rate limiting messages now include PID of the process that causes the rate limiting.
* The TCP server error messages now include the IP address of the remote host.
* The *imjournal* module no longer stops receiving logs after switching to the persistent *journald* configuration.
* Logging to the runtime journal no longer completely stops after a reboot when the machine's clock was set to an earlier time.
* Previously, when the *logrotate* utility with "copytruncate" option was rotating a log file, the *imfile* module might not have read all of the log messages from the file being rotated. As a consequence, these log messages were lost. The *imfile* module has been extended to handle this situation. As a consquence, messages are no longer lost when *logrotate* "copytruncate" is used on log files.
Customers using custom modules are advised to update their modules for the current rsyslog version.
See also the Deprecated Functionality chapter for information about deprecated *rsyslog* options.