Working with logs

This topic describes the log files associated with

Unknown macro: {multi-excerpt-include}

.

The following log files, which are located in the BDSSAInstallationDirectory/logs directory, are associated with BMC BladeLogic Decision Support for Server Automation:

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/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*

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

Unknown macro: {multi-excerpt-include}

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

Page tree

Working with logs