Planning and configuring for measuring application availability

In addition to using the Application Availability Analysis Tool, you can also configure Application Monitoring to monitor each application controller’s status. You can define either a Process Application Monitor or a Custom Application Monitor.

If you configure Application Monitoring solely for the purpose of checking on uptime status and do not want the Application Monitoring feature to automatically restart or move applications, you should set the Action on Application Failure parameter to just Notify and set the Restart Count to zero. (The default is three.)

Ensure that there is adequate space for the clavan.log file on the file system on which it is being written. Disk storage usage is a function of node and application stability (not availability), that is, of the number (not duration) of node or application failures in a given time period. Roughly speaking, the application availability analysis tool will use 150 bytes of disk storage per outage. For example, on a node that fails once per week and has one application running on it, where that application never fails on its own, this feature uses about 150 bytes of disk storage usage per week.

Whenever verification runs, it determines whether there is enough space for the log on all nodes in the cluster.