Adding an OS Command

You can specify an Operating System command or script that will be called in Notification Rules. The OS Command is run on the machine where the Management Service is running, and is run as the user who started the Management Service. The OS command (or script) must exist and be placed on each Management Service host machine that connects to the Management Repository. The OS Command must use an absolute pathname and the pathname has to be the exact same on each Management Service machine. The OS Command must be executable by the user who started the Management Service. This must be done before setting up and Notification Rules.

Note: OS commands must be configured by a privileged user before users can choose to select one or more of these OS command methods while creating/editing a notification rule.

The following information is required for each OS command notification method:

Name
Description
OS Command

You must enter the full path of the OS command/script in the OS command field (e.g. /u1/bin/myscript.sh). Command line parameters can be included after the full path (Example: /u1/bin/myscript.sh arg1 arg2). If you are using a UNIX script then you must include a header in the script (Example: #!/bin/sh)

An example of the required information is shown below.

Name ISIS Ticketing

Description Notification method to log an ISIS ticket for a severity occurrence

OS Command /private/mozart/bin/logTicket.sh

Note: There can be more than one OS Command configured per system.

For information about the MGMT_SEVERITY table, the environment variables set by the notification system, the severity types that relate to a target's availability, and how metric severity information is passed to the OS command, see About Passing Metric Severity Information.

Adding an OS Command

Related Topics