Difference between revisions of "Event"
m (→How events are created) |
m |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Welcome_to_Veloopti_help|Home]] > [[:Category:An Overview|An Overview]] > [[:Category:Concepts|Concepts]] > [[Event|Events]] | ||
| + | ---- | ||
| + | |||
== 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''. | 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''. | ||
| Line 29: | Line 31: | ||
=== An event storm rule detect a threshold violation and generates an event; === | === An event storm rule detect a threshold violation and generates an event; === | ||
| − | == | + | == Agent event processing == |
| + | The Veloopti agent will process events as they are received in a [https://en.wikipedia.org/wiki/FIFO_(computing_and_electronics) first in first out] basis. This means that the oldest events are processed first before newer ones. This is to help keep the storm detection and duplication occurrence in order. | ||
| − | + | The Veloopti agent is limited to sending one event per second to the Veloopti servers. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Event properties == | == Event properties == | ||
| − | + | [[Category:Concepts]] [[Category:Events]] | |
| − | |||
| − | [[Category:Events]] | ||
Latest revision as of 16:53, 13 December 2018
Home > An Overview > Concepts > Events
Contents
- 1 Overview
- 2 Where events come from
- 3 Agent event processing
- 4 Event properties
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.
2.4 An event storm rule detect a threshold violation and generates an event;
3 Agent event processing
The Veloopti agent will process events as they are received in a first in first out basis. This means that the oldest events are processed first before newer ones. This is to help keep the storm detection and duplication occurrence in order.
The Veloopti agent is limited to sending one event per second to the Veloopti servers.