Create Alarm History table using Postgres Triggers
Description
Sometimes, when debugging a correlation issue, it's useful to have the exact sequence of events that lead to a specific situation. But alarms as designed today doesn't keep track of history.
Minor
Sometimes, when debugging a correlation issue, it's useful to have the exact sequence of events that lead to a specific situation. But alarms as designed today doesn't keep track of history.
It can be done using PostgreSQL triggers as described here : http://www.postgresql.org/docs/8.1/static/plpgsql-trigger.html#PLPGSQL-TRIGGER-AUDIT-EXAMPLE
The operations (INSERT, UPDATE, DELETE) done in the alarms table will be automatically audited in a new "alarm_history" table.
What do you think ?