This topic contains information about the installation and operation log files that are installed by the product. You can use the log files to identify issues with the product. For information about using the support utility to help you collect the log files, see Using the support utility.
Use the installation log file to identify problems that occurred during the installation. The installation log file is bsmdashboards_install_log.txt, and is located in the following directories:
- (For Microsoft Windows) %TEMP% (C:\Documents and Settings\username\Local Settings\Temp)
- (For UNIX or Linux) /var/tmp
Operations logs for BMC Dashboards for BSM are located in the following directories:
- For Microsoft Windows:
- %BSMDASHBOARDS_HOME%\DIL\CIS\logs
- %BSMDASHBOARDS_HOME%\BSMDashboards\logs
- %BSMDASHBOARDS_HOME%\BSMDashboards\derby\databases
- (If you installed Tomcat with BMC Dashboards for BSM) %BSMDASHBOARDS_HOME%\BSMDashboards\tomcat\logs
- For UNIX or Linux:
- $BSMDASHBOARDS_HOME/BSMDashboards/CIS/logs
- $BSMDASHBOARDS_HOME/BSMDashboards/logs
- $BSMDASHBOARDS_HOME/BSMDashboards/derby/databases
- (If you installed Tomcat with BMC Dashboards for BSM) $BSMDASHBOARDS_HOME/BSMDashboards/tomcat/logs
The following logs are enabled by default and set to the INFO level:
Log files | Location | Purpose |
|---|---|---|
BMC Dashboards for BSM logs | DashboardsInstallationDirectory\BMCDashboardsForBSM\ | The bsmdashboards.log and bsmdashboards-stdout.log files have calls from the BMC Dashboards for BSM user interface to the application server. These logs files provide authentication details and information about the BMC Atrium Data Integation Layer (BMC Atrium DIL) connectivity and the Derby database. |
Application server logs | DashboardsInstallationDirectory\BMCDashboardsForBSM\ | These logs provide information about application server activities. |
BMC Atrium DIL logs | DashboardsInstallationDirectory\BMCDashboardsForBSM \DIL\CIS\logs | These logs provide information about all BMC Atrium DIL-related activities (for example, caches, calls from the application server to BMC Atrium DIL). |
If you need to change the logging level to provide more details, you can change the application server logs and the BMC Atrium DIL logs to DEBUG.
To change the application server log to DEBUG
- Navigate to the DashboardsInstallationDirectory\BMCDashboardsForBSM\BSMDashboards\tomcat\webapps\bsmdashboards\WEB-INF\classes\log4j-config.xml file.
- Change the priority value to DEBUG.
- Restart the application server.
To change the BMC Atrium DIL logs to DEBUG
- Navigate to the DashboardsInstallationDirectory\BMCDashboardsForBSM\DIL\CIS\conf\server\log4j.properties file.
Scroll to the end of the file and update the following WARN values to DEBUG:
log4j.logger.com.bmc.dil.proc=WARN log4j.logger.com.bmc.dil.config=WARN log4j.logger.com.bmc.dil.shared.config=WARN log4j.logger.com.bmc.dil.util=WARN
The updated values are shown below:log4j.logger.com.bmc.dil.proc= DEBUG log4j.logger.com.bmc.dil.config= DEBUG log4j.logger.com.bmc.dil.shared.config= DEBUG log4j.logger.com.bmc.dil.util=DEBUG
Edit the DashboardsInstallationDirectory\BMCDashboardsForBSM\CIS\conf\dil\dil.properties file and add the following line to it:
dil.logging=true
- Restart the BMC Atrium DIL service.
To clean up the logs
Follow the steps given below to clean up the logs as using the DEBUG value causes the log file to fill quickly.
- Stop the application server service and the BMC Atrium DIL services.
- Archive the old log files.
- Delete the log files manually.
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks