Known issues in IBM Security QRadar SOAR Platform 51.0.4.0

There is currently one known issue in IBM Security QRadar SOAR Platform 51.0.4.0 at present.

Feature Issue

Feature	Issue
Export incidents to Excel	Export Incidents to Excel: logging set to `DEBUG` by default - causes performance issues. There are some problem related to the default logging settings related to exporting incidents to Excel: Logging is set to `DEBUG` by default, rather than `ERROR` or `INFO`. The messages go to `monitoring.log`, rather than `client.log`. As a result, every time an export incidents to Excel report is run, large amounts of data with at least 7 lines per incident of `DEBUG` level SQL messages are sent to `monitoring.log`. To work around this problem, change the log level from `DEBUG` to `INFO`. _{IBM tracking code: SOAR-20450}

Export incidents to Excel

Export Incidents to Excel: logging set to DEBUG by default - causes performance issues.

There are some problem related to the default logging settings related to exporting incidents to Excel:

Logging is set to DEBUG by default, rather than ERROR or INFO.
The messages go to monitoring.log, rather than client.log.

As a result, every time an export incidents to Excel report is run, large amounts of data with at least 7 lines per incident of DEBUG level SQL messages are sent to monitoring.log.

To work around this problem, change the log level from DEBUG to INFO.

_{IBM tracking code:
SOAR-20450}