Incident did not get created even though the Situation was created for Node Down

Products

• DX SaaS

Issue/Introduction

2 devices were down on 10th November, and we have the alarm and situation created in DX O2 but the incident did not create for them. Please can you let us know the reason why the incident was not created. 

Resolution

The policy is configured for stable  situations and age less then 30 mins. . In this case, the situation appears to have stabilized only after about 57 minutes, so it did not meet the policy criteria.

    
Additionally, based on the situation definition, the stable time is set to 15 minutes with an auto-extend of another 15 minutes. I can see that new alarms were still being added (for example, alarm <specific alarm id> was added 11 minutes later), along with a few others. Because of these incoming alarms, the stable time window kept extending, resulting in the situation stabilizing only after roughly an hour.

    
Due to this extended stabilization period, it did not match the policy to create the incident. You may need to review the notification policy and the custom situation definition.