We use the AlarmClientManager to update alarms. Specifically, we decided that certain alarms MUST not be removed from the new alarms stack. So we simply check each alarm that is not new, and if it matched some of the MIP items we decided the alarm must not be closable on, we update the alarm back to new.
This works great but when the alarm is about 12 hours old (reportedly) the alarm is no longer getting updated, even after we get the last 100’000 alarm lines. We do the update when we get an “ChangedAlarmIndication”. Is there any reason why old alarms would not updated anymore?
Thanks
Edit: Our client usually has a few tens of thousands of closed alarms at any given time.
It looks like in some circomstances the the ChangedAlarmIndication could “miss” an alarm. I don’t know why this would happen but we found a workaround. If we find that an active item should have an alarm in the new stack, we just check the new stack to see if it exists and if it does not, we look for an old alarm and update it.
When you change the status of the alarm, do you receive ChangedAlarmIndication? If you do not receive it you check the alarm by reading it again and can see that the alarm has changed even if you did not receive ChangedAlarmIndication? So the changed alarm is OK but the issue is missing the ChangedAlarmIndication message?
If this is not correct please try to explain in other words.
Hi Rie, sorry for the delay. Yes, this is accurate. We are working on a system that receives thousands of alarms a day. We have limited access to the system but indeed, it does seem that we would not get the ChangedAlarmIndication for alarms older than 12 hours, but only rarely. Our workaround like we said is to check all our active sensors on the map (custom MIP items) and if one of them is active and not showing in the new alarms list, we find and old alarm and change it’s status to new.