Forum Discussion

Issac's avatar
Issac
Contributor II
18 days ago
Solved

Event Policy expiry delay during outage

Hi All,

What happens when collectors has an communication issue with  central database for more than 2 hrs , because we have some event policy set to expire if the event didn't rigger for 60 mins . During this  network outage the existing alarms will be cleared if the collector doesn't send update about its polled devices?

 

  • In the described scenario the active event will expire.

    Active events are stored in the primary DB; if an active event does not get an occurrence count increase from another trigger of the alert matching that entity (ex. device) and that event policy, which cannot occur if the device that would trigger that alert resides on a Collector to which the DB cannot communicate and that event policy has an expiration, then expiration will occur as the timer is based on the last occurrence of that event.

2 Replies

  • In the described scenario the active event will expire.

    Active events are stored in the primary DB; if an active event does not get an occurrence count increase from another trigger of the alert matching that entity (ex. device) and that event policy, which cannot occur if the device that would trigger that alert resides on a Collector to which the DB cannot communicate and that event policy has an expiration, then expiration will occur as the timer is based on the last occurrence of that event.

    • Issac's avatar
      Issac
      Contributor II

      Yes expected reply , but here we some improvement during the network outages . Because again the existing alerts will clear during the outage and alerts will be re-created when connectivity is restored . If tickets are enabled then its a duplicated.