Table of Contents
Advertisement
Required Member
description
severity
Workflows executing as alert actions may use the audit function to generate audit log entries.
It is recommended that any relevant debugging information be generated to the audit log via the
audit function. For example, here is a workflow that executes failover if in the clustered state --
but audits any failure to reboot:
EXAMPLE 27
Workflow Auditing Failure to Reboot
For example, here is a workflow that executes failover if in the clustered state -- but audits any
failure to reboot:
var workflow = {
name: 'Failover',
description: 'Fail the node over to its clustered peer',
alert: true,
setid: true,
execute: function (params) {
/*
* To failover, we first confirm that clustering is configured
* and that we are in the clustered state. We then reboot,
* which will force our peer to takeover. Note that we're
* being very conservative by only rebooting if in the
* AKCS_CLUSTERED state: there are other states in which it
* may well be valid to failback (e.g., we are in AKCS_OWNER,
* and our peer is AKCS_STRIPPED), but those states may also
* indicate aberrent operation, and we therefore refuse to
* failback. (Even in an active/passive clustered config, a
* FAILBACK should always be performed to transition the
* cluster peers from OWNER/STRIPPED to CLUSTERED/CLUSTERED.)
*/
var uuid = params.uuid;
var clustered = 'AKCS_CLUSTERED';
audit('attempting failover in response to alert ' + uuid);
try {
} catch (err) {
}
Type
String
String
run('configuration cluster');
audit('could not get clustered state; aborting');
return;
Using Workflows for Alert Actions
Description
A human-readable string describing
the alert.
The severity of the event that
precipitated the alert.
Maintenance Workflows
599
Advertisement
Table of Contents
