How to Setup Performance Monitor Logging for HFM Processes

How to Setup Performance Monitor Logging for HFM Processes [Windows 2003 only] [ID 953372.1]

		Modified 02-MAY-2011 Type TROUBLESHOOTING Status PUBLISHED

In this Document
  Purpose
  Last Review Date
  Instructions for the Reader
  Troubleshooting Details

Applies to:

Hyperion Financial Management - Version: 4.0.0.0.00 to 11.1.1.3.00 - Release: 4.0 to 11.1
z*OBSOLETE: Microsoft Windows Server 2003

Purpose

This article will provide configuration information for setting up a Counter Log under Performance Logs and Alerts to keep track of HFM processes [Windows 2003 machines only].

Last Review Date

October 15, 2009

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

Here is an example of Counter information for the configuration file.
Note: The counters in the configuration may need to be edited. Currently the configuration file looks like:



[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(HsvDataSource)\*

\Process(HsvDataSource#1)\*

\Process(HsvDataSource#2)\*

\Process(HsvDataSource#3)\*

\Process(HsxServer)\*

\PhysicalDisk\*

\System\*

1. Copy the above configuration, edit as following, and save as basic_hfm_perfmon.txt

[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 as .csv
[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. The logs should last about 8 hours, however try not to generate large files.

o The system impact of logging should be negligible, but you can easily monitor the resources being used by the logging service by tracking the "smlogsvc.exe" process to verify that logging is not placing a burden on the server.

[version] - Set to nnnnnn to end file name with
[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 you have running, but having fewer monitored means we could miss the issue completely.

2. The syntax to create the Counter 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 from the same directory as the config file as well.
The collection does need to be manually started initially and after each server reboot. The syntax to manually start from a Command prompt is: logman start counter basic_hfm

Final Results: