To collect user-specific performance data:
The following subsections describe the steps in this procedure.
The fields of a user-defined record store two types of information, key information and data information. You will need to consider what to store as key information and what to store as data information.
A user-defined record for storing user-specific performance data is a multi-instance record in which one or more rows can be stored by one collection run. To identify each record instance in one user-defined record, key information must be set. If you specify multiple user-created data files in the jpcuser command, you must set key information that uniquely identifies each record instance across all of the specified files. The following table shows the types of key information.
Table 6-20 Types of key information
Type | Field name | Explanation |
---|---|---|
Transaction type | Trans Type | Identifies the instance type. |
Transaction key | Trans Data Key (numeric type) | Identifies each of the instances that have the same transaction type. |
Trans String Key (string type) |
The transaction type is used to identify the type of the performance data. For example, assume that information about a database is stored in one record and information about a Web server is stored in another record. In this case, you can use DATABASE and WEB as transaction types to indicate which type of information (information about a database or information about a Web server) is stored.
When there are multiple instances that have the same transaction type, the transaction key is used to identify each instance. If neither the Trans Data Key field nor the Trans String Key field is set, or the same value is set for multiple transaction keys, the record instances cannot be identified uniquely. As a result, the first record instance is used.
As data information, user-defined records can store three types of numeric data (double, long, and ulong types), three lengths of string data, and time data. The number of data items that can be stored differs depending on the user-defined record. For numeric data of the PI record type, either average or cumulative can be selected as the consolidation rule.
Select the user-defined record to be used based on the performance data to be collected. Note that a user-defined record that can store a larger amount of information consumes a larger amount of memory and other resources. We recommend that you select the user-defined record whose size is the minimum necessary.
The following table shows the number of fields for each type of user-defined record.
Table 6-21 Number of fields for each type of user-defined record
Record type | User-defined record type | Number of fields | ||
---|---|---|---|---|
Numeric data | String data | Time data | ||
PD record type | User Data Detail (PD_UPD) | 2 ![]() | 1 + 2 + 4 = 7 | 1 |
User Data Detail - Extended (PD_UPDB) | 5 ![]() | 5 + 5 + 5 = 15 | 1 | |
PI record type | User Data Interval (PI_UPI) | 4 ![]() | 1 + 2 + 4 = 7 | 1 |
User Data Interval - Extended (PI_UPIB) | 10 ![]() | 5 + 5 + 5 = 15 | 1 |
The following table shows the criteria for selecting the recommended user-defined record.
Table 6-22 Criteria for selecting the recommended user-defined record
Will cumulative data be stored as the performance data? | Will many types of performance data be stored? | Recommended user-defined record |
---|---|---|
Yes | No | PI_UPI |
Yes | Yes | PI_UPIB |
No | No | PD_UPD |
No | Yes | PD_UPDB |
User commands are scripts that are used to collect performance data to generate user-created data. You must code the scripts so that performance data is output in the format used for user-created data files.
For details about the format of user-created data files, see 6.4.5 Format of user-created data files.
To verify the user-created data output by the user commands, execute the jpcuser command in the following format:
/opt/jp1pc/agtu/agent/jpcuser/jpcuser PI_UPI -file user-created-data -debug 1
When the command is executed, the following debug log file is generated:
/opt/jp1pc/agtu/agent/jpcuser/debug/jpcuser_dbg_01.log
Use the debug log file to check for errors.
For details about the jpcuser command, see 6.4.4 Format of the jpcuser command.
The following explains how to set up the functionality for periodically executing user commands, to periodically collect user-specific performance data.
To periodically collect user-specific performance data.
Figure 6-3 Properties for functionality for periodically executing user commands
Table 6-23 Setting properties for user records
Property | Value | Description | Default value |
---|---|---|---|
Execute | Yes/No | Specify whether to use functionality for periodically executing user commands.
| No |
UserCommand | Absolute path | Specify the absolute path for user commands. The maximum length of the string that can be specified for an absolute path is 255 bytes. Alphanumeric characters and symbols except for the following characters can be specified: | < > | Blank |
The user data file contains data that the jpcuser command has converted from user-created data into a record format that can be managed by PFM - Agent for Platform. The data in the user data file is stored in user-defined records every time PFM - Agent for Platform collects records. Make sure that PFM - Web Console is set so that PFM - Agent for Platform will collect user-defined records.
For details about how to collect records, see the chapter on Performance Management functionality in the Job Management Partner 1/Performance Management Planning and Configuration Guide.