Page History
...
- Part 1: Creating custom service monitors
- Part 2: Creating custom service monitors with retained data collection collection
- Part 3: Creating plugin service monitors
Uptime Infrastructure Monitor provides many built in service monitors that allow you to monitor and alert on a wide array of services and applications within your enterprise. However, the standard Uptime Infrastructure Monitor service monitors may not be adequate to monitor all of the systems, applications and proprietary devices in your environment. In some cases, you may want to capture metrics that are unique to your environment. To do this, you can define custom service monitors to monitor custom services and applications to provide the level of in depth performance monitoring that you require. Using custom service monitors, you can monitor and graph historical performance data from just about any device in your environment.
...
The Custom service monitor template has the following monitor specific settings available: Based on the settings used in the example
| Option Name | Description | Example |
|---|---|---|
| Script Name | The script name is the path to your monitoring station script, |
...
| this is the script that Uptime Infrastructure Monitor will execute when running this service monitor. Be sure to use the complete path wherever possible and that the path is to a locally mounted volume. For Windows script paths you must use UNIX style directory separators (/ instead of \) and also place double quotes around the entire script name | UNIX/Linux example: /usr/local/uptime/check_temp.sh Windows example: C:/my scripts/check_temp.bat | |
| Arguments | These are the arguments that you would like Uptime Infrastructure Monitor to pass into your monitoring station script. No arguments are required but please be aware that Uptime Infrastructure Monitor will automatically include the selected hostname as the first argument to your script. | temp 60 80 |
| Output Warning | This is the warning threshold used against the output returned from your monitoring station script. This is a textual comparison. You must select both a comparison method and a search string to enable the warning level threshold | Output contains: "warning" |
| Output Critical | This is the critical threshold used against the output returned from your monitoring station script. This is a textual comparison. You must select both a comparison method and a search string to enable the critical level threshold | Output contains: "critical" |
Based on the settings used in the example monitoring station script, configure the monitor with the following setting:
- Enter a name and description for the monitor.
...
- Select a host from the dropdown menu. Be sure to select the same host that your agent side script is on
...
- In the Script Name field, enter the path to the custom script on your monitoring station. On Windows systems be sure to use UNIX style / instead of \ and put quotation marks around your path. For example: "C:/my files/check_temp.bat"
...
- In the Arguments field, enter the arguments for the script. Uptime Infrastructure Monitor adds the agent name as the first argument automatically so do not include it.
...
- Select contains from the Warning dropdown and enter WARNING as the search text.
...
- Select contains from the Critical drop down and enter CRITICAL as the search text.
- Complete the remainder of the monitor template as you would for a normal service monitor.
Example monitor configuration
The image below illustrates a sample monitor configuration. This service monitor will indicate indicates a WARN or CRIT whenever the monitoring station custom script returns WARNING or CRITICAL in its output.
