3.5.1 Matrix Server Administration Guide

Chapter 13: Configure Service Monitors 232

can create a custom Start or Stop script for the action and specify it on the

Scripts tab for the monitor.

The default order for starting is:

• Run the monitor’s starting activities (if any)

• Run the custom Start script (if any)

If you want to reverse this order, preface the Start script with the prefix

[pre] on the Scripts tab.

The default order for stopping is:

• Run the custom Stop script (if any)

• Run the monitor’s stopping activities (if any)

If you want to reverse this order, preface the Stop script with the prefix

[post] on the Scripts tab.

Event Severity

By default, Matrix Server treats the failure or timeout of a Start or Stop

script as a failure of the associated monitored service and may initiate

failover of the associated virtual hosts. Configuration errors can also

cause this behavior.

Such a failure or timeout creates an event associated with the monitor on

the server where the failure or timeout occurred. You can view these

events on the Management Console and clear them from the Console or

command line after you have fixed the problems that caused them.

You can configure the failover behavior with the Event Severity attribute.

There are two settings:

CONSIDER. This is the default value. Events are considered when Matrix

Server makes failover decisions.

IGNORE. Events are ignored and Start or Stop script failures will not

cause failover. This is useful when the action performed by the Start and

Stop scripts is not critical, but is important enough that you want to keep

a record of it.

To configure event severity from the command line, use this option: