ePO 5.x has added logging capability to include detailed SQL logging to the
Orion.log file. The additional logging capability must be used only for troubleshooting purposes. This logging is resource-intensive and can cause many performance issues.
The configuration for this extra logging must be included in the
log-config.xml file. But, sometimes, this log configuration might be missing from the
log-config.xml file. This issue can occur after an upgrade from ePO 4.6. The issues occur when the upgrade carries over the existing
log-config.xml file. It's seen when you've added some additional configuration to this file. In doing so, the new loggers that are normally included with a fresh installation of ePO 5.x aren't added. The default behavior for this extra logging is to be on. So, if these additional loggers are missing from the
log-config.xml file, it causes them to be turned on and results in performance issues.