Download Performance Sentry User Manual

Transcript
4
Runtime Parameters Reference
The Performance Sentry Collection Service runs unattended, using runtime parameters that are
stored in the Data Collection Set DCSX xml file. A Data Collection Set (DCS) defines the
performance objects and counters that are collected, the collection interval, the location of the
data files, the file duration, the time of day the data file is closed and a new file opened, and many
other runtime parameters. This section of the manual describes each of the runtime parameters
that are used to control the operation of the Performance Sentry Collection Service.
When you install the Performance Sentry performance data Collection Service, as described in
Chapter 2, the service automatically uses the parameters defined in the Default Collection Set
collection set. When you activate a Data Collection Set using the Performance Sentry
Administration application or the DmCmd Automation Interface, the Performance Sentry
Collection Service uses the parameter values you specify. When activating a Data Collection Set
using the Performance Sentry Administration, it will always assign the Data Collection Set and
then restart the collection cycle with the new parameters. The DmCmd automation interface
provides the flexibility to perform these two steps separately.
For convenience when you are editing a DCS using the Sentry Administration program, data
collection service parameters are organized into the following groups:
•
Cycle – parameters that determine the collection interval, the cycle time, cycle duration,
and actions taken at cycle end.
•
Scheduling — parameters that control the next DCS or collection period activation.
•
File Contents — parameters that control the content of the data collected.
•
File Management — parameters that determine the location and management of the
Performance Sentry collection files.
•
Messaging — parameters that control the error and information messages that the
service produces.
Some of the parameters have no defaults and must be specified in order to use the function.
54