Escalation policy is not being triggered when expected by the user.
User is concerned that an event raised in an underlying domain like Smarts IP or Smarts NPM is delayed in processing by SAM for about 60 seconds and then a further delay of 60 seconds in the escalation policy so the policy is not triggering within 120 seconds.
All supported releases of Smarts
The product is working as designed. The perceived delays are in fact related to the smoothing interval which has been set to greater than 60 seconds.
Decreasing the smoothing interval to under 60 seconds removed the delay in event processing in SAM and removing the 60 second delay configured in the escalation policy removed the delay in triggering.