Hi Dojo,
I have a correlation rule that is triggered by the Service protocol whenever an alarm reaches a Critical or Major severity.
The correlation rule is configured to trigger on single events. However, I noticed that if a service is already in a Critical state and the service is restarted, the correlation rule is triggered again when the service returns to the Active state, even though the same Critical alarm is still present.
Is there a way to prevent the correlation rule from triggering again in this scenario?
Regards,
Hi Dario,
I was waiting to see if anyone else had a better suggestion, but it does not seem like anyone is responding to this question.
One possible way to avoid triggering the correlation rule again (or at least prevent executing the same action twice) would be to add a script that checks whether the element was restarted or whether there is already an active alarm that was previously created. If either condition is true, then the logic executed by the correlation rule could simply be skipped.
I’m not entirely sure whether this would fit your setup, but it might be a possible approach worth considering.
Kind regards,