MENU
An administrator has been tasked with creating an alert in VMware Cloud Foundation (VCF) Operations with the following settings:
Wait cycle: 2
Cancel cycle: 2
Assuming the alert is not resolved, how much time elapses by default between the symptom triggering and the alert automatically cancelling itself?
To calculate the elapsed time correctly, we must identify the specific start and end points defined in the VMware operations lifecycle.
Default Collection Interval: VCF Operations collects data every 5 minutes.
Symptom Triggering (The Start Point): A symptom does not 'trigger' the moment a threshold is breached. Instead, it triggers only after the Wait Cycle is completed. With a Wait Cycle of 2, the symptom triggers at the 10-minute mark ($2 times 5text{ minutes}$). This is the 'Triggering' event referred to in the question.
Alert Cancellation (The End Point): For an alert to cancel automatically, the condition must remain 'False' for the duration of the Cancel Cycle. With a Cancel Cycle of 2, this requires an additional 10 minutes ($2 times 5text{ minutes}$) after the condition has cleared.
The Timeline Breakdown:
T+0 to T+10: Wait Cycles are occurring (Alert is not yet triggered).
T+10: Symptom Triggers (Event A).
T+10 to T+20: Cancel Cycles are occurring (Assuming the condition became false immediately at T+10).
T+20: Alert Automatically Cancels (Event B).
The time elapsed between Event A (Trigger) and Event B (Cancel) is exactly 10 minutes.
VCF Operations (v9.x) Documentation: Understanding How Wait and Cancel Cycles Affect Alert Generation.
Currently there are no comments in this discussion, be the first to comment!