1,774
edits
Changes
m
Events enter into your organisation though the following methods:# A policy running on a Veloopti agent 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''
Once === A policy on a Veloopti Agent detects a breach ===Policies that run on a Veloopti Agent are able to send an event to Veloopti. ==== A logfile policy detects a match ==== ==== A SNMP trap is received that matches ==== === 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; === == How events are created == When the condition to create an event has been forwarded to met it is processed by Veloopti where it is processed according to confirm that the following logicevent can be raised in your organisation.
no edit summary
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''.
== How Where events enter Veloopti come from ==Events come into Veloopti in the following ways:
# It is injected by the Veloopti agent Application Programming Interface (API)
IF event matches [[Outage|outage]] rule THEN