6.7.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
(2) Monitoring the startup status of a specific service
(3) Monitoring whether multiple processes are all running
(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

(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 on which only one of the following processes is normally running, set an abnormal alarm to report when multiple processes (two or more) are running, or have stopped.

Table 6‒11: Example of specific process start
Program name	Process name
`GyoumuProcess.exe`	`GyoumuProcess`

To monitor the startup status of a specific process:

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

GyoumuProcess Monitor

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

Process01 Kind: Select Command Line.
Process01 Name: Enter GyoumuProcess (do not specify the .exe extension).
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 6‒12: 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.

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

Perform the above settings and then click the Add button, and then perform these additional settings:

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

Conditional expressions in an alarm are evaluated using AND. To monitor only the results for Application Status without specifying an instance, specify only Application Status, <>, and NORMAL.

To Page Top

(2) Monitoring the startup status of a specific service

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

The following sets an abnormal alarm to be reported when the following service application stops.

Table 6‒13: Example of specific service startup
Display name	Service name
`Windows Audio`	`AudioSrv`

To monitor the startup status of a specific service:

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

AudioSrv Monitor

Set the AudioSrv Monitor property generated in the Application monitoring setting tree as follows:

Process01 Kind: Select Service Name.
Process01 Name: Enter AudioSrv (the service name).
Process01 Range: Enter 1-1.

As a result of the above settings, when the service 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 6‒14: 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.

Specify alarm settings as follows.

Record: Select Application Summary (PD_APP).
Monitored field: Select Application Name.
Condition: Select =.
Abnormal value: Enter AudioSrv Monitor (the instance name set in step 1).
Warning value: Enter AudioSrv 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.

Conditional expressions in an alarm are evaluated using AND. To monitor only the results for Application Status without specifying an instance, specify only Application Status, <>, and NORMAL.

To Page Top

(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 6‒15: Example of startup for five processes
Program name	Process name
`GyoumuProcess1.exe`	`GyoumuProcess1`
`GyoumuProcess2.exe`	`GyoumuProcess2`
`GyoumuProcess3.exe`	`GyoumuProcess3`
`GyoumuProcess4.exe`	`GyoumuProcess4`
`GyoumuProcess5.exe`	`GyoumuProcess5`

To monitor whether multiple processes are all running:

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

GyoumuProcess Monitor

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

Process01 Kind: Select Command Line.
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 6‒16: 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.

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. Because conditional expressions in an alarm are evaluated using AND, an abnormal alarm cannot be set to report for a running process count other than from 1 to 5.

To Page Top

(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 are running and multiple 1234567890123456789012345678901A processes are running or stopped.

Table 6‒17: Example of processes running for which the first 31 bytes of the names are the same
Program name	Process name
`1234567890123456789012345678901A.exe`	`1234567890123456789012345678901A`
`1234567890123456789012345678901B.exe`	`1234567890123456789012345678901B`

To monitor whether a given process is running:

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

Long Name Process Monitor

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

Process01 Kind: Select Command Line.
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 6‒18: 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.

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 another monitoring method than what has already been used, use an instance name different than that above, and add the instance name to the condition in the Application Name field of the alarm setting.

To Page Top