Alert Severity Update Behavior When Reopened by a New Event

Hasini Chukka
Tera Contributor
 

When an Alert is reopened due to a new event being received within the 4-hour window, and the new event has a different severity from the existing Alert, will the Alert's severity be updated to match the new event's severity? If yes, how does this update happen?

 
1 REPLY 1

HasanM
Kilo Sage

Hi @Hasini Chukka ,

Yes. If a new event with the same message key arrives while the alert is closed but still within the reopen window, the alert is reopened and its severity is updated to match the new event. The alert always reflects the severity of its most recent event. It doesn't keep the previous severity or escalate to the highest one seen.

How it happens:

  1. Event rules run first, so any severity transform is applied before matching.
  2. The event matches the closed alert by message key and reopens it.
  3. The alert is updated from the new event (severity, description, additional information, last event time) and the reopen count goes up.
  4. Alert Management rules then run against the updated alert.

A few exceptions:

  • A Clear event (severity 0) closes the alert and doesn't reopen it.
  • Outside the reopen window, a new alert is created instead.
  • An alert that repeatedly opens and closes may be flagged as flapping.
  • Custom business rules on em_alert can override this behaviour.

To verify, send a Critical event and let the alert close. Then send a Minor event with the same source, node, type and resource within the window. The alert should reopen as Minor, and the change will show in its Events related list.

Hope this helps. If it answers your question, please mark it as helpful.