Using sample scripts for monitoring

PATROL for Scripting enables you to use custom scripts to monitor your environment, and BMC provides some basic scripts to help you get started with the monitoring. You can create realistic and customizable scripts through an external scripting tool, and then configure them from a local or a remote computer and start the monitoring. For details about how to configure scripts, see Configuring-LINUX-UNIX-shell-script-monitor-type and Configuring-OS-command-line-execution-monitor-type.

This topic provides descriptions of the scripts that are provided by BMC and instructions for managing these scripts. For instructions about defining the script output, see Defining-the-script-output.

Note

When executing scripts, the KM requires the same user privileges as a real user would. For example: if you would normally require administrator-level privileges to access the monitored application, the KM requires the same level of privileges to run a script on that application.

The following topics are presented:

Related topics

Configuring-after-installation

Defining-the-script-output

File-based-configuration

Distributing-script-files-to-remote-computer

Using Sample scripts

Part 3 of this four-part video series introduces you to the sample scripts that are provided with the KM and the common use cases that they support. To view Part 2 in this series, see https://youtu.be/pur74iytl7U

icon-play.png https://youtu.be/8UlHY-dpGgg

 

Provided scripts

The following scripts are provided and cannot be deleted or replaced without administrator permissions:

To view the list of available scripts

Note

Script attributes of scripts provided by BMC do not support non-English characters.

  1. Navigate to $PATROL_HOME\..\TRO\Conf\Scripts\Samples.
  2. To modify the list, click the relevant column heading to sort the list based on a specific column. 
    To sort in reverse order, click the column heading again.

To add custom scripts

  • You can use scripts located from on your remote or local device. 
  • If the script does not exist on the remote device and is located on your local monitoring system, the script will be automatically copied to the Scripts folder. (%PATROL_HOME%/TRO/Conf/Scripts/DeviceName or %PATROL_HOME%/TRO/Conf/Scripts)

To delete scripts from the list

Note

You cannot delete default scripts that are delivered with PATROL for Script KM. 

  1. Navigate to $PATROL_HOME\..\TRO\Conf\Scripts\Samples. 
  2. Select one or multiple scripts to delete and click the Delete button. 
  3. Click Yes in the confirmation message.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*