Job Management Partner 1/Performance Management User's Guide

[Contents][Glossary][Index][Back][Next]


4.1.1 Modifying the recording options for performance data

You can modify the recording options for performance data collected by Agent Collector and Remote Monitor Collector services. The recording options for performance data include:

Each record has specific recording options for performance data. For some records, however, you cannot modify the options. For details, see the description of properties in an appendix of the appropriate PFM - Agent or PFM - RM manual.

You can modify the recording options for performance data in one of two ways:

Each of these is described below.

Organization of this subsection
(1) Modifying the recording options for performance data by using the monitoring console
(2) Modifying the recording options for performance data by using commands

(1) Modifying the recording options for performance data by using the monitoring console

To modify the recording options for performance data by using the monitoring console, use the Services window in PFM - Web Console.

To modify the recording options for performance data by using the monitoring console:

  1. Log on to PFM - Web Console from the browser of the monitoring console.
    You need to log on as a user with administrator user permissions. You must have administrator user permissions to use the Services window.
    The main window of PFM - Web Console appears.
  2. In the navigation frame of the main window, select the Services tab.
    The Services window appears.
  3. In the navigation frame of the Services window, expand the hierarchy under the Machines folder.
    The hierarchy displays folders with the same names as the hosts where Performance Management services are installed. When you expand one of these folders, the services installed on that host are displayed. The name of each service is represented by a service ID. For details on service IDs, see the description of the service naming rules in an appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide and the list of identifiers described in the appropriate PFM - Agent or PFM - RM manual.
    The service ID format differs depending on whether the product name display function is enabled. For details on the product name display function, see the chapter that describes the Performance Management functions in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
  4. Expand the hierarchy under the folder with the name of the host for which you want to modify the recording options for performance data, and select a node for which you want to modify the recording options for performance data.
    For PFM - RM, select the node according to which performance data recording option you would like to change. The following table lists the corresponding node to select for the option to be changed.

    Table 4-1 Items to be modified and nodes to be selected

    Item to be modified Node to be selected
    Remote Monitor Collector service Remote agent or group agent
    The data to be recorded No Yes
    The frequency of data collection Yes No
    The offset at which to start collecting data Yes No
    Specifies the condition for registering records in the store database. Yes No

    Legend:
    Yes: Can be selected.
    No: Cannot be selected.
    The selected node is marked with a checkmark.
  5. In the method frame, select Properties.
    The Properties window of the selected node is displayed with the properties shown hierarchically.

    Figure 4-1 Example of the hierarchy of the properties of a node

    [Figure]

    The following table lists the record type corresponding to each node.

    Table 4-2 Record type corresponding to each node

    Node Record type
    Detail Records PD record type
    Interval Records PI record type
    Log Records PL record type
  6. Expand the hierarchy under the node containing the record for which you want to modify the recording options, and select the desired record.
    When you expand the node for a record type, the nodes for records of that record type are displayed. The name of each record is represented by the corresponding record ID without the database ID.
    The selected record is marked with a checkmark and the settings of the specific recording options are displayed at the bottom of the information frame.
  7. Modify the definitions of the recording options for the record.
    The properties of the selected record are displayed at the bottom of the information frame.

    Figure 4-2 Example of settings for recording options

    [Figure]

    Modify the property settings. The following table lists descriptions, settings, and nodes that can be modified for each property.

    Table 4-3 Description and settings and nodes that can be modified for each property

    Property name Description and settings Node that can be modified.
    Description Displays the description for the selected record. --
    Log Specifies whether to record collected records in the Store database.
    • Yes: Records
    • No: Does not record

    • Agent Collector
    • Remote agent
    • Group agent
    Collection Interval# Specifies a numerical value from 0 to 2,147,483,647 for the interval time for collecting records. The time is in seconds.
    0 means that records will not be collected.

    • Agent Collector
    • Remote Monitor Collector
    Collection Offset# Specifies a numerical value from 0 to 32,767 for the offset at which to start collecting records. The time is in seconds.
    For example, all records with the offset value of 0 are collected simultaneously each time. A record with the offset value of 20 is collected 20 seconds after the records with the value of 0.

    • Agent Collector
    • Remote Monitor Collector
    Sync Collection With# A record appears to synchronize collection with. --
    LOGIF Allows you to specify the conditional expression to use for records to be recorded in the database. Records are recorded according to the condition specified here. Because the condition set here is applied to data stored in the Store database, it does not affect data collection performed by the Agent Collector service or the Remote Monitor Collector service.
    Click the text box to display the LOGIF Expression Editor window in a separate window. In the LOGIF Expression Editor window, you can create conditional expressions by specifying desired fields, operators, criteria values, and other items. Click the OK button to accept the settings, and the conditional expression you have just created is inserted in the LOGIF text box. For further details, see the description for the LOGIF Expression Editor window in the manual Job Management Partner 1/Performance Management Reference.

    • Agent Collector
    • Remote Monitor Collector

    Legend:
    --: Not applicable

    #:
    The Sync Collection With property and either the Collection Interval or Collection Offset property are mutually exclusive.

    Notes:
    • Increasing the number of records for which performance data is collected might affect your disk space or system performance. When you set up records to be collected, make sure you only set those items that are necessary for monitoring, always considering your requirements for performance data collection, such as the required free disk space and the record collection interval. For information on the required free disk space, see the appendix describing system estimation in the appropriate PFM - Agent or PFM - RM manual. For details on disk space requirements, see the appendix describing system estimation in the appropriate PFM - Agent or PFM - RM manual.
    • For the Collection Interval for record collection, either use the default value or specify a value that is both 60 seconds or more and a factor of 3,600. When you have to specify a value that is more than 3,600 seconds (one hour) for the Collection Interval, choose a number that is both a multiple of 3,600 and a factor of 86,400 (24 hours). If the Collection Interval is set to a value less than the default value or to less than 60 seconds, the Agent Collector and Agent Store services on the PFM - Agent host or the Remote Monitor Collector and Remote Monitor Store services on the PFM - RM host might be overloaded, which might make it impossible to save the collected performance data.
    • When you modify the value for the Collection Offset, which is the offset value at which to start collecting records, choose a number with the overall load of the data collection in mind.
    • Even if the Collection Interval for the PI record type is set to a value that is not a multiple of 60 seconds, the performance data is summarized together with other record types at the same collection times. The seconds portion is discarded and the data is saved with only the minute values.
      Examples:
      When 30 seconds is specified for the Collection Interval:
      Collection time Time of the performance data to be saved
      12:01:00
      12:01:30
      12:02:00
      12:02:30
      12:01:00
      12:01:00
      12:02:00
      12:02:00
      When 90 seconds is specified for the Collection Interval:
      Collection time Time of the performance data to be saved
      12:00:00
      12:01:30
      12:03:00
      12:04:30
      12:00:00
      12:01:00
      12:03:00
      12:04:00
  8. Click the OK button.
    The settings that you have modified take effect.

