Actions field descriptions

There are many fields pertaining to actions in IBM® Sterling Control Center Monitor.

Field Name Description
Description Text describing the action. Optional.
Name The name of the action. An action is an activity that IBM Sterling Control Center Monitor performs when an event triggers a rule.
Alert Severity A number from 0-3 that indicates how severe or critical the alert is. Severity is indicated on the Queued or Completed Activity monitors, or the Handled or Active Alerts monitors, with a color-coded icon.

To choose a severity level, select one of the following:

0–In compliance (no alert icon generated). A severity level 0 alert is not an alert, but it causes the system to automatically handle any existing alerts that are related to the same SLC or linked rule instance.

1 – High-severity alert (red alert icon generated)

2 – Medium-severity alert (orange alert icon generated)

3 – Low-severity alert (yellow alert icon generated)

Send Email

You can add email addresses to an action in the form of an email list or lists. Below are the fields displayed after selecting Send email:

To: The email addresses of recipients to be notified when this action is triggered or click Import Addresses to import a list from local computer.

Subject: Text to be inserted in the email's subject line. If you specify a To: address, Subject is required.

Message: The text of the email. Optional.

Generate SNMP Trap Turn on this option to generate an SNMP trap to the host defined in the IBM Sterling Control Center Monitor SNMP Host settings. SNMP Host system settings must be configured to generate traps.
Execute operating system command Execute the specified executable command file on the computer where the IBM Sterling Control Center Monitor engine is installed, and pass an XML string of the event that triggered the rule to the command file (if no other parameters are passed to the command).

You can also pass parameters to the command. These parameters can use variables (such as &processName;) which are replaced by the event values. If you designate parameters to pass to the command, IBM Sterling Control Center Monitor does not automatically pass the entire XML string of the event to the command.

Click Insert variable to open Select a variable to insert.

Example: An action could specify an operating system command that references a user-created script which, if a Process fails, writes Process statistics data to a Help desk file.

You should thoroughly validate any user-created scripts before using them with IBM Sterling Control Center Monitor.

Run the Sterling Connect:Direct server command A command sent to the Sterling Connect:Direct® server for execution. You can type the entire command or select a command template. If you select a command template, IBM Sterling Control Center Monitor replaces any variables fields (fields beginning with “&” and ending with ";") with the actual values from the event record.

For example, selecting Delete Process Command from the Command Template displays the following command:

delete process pname=&processName; pnumber=&processId;

Note: It is not necessary to terminate server commands with an additional semicolon.

IBM Sterling Control Center Monitor replaces &processName; with the Process name and &processId; with the Process ID from the event.

The command must use valid Sterling Connect:Direct syntax.

Command template: A template that gives you suggestions on server command syntax, for use in creating alerts. You can make changes to a command after displaying the template.

For example, selecting Delete Process Command from the Command Template displays the following:
delete process pname=&processName; pnumber=&processId;

The server to run the command: The name of the server on which to run the server commands entered.

Permissions Fields under Permissions are described below:

Allowed to use this action: When selected, this option makes the action public and available for selection by all users. Once a public action is referenced by any other object, you cannot make it private by restricting visibility to specific roles/users.

Roles that can edit this action: When restricted roles are selected, this option allows only restricted users in the selected roles to view/select/edit the action.

Restricted roles with rights to modify this action. If no roles are selected, then only an unrestricted user (admin) can modify this action.