I am running a 2 server redundant system with PMI, FSQL, and Reporting plug in installed on both. Yesterday in FSQL I ran the pre-installed Clean Alarmlog group. On a simular note, i also kicked over to the second server in FSQL (redundancy is configured between the two).
After these two events occured, it seemed as if I just totally stopped logging any alarms. I went into FSQL and looked at my alert settings on both machines. Neither one has alarmlog nor alarmstatus typed in for the tables, which i found to be very odd. I typed in the table names on both machines.
This morning when we looked at the alarm history, the same alarm was on the list multiple times. What would cause this???
I preformed a truncate statement on the alarmlog which effectively purged it. After I purged it, I still had about a dozen alert bits that should have generated alarms. Will I only get an alarm on a transition from false to true (assuming my bits all alarm on high state)???
We have had two new alarms since and they are working as expected. Any other insight anyone can offer into how the alarming mechanism works???