Valid values or default values vary with each record. For details on valid values, ranges of values, or default values, see the chapter explaining records in each PFM - Agent or PFM - RM manual.

(2) Modifying the recording options for performance data by using commands

To modify the recording options for collecting performance data in the database, follow these general procedures:

  1. Use the jpcasrec output command to output the current definitions of the recording options to an XML file.
  2. Based on the resulting XML file, modify the definitions of the recording options.
  3. Use the jpcasrec update command to update the definitions of the recording options with the modified XML file.

Each procedure is described below.

(a) Using the jpcasrec output command to output the definitions of the recording options

On the host where PFM - Web Console is installed, execute the jpcasrec output command. The jpcasrec output command connects to the agent to obtain the definition information of the recording options for the Store database, and outputs this information to an XML file.

To output the definition of the recording options by using the jpcasrec output command:

  1. Log on to the host where PFM - Web Console is installed.
    You need to log on as a special user with special permissions, as shown below:
    • In Windows:
      Administrator permissions
    • In UNIX:
      root user permissions
  2. Execute the jpcmkkey command.
    Execute the command to create an authentication key file.
     
    jpcmkkey -user administrator
  3. Execute the jpcasrec output command.
    For example, if you want to output to the parameter file named asrec.xml the definition information of the recording options for the Store database of PFM - Agent with the service ID of TA1host1, use the following command:
     
    jpcasrec output -o asrec.xml TA1host1
     
    When the command is executed, the definition information of the recording options is output to the specified XML file.
    An example of this output is shown below.
     
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE pr-cli-parameters SYSTEM "asrec_params.dtd">
    <pr-cli-parameters ver="0100">
    <agent-store-db-record-definition>
    <service id="TA1host1">
    <record id="PD_DEV">
    <!-- Description : Devices Detail -->
    <log>Yes</log>
    <collection-interval>60</collection-interval>
    <collection-offset>0</collection-offset>
    <logif> </logif>
    </record>
    <record id="PD_GEND">
    <!-- Description : Generic Data Detail -->
    <log>No</log>
    <collection-interval>60</collection-interval>
    <collection-offset>0</collection-offset>
    <logif> </logif>
    </record>
        ...
        ...
        ...
    </service>
    </agent-store-db-record-definition>
    </pr-cli-parameters>

