Changes

Jump to: navigation, search

Event

1,226 bytes removed, 22:58, 4 December 2017
m
How events are created
=== An event storm rule detect a threshold violation and generates an event; ===
 
== How events are created ==
 
Metrics are continually streamed in from the agent that reflects the current state of the performance of the server. The metrics 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|outage]] rule THEN
IF outage rule = suppress THEN
Suppress the event
EXIT
ELSE IF outage rule = auto close THEN
<b>Create the event</b> 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 [[Event_lifecycle#Previous_events_and_duplicates|duplicate count]] by one
ELSE IF event matches an existing event with the same severity THEN
Increment the existing events [[Event_lifecycle#Previous_events_and_duplicates|duplicate count]] by one
ELSE
<b>Create the event</b>
IF the event has a notification THEN
Perform the notification
END IF
END IF
== Event properties ==
[[Category:Event Administration]] [[Category:Events]]

Navigation menu