Changes

There are three levels of permissions in Actionswith running an action.;'''Operator''': Operator level actions require the lowest level of permissions to be run. Any user in an application that is a member of the ''Operator'' role can run an operator level action.;'''Power User''': Power User level actions require more permissions than Operator level and lower than Administrator level actions. Users that can run Power User level actions can also run Operator level actions. Any user in an application that is a member of the "Power User" role can run Power User and Operator level actions.;'''Administrator''': Administrator level actions require the highest level of permissions. Users that are able to run Administrator level actions can also run Power User and Operator actions. Any user in an application that is a member of the "Administrators" role can run Administrator, Power Users and Operator level actions.

Actions can be run directly on a server that has a Veloopti agent. When clicking To do this, click on the server name in either the main node page, or the node page in of an application; there . There is a side menu item named ''Actions '' where they can be run.

|The Audit This is the audit log for the action. It contains a list of the things that have been changed on the action over time.

The name of the policy is used to as a reference it from in different places in Veloopti. An action needs to have a unique name in the [[Application|Application]] that it is resides in.

The description is where you enter some text that describes what the action does. This description is used in other places like in policies.

There are three levels of actions in Veloopti: Operator; Power User and Administrator. Each action level is able to be run by users who are members of a role that have the appropriate permission assigned to itcertain roles.

|IDExecutable|A [[Glossary_of_acronyms#GFree text|GUID]] The name of the binary executable or script that distinguishes all of the messages. Primarily used to tell similar events apart.action runs

|SeverityInitial Directory|Standard categorisation based on the significance of an event:Free text*'''Information''' - |The event does not require any immediate action and does not represent an exception.*'''Warning''' - The event directory that the binary executable is generated when an [[Application|application]] is approaching a thresholdlocated in. Warnings are intended Use this if you want to notify you in order use relative paths for you to take either the necessary actions to prevent an exception occurring. *'''Exception''' - This mean that the [[Application|application]] is impacted and presents a failure, performance degradation Executable or loss any of functionality (web server down, database stopped responding, ''etc'')the Arguments.

|StatusDescription|The state Free text|A description of event being either open or closed.the argument that is there to help you remember what it is used for

|NodeArgument|Free text|The name of the [[Node|node]] where argument as it should appear on the command line. Generally it is the field proceeding the event was received"=" sign. ''i.e.'' '''path'''=c:\program files\

|First OccurredValue|Free text|The date/time value that the event was detected should be represented by the management applicationargument. {| class="wikitableGenerally it is the field that follows the " style="text-align: left;"|sign. ''i.e.'Type'''|path='''First occurredc:\program files\'''

|PolicyPrompt for value|Check box|The time that the Veloopti agent detected the event

|LogfileSurround with quotes|Check box|The date/time that appears in the logfile. If this does not exist then it is the date/time that the Veloopti agent performed the logfile scan.

|SNMP TrapAdd|Button|The date/time that appears in the SNMP trap

|APITimeout|Numeric > 0|The date/time amount of seconds that is sent through the API. If this does not exist then action can run for before it is the date/time that killed by the Veloopti agent received the API event.Agent

|}Name|Free text|The name of the environment variable that should be created before the action is started. This can be helpful for binaries/scripts that need environment variables set up before they can be run.

|ReceivedValue|The date/time Free text|This is the value that the event was received by the Veloopti [[Agent_controller|agent controller]]environment variable should be set to.

|Last OccurredAdd|This is Button|After the last time that an event was received that matched environment name and value has been set you use this add button to add it and move on to the event parameters. It next, if there is the latest "First Occurred" date of the last event that was receivedone.

|ITIL ComponentDelete|Button|The Delete button is located in the [[Glossary_of_acronymsGlossary_of_terms#IF|ITILfeedback]] component that section. It allows for you to delete the event relates to: Availability, Capacity, Performance or Securityaction.

|Custom event propertiesSave|Custom event properties appear at Button|The Delete button is located in the bottom of the standard event properties[[Glossary_of_terms#F|feedback]] section. These are properties It allows you to save any changes that are specific you may have made to the event. This can be things like: eventID for windows event logs; URL for URL monitor policy; or anything for an inbound API policyaction.

This tab contains the audit log for the eventAction. Anything that occurs in relation to the event Action occurs here.# The time the event Action was first openedcreated# Severity increases and decreasesAll of the times the action was edited# Notifications that were sent to users# Action results# The closure Any timethe action is run on a node or from an event