Configuring user names and memory usage in TM1 Web logs
In IBM® Planning Analytics Local version 2.0.8, user names and memory usage can be included in TM1® Web logs.
For TM1 Web logs version 2.0.69 or earlier, you can turn on this optional logging by setting the
logging level of log4j.logger.com.ibm.cognos.tm1 to DEBUG in
the \tm1_64\webapps\tm1web\WEB-INF\configuration\log4j.properties file.
If you are using TM1 Web logs version 2.0.70 or later, turn on this optional logging by setting
the logging level of logger.tm1.level to DEBUG in the
\tm1_64\webapps\tm1web\WEB-INF\configuration\log4j2.properties file.
This logging option makes it easy to see when a user runs an active form, workbook, or cube that renders too many rows. You can review the audit logs and reduce the number of rows in the rendering.
The following information is included in logs:
- Timestamp
- Application and Active Form name
- Number of rows that were generated
- User name
- Current heap memory after the websheet renders
For more information, see Configuring and enabling IBM TM1 Web logging for versions 2.0.69 and earlier or Configuring and enabling IBM TM1 Web logging for versions 2.0.70 and later.
Example log when you open an active form
<TIMESTAMP>:CLASSNAME:Constructed view for <ActiveFormViewid> contains <#> rows, by user '<username>'.
<TIMESTAMP>:CLASSNAME:Current heap memory usage: <MB>
Example log when you open a workbook
<TIMESTAMP>:CLASSNAME:Creating WorkbookMetaData for <sheet name>, by user '<username>'.
<TIMESTAMP>:CLASSNAME:Current heap memory usage: <MB>
Example log when you open a cube view
<TIMESTAMP>:CLASSNAME:Exit from getUpdatedCubeViewData, updatedData: class name, username: <username>.
<TIMESTAMP>:CLASSNAME:Current heap memory usage: <MB>