![]() ![]() ![]() |
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. |
![]() ![]() ![]() |