Description of problem:
Event flooding mechanism takes in account deleted events.
Starting with 3.5 release we have now an option to remove .Event/Alert from UI.
Once an Alert is removed, it is marked a "deleted" in the audit_log table and is not returned to the client in next retrivals
But, to implement the event flooding we use cache mechanism, the removed event is not removed from cache and therefor subsequent event during the event flooding period will not be shown to the user
Version-Release number of selected component (if applicable):
the problem is
Steps to Reproduce:
1.Do any action that generates an Event/Alert
2.Dismiss the generated Event/Alert from UI
3.Repeat step 1 withing the flood rate (defined in AuditLogType.java)
The second Event/Alert is suppressed
The dismissed event should be cleaned from cache and the second generated event from step 3) should be shown
Note that at the moment, only alerts can be dismissed.
Discussing it offline with Eli, we agreed that the current behavior is okay.
If, for example, we have an alert with flood rate of 30 seconds, and the flow is as follows:
1. Sec 1: Alert is triggered.
2. Sec 2: Alert is dismissed.
3. Sec 3: Alert is triggered again.
In "3" I wouldn't like to see the alert again, only if it is triggered again after 30 seconds.