Difference between revisions of "Action"

From Veloopti Help
Jump to: navigation, search
m
m
Line 3: Line 3:
  
 
== 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 command 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 ==
+
== Permissions ==
−
Events come into Veloopti in the following ways:
+
There are three levels of permissions with running an action. Each permission is associated with a different [[role|role]] that is increment in capability.
  
−
# A policy on a Veloopti Agent detects a breach;
+
;'''Operator'''
−
## A logfile policy detects a match;
+
: 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.
−
## A SNMP trap is received that matches;
+
;'''Power User'''
−
# A metric threshold is violated;
+
: Power User level actions require more 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.
−
# An event storm rule detect a threshold violation and generates an event; ''and''
+
;'''Administrator'''
−
# It is injected by the Veloopti agent Application Programming Interface (API)
+
: 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 policy on a Veloopti Agent detects a breach ===
+
== Where actions can be run ==
−
Policies that run on a Veloopti Agent are able to send an event to Veloopti.
+
Actions can be run in two different locations: on servers; ''and'' through an event.
  
−
==== A logfile policy detects a match ====
+
=== Actions on servers ===
 +
Actions can be run directly on a server that has a Veloopti agent installed. To do this, click on the server name in either the main node page, or the node page of an application. From the server there is a side menu item named ''Actions'' where actions can be run.
  
−
==== A SNMP trap is received that matches ====
+
=== Actions on events ===
 +
Actions can also be run from an Event. <more here>
  
−
=== A metric threshold is violated ===
+
[[Category:Actions]]
−
Metrics that are sent by the Veloopti Agent are able to have a threshold set on it through the [[Threshold_engine|Threshold engine]]
 
−
 
 
−
=== It is injected by the Veloopti agent Application Programming Interface (API) ===
 
−
 
 
−
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]]
 

Revision as of 22:53, 21 March 2018

Home > Administration > Action Administration > Action

1 Overview

An action is a command 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.

2 Permissions

There are three levels of permissions with running an action. Each permission is associated with a different role that is increment in capability.

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 more 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

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

3.1 Actions on servers

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

3.2 Actions on events

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

Retrieved from "http://help.veloopti.com.au/index.php?title=Action&oldid=4335"