Action page

From Veloopti Help
Revision as of 22:13, 19 March 2018 by Nigel (talk | contribs)
Jump to: navigation, search

Home > Using > Standard User Interface > Pages > Action page



1 Overview

An action is a command that can be remotely run on a node that has a Veloopti agent installed on it. Actions come in three levels of permissions: Operator; Power User; and Administrator.

1.1 Permissions

There are three levels of permissions with 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 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.

1.2 Where actions can be run

Actions can be run in two different locations: on servers and through an event.

1.2.1 Actions on servers

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

1.2.2 Actions on events

Actions can also be run from an Event. <more here>

2 Action tabs

Action tabs
Tab Description
Overview This tab contains the main overview of the Action
Attributes The attributes of the action are the commands and parameters that are run on the node.
History This shows the results of an action that has been run while the event was open.
Audit log This is the audit log for the action. It contains a list of the things that have been changed on the action over time.

2.1 Overview

Name

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

Description

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

Type

The action type is currently limited to a command type action. More of these will be released in the future.

Level

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 certain roles.


2.2 Attributes

Event properties
Property Property type Description
Executable Free text The name of the binary executable or script that the action runs
Initial Directory Free text The directory that the binary executable is located in. Use this if you want to use relative paths for either the Executable or any of the Arguments.
Description Free text A description of the argument that is there to help you remember what it is used for
Argument Free text The name of the argument as it should appear on the command line. Generally it is the field proceeding the "=" sign. i.e. path=c:\program files\
Value Free text The value that should be represented by the argument. Generally it is the field that follows the "=" sign. i.e. path=c:\program files\
Prompt for value Check box
Surround with quotes Check box
Add Button
Timeout Numeric > 0 The amount of seconds that the action can run for before it is killed by the Veloopti 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.
Value Free text This is the value that the environment variable should be set to.
Add Button After the environment name and value has been set you use this add button to add it and move on to the next, if there is one.
Delete Button The Delete button is located in the feedback section. It allows for you to delete the action.
Save Button The Delete button is located in the feedback section. It allows you to save any changes that you may have made to the action.

2.3 History

Any actions that have been run that are associated with this event appear here.

2.4 Audit Log

This tab contains the audit log for the Action. Anything that occurs in relation to the Action occurs here.

  1. The time the Action was created
  2. All of the times the action was edited
  3. Any time the action is run on a node or from an event