Difference between revisions of "Action"

From Veloopti Help
Jump to: navigation, search
(Created page with "Home > Administration > Action Administration > Action ---- == Overvi...")
 
m
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
[[Welcome_to_Veloopti_help|Home]] > [[:Category:Administration|Administration]] > [[:Category:Action Administration|Action Administration]] > [[Action|Action]]
+
[[Welcome_to_Veloopti_help|Home]] > [[:Category:An Overview|An Overview]] > [[:Category:Concepts|Concepts]] > [[Action|Actions]]
 
----
 
----
  
 
== Overview ==
 
== Overview ==
−
According to ITIL events can can be defined as: ''any detectable or discernible occurrence that has significance for the management of the IT Infrastructure or the delivery of IT service and evaluation of the impact a deviation might cause to the services''.
+
An action is a executable binary or script that can be run locally on a node that has a Veloopti agent installed on it. An action can be initiated manually through the Veloopti GUI directly from a node; ''or'' manually and automatically through an event that is associated with the node. Actions come with three levels of permissions: Operator; Power User; ''and'' Administrator.
  
−
== Where events come from ==
+
Actions are associated with a node using [[Group|groups]]
−
Events come into Veloopti in the following ways:
 
  
−
# A policy on a Veloopti Agent detects a breach;
+
== Permissions ==
−
## A logfile policy detects a match;
+
There are three levels of permissions with running an action. Each action is associated with a different [[permission|permission]] that are members of [[roles|roles]].
−
## A SNMP trap is received that matches;
 
−
# A metric threshold is violated;
 
−
# An event storm rule detect a threshold violation and generates an event; ''and''
 
−
# It is injected by the Veloopti agent Application Programming Interface (API)
 
  
−
=== A policy on a Veloopti Agent detects a breach ===
+
;'''Operator'''
−
Policies that run on a Veloopti Agent are able to send an event to Veloopti.
+
: Operator level actions require the lowest level of permission 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 higher permissions than Operator level actions. Roles 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. Roles that can 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 User and Operator level actions.
  
−
==== A logfile policy detects a match ====
+
== Where actions can be run ==
 +
In Veloopti actions can be run in two different places: on a node; ''and'' through an event.
  
−
==== A SNMP trap is received that matches ====
+
=== Actions on nodes ===
 +
Actions can be run directly on a node that has a Veloopti agent installed. To do this, click on the node name in either the main node page, or on the node page of an application to view the node details. On the left side menu click on the item named ''Actions'' where actions can be manually run.
  
−
=== A metric threshold is violated ===
+
=== Actions on events ===
−
Metrics that are sent by the Veloopti Agent are able to have a threshold set on it through the [[Threshold_engine|Threshold engine]]
+
Actions can be run from an Event after it has been received.  To do this click on the event and navigate to the "Action" tab.  From here any actions configured to be able to run from the event can be run. Actions can only be run on open events.
 +
:[[file:Warning.png|20px]]             '''Note: Unlike actions run on nodes, actions run from an event do not have levels of permissions associated with them. This means anyone who can see the event can run the action.'''
  
−
=== It is injected by the Veloopti agent Application Programming Interface (API) ===
+
[[Category:Concepts]] [[Category:Actions]]
−
 
 
−
The Veloopti agent is able to receive events through the inbound API method.
 
−
 
 
−
=== An event storm rule detect a threshold violation and generates an event; ===
 
−
 
 
−
== Event properties ==
 
−
 
 
−
[[Category:Action Administration]] [[Category:Action]]
 

Latest revision as of 18:02, 11 May 2020

Home > An Overview > Concepts > Actions

1 Overview

An action is a executable binary or script that can be run locally on a node that has a Veloopti agent installed on it. An action can be initiated manually through the Veloopti GUI directly from a node; or manually and automatically through an event that is associated with the node. Actions come with three levels of permissions: Operator; Power User; and Administrator.

Actions are associated with a node using groups

2 Permissions

There are three levels of permissions with running an action. Each action is associated with a different permission that are members of roles.

Operator
Operator level actions require the lowest level of permission 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 higher permissions than Operator level actions. Roles 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. Roles that can 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 User and Operator level actions.

3 Where actions can be run

In Veloopti actions can be run in two different places: on a node; and through an event.

3.1 Actions on nodes

Actions can be run directly on a node that has a Veloopti agent installed. To do this, click on the node name in either the main node page, or on the node page of an application to view the node details. On the left side menu click on the item named Actions where actions can be manually run.

3.2 Actions on events

Actions can be run from an Event after it has been received. To do this click on the event and navigate to the "Action" tab. From here any actions configured to be able to run from the event can be run. Actions can only be run on open events.

Warning.png             Note: Unlike actions run on nodes, actions run from an event do not have levels of permissions associated with them. This means anyone who can see the event can run the action.
Retrieved from "http://help.veloopti.com.au/index.php?title=Action&oldid=5575"