Logging in Remedy Smart Reporting

Remedy Smart Reporting has several logging facilities for different parts of the application. The main Remedy Smart Reporting application log (smartreporting.log) is in the C:\Program Files\BMC Software\ARSystem\SmartReporting\appserver\logs directory. The smartreporting.log file contains error and warning messages and information about Remedy Smart Reporting.

You can configure Remedy Smart Reporting to log additional debugging information in this file. Go to the log4j.properties file in C:\Program Files\BMC Software\ARSystem\SmartReporting\appserver\webapps\ROOT\WEB-INF and uncomment the following line:

log4j.category.com.hof=DEBUG

This sets the logging level to DEBUG. 

Note

When you set the log level to DEBUG, the log file size increases quickly. After you have finished debugging, turn the debugging off by commenting the following line:
log4j.category.com.hof=DEBUG

Then, restart the Remedy Smart Reporting server.

Alternatively, you can 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:

  • arsystem_install_log located at InstallationPath\BMC Software\ARSystem
  • SmartReportingInstallLog located at InstallationPath\BMC Software\ARSystem\SmartReporting

Linux:

  • arsystem_install_log located at InstallationPath\opt\bmc\arserver\
  • SmartReportingInstallLog located at InstallationPath\opt\bmc\arserver\smartreporting

Changing default user role

See the log files located in the InstallationPath\AR\Arserver\Db\smartreporting.log directory.

Onboarding and importing content issues

See the following log files located in the InstallationPath\BMC Software\ARSystem\SmartReporting\appserver\logs directory:

  • sr.log
  • sr-error.log
  • smartreporting.log

Performance issues

Perform the following steps for logging the performance issues:

  1. Enable the debug logging level in the log4j.properties file located at SmartReportingInstallationDirectory\BMCSoftware\ARSystem\SmartReporting\appserver\webapps\ROOT\WEB-INF.
  2. Change the value of the log4j.rootCategory parameter from ERROR to DEBUG.
  3. Uncomment the # log4j.category.com.hof=DEBUG line.
  4. Save the changes.
  5. Restart Remedy Smart Reporting.
  6. Replicate the performance issue in the browser and collect all the logs from the following directory:
    InstallationPath\BMC Software\ARSystem\SmartReporting\appserver\logs

In addition to the log file, you can check the Performance Analysis Snap Shot Tool to find out the root cause of the performance issues. This Yellowfin utility indicates which processes are slow. For more information, see Performance Analysis Snap Shot Tool in the Yellowfin knowledge base. 

User synchronization issues

  • Reporting Logs : InstallationPath\AR\Arserver\Db\smartreporting.log 
  • Plugin Logs: InstallationPath\AR\Arserver\Db\arjavaplugin.log
  • Filter Logs : InstallationPath\AR\Arserver\Db\arfilter.log

Common content synchronization issues

Plugin logs:

  • InstallationPath\AR\Arserver\Db\smartreporting.log
  • InstallationPath\AR\Arserver\Db\arjavaplugin.log

Reporting logs: InstallationPath\appserver\logs\smartreporting.log

Service outages

See the following log files located in the <Install Path>\BMC Software\ARSystem\SmartReporting\appserver\logs directory:

  • smartreporting.log
  • jdbc.log
  • source.log
  • <Servicename>-stderr

Data source connection issues

Reporting logs: InstallationPath\appserver\logs\source.<datasourceID>.log. For example, source.12345.log. For more information, see Data-source-connection-logs.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*