How to Setup Microsoft Performance Monitor Logging for Hyperion Financial Management Application Processes

How to Setup Microsoft Performance Monitor Logging for Hyperion Financial Management Application Processes [ID 953294.1]

		Modified 11-OCT-2011 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution

Applies to:

Hyperion Financial Management - Version: 4.0.0.0.00 to 11.1.2.0.00 - Release: 4.0 to 11.1
Information in this document applies to any platform.

Goal

This article will provide configuration information for setting up a Microsoft Performance Monitor to log counters specific to Hyperion Financial Management (HFM) application processes.

Solution

On Microsoft Windows 2003 servers, a log Collection can be created using a script to ensure proper setup by copying the following section into a new text file and following the steps below:

[name]
Basic_HFM

[sample]
36

[format]
csv

[newfile]
true

[max]
10

[version]
nnnnnn

[counters]
\Memory\*
\Network Interface(*)\*
\Processor(*)\*
\Process(_Total)\% Processor Time
\Process(_Total)\Private Bytes
\Process(CasSecurity)\*
\Process(HsvDataSource)\*
\Process(HsvDataSource#1)\*
\Process(HsvDataSource#2)\*
\Process(HsvDataSource#3)\*
\Process(HsxServer)\*
\PhysicalDisk\*
\System\*

1. Copy the above into a new TEXT file and save as basic_hfm_perfmon.txt. Explanation of the entries is as follows:

[name] - Provide name to indicate this counter is for Basic_HFM.
[sample] - Interval to sample data will be every 36 seconds.
[format] - Log file name will be saved in csv format.
[newfile] - Set to true to generate new file when max has been reached.
[max] - Set to 10 mb for max file size.

o The Max size of the log file is currently set to 10 Mb. A new file is generated when the old file reaches 10 Mb.
o Monitor the logs to see how fast they switch from one to another. Generally 6-8 hours of logs are generated per log file.

[version] - Set to nnnnnn to end the file name with numeric values.
[counters] - Verify how the HFM processes show in Task Manager on your HFM application server.

o If they appear as HsvDat~1, HsvDat~1#1...HsxSer~2, then make the changes in the configuration file to match.
o If you have more than 4 applications in the list, please add additional \Process(HsvDataSource#X)\* entries to account for all possible HFM applications.
o It is OK to have more HsvDatasource process than the actual number HFM applications running, but having fewer monitored means the monitoring could miss gathering the proper application process completely.

2. The syntax to create the log collection from a Command prompt is: logman create counter -config basic_hfm_perfmon.txt

Provide the full path to the "basic_hfm_perfmon.txt" file if the command is not run from the directory where the file resides. You can drop the statement above into a new CMD file and execute it from the same directory as the config file.
The collection does need to be manually started after each server reboot. The syntax to manually start from a Command prompt is: logman start counter basic_hfm

The system impact of performance monitor logging should be negligible. The impact of logging can be verified by monitored the resources being used by the logging service "smlogsvc.exe" to ensure that logging is not placing a burden on the server.

Screen shot showing the Basic_HFM collection in Performance Monitor:

Note that it is possible to create logging collections manually. However, the use of a script to create the collection is preferable to the manual method since counters for process like HsvDatasource.exe can only be added if the process is currently running. This means that you cannot add counters for 3 HsvDatasource.exe process unless all 3 HFM applications are currently running. The script method also ensures that multiple HFM application servers are configured identically.