6.5 Developing Automation Scripts for Alarms

The Automation feature in Operations Center allows users to define actions that are triggered by activities or condition changes that occur in the network. The feature is explained in Defining and Managing Automation Events in the Operations Center 5.6 Server Configuration Guide. One of the automation actions is running a script.

For example, the following script instructs Operations Center to audit the actions performed against alarms.

/////////////////////////////////////////////////////////////  AuditActions.fs
writeln( "Auditing Actions Against Alarms..." );

//  Filename that the Actions should be logged too
var fpAudActionFile = "../logs/ActionAudit.log";

//  Variable to hold the auditing output
var str = "" + '\n';

//  Build the current date and time
var RightNow = new Date();
str += RightNow.getDate() + "‑";
str += RightNow.getDay() + "‑";
str += RightNow.getFullYear() + " ";
str += RightNow.getHours() + ":";
str += RightNow.getMinutes() + ":";
str += RightNow.getSeconds();

//  Tag the Action to a person
str += ' User "' + user + '" ran the command "' + command + '" against alarm:\n';

// Grab the top level alarm information
for( var i = 0; i < alarms.length; ++i )
{
  str += 'Alarm: ' + alarms[i].getID() + ', element: ' + alarms[i].getElement().getDName();

  // Grab the actual alarm... if you issued a "Delete" it might be gone already
  for( p in alarms[i].properties )
  {
    str += '\n\t' + p + " = " + alarms[i][p];
  }
}

//   Open the logging file
var writer = new java.io.PrintWriter( new java.io.FileOutputStream( fpAudActionFile, true ) );

//   Write the string we built to the file
writer.println( str );

//   Close the file
writer.close();

// EOF() AuditActions.fs

To implement this script:

The variables available during script execution depend on the event that triggered that script. Table 6-1 lists the global variables associated with alarm events.