breb
Contributor
Contributor

Wait cycle in alert or symptom definition

Hello,

if I make symptom definition p.e.
warning: latency > 20ms
critical:  latency >40ms

Wait cycle:1, Cancel cycle: 1

alert definiton
"latency too high" (using 2 symptoms above)
Wait cycle:2, Cancel cycle: 1

I'm expecting to see an alert after 10min if latency above 20ms, but is triggering after 5 min?
I have put also vm in maintenace mode after changing wait cycle to 2, to refesh alert definitions.

Question is:
Shouldn't I expect the same result i.e. triggering after 10 minutes in both cases:

1. symptom: Wait cycle:1, Cancel cycle: 1
    Alert: Wait cycle:2, Cancel cycle: 1

2. Symptom: Wait cycle:2, Cancel cycle: 1
    Alert: Wait cycle:1, Cancel cycle: 1



 

0 Kudos
2 Replies
KabirAli82
Expert
Expert

That should not happen;

https://docs.vmware.com/en/vRealize-Operations-Manager/8.2/com.vmware.vcom.core.doc/GUID-251F60F2-52...

 

The wait cycle setting helps you adjust for sensitivity in your environment. The wait cycle for the alert definition goes into effect after the wait cycle for the symptom definition results in a triggered symptom. In most alert definitions you configure the sensitivity at the symptom level and configure the wait cycle of alert definition to 1. This configuration ensures that the alert is immediately generated after all of the symptoms are triggered at the desired symptom sensitivity level.


Was I helpful? Give a kudo for appreciation!
Braindumping @ http://kablog.nl/
Tweeting @ https://twitter.com/_Kabir_Ali_
0 Kudos
breb
Contributor
Contributor

Hello Kabir

can you please answer me this only with yes or no? I think it is yes but can be wrong

Shouldn't I expect the same result i.e. alert triggering after 10 minutes in both cases:

1. symptom: Wait cycle:1, Cancel cycle: 1
    Alert: Wait cycle:2, Cancel cycle: 1

2. Symptom: Wait cycle:2, Cancel cycle: 1
    Alert: Wait cycle:1, Cancel cycle: 1




0 Kudos