ManageEngine® Applications Manager


Script Monitors

<< Prev

Home

Next >>

Script Monitors

 

Applications Manager provides Script Monitoring functionality to automatically monitor the output of ad-hoc Windows/Linux/Solaris scripts that are used in-house.

 

Availability tab, gives the Availability history for the past 24 hours or 30 days. Performance tab gives the Health Status and events for the past 24 hours or 30 days. List view enables you to perform bulk admin configurations.

 

Overriding Availability and Response Time of the Script:


This option would be useful, if you want to override the response time measured for custom scripts using a defined value in the output file. Applications Manager looks for few reserved keywords in the output file, if it matches then it will replace the corresponding attribute.


For eg., if the script output is looking like this,

script_availability=1 (Allowed values are 0 or 1. "0" refers to success. "1" refers to failure.)
script_message=Server is not running.
script_responsetime=10


Then while parsing the output file, script_availability value will be taken and based on that the availability is calculated.The same is the case for response time.


Examples:


Sample Scalar Usecase


Let's assume you want to monitor a script < filesystem.sh> present under /home/test-solaris/ in test-solaris machine. The output from this script is dumped to output.txt file present under the same directory. The format of output.txt is as shown below

SystemTemperature=37
TimeSinceLastReboot=30
TopPaginApp=sendmail
IOReads=1050


Setting up Script Monitor:


The success message should be displayed. Click Monitor Details > Script Monitor and go to the create script, to view the details.


Sample Table Usecase


Let's assume you want to monitor a script <prustat.sh> present under /home/test-solaris/ in test-solaris machine. The output from this script is dumped to output.txt file present under the same directory. The format of output.txt is as shown below


"<--table prustat starts-->"
PID CPU Mem Disk Net COMM
7176 0.88 0.70 0.00 0.00 dtrace
7141 0.00 0.43 0.00 0.00 sshd
7144 0.11 0.24 0.00 0.00 sshd
3 0.34 0.00 0.00 0.00 fsflush
7153 0.03 0.19 0.00 0.00 bash
99 0.00 0.22 0.00 0.00 nscd
7146 0.00 0.19 0.00 0.00 bash
52 0.00 0.17 0.00 0.00 vxconfigd
7175 0.07 0.09 0.00 0.00 sh
98 0.00 0.16 0.00 0.00 kcfd
"<--table prustat ends-->"


Note the table headers <--table prustat starts-->. This is mandatory and should follow the same format as mentioned. Here "prustat" should be replaced by the Table Name explained below


Setting up Script Monitor


You can use script monitor to monitor the SNMP OIDs

 

Please look at the steps below for creating a script monitor,

Then use the default parameters for configuring the remaining attributes.

 

Note: See another simple example of forcing a key value pair into a output file, discussed in our forums.

See Also


Creating New Monitor - Script Monitors

 

 

<< Prev

Home

Next >>

Database Query Monitor

Windows Performance Counters