-
Titel
Cannot specify my custom Script Action for a rule. -
Beschreibung
When building a Script Action for a rule, how to specify the script name?
The Help indicates, where to put the script, but the list of scripts does not show my custom groovy script.
How to enter my own script name or add something to this list?
Reference attached screenshot 'Script Action.bmp'. -
Ursache
The Help instructions are inaccurate in stating, that the rule runs the script from the /scripts directory.
-
Lösung
This now documented in the FoglightCreatingActions_Field.pdf
Import the script into the FMS using monitoring policy import as a persistable-script object, so it then becomes selectable from the Script Action list.
1) Create a text file containing the script replacing the YOUR_SCRIPT_NAME below with your desired script name and the contents of your script where designated.
The code below is for reference only, use the attached script to edit appropriately.
YOUR_SCRIPT_NAME</p></persistable-script></foglight-config></p><p><strong>YOUR SCRIPT HERE</strong></p><p>
<strong>YOUR_SCRIPT_NAME2) The saved text file can then be imported into the Foglight Management Server using util:configimport command. For example:
$FGLHOME/bin/fglcmd{.sh or .bat} -usr -pwd -cmd util:configimport -f /tmp/myscript.txt
STATUS: FGL-11165 was implemented in the Foglight Creating Actions Field guide available in 5.6.4
-
Anhänge
