I have a database that records all the alarms in my Ignition gateway, which I’m planning to use in a different piece of software. I noticed today that every alarm entry is recorded twice, once with an eventtype of 1 and then again with 0. Since my alarms are all Boolean triggers, it makes sense that this is an “alarm active” and “alarm inactive” flag.
I want to know if there’s a way to suppress the second (“inactive”) entry. It’s unneeded in my application, and it’s just doubling the size of my database for no reason. Obviously, I know I can query the database to filter these results out; I’d just rather the storage space weren’t taken up at all, if that’s possible.
Is there an alarm setting that I missed that keeps from logging this second entry?
Looking at how this field is used by the alarm system of Ignition, I doubt you can turn this off. This field is partially used in determining how long a configured alarm is in a specified state (Active, Inactive, Acknowledged), as well as providing a timestamp of when the state changed. This is one of the integral parts of the Alarm system of Ignition so disabling it would likely cripple said system.