Using the new --configLog file option of the correlator executable, you can now specify the path to the configuration log file. The configuration log file contains the correlator's configuration, that is, the contents of all YAML configuration files and properties files as well as the correlator startup arguments and environment. The configuration log is a good way to capture useful diagnostic information from the correlator's startup in performance-critical situations where it is not acceptable to enable the input log. This option was already added with 10.5.1. However, the documentation has only been updated with 10.5.2. See also Starting the correlator.

The results of a eplMemoryProfileMonitorInstanceDetail request are now returned using the following sort order:

The startup log stanza is now repeated even when logging is going into stdout/stderr via the --rotateLogs management request while using the engine_management tool (see also Shutting down and managing components) or by using SIGHUP in Linux.