Difference between revisions of "Action"
From Veloopti Help
(Created page with "Home > Administration > Action Administration > Action ---- == Overvi...") |
m |
||
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:Administration|Administration]] > [[:Category:Action Administration|Action Administration]] > [[Action|Action]] |
---- | ---- | ||
Revision as of 21:12, 21 March 2018
Home > Administration > Action Administration > Action
Contents
1 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.
2 Where events come from
Events come into Veloopti in the following ways:
- A policy on a Veloopti Agent detects a breach;
- A logfile policy detects a match;
- 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)
2.1 A policy on a Veloopti Agent detects a breach
Policies that run on a Veloopti Agent are able to send an event to Veloopti.
2.1.1 A logfile policy detects a match
2.1.2 A SNMP trap is received that matches
2.2 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
2.3 It is injected by the Veloopti agent Application Programming Interface (API)
The Veloopti agent is able to receive events through the inbound API method.