Multi-host Availability Monitoring

Availability Monitoring can be configured to monitor the availability of defined entities across multiple servers (hosts). For example, server \HOST1 can be configured to monitor the application 'my_app' that is running on another server named \HOST2.

This is done by setting up the AVAILABILITY Configuration with a statement that includes the required server name, a mandatory separator (.) followed by the application name, such as.

...(<server-name>.<entity-name>)

Multi-host Availability allows application and entity configurations to be centrally defined and distributed. Additionally, resources from across the network can be logically grouped together and monitored from a single point.

A maximum of 200 of distinct nodes can be referenced in a single AVAILABILITY Configuration and no single node can be monitored for availability by more than 10 remote nodes. Please refer to the AVAILABILITY Configuration Syntax for details.

Example 1

The following configuration is installed on the machine \HOST1. The machine \HOST2 is where the application 'my_app' is installed and from where it is to be monitored by \HOST1.

SUBSYS AVAILABILITY
PROCEXE ADDEXE (\HOST2.my_app)

In the following diagram, you can see the effects of this configuration. An executable, running on \HOST2, has been defined as an entity on \HOST1.

Example 2

This example demonstrates adding remote components to a logical application group. Again, this AVAILABILITY Configuration is installed on machine \HOST1.

SUBSYS AVAILABILITY
PROCEXE ADDEXE (\HOST2.my_app)
APPLICATION ADDAPP (APPL1, \HOST2.my_app)

The effect of adding the second configuration line gives the following diagram.

APPL1 is a monitored entity configured on \HOST1. Part of the entity APPL1 is an application 'my_app' on \HOST2.