(b) Modify the definitions output by the jpcasrec output command

Modify the definitions of the recording options in the XML file generated by the jpcasrec output command. You can use any text editor or XML editor to edit the XML file.

The file format and the settings for each tag are described below. Edit the file if necessary.

Notes:
  • Increasing the number of records for which performance data is collected might affect your disk space or system performance. When you set up records to be collected, make sure you only set those items that are necessary for monitoring, always considering your requirements for performance data collection, such as the required free disk space and the record collection interval. For details on the required disk space, see the description of system estimates in an appendix of each PFM - Agent or PFM - RM manual.
  • For the Collection Interval for record collection, either use the default value or specify a value that is both 60 seconds or more and a factor of 3,600. When you have to specify a value that is greater than 3,600 seconds (one hour) for the Collection Interval, choose a number that is both a multiple of 3,600 and a factor of 86,400 (24 hours). Specifying a value less than the default value or 60 seconds might increase both the number of open files and the amount of memory use. That would prevent the Store database from functioning normally, causing the collected performance data to be lost without being saved.
    Valid values or default values vary with each record. For details on valid values, ranges of values, or default values, see the chapter explaining records in each PFM - Agent or PFM - RM manual.
  • When you modify the value for the Collection Offset, which is the offset value at which to start collecting records, choose a number while keeping in mind the overall load of the data collection.
 

The following table describes tags contained in a <logif> tag (for conditional expressions for recording in the database), and their settings.

Table 4-6 Conditional expression for recording in the database (<logif> tag)

Tag name Required Settings
<and> ... </and> No Used to combine two <expression> tags with AND operation when more than one <expression> tag (logical expressions) is used.
The two <expression> tags to be combined with AND operation are enclosed in an <and> tag pair.
Conditional expressions consist of binary operations that can be nested.
More than one <and> tag can be used when more than one <expression> tag is used.
<or> ... </or> No Used to combine two <expression> tags with OR operation when more than one <expression> tag (logical expressions) is used.
The two <expression> tags to be combined with OR operation are enclosed in an <and> tag pair.
Conditional expressions consist of binary operations that can be nested.
More than one <or> tag can be used when more than one <expression> tag is used.
<expression> ... </expression> No Specifies the condition for determining whether to record to the database.
Use the following format:
Specifies field condition "value"
(without any intervening spaces)

field:
Specifies the field to be compared.
For details on available fields, see the chapter explaining the records in each PFM - Agent or PFM - RM manual.

condition:
Use one of the operators shown below. Note that you must use &lt; for < and &gt; for > according to XML file conventions.
  • =
    The value of the field is equal to the value.
  • <
    The value of the field is less than the value.
  • <=
    The value of the field is equal to or less than the value.
  • >
    The value of the field is more than the value.
  • >=
    The value of the field is equal to or more than the value.
  • <>
    The value of the field is not equal to the value.

value
Specifies the criteria value to determine whether to record performance data. A valid value can be an integer value, a decimal, or characters of less than 2,049 bytes in length. A valid value varies with the specified field.

Legend:
No: Can be omitted
Note that the values for the omitted items are not updated.

(c) Using the jpcasrec update command to update the definitions of the recording options

On the host where PFM - Web Console is installed, execute the jpcasrec update command. The jpcasrec update command updates the definition information of the recording options for the Store database with the modified XML file.

To update the definition of the recording options by using the jpcasrec update command:

  1. Log on to the host where PFM - Web Console is installed.
    You need to log on as a special user with special permissions, as shown below:
    • In Windows:
      Administrator permissions
    • In UNIX:
      root user permissions
  2. Execute the jpcasrec update command.
    For example, when you want to update the definition of the recording options based on the contents of the file asrec.xml, use the following command:
     
    jpcasrec update asrec.xml

[Contents][Back][Next]


[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.