Difference between revisions of "Event"

From Veloopti Help
Jump to: navigation, search
m
m
 
(11 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''.
 +
 +
== 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)
 +
 +
=== 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 ====
  
−
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''.
+
==== 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.
  
−
== How events enter Veloopti ==
+
=== An event storm rule detect a threshold violation and generates an event; ===
  
−
The flow of an event into Veloopti is described as follows
+
== 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.
  
−
IF event matches [[Outage|outage]] rule THEN
+
The Veloopti agent is limited to sending one event per second to the Veloopti servers.
−
      IF outage rule = suppress THEN
 
−
          Suppress the event
 
−
          EXIT
 
−
      ELSE IF outage rule = auto close THEN
 
−
          Close the event
 
−
          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 severity to match the new one
 
−
    Increment the existing events [[Event_lifecycle#Previous_events_and_duplicates|duplicate count]] by one
 
−
ELSE IF event matches an existing event with the same severity THEN
 
−
    Increment the [[Event_lifecycle#Previous_events_and_duplicates|duplicate count]] by one
 
−
ELSE
 
−
    Create the event
 
−
    IF the event has a notification THEN
 
−
          Perform the notification
 
−
      END IF
 
−
  END IF
 
  
 +
== Event properties ==
  
−
[[Category:Events]]
+
[[Category:Concepts]] [[Category:Events]]

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

Retrieved from "http://help.veloopti.com.au/index.php?title=Event&oldid=4583"