Author Topic: Event Processing - Variation on Delayed Action Example?  (Read 152 times)

Staj

  • Jr. Member
  • **
  • Posts: 59
    • View Profile
Event Processing - Variation on Delayed Action Example?
« on: July 27, 2020, 03:53:20 am »
We currently have a some EPP rules that are the same as the Delayed Action Example in the documentation but we wanted to do the same thing for the uptime alert as well. We want to cause a notification action to occur if a node goes back up after the downtime has been longer than N (the length of the downtime timer) but don't want to cause a notification action to occur if the node goes back up if the downtime has been shorter than N (the length of the downtime timer).

I'm assuming the best way to do this is to utilise the Persistent Storage functionality? Set a timestamp when it goes down and have another rule that deletes the stored value if it goes back up before N (through use of a filtering script) and another rule that executes a notification action if it goes back up after N (through use of a filtering script)?

Any advice on specifics would be helpful.
« Last Edit: July 27, 2020, 07:20:22 am by Staj »

Victor Kirhenshtein

  • Lead Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 7056
    • View Profile
Re: Event Processing - Variation on Delayed Action Example?
« Reply #1 on: July 29, 2020, 02:31:26 pm »
Yes, persistent storage (or custom attribute on a node) that holds timestamp of last SYS_NODE_DOWN would be best solution.

Best regards,
Victor