Creating a custom signature script
You can create a custom signature script for policy checks in InfoScale Operations Manager. When creating the script you can use any programming language. Also, the custom signature script can have any type of code.
You must ensure the following when you create the custom signature script:
-
Script must return 0 for success.
-
Script must return a value other than 0 for errors.
In case of error, the script must print as follows:
Related information
Table: Script output when an error occurs
| Item | Value |
|---|---|
| RESULT_RC | Any of the following exit codes\: |
| - 0 - Check passed. | |
| - 1 - Check fails with warning. | |
| - 2 - Check fails with error. | |
| - 100 - Not supported or cannot run check. | |
| RESULT_TXT | Displays the failure message. |
| RESULT_REMEDY | Displays the message that helps resolve the problem. |
The custom signature script must support the --what command line argument, which ensures the following output when you use the
custom signature script.pl --what command:
Table: Output of the command:custom signature script.pl --what
| Item | Value |
|---|---|
| CHECK_ID | Displays a unique value. This value can be a number or a string. |
| The CHECK_ID and the name of the script file need to be the same for the custom signature to work properly. | |
| Example: PC_VXVM_UNUSED_VOLUMES | |
| CHECK_NAME | Displays the name of the custom signature. |
| CHECK_DESCRIPTION | Displays the description for the signature. |
| CHECK_KEYWORDS | Displays the category to which the custom signature belongs. |
| Example: UTILIZATION,VXVM,PERFORMANCE,VCS |
Note: The custom signature must return the code 0 on successful installation on Management Server using thepcregutility. It must not give any other output.
More Information