Skip to Content

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 <smart_reporting_tomcat_installation_directory>\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 log4j2.xml file in <smart_reporting_tomcat_installation_directory>\appserver\webapps\smartreporting\WEB-INF and uncomment the following line:

<!-- uncomment to set everything under com.hof and bi.yellowfin to debug -->
<!--
<Logger name="com.hof" level="DEBUG" />
<Logger name="bi.yellowfin" level="DEBUG" />
        -->
This sets the logging level to DEBUG. 

Warning

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:
<!-- uncomment to set everything under com.hof and bi.yellowfin to debug -->
<!--
<Logger name="com.hof" level="DEBUG" />
<Logger name="bi.yellowfin" level="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

Upgrade issues

Microsoft Windows:
Navigate to the path from where you ran the installation files.
SmartReporting2002Patch3InstallLog-YYYYMMDD.log

Linux:
Navigate to the path from where you ran the installation files.
SmartReporting2002Patch3InstallLog-YYYYMMDD.log

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 <smart_reporting_tomcat_installation_directory>
\appserver\logs directory:

  • sr.<date>.log
  • sr-error.<date>.log
  • smartreporting.log

Performance issues

Perform the following steps for logging the performance issues:

  1. Enable the debug logging level in the log4j2.xml file located at SmartReportingtomcatInstallationDirectory\appserver\webapps\smartreporting\WEB-INF.
  2. Uncomment the following line:
    <!-- uncomment to set everything under com.hof and bi.yellowfin to debug -->
    <!--
    <Logger name="com.hof" level="DEBUG" />
    <Logger name="bi.yellowfin" level="DEBUG" />
            -->
  3. Save the changes.
  4. Restart Remedy Smart Reporting.
  5. Replicate the performance issue in the browser and collect all the logs from the following directory:
    SmartReportingtomcatInstallationDirectory\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: SmartReportingtomcatInstallationDirectory\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*

Remedy Smart Reporting 20.02