Policy:Command Execution Policy Page
1 Overview
The Command Execution Policy Page is used to create and edit the Command Execution policy. This policy can then be linked to a Policy Group for deployment onto a managed node.
3 Tabs
3.1 Overview
NAME The title of the policy that can be used to tell the policy apart from others
DESCRIPTION Describes the policy and explains what it does
TYPE Command Execution
NODE OVERRIDES CONDITIONS Enabling this slider makes the Node Overrides tab visible.
3.2 Attributes
EXECUTABLE The full path (including the binary) of the executable to run. Don't include arguments here, there is a separate field for that below
INITIAL DIRECTORY Otherwise known as the current working directory, this is a location in your filesystem to start running the executable from.
ARGUMENTS Enter your command line arguments here. Most people put them all in one line, but if you choose to separate them, they will all be joined by a space character when the command runs.
ENVIRONMENTAL VARIABLES
Name
Value
3.3 Conditions
Click on the 'add' button to the right to add a condition rule SEVERITY
EVENT SHORT DESCRIPTION
EVALUATE
Metric
Operator
Value
CREATE EVENT
EVENT SEVERITY
EVENT SHORT DESCRIPTION
EVENT LONG DESCRIPTION
AUTO ACTION
CLOSE EVENT IF AUTO ACTION RUNS SUCCESSFULLY
EVENT ACTIONS
HELP TEXT
NOTIFICATION WORKFLOW
3.4 Node Overrides
One policy can run on multiple nodes using the same conditions to create events. Individual nodes may require different threshold values in these conditions for effective monitoring. This is known as a "Node override condition".
This is currently not enabled.
3.5 Schedule
TYPE
EVERY
3.6 Audit Log
DATE/TIME
USER
EVENT
ACTION
3.7 View Data
SELECT YOUR NODE
Only nodes with this policy currently deployed are able to be selected.
The node is up