Event

From Veloopti Help
Revision as of 21:23, 20 August 2017 by Nigel (talk | contribs) (How events are created)
Jump to: navigation, search

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 How events are created

When the condition to create an event has been met it is processed by Veloopti where it is processed to confirm that the event can be raised in your organisation.

IF event matches outage rule THEN
     IF outage rule = suppress THEN
          Suppress the event
          EXIT
      ELSE IF outage rule = auto close THEN
          Create the event and close it
          EXIT
      END IF
END IF
 
IF event matches one or more storm rules THEN
    Perform the storm rule(s)
END IF
 
IF event matches an existing event with a different severity THEN
    Change the existing events severity to match the new one
    Increment the existing events duplicate count by one
ELSE IF event matches an existing event with the same severity THEN
    Increment the existing events duplicate count by one
ELSE
    Create the event
    IF the event has a notification THEN
         Perform the notification
     END IF
 END IF

4 Event properties