Online Help for Administrators > Log files

SHR log files

SHR uses the log4j API for most of it logging purposes. It maintains a log file for each of the its modules, such as collector, loader, metadata repository, internal monitoring, Administration Console, package manager, and data processing. These log files are placed in the %PMDB_HOME%\log folder. SHR also maintains an application-wide log file that contains error messages from all the modules. These log file can be used for troubleshooting purposes.

The log files available in SHR are as follows:

Log file Module Description
BSMRApp.log NA Application-wide log file that contains error messages from all the SHR modules except data processing.
collections.log Collector Contains collection framework-related log messages such as data sources configured, collection job scheduling and maintenance information.
transform.log Collector Contains log messages related to data reconciliation, mapper, enrichment, data staging, and purging of staging area.
hpacollector.log Collector Contains log messages related to HP Performance Agent collection.
topologycollector.log Collector Contains log messages related to topology collection.
dbcollector.log Collector Contains log messages related to database collection.
loader.log Loader Contains log messages related to data loading from the stage area to the data store.
metadata.log Metadata Repository Contains log messages related to metadata repository persistence, access, and modification.
Bsmrim.log Internal Monitoring Contains log messages related to the internal monitoring of data processing job streams, Sybase IQ database, PMDB platform, and Content Packs.
bsmrfrontend Administration Console Contains log messages related to the Administration Console UI web application.
dw_abclauncher.log Data processing Contains log messages related to job streams. Log messages specific to a process can be seen in the process specific log file. For example, loader.log for the loader process.
packagemanager.log Package Manager Contains log messages related to Content Pack installation and uninstallation.
postinstallconfig.log Post Install Contains log messages related to the database creation, database schema creation, and other post-install configuration tasks.
trend.log Aggregate, trendproc, trendtimer Contains messages for all of SHR’s back-end processes. Each message specifies the start and end times for the logged process.
aggregate.log Aggregate Contains log messages related to the loading of data from the rate tables to the hourly, daily, and forecast tables, and from the hourly tables to the daily tables.
audit.log Aggregate, trendproc, trendtimer Records the start times, end times, and durations of back-end processes. When a process begins, the file assigns a PID (process identification number), and then it records when the process ends, showing that the PID for the process was terminated.
backend.log Aggregate, trendproc, trendtimer Contains log information for all the data processing job steps. It also contains the logs for the Trend Sum, Loader, and SQL Executor programs.
License.log License Contain messages for license-related tasks.

SHR service log files

All SHR services have a log file associated with it. These log files contain console error messages. These log files are not controlled through log4j API and are overwritten during service startup.

Log file Service
BSMRService.log Log file for the Performance Management Database (PMDB) Platform Administrator Service.
BSMRCollectionService.log Log file for the PMDB Platform Collection Service.
BSMRDBLoggerService.log Log file for the PMDB Platform DB Logger Service.
BSMRIMService.log Log file for the PMDB Platform IM Service.
SybaseService.log Log file for the PMDB Platform Sybase IQ Service.
Trend.log Log file for PMDB Platform Timer service
Activemq.log Log file for PMDB Platform Message Broker
Postgresql-<date and time>.log Log file for the SHR PostgreSQL service.

Log file message format

All entries in the log files have the following format

Format Description
Timestamp The timestamp field represents the time the log entry occurred. It uses a 24-hour clock with the YYYY-MM-DD hh:mm:ss,nnn format.
Severity The severity field is the severity level for the log entry. The severity levels are DEBUG, INFO, WARN, ERROR, FATAL.
Class_name The fully qualified class name of the caller issuing the logging request.
Method_name The method name where the logging request was issued.
Message The application-supplied message associated with the logging event.


© 2010 - 2013 Hewlett-Packard Development Company, L.P.