Need an explanation of Duration as it pertains to an event definition

### Need an explanation of Duration as it pertains to an event definition

book

calendar_today

#### Products

SYSVIEW Performance Management NXBRIDGE - SYSVIEW/ENDEVOR

#### Issue/Introduction

If the SCHEDULE for a particular event type is set to a value such as 5 minutes and the Duration for an event definition rule type Upper, trigger level Status is set to a value such as 2, what is the behavior? This is the online help information: The duration, in minutes, used to determine if there has been a change in the metrics status. This is the number of intervals in minutes that are summarized or averaged to compute the current value. This is a little unclear and I am not finding any further explanation of Duration in docops that seems to apply, the only discussion is relating to a rule type Change. If it is a rule type Upper, then does the Schedule value for the event type determine the behavior? In other words, if we are monitoring MQ queue depth, does the event fire if the condition happens to exist when the sample is taken every five minutes whether it has been occurring for 1 second or 299 seconds? Please refer me to more complete documentation if there is any, thanks, or explain how the combination of rule type Upper, trigger level Status, Schedule and Duration interact.

Release:
Component: SYSVW

#### Resolution

example of using a DURATION of 5 with a queue depth VALUE of 3.

I.E. using a Duration of 5 and a Value of 3 on the threshold definition
The first check determines that the value is 3
The second check determines that the value is 2
The third check determines that the value is 3
The fourth check determines that the value is 2 The fifth check determines that the value is 10.
The total is 20 Divided by 5 the value is 4 So, the value of 4 is above the Value of 3 and it will pop.

In the next check the first value has rolled off so:
The first check (from before) determines that the value was 2
The second check (from before) determines that the value was 3
The third check (from before) determines that the value was 2
The fourth check (from before) determines that the value was 10
The new fifth check determines that the value is 0.
The new total is 17. Divided by 5 results in 3.4 The threshold STATUS does not change as it is still above 3.

So, the oldest value (based upon the duration of 5) continues to roll off being replaced by on the back end with the value of the newest check.

In the next check the values become: 3 2 10 0 0 15 / 5 = 3 (still equal to the value of 3 so no change)

In the final check the values change to: 2 10 0 0 0 12 / 5 = 2.4 So, the STATUS will change for the variable since it has dropped below the Limit of 3 so the threshold would change back to normal.