Hitachi

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


4.1.6 Setting up a monitoring target in Services

To set up a monitoring target in Services:

  1. Create an application.

  2. Specify application properties (the name of the application to be monitored and a threshold value).

  3. Bind an alarm table to the monitoring agent.#

#

To bind an alarm table, use the Agents tree window of PFM - Web Console.

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

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, select the Services tab.

    The Services window appears.

  3. From the navigation frame, expand the hierarchy under the Machines folder.

    A folder with the name of the host on which Performance Management service is installed appears. When you expand the folder with the host name, the services installed on this host appear.

    The name of each service is displayed as a service ID. For details about service IDs, see C. List of Identifiers and the section that describes service-naming rules in the appendix of the JP1/Performance Management Planning and Configuration Guide.

    The service ID format differs depending on whether the product name display function is enabled. For details about this function, see the chapter that describes the functions of Performance Management in the JP1/Performance Management Planning and Configuration Guide.

  4. Expand the hierarchy under the monitoring agent host's folder and select a remote agent (device-ID<product-name>).

    A check mark is displayed for the selected remote agent.

  5. In the method frame, select the Properties method.

    The Service Properties window appears.

  6. Under the Remote Monitor Configuration tree, select the ADDITION OR DELETION A SETTING tree.

  7. On the bottom of the information frame, specify an application name in ADD AN APPLICATION MONITORING SETTING.

    The following rules apply to application names and the character string that can be specified:

    • The user specifies a desired application name. The specified application 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 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.

  8. Click the OK button.

    In the Service Properties window, under the Remote Monitor Configuration - Application monitoring setting tree, an application name tree is generated.

(2) Specifying application properties

  1. After you have performed the procedure in (1) Creating an application, open the Service Properties window again and select an application name generated under the Remote Monitor Configuration - Application monitoring setting tree.

    A window for entering property information appears at the bottom of the information frame.

  2. Specify properties.

    Specify a virtual environment identifier, a monitoring label, a monitoring field, a monitoring condition, and the minimum and maximum threshold values for the number of monitoring targets. You can specify multiple pieces of process information. The following table lists and describes the properties.

    Table 4‒3: Application property settings

    Item

    Property name

    Description

    Field name in the corresponding record

    Virtual environment identifier

    Virtual Environment ID#1

    If you are operating on a virtual system, enter an ID for identifying a specific virtual environment. By specifying this item, you can restrict the operation 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.

    Virtual Env ID field of the PD_APP2 record

    Monitoring label

    MonitoringXX 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

    Monitoring field

    MonitoringXX Field

    Select Program Name, Command Line, Service Name, or None.

    • Program Name

      The specified value is compared to the value of the Program Name field of the PD_APS record.

    • Command Line

      The specified value is compare to the value of the Command Line field of the PD_APS record.

    • Service Name

      The specified value is compared to the value of the Service Name field of the PD_ASVC record.

    • None

      No evaluation.

    The default is None.

    Monitoring Field field of the PD_APPD record

    Monitoring condition#3

    MonitoringXX Condition

    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).

    The default is one space.

    Monitoring Condition field of the PD_APPD record

    Minimum and maximum threshold values for the number of monitoring targets#4

    MonitoringXX Range

    Enter the lower and upper threshold values for the number of monitoring targets by connecting the two values with a hyphen (-), such as 1-2.

    You can specify from 0 to 65535.

    The default is 0-0.

    • Minimum value

      Monitoring Min field of the PD_APPD record

    • Maximum value

      Monitoring Max field of the PD_APPD record

    #1

    For the Virtual Environment ID property, you must check the Virtual Env ID field of the PD_APS record and enter the same character string as that specified in this field.

    #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

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

      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 128 bytes or more characters for the monitoring condition (MonitoringXX 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 is not case-sensitive when identifying monitoring targets in the default setting. In contrast, when the OS of the monitored host is UNIX, the monitoring condition is case-sensitive when identifying 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 specify Program Name for the MonitoringXX Field property, specify the Windows program extension (such as .exe) for the MonitoringXX Condition property.

    • Make sure that the character string you enter in the MonitoringXX Condition property 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, the Service Name field of the PD_ASVC record, and 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

      ###

    #4

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

  3. Click the OK button.

    The settings you specified take effect.

(3) 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.

To bind an 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.

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

Table 4‒4: 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.