Use this page to configure one or more application monitors
for application controllers to use to monitor specific applications
and processes for applications in the resource group.
You can define an application monitor to detect the unexpected
termination of a process or to periodically poll the termination of
an application and take automatic action upon detection of a problem.
Additionally, you can specify scripts to use for notification, cleanup,
and restarting applications in the resource group upon detection of
an unexpected termination of a process or other application failures.
You can configure multiple application monitors and associate them
with one or more application controllers.
Fields
- Process type
- Select whether the process type you want to create is a Process
application monitor or a Custom application
monitor.
- Application monitor name
- Specify a unique name for the new application monitor. The name
you specify must consist of a minimum of one alphanumeric character
and a maximum of 64 alphanumeric characters. You can use alphabetic
characters of A - Z and a - z, numbers of 0 - 9, and the underscore
(_) character. A name cannot begin with a number and cannot be a PowerHA® reserved word.
- Process to monitor
- Specify the full path and file name of one or more processes to
use for checking application status. This option is available only
when you select Process Monitor as the Monitor
Type for the application monitor.
- Monitor script
- Specify the full path and file name of a method to use for checking
application status. This option is available only when you select Custom
Monitor as the Monitor Type for
the application monitor.
- Monitor mode
- Select the mode for monitoring the application:
- Startup Monitoring
- Select this mode to have the application monitor check that the
application controller has successfully started within the specified
stabilization interval. Select this mode if you are configuring an
application monitor for an application that you plan to include in
a parent resource group. This application monitor is in addition to
other application monitors that you might need for dependent resource
groups.
- Long-Running Monitoring
- Select this mode to have the application monitor check that the
application controller is running successfully. The application monitor
checks the application after the specified stabilization interval
has passed. This is the default mode.
- Both
- Select this mode to have the application monitor check that the
application controller has started successfully. The application monitor
then periodically monitors that the application controller is running
after the stabilization interval has passed.
- Action on application failure
- Select the type of action you want the new application monitor
to take after all attempts to restart the application controller have
reached the limit.
- Fallover
- Select this option to have the application monitor run the specified Notify script
and to take no further action.
- Notify
- Select this option to have the application monitor move the resource
group that contains the monitored application to another node in the
cluster.
- Notify script
- Specify the full path and file name of a user-defined method to
perform notification when a monitored application fails. This method
runs each time an application is restarted, fails completely, or falls
over to the next node in the cluster. You must specify this information
when you specify Notify as the action to take
when an application fails. It is preferred that you configure this
method.
Note: Notify scripts are run only on failure for long - running
monitors regardless of the Action on application failure option
that you selected.
- Cleanup script
- Specify the full path and file name of the script to run to stop
the application. The default script to use is the stop method defined
for the application controller when the application controller was
configured. If you have multiple application controllers, specify
the stop script that is used for the associated application controller
to which this application monitor applies. If you are configuring
an application monitor to be used only in the startup monitoring mode,
you do not need to specify a cleanup script. PowerHA SystemMirror will not use it.
- Restart script
- Specify the full path and file name of the script to run to start
the application. The default script to use is the start method that
was defined for the application controller when the application controller
was configured. If there are multiple application controllers, there
is no default script. If you are configuring an application monitor
to be used only in the startup monitoring mode, you do not need to
specify a restart script. PowerHA SystemMirror
will not use it.
Actions
- Add Another
- Click Add Another to add another set of
fields so that you can create and configure another application monitor
for your custom resource group. All fields for the added application
monitor are inactive until you select the first field, typically the
name field. All fields for the added application monitor are inactive
until you specify information for the Application Monitor
Name field. Then all fields are enabled.
- Remove
- Click Remove to remove the content from
the first set of application monitor fields and disable all fields
after the Application Monitor Name field. If
applied to an added application monitor on the page, this action removes
the entire set of fields for the added monitor.