1,774
edits
Changes
m
According to ITIL events 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 defined as: initiated manually through the Veloopti GUI directly from a node; ''any detectable or discernible occurrence '' manually and automatically through an event that has significance for is associated with the management node. Actions come with three levels of the IT Infrastructure or the delivery of IT service permissions: Operator; Power User; ''and evaluation of the impact a deviation might cause to the services''Administrator.
# A policy on a Veloopti Agent detects a breach;'''Operator'''## A logfile policy detects : Operator level actions require the lowest level of permission to be run. Any user in an application that is a matchmember of the ''Operator'' role can run an operator level action.;'''Power User'''## A SNMP trap is received : 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 matches;# A metric threshold is violated;# An event storm rule detect a threshold violation member of the "Power User" role can run Power User and generates an eventOperator level actions.; ''and'Administrator'''# It : 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 injected by a member of the Veloopti agent Application Programming Interface (API)"Administrators" role can run Administrator, Power User and Operator level actions.
=== A metric threshold is violated ===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:ActionActions]]
no edit summary
== Overview ==
== Where events come from Permissions ==Events come into Veloopti There are three levels of permissions with running an action. Each permission is associated with a different [[role|role]] that is increment in the following ways:capability.
=== A policy on a Veloopti Agent detects a breach =Where actions can be run ==Policies that Actions can be run in two different locations: on a Veloopti Agent are able to send servers; ''and'' through an event to Veloopti.
==== 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>