Enabling diagnostic data logs

Procedure

For Report Builder

To enable diagnostic data collection for report executions in Report builder, a new set of logs is now written to the server/logs/directory/rs-lqe-query.log file.

The new logs are enabled by default in the server/conf/rs/log4j2.xml file:

<!-- LQE-RS log file -->
        <RollingFile name="lqeRsLog" filename="${dir}/${app}-lqe-query.log" filePattern="${dir}/${app}-lqe-query-%i.log">
            <PatternLayout pattern="${pattern}"/>
            <Policies>
                <SizeBasedTriggeringPolicy size="10 MB"/>
            </Policies>
            <DefaultRolloverStrategy max="5"/>
        </RollingFile>

For Lifecycle Query Engine
Lifecycle Query Enginenow logs performance and sizing metrics in a specialized log file, lqe-rs.log. The diagnostic data is useful for comparing an existing Lifecycle Query Engine implementation with the new Lifecycle Query Engine relational store.
Note: This data is collected only if the Lifecycle Query Engine relational store is enabled.
The lqe-rs.log file contains the following information:
- System specifications of the server that hosts Lifecycle Query Engine:
  - Operating system
  - Amount of RAM
  - Number of processors
- Metrics for any major data source operations such as reindexing or validation.
- Size of every table in the Lifecycle Query Engine relational store.
If the following lines are not available, add them to the conf/lqe/log4j2.xml file to enable logging:
```

		<RollingFile name="lqeLog" filename="${dir}/${app}.log" filePattern="${dir}/${app}-%i.log">
			<PatternLayout pattern="${pattern}"/>
			<Policies>
				<SizeBasedTriggeringPolicy size="10 MB"/>
			</Policies>
			<DefaultRolloverStrategy max="5"/>
		</RollingFile>
```