Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Working with logs

This topic describes the log files associated with 

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

.

The following log files, which are located in the BDSSAInstallationDirectory/logs directory, are associated with 

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

:

Log file name and location

Description

BDSSAInstallationDirectory/logs/blauthprovider.log

BMC Server Automation authentication provider log

BDSSAInstallationDirectory/logs/blrptadmin.log

Report Administration Utility log

BDSSAInstallationDirectory/logs/etl/timeStamp/
site_siteID_timeStamp_run_etl.log

ETL log (update IBM Cognos model and process permissions-related log)

BDSSAInstallationDirectory/logs/etl/
etl_performance_YYYYMMDDhhmmss_info.log

ETL performance log
To generate this log file, use the following command from the BDSSAInstallationDirectory\etl\bin directory:

nsh get_etl_performance_info.nsh -d <n>

The d option generates the detailed log for last n days.

BDSSAInstallationDirectory/logs/etl/etl_debug.log

ETL debugging log

BDSSAInstallationDirectory/logs/install.log

BMC BladeLogic Decision Support for Server Automation installation log

The following log collector configuration files contain the log generation parameters:

Log collector configuration file name and location

Associated with

BDSSAInstallationDirectory/portal/configuration/bl_log4j.properties

BMC Server Automation authentication

BDSSAInstallationDirectory/bin/blreports_log4j.properties

Report Administration Utility

BDSSAInstallationDirectory/bin/etl_log4j.properties

ETL (update Cognos model and process permissions-related)

The following table shows the logging utilities with their definitions that are defined in these files:

Logging utility

Definition

Info

log4j.logger.com.bladelogic.warehouse.common.util.BlLogger.Info=INFO, LOGFILE
|STDERR
|STDOUT

Error

log4j.logger.com.bladelogic.warehouse.common.util.BlLogger.Error=ERROR, LOGFILE
|STDERR
|STDOUT

Debug

log4j.logger.com.bladelogic.warehouse.common.util.BlLogger.Log=DEBUG, LOGFILE
|STDERR
|STDOUT

Messages can be written to LOGFILE,STDERR, or STDOUT. Usually STDERR or STDOUT specify that messages be redirected to the system console. LOGFILE specifies that message be written to the log file. By default, 

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

messages are written to the log files listed in this topic.

 

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