Changes

Jump to: navigation, search

Policy:Command Execution Policy Page

4,005 bytes added, 18:06, 6 October 2020
Update details
=== 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.
=== 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 Also known as the current working directory, this is a location in your filesystem to start running the executable from. This can help the executable/script to find any configuration or other files that need to reside in the same file location as itself.
'''ARGUMENTS'''Enter your command line arguments hereThe parameters that are given after the name of the program are known as Command Line Arguments. Most people put them all in one line, but if you choose Veloopti provides a way of passing these to separate them, they will all be joined by a space character when the command runsexecutable/script.
::'''VALUE'''
::If there are more than one argument then they are joined together separated by a space character.
'''ENVIRONMENTAL VARIABLES'''NameVeloopti can add an environment variable that may be used by the program as as a part of the standard environment variable set. Once the program completed the environment variable ceases to be available.Value::'''NAME''' The name of the variable. This is the part that appears before the =::'''VALUE''' The value of the variable. This is the part that appears after the =
=== Conditions ===
Click on the 'add' button to the right to add a condition rule.The rules may be moved up and down by clicking on the rule changing its position. Click on the [Add] button to bring up the dialogue to add a condition to the policy. NOTE: Currently changing the position of order of the rules does not do anything as they are evaluated in order of severity. '''SEVERITY''' The severity that appears on the event that is raised by a threshold violation of the rule '''EVENT SHORT DESCRIPTION''' The short event description that appears on the event that is raised
EVENT SHORT DESCRIPTION::'''EVALUATE'''Either add a new row by clicking on the [Add] button or click on an existing row to enter the edit condition dialogue box.
EVALUATE:::'''Metric''' Select a metric upon which to perform a threshold evaluation. The options available are:::::Standard Out (text)::::Standard Out (Number)::::Error Out::::Exit Code::::Run Duration (seconds)::::Timed out
:::'''Operator'''Select an operator to perform against the Metricabove. Different options are available for different metrics.::::Equals::::Contains::::Doesn't Contain::::Does not equal::::Regular Expression Match::::Regular Expression Suppress Matches
Operator:::'''Value''' Enter a value to compare the metric against using the operator.
Value::'''BREACH AND RESET''':::'''Breach duration''' Enter the number of consecutive breaches that need to occur for an event to be raised
:::'''Reset Duration''' Enter the number of consecutive reset conditions, the number that the metric must be (usually) below, for the event severity to be set to Normal
::'''CREATE EVENT'''
EVENT SEVERITY::'''Event Severity''' The severity that appears on the event that is raised by a threshold violation of the rule
EVENT SHORT DESCRIPTION::'''Event Short Description''' The short event description that appears on the event that is raised
EVENT LONG DESCRIPTION::'''Event Long Description''' The long description that appears in the event
AUTO ACTION::'''Auto Action''' Select an action to run automatically when the condition of raising an event is met.
CLOSE EVENT ::'''Close event if auto action runs successfully''' IF AUTO ACTION RUNS SUCCESSFULLYthe auto actions runs successfully then the event will be closed.
::'''EVENT ACTIONS''' These actions are available to be run by any user that has the "Run Action from Event" permission. Unlike normal actions it does not rely on the Action "Level" permission of Operator, Power User or Administrator
::'''HELP TEXT''' This text appears on the event in the "Help" section.
::'''NOTIFICATION WORKFLOW''' Select the Notification Workflow that will be used for notifications and escalations.
=== Node Overrides ===
=== Schedule ===
'''TYPE'''::'''Basic''' Run the policy once per minute or once per hour::'''Time of day''' Run the policy once her day::'''Custom''' Run the policy on a complex schedule '''EVERY'''::'''Basic''' Select "Minutes" or "Hours" and type when on the minute or hour the policy should run.::'''Time of day''' Select hour and minute and the weekday(s) that the policy should run.::'''Custom''' Select "Minutes" or "Hours" and type when on the minute or hour the policy should run. Select the time range when the policy should be active: e.g. 9:00am - 5:00pm. Welect the weekday(s) that the policy should run on.
EVERY
=== Audit Log ===
'''DATE/TIME''' The date/time that the audit event occurred
'''USER''' The user that initiated the audited event
'''EVENT ACTION''' A description of what happened to the policy. Blue text indicates that it is a link to the described item.
'''ACTION''' If an action is available for the audit item it can be initiated here. For instance, roll back the policy to the previous version or restore the accidentally deleted policy.
=== View Data ===
'''SELECT YOUR NODE Only nodes with this policy currently ''' Use the drop down list box to select the node that it is deployed are able to . Graphs will then be selectedvisible in the below space that contains the metrics that have been collected over the last hour.    
[[fileNOTE:Node_server_up_iconOnly nodes with this policy currently deployed are able to be selected.png|20px]] The node is up
[[Category:Views]] [[Category:Policies]]

Navigation menu