Difference between revisions of "Event"

Latest revision as of 16:53, 13 December 2018

Home > An Overview > Concepts > Events

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:

1. A policy on a Veloopti Agent detects a breach;
   1. A logfile policy detects a match;
   2. A SNMP trap is received that matches;
2. A metric threshold is violated;
3. An event storm rule detect a threshold violation and generates an event; and
4. 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.

4 Event properties