Notes on records
This section provides notes about record collection.
- Organization of this page
Notes about preparing for collection of performance data
The following point should be noted before you collect performance data:
- Changing registry
-
This note is applicable to Windows.
PFM - RM for Platform supports operation in an environment that is set up by the OS-provided standard method.
If you use special OS settings, such as by using a registry editor to directly edit registry information, performance data might not be collected correctly even if such customization is disclosed in the Microsoft technical support information.
- Collecting historical data
-
For each record, PFM - RM for Platform stores historical data for all monitoring targets in an instance, or historical data summarized for each group agent, in the same data file. The maximum size limit for each data file is 2 gigabytes. Therefore, if an instance contains many monitoring targets or if a record contains many instances, it might not be possible to store all of the historical data in the Store database.
Of all the data collected, the historical data summarized for each group agent might cause a data file space shortage. Therefore, when using a group agent for monitoring, we recommend that you use real-time monitoring rather than monitoring based on historical data.
If you monitor based on history, you need to reduce the number of monitoring targets in the instance to prevent the data file size from exceeding 2 gigabytes, or use the LOGIF property to reduce the amount of data that is to be stored in the Store database.
For details about how to estimate the disk space that the Store database will occupy, see A. Estimating System Requirements.
Notes about identifying record instances
The following note is about identifying record instances.
- When instances are not identified uniquely
-
This note applies only when the monitored host is running Windows.
PFM - RM for Platform collects performance data by referencing the most recent information at specific intervals. If PFM - RM for Platform cannot identify the record instance uniquely from the information acquired from the OS, it adds a number in the format #n (n: 1, 2, 3, ...) at the end of the following field:
Record name
Field name
Network Interface Overview (PI_NET)
Interface (INTERFACE)
Notes about changing the system resources for the monitored host
The following note concerns changing the system resources for the monitored host.
- Performance data before and after system resources are changed
-
When you change system resources for the monitored host, continuity between the performance data collected before and after the change is lost. Therefore, the performance data before and after the change must be handled as different sets of performance data.
Notes about records
- Data values in a record whose instance name is _Total
-
The total and average values of all instances are collected as data values in the record whose instance name is indicated as _Total among all multi-instance records. If the instance environment is changed during the collection interval, values might not match.
- Value exceeding the data type defined in the data model
-
PFM - RM for Platform does not support a value that is outside the permissible range for the data type defined in the data model. If a value exceeding the data type defined in the data model is collected, the values that are displayed might not be accurate.
- When records are not created
-
If PFM - RM for Platform cannot collect the performance data for the field that is defined as the ODBC key field, no record is created.
- Fields for which performance data is not collected during the first collection
-
Non-PD records contain fields for which performance data is not collected during the first collection. For these fields, performance data is collected during the second and subsequent collections.
- When accurate performance data cannot be collected because of an action specific to the virtualization facility
-
You might not be able to collect accurate performance data due to an action specific to the virtualization facility, such as a time jump.
- When accurate performance data cannot be collected from an AIX monitored host
-
If the instance settings of PFM - RM for Platform satisfy all of the following conditions, you might not be able to collect accurate performance information:
-
An AIX host is set for the monitored host.
-
The iostat kernel parameter of the monitored host is set to false.
-
The sar command was executed on the monitored host.
-
The Std_Category or Disk_Category property of the instance is set to Y.
When PFM - Agent for Platform is running on the monitored host, you might not be able to collect accurate performance information if the instance settings satisfy all of the following conditions:
-
An AIX host is set for the monitored host.
-
The iostat kernel parameter of the monitored host is set to false.
-
The Agent Configuration - sar Command Monitoring property of PFM - Agent for Platform running on the monitored host is set to Y.
-
The Std_Category or Disk_Category property of the instance is set to Y.
If the Std_Category property is set to Y, you might not be able to collect CPU-related performance information. If the Disk_Category property is set to Y, you might not be able to collect disk-related performance information.
-
- When accurate performance data cannot be collected because of a change in the disk device
-
If the disk device indicated by the disk device name is changed by a change to the system, for example, continuity is lost in the performance information captured after the change to the system, even if the disk device name remains the same.
- When accurate performance data cannot be collected because of the state of the mounted remote file system
-
Only operate PFM - RM for Platform when the information in the mounted remote file system can be referenced (the state in which the df command can be executed normally). If the Disk_Category property of the instance is set to Y while the mounted remote file system is not responding, the Remote Agent service cannot collect correct performance data. For details about how to recover from this state, see 10.2.3 PFM - RM for Platform was started, but no performance data is being collected.
- When collection takes a long time
-
Collection may take a long time depending on the load on the system or network. In such a case, implement the connection test described in 10.2.5 The message "KAVL17016-W Performance data was not saved to the Store database because it is the same as previous performance data." is output to the common message log and set a value larger than the time measured in the connection test to the collection interval for the collection process (setting item Interval in the instance environment) and the collection interval for each item of performance information (setting item Collection Interval for each record).
Other notes
-
Interface information specified by using the NIC teaming function in Windows cannot be collected.
-
A Windows host can only be monitored if the language of the Windows environment on the monitored host matches that of the RM host, or if the monitored host is running an English-language version of Windows.
-
Language environments other than Japanese, English, and Chinese support only the ASCII character set. In such environments, non-ASCII characters in performance data are not displayed correctly.
-
Setup files are not updated unless items such as the data model are changed. As a result, the version number displayed in message KAVE05908-I when the jpcconf agent setup command is executed might be different from the product's actual version number.