Hitachi

JP1 Version 12 for UNIX Systems JP1/Performance Management - Agent Option for Platform Description, User's Guide and Reference


7.3.4 Example of using an alarm when collecting information about the application operating status

This subsection provides an example of using an alarm with the function that collects information about the application operating status.

Organization of this subsection

(1) Monitoring the startup status of a specific process

The following explains settings for monitoring whether a specific process is running, from several monitoring targets.

For environments in which only one of the following processes is normally running, the following procedure sets an abnormal alarm to be reported when multiple processes (two or more) are started or stopped.

Table 7‒10: Example of specific process start

Process name

Command line

GyoumuProcess

GyoumuProcess -a 1

  1. Set the instance name for ADD AN APPLICATION MONITORING SETTING in the ADDITION OR DELETION A SETTING tree as follows:

    GyoumuProcess Monitor

  2. Set the GyoumuProcess Monitor property generated in the Application monitoring setting tree as follows:

    Process01 Kind: Select Execute.
    Process01 Name: Enter GyoumuProcess. (Enter the process name)
    Process01 Range: Specify 1-1.

    As a result of the above settings, when the process is running, the values of the Process01 Count, Process01 Status, and Application Status fields in the PD_APP record are displayed as follows in the report.

    Table 7‒11: Results for the values of each field in the PD_APP record

    Field name

    Value

    Process01 Count

    1#1

    Process01 Status

    NORMAL#2

    Application Status

    NORMAL#2

    #1

    This indicates the number of corresponding processes running.

    #2

    This indicates that there is no issue.

  3. Specify alarm settings as follows:

    Record: Select Application Summary (PD_APP).
    Monitored field: Select Application Name.
    Condition: Select =.
    Abnormal value: Enter GyoumuProcess Monitor.
    Warning value: Enter GyoumuProcess Monitor.

    After specifying the above settings and clicking the Add button, specify these additional settings:

    Record: Select Application Summary (PD_APP).
    Monitored field: Select Application Status.
    Condition: Select <>.
    Abnormal value: Enter NORMAL.
    Warning value: Enter NORMAL.

Alarm conditions are evaluated using AND. To monitor only the results for Application Status without specifying an instance, specify only Application Status, <>, and NORMAL.

(2) Monitoring the startup status of a process containing arguments

The following explains settings for monitoring whether a process containing arguments is running.

The following procedure sets an abnormal alarm to be reported when the following process containing arguments stops.

Table 7‒12: Example of starting the process with arguments

Process name

Command line

GyoumuProcess

GyoumuProcess -a 1

  1. Set the instance name for ADD AN APPLICATION MONITORING SETTING in the ADDITION OR DELETION A SETTING tree as follows:

    GyoumuProcess Monitor

  2. Set the GyoumuProcess Monitor property generated in the Application monitoring setting tree as follows:

    Process01 Kind: Select Command Line.
    Process01 Name: Enter GyoumuProcess. (Enter the command line)
    Process01 Range: Enter 1-1.

    As a result of the above settings, when the process is running, the values of the Process01 Count, Process01 Status, and Application Status fields in the PD_APP record are displayed as follows in the report.

    Table 7‒13: Results for the values of each field in the PD_APP record

    Field name

    Value

    Process01 Count

    1#1

    Process01 Status

    NORMAL#2

    Application Status

    NORMAL#2

    #1

    This indicates the number of corresponding processes running.

    #2

    This indicates that there is no issue.

  3. Specify alarm settings as follows:

    Record: Select Application Summary (PD_APP).
    Monitored field: Select Application Name.
    Condition: Select =.
    Abnormal value: Enter GyoumuProcess Monitor (the instance name set in step 1).
    Warning value: Enter GyoumuProcess Monitor (the instance name set in step 1).

    After specifying the above settings and clicking the Add button, specify these additional settings:

    Record: Select Application Summary (PD_APP).
    Monitored field: Select Application Status.
    Condition: Select <>.
    Abnormal value: Enter NORMAL.
    Warning value: Enter NORMAL.

Alarm conditions are evaluated using AND. To monitor only the results for Application Status without specifying an instance, specify only Application Status, <>, and NORMAL.

(3) Monitoring whether multiple processes are all running

The following explains settings for monitoring whether monitored processes are all running.

The following procedure sets an abnormal alarm to be reported when at least one of the following five processes has stopped, but not to be reported when they are all running.

Table 7‒14: Example of startup for five processes

Process name

Command line

GyoumuProcess1

GyoumuProcess1 -a 1

GyoumuProcess2

GyoumuProcess2 -a 2

GyoumuProcess3

GyoumuProcess3 -a 3

GyoumuProcess4

GyoumuProcess4 -a 4

GyoumuProcess5

GyoumuProcess5 -a 5

  1. Set the instance name for ADD AN APPLICATION MONITORING SETTING in the ADDITION OR DELETION A SETTING tree as follows:

    GyoumuProcess Monitor

  2. Set the GyoumuProcess Monitor property generated in the Application monitoring setting tree as follows:

    Process01 Kind: Select Execute.
    Process01 Name: Enter GyoumuProcess*.#
    Process01 Range: Enter 1-5.
    #

    The wildcard character * is used for the process number. The wildcard character ? can also be used, in place of a single character.

    As a result of the above settings, when the five processes are running, the values of the Process01 Count, Process01 Status, and Application Status fields in the PD_APP record are displayed as follows in the report.

    Table 7‒15: Results for the values of each field in the PD_APP record

    Field name

    Value

    Process01 Count

    5#1

    Process01 Status

    NORMAL#2

    Application Status

    NORMAL#2

    #1

    This indicates the number of corresponding processes running.

    #2

    This indicates that there is no issue.

  3. Specify alarm settings as follows:

    Record: Select Application Summary (PD_APP).
    Monitored field: Select Process01 Count.
    Condition: Select <.
    Abnormal value: Enter 5.
    Warning value: Enter 5.

