2.5

At the highest level, you configure parameters to enable aurora_mon to start, stop, and monitor applications.
You specify the start, stop, and monitor commands as shell scripts or operating system executable files that
aurora_mon can invoke. Application developers can implement these commands according to the needs of
their environment. Other parameters enable you to specify how often to monitor an application and what
action to take. See “aurora_mon Configuration Parameters,” on page 154 for a description of aurora_mon
configuration parameters.
aurora_mon Configuration Parameters
You use aurora_mon parameters to configure aurora_mon to start, stop, and monitor applications, and to
specify how often to monitor an application and what action to take. You specify configuration parameters as
key-value pairs.
Configuration Guidelines
Use caution when modifying parameters. Do not modify the name and desc parameters, and do not modify the
app_priority parameter as it represents start order dependencies between various applications. Take a
snapshot backup of the virtual machine before modifying parameters, in case you need to revert.
Parameters you might find it useful to modify include the following.
n
heartbeat_period
n
heartbeat_fail_action
n
heartbeat_ignore_fail_count
n
app_restart_retry_count
After you modify a parameter, you must stop and restart aurora_mon for your changes to take effect.
Table 13-2. Aurora_mon Parameters
Parameter Description
name (required) Name of the application. A short representative name that can contain the
following characters: a-z, A-Z 0-9, _(underscore),–(dash), and no whitespaces.
You use this name to invoke commands on aurora_mon for this application.
descr (required) A longer but concise description of the application. The description is displayed
in the CMS UI.
app_priority (optional, defaults to 0) A number from 0 to 99 that represents the global start/stop priority of the
application in relation to other applications being monitored by aurora_mon.
Applications are started and stopped in priority order (0 being the highest
priority, 99 being the lowest). An application with a lower priority is started
only after all applications with a higher priority have been started. Applications
are stopped in the reverse order. All lower priority applications are stopped
before an applications with a higher priority is stopped. If a priority is not
specified, it defaults to 0 (highest priority).
app_start_cmd (required) Command you use, such as any program, script, or executable file, to start the
application. The start command is successful if the command exits with a zero
exit code. If the command does not complete in 300 seconds it is forcibly
terminated.
Stdout/stderr can be captured by the aurora_mon daemon if required
(through –o and -e options of the aurora_mon daemon), otherwise it is
redirected to /dev/null). To run the command as a specified user, you must
have an su –c wrapper or have set the setuid bit of the application.
If you do not require a start command, you can use a command that exits with
a zero exit code, for example /bin/true. An example of this is where the
application is monitoring the amount of disk space on a mount point. There is
no application to start.
VMware vFabric Data Director Administrator and User Guide
154 VMware, Inc.