I've been noticing that I'm missing a lot of alarm notifications. A little bit about my configuration:
- I have a 5-minute collection interval
- My raw data interval is 20 seconds
- Many of my alarm conditions (especially for faulty sensors or power fluctuations) occur when a get a brief low or high spike that triggers the alarm conditions.
Usually, the spikes occur within my 5-minute collection interval and the sensor returns to normal before the end of the interval. Consequently, the system clears the alarm before the collection interval ends and, therefore, I never receive the notification email. The only way I have discovered these alarms is because I have an alarm counter set on my dashboard. However, by the time I check the dashboard, it is too late to do anything about the issue that causes the alarm.
Perhaps this is by design? If so, is it possible to reconfigure my states and notifications so that notifications aren't dependent on the chosen collection interval? I suppose one option is to reduce my collection interval, but this isn't a good option because a) the minimum collection interval is 1 minute and I have 20 second data; and b) collection events tend to "freeze" the system until they complete. [BTW, I would like to reduce my collection interval so that my data is more "real time", but the system freezes become really distracting when viewing data in the interface.]
A couple better options come to mind:
- Provide a "latching" option. RTMC Pro has this option and I use it all the time. Latching means that the alarm remains active until it is manually acknowledged.
- Send alarm notifications as soon as they occur, regardless of the collection interval.
- Queue alarm notifications as soon as they occur and send the notifications at the end/start of the collection interval. This option isn't as good as the above option because there the notifications are delayed, but it is better than missing notifications entirely.