If all five processes are running, no alarm is reported. An alarm is reported when at least one process stops. Since alarm conditions are evaluated using AND, an abnormal alarm cannot be set to report for a running process count other than from 1 to 5.

(4) Monitoring whether a given process is running when there are multiple processes for which the first 31 bytes of the names are the same

The following explains settings for monitoring whether a given process is running when there are multiple processes for which the first 31 bytes of the names are the same.

The following procedure sets an abnormal alarm to be reported when either of the following two processes is running and multiple 1234567890123456789012345678901A processes are started or stopped.

Table 7‒16: Example of processes running for which the first 31 bytes of the names are the same

Process name

Command line

1234567890123460000000000000000A

1234567890123456789012345678901A -A

1234567890123456789012345678901B

1234567890123456789012345678901B -B

  1. Set the instance name for ADD AN APPLICATION MONITORING SETTING in the ADDITION OR DELETION A SETTING tree as follows:

    Long Name Process Monitor

  2. Set the Long Name Process Monitor property generated in the Application monitoring setting tree as follows:

    Process01 Kind: Select Execute.
    Process01 Name: Enter 1234567890123456789012345678901A.
    Process01 Range: Enter 1-1.

    As a result of the above settings, when only one 1234567890123456789012345678901A process is running, the values of the Process01 Count, Process01 Status, and Application Status fields in the PD_APP record are displayed as follows in the report.

    Table 7‒17: Results for the values of each field in the PD_APP record

    Field name

    Value

    Process01 Count

    1#1

    Process01 Status

    NORMAL#2

    Application Status

    NORMAL#2

    #1

    This indicates the number of corresponding processes running.

    #2

    This indicates that there is no issue.

  3. Specify alarm settings as follows:

    Record: Select Application Summary (PD_APP).
    Monitored field: Select Application Name.
    Condition: Select =.
    Abnormal value: Enter Long Name Process Monitor (the instance name set in step 1).
    Warning value: Enter Long Name Process Monitor (the instance name set in step 1).

    After specifying the above settings and clicking the Add button, specify these additional settings:

    Record: Select Application Summary (PD_APP).
    Monitored field: Select Application Status.
    Condition: Select <>.
    Abnormal value: Enter NORMAL.
    Warning value: Enter NORMAL.

In addition to the above monitoring, to monitor the 1234567890123456789012345678901B process using a monitoring method other than what has already been used, use an instance name different than the one above, and add the instance name to the condition in the Application Name field of the alarm setting.

(5) Monitoring whether a process in the global zone environment is running when PFM - Agent for Platform is installed in a Solaris global zone environment

The following explains settings for monitoring whether a process is running in a monitored global zone.

When the following process is running in both of the global zone environment and a non-global zone environment, the following procedure sets an abnormal alarm to be reported when multiple processes are running or stopped in the global zone.

Table 7‒18: Example of the process running in the global zone environment

Process name

Command line

GyoumuProcess.exe

GyoumuProcess

  1. Set the following for ALL Zone Collection for Process in the Agent Configuration tree.

    Yes
  2. Set the instance name for ADD AN APPLICATION MONITORING SETTING in the ADDITION OR DELETION A SETTING tree. Then, specify as follows for ADD AN APPLICATION MONITORING SETTING FOR VIRTUAL ENVIRONMENT:

    ADD AN APPLICATION MONITORING SETTING:Global Zone Process Monitor
    ADD AN APPLICATION MONITORING SETTING FOR VIRTUAL ENVIRONMENT:0
  3. Click the OK button.

  4. Set the Global Zone Process Monitor, Virt ID = 0 property generated in the Application monitoring setting tree as follows:

    Process01 Kind: Select Execute.
    Process01 Name: Enter GyoumuProcess.
    Process01 Range: Enter 1-1.

    As a result of the above settings, when only one GyoumuProcess process is running, the values of the Process01 Count, Process01 Status, and Application Status fields in the PD_APP record are displayed as follows.

    Table 7‒19: Results for the values of each field in the PD_APP record

    Field name

    Value

    Process01 Count

    1#1

    Process01 Status

    NORMAL#2

    Application Status

    NORMAL#2

    #1

    This indicates the number of corresponding processes running.

    #2

    This indicates that there is no issue.

  5. In the navigation frame of the Main window, click the Alarms tab.

    The Alarm Tree window appears.

  6. Expand the contents of the UNIX directory to display the existing alarm tables.

  7. Select New Alarm Table in the method frame, and create an alarm table. Set the following basic information in the new alarm table:

    Product: Select UNIX(7.6).
    Alarm table name: Enter AlarmTable1.
    Alarm name: Enter GyoumuProcess Alarm.
  8. Click the Next button.

  9. Specify alarm settings as follows:

    Record: Select Application Summary (PD_APP).
    Monitored field: Select Application Name.
    Condition: Select =.
    Abnormal value: Enter Global Zone Process Monitor (the instance name set in step 2).
    Warning value: Enter Global Zone Process Monitor (the instance name set in step 2).

    After specifying the above settings and clicking the Add button, specify these additional settings:

    Record: Select Application Summary (PD_APP).
    Monitored field: Select Application Status.
    Condition: Select <>.
    Abnormal value: Enter NORMAL.
    Warning value: Enter NORMAL.