Logging in Remedy Smart Reporting
For latest version of this topic, go to the
Remedy Smart Reporting documentation
.
BMC Remedy Smart Reporting has a number of different logging facilities for different parts of the application. The main BMC Remedy Smart Reporting application log is named smartreporting.log and is located at C:\Program Files\BMC Software\ARSystem\SmartReporting\appserver\logs. The smartreporting.log file contains error and warning messages and information about BMC Remedy Smart Reporting. You can configure BMC Remedy Smart Reporting to log additional debugging information in this file. For this, go to the log4j.properties file located at C:\Program Files\BMC Software\ARSystem\SmartReporting\appserver\webapps\ROOT\WEB-INF and uncomment the following line:
|
This sets the logging level to DEBUG.
Note
When you set the log level to DEBUG, the log file size increases quickly. BMC recommends that after you have finished debugging, turn the debugging off by commenting the following line:log4j.category.com.hof=DEBUG
Restart the BMC Remedy Smart Reporting Server after commenting the above statement, else replace DEBUG with INFO to stop the DEBUG logging.
The following table lists the logs that you can refer to for issues in Remedy Smart Reporting:
| Issue | Log Details |
|---|---|
Install and Upgrade issues | Microsoft Windows:
Linux:
|
| Onboarding and importing content issues | See the following log files located in the
|
| Performance issues | Perform the following steps for logging the performance issues:
In addition to the log file, you can check the Info Threads to find out the root cause of the performance issues. For more information, see InfoThreadrunner. This is a Yellowfin utility that indicates which processes are slow. |
| User synchronization issues |
|
| Service outages | See the following log files located in the
|
Comments