Script Monitoring templates help you create custom scripts to monitor custom parameters .
Follow the steps given below to add script templates
Example:
cscript ${FileName}.vbsNote that ${FileName} must be followed by script file extension. You may also pass arguments. Argument list may use variable ${DeviceName} which will be replaced with the monitored machine name in run time. Other supported variables are ${UserName} - WMI/CLI username, ${Password} - WMI/CLI password, ${SNMPRead}- SNMP read community string. For example, cscript ${FileName}.vbs ${DeviceName} ${UserName} ${Password} Script Output Format In order to store the result of the script in DB, the output must be in the format given below. Data: Instance1 value1 Instance2 value2 ... ... InstanceN valueN Exit code will be used to set the status of the script monitor. Exit code "0" for up , any other exit code for down. Only numeric values are allowed as statistical data. The instance name and value must be separated by a TAB space(t). Status checking scripts may NOT contain data part. If there is no message in output, a default message will be used for alarm message. |
You have successfully created a script monitoring template
Editing Script Templates
To Edit a script template
Importing/Exporting Script Templates
The import/export options allows you to share scripts that are created by you with OpManager Plus community and use the scripts shared by others. Use this form to share the script with OpManager Plus community.
Import scripts
The script has been successfully imported to OpManager Plus.
Export Scripts
Copying Scripts
OpManager Plus allows you to save a copy of the script, modify it and use it for other monitoring requirements.
Deleting Scripts
To delete a script, click on the the Delete icon corresponding the script template.