Hitachi

JP1 Version 12 JP1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference


4.1.2 Setting up monitoring targets in the Agents tree

To set up a monitoring targets in the Agents tree:

  1. Create an application.

  2. Bind an alarm table to the monitoring agent.

To collect operation status information on a per-process or per-service basis, specify only a single process or service in the application when creating it. To collect operation status information on a per-application basis, specify multiple processes or services in the application when creating it.

The following subsections provide a detailed description of how to set up a monitoring target.

Organization of this subsection

(1) Creating an application

  1. From the browser of the monitoring console, log in to PFM - Web Console.

    The Main window appears.

  2. In the navigation frame of the Main window, click Agents.

    The Agents tree window appears.

  3. In the Agents tree of the navigation frame, select a remote agent (device-ID<product-name>).

    A check mark is displayed for the selected remote agent.

  4. In the method frame, select the Process Monitoring Settings method.

    The Process Monitoring Settings window appears.

    [Figure]

  5. To create a new application, click the Create button. To modify an existing application, from Application Definitions, select the application definition you want to modify, and then click the Edit button.

    You cannot select a group of application definitions.

    The Process Monitoring Settings > Create a New Application Definition window or the Process Monitoring Settings > Edit an Application Definition window appears.

    [Figure]

  6. To create a new application, specify an application definition name in Application definition name.

    Application definition names and the character strings that can be specified must obey the following rules:

    • The user specifies a desired application definition name. The specified application definition name is stored in the Application Name fields of the PD_APP2, PD_APPC, and PD_APPD records, and is used as the identifier for identifying a specific application. Therefore, specify a unique name for the application definition name.

    • You can specify from 1 to 63 bytes of single-byte alphanumeric characters and symbols, excluding the following:

      Tab (\t) \ : ; , * ? " ' <> |

    • You can specify a maximum of 64 applications.

  7. If you are operating in a virtual system, specify a virtual environment identifier in Virtual environment ID.

    If you are operating in a virtual system, enter an identifier for identifying a specific virtual environment. By specifying an identifier, you can limit the monitoring targets to processes in a specific environment.

    You can specify from 1 to 63 bytes of single-byte alphanumeric characters and symbols, excluding the tab character (\t). The identifier you specify is compared to the value of the Virtual Env ID field of the PD_APS record.

    Note:

    Make sure that the character string you enter in Virtual environment ID matches what is entered in the Virtual Env ID field of the PD_APS record.

    Any character in the information to be acquired that is not in the ASCII character set range of 0x20 to 0x7E will be converted to a hash mark (#: 0x23) before it is stored in the Virtual Env ID field of the PD_APS record. Note that multi-byte characters are processed in single-byte units during conversion. For example, the multi-byte (full-width) letter [Figure] is converted as follows:

    Information to be acquired

    Information after conversion

    Character encoding

    Binary

    Binary

    Character string

    Shift-JIS

    8260

    2360

    #`

    EUC

    A3C1

    2323

    ##

    UTF-8

    EFBCA1

    232323

    ###

  8. Specify detailed information for the application.

    The following table shows the detailed information that you can specify in the Process Monitoring Settings > Create a New Application Definition window or the Process Monitoring Settings > Edit an Application Definition window.

    Table 4‒1: Detailed application information that can be specified

    Setting

    Description

    Field name in the corresponding record

    Name#1

    Enter a condition for identifying a specific monitoring target.

    You can specify a maximum of 4,096 bytes of single-byte alphanumeric characters and symbols, excluding the tab character (\t).

    Monitoring Condition field of the PD_APPD record

    Label

    Specify a label for identifying a specific monitoring condition.

    You can specify a maximum of 31 bytes of single-byte alphanumeric characters and symbols, excluding the tab character (\t).

    The default is MonitoringXX#2.

    If you do not enter any value, the default MonitoringXX#2 is set.

    Specify a unique name for the monitoring label.

    Monitoring Label field of the PD_APPC and PD_APPD records

    Type

    Select Program, Command Line, Service, or No selection.

    • Program

      The specified value is evaluated using the value of the Program Name field of the PD_APS record.

    • Command Line

      The specified value is evaluated using the value of the Command Line field of the PD_APS record.

    • Service

      The specified value is evaluated using the value of the Service Name field of the PD_ASVC record.

    • No selection

      No evaluation.

    Monitoring Field field of the PD_APPD record

    Minimum#3

    Enter the lower threshold value for the number of applications to be monitored.

    You can specify a value from 0 to 65535. The default is 0.

    Monitoring Min field of the PD_APPD record

    Maximum

    Enter the upper threshold value for the number of applications to be monitored.

    You can specify a value from 0 to 65535. However, you must specify a value that is greater than or equal to the value specified for Minimum. The default is 0.

    Monitoring Max field of the PD_APPD record

    #1

    • You can use the wildcard characters * and ? when specifying a name.

      An asterisk (*) represents zero or more instances of any character, and a question mark (?) represents any single character.

      If the monitoring target process' command line itself contains characters such as an asterisk (*) or a question mark (?), you cannot specify a monitoring condition based on complete matching.

      For example, suppose that the three processes listed below exist. If you enter /bin/sample "*" as the monitoring condition, the * in the monitoring condition is treated as a wildcard, and as a result all three processes are considered to match the monitoring condition.

      /bin/sample "*"

      /bin/sample "abc"

      /bin/sample "def"

    • Note the following if you specify a Name of 128 bytes or more as a monitoring condition when setting up collection of process operation status information: The Monitoring Condition field of the PD_APPD record will display only the first 127 bytes of the specified monitoring condition. However, monitoring will occur using the complete specified monitoring condition.

    • When the OS of the monitored host is Windows, the monitoring condition specified for Name is not case-sensitive when used to identify monitoring targets in the default setting. When the OS of the monitored host is UNIX, on the other hand, the monitoring condition specified in Name is case-sensitive when used to identify monitoring targets in the default setting. For details about how to specify whether the monitoring condition will be case-sensitive when identifying monitoring targets, see 4.1.12 Specifying whether process or service names to be used as monitoring targets will be case-sensitive.

    • When the OS of the monitored host is Windows, if you select Program for Type, specify the Windows program extension (such as .exe) for Name.

    • Make sure that the character string you enter in Name matches what is entered in the Program Name field of the PD_APS record, the Command Line field of the PD_APS record, and the Service Name field of the PD_ASVC record.

      Any character in the information to be acquired that is not in the ASCII character set range of 0x20 to 0x7E will be converted to a hash mark (#: 0x23) before it is stored in the Program Name field of the PD_APS record, the Command Line field of the PD_APS record, and the Service Name field of the PD_ASVC record. Note that multi-byte characters are processed in single-byte units during conversion. For example, the multi-byte (full-width) letter [Figure] is converted as follows:

      Information to be acquired

      Information after conversion

      Character encoding

      Binary

      Binary

      Character string

      Shift-JIS

      8260

      2360

      #`

      EUC

      A3C1

      2323

      ##

      UTF-8

      EFBCA1

      232323

      ###

    #2

    A value from 01 to 15 is set for XX. A numeric value corresponding to the Monitoring Number field of the PD_APPC and PD_APPD records is set.

    #3

    To monitor a process that generates child processes, specify an appropriate numeric value by referring to 10.2.4 Alarms related to process monitoring are not reported as intended.

    Note

    From the Input support > Agent pull-down menu, select a remote agent for a monitored host and click the Add button. The Process Monitoring Settings > Create a New Application Definition > Add from monitoring-targets window# or the Process Monitoring Settings > Edit an Application Definition > Add from monitoring-target window# appears. You can then select a process and set up its properties.

    #

    For monitoring-targets, Running Process, Running Command Lines, or Services is displayed depending on what is specified for Type in the Process Monitoring Settings > Create a New Application Definition window or the Process Monitoring Settings > Edit an Application Definition window.

    If you selected Program for Type in these windows, Running Processes is displayed. If you selected Command Line, Running Command Lines is displayed. If you selected Service, Services is displayed. By default, Running Processes is displayed.

  9. Click the OK button.

    The settings you specified take effect.

Shown below is the procedure for setting up properties from the Process Monitoring Settings > Create a New Application Definition > Add from monitoring-target window# or the Process Monitoring Settings > Edit an Application Definition > Add from monitoring-target window# in steps 8 and beyond under (1) Creating an application.

#

For the monitoring target type, Running Processes, Running Command Lines, or Services is displayed depending on what is specified for Type in the Process Monitoring Settings > Create a New Application Definition window or the Process Monitoring Settings > Edit an Application Definition window.

If you selected Program for Type in these windows, Running Processes is displayed. If you selected Command Line, Running Command Lines is displayed. If you selected Service, Services is displayed. By default, Running Processes is displayed.

  1. Execute steps 1 through 7 in (1) Creating an application.

  2. From Input support > Agent pull-down menu, select a remote agent for the monitored host and click the Add button.

    The Process Monitoring Settings > Create a New Application Definition > Add from monitoring-target window or the Process Monitoring Settings > Edit an Application Definition > Add from monitoring-target window appears.

    [Figure]

  3. From the pull-down menu on the left side of the Display button, select a monitoring target type (Running Processes, Running Command Lines, or Services) and click the Display button.

    A process list is displayed at the bottom of the Process Monitoring Settings > Create a New Application Definition > Add from monitoring-target window or the Process Monitoring Settings > Edit an Application Definition > Add from monitoring-target window.

    In the process list, by specifying a keyword in Filter and clicking the Search button, you can display only those processes that include the keyword in their process names. Clicking the Clear button will take you back to the original process list.

  4. From the process list, select the process you want to monitor and click the OK button.

    The Process Monitoring Settings > Create a New Application Definition > Add from monitoring-target window or the Process Monitoring Settings > Edit an Application Definition > Add from monitoring-target window closes, and the display will return to the Process Monitoring Settings > Create a New Application Definition window or the Process Monitoring Settings > Edit an Application Definition window.

  5. Modify the necessary items in the displayed window.

    For details about the settings, see Table 4-1 Detailed application information that can be specified.

  6. Click the OK button.

    The new settings take effect.

(2) Binding an alarm table to the monitoring agent

Bind an alarm table for monitoring the operation status information to the monitoring agent. The alarm for monitoring the operation status information is called the Application Status alarm. Edit it as needed. For details about this alarm, see Application Status in 6. Monitoring Template. If you monitor a process that generates child processes, specify an alarm-reporting method by referring to 10.2.4 Alarms related to process monitoring are not reported as intended.

You can use one of the following two methods to bind an alarm table:

To bind the alarm of PFM RM Platform Template Alarms [APP] 09.10:

  1. From the browser of the monitoring console, log in to PFM - Web Console.

    The Main window appears.

  2. In the navigation frame of the Main window, click Agents.

    The Agents tree window appears.

  3. In the Agents tree of the navigation frame, select a remote agent (device-ID<product-name>).

    A check mark is displayed for the selected remote agent.

  4. In the method frame, select the Process Monitoring Settings method.

    The Process Monitoring Settings window appears.

  5. Click the Start button for Process monitoring alarm settings.

    The alarm table is bound to the monitoring agent.

To bind a user-created alarm table:

  1. From the browser of the monitoring console, log in to PFM - Web Console.

    The Main window appears.

  2. In the navigation frame of the Main window, click Agents.

    The Agents tree window appears.

  3. In the Agents tree of the navigation frame, select a remote agent (device-ID<product-name>).

    A check mark is displayed for the selected remote agent.

  4. In the method frame, select Bind Alarm Table.

    The Bind Alarm Table [Select Alarm Table] window appears.

  5. Select an alarm table displayed under the RM Platform folder and click the OK button.

    The alarm table is bound to the monitoring agent.

If you want to monitor the status of a specific process only, you can create an alarm based on one of the following conditional expressions for monitoring.

Table 4‒2: Conditional expression for monitoring a specific process only

Item

Conditional expression

Record

Application Process Count (PD_APPC)

Field

Application Name

Monitoring Label

Monitoring Status

Abnormal and warning conditions#1

Application Name = Name#2

AND Monitoring Label = Label#2

AND Monitoring Status = ABNORMAL

#1

For the abnormal and warning conditions, specify the same condition.

#2

Specify the application name to be monitored and a monitoring label.