We want to age out our active events, I.e. close them, after a certain amount of time. This is mostly for stateless events like log messages or stateful events where a clearing event was missed for some reason. A simple time based automation rule will not work for us since we want to age different events for different amounts of time.
What we have done to solve the problem at our site is to add a custom message attribute to all events called AgeToClose that has the number of minutes an event should remain active. We have a script that runs every 5 minutes and closes events that have exceeded the age for that event by comparing against the time last received.
I would like to see a similar time to live field for events supported in the product. Alternatively allow time based automation rules to use a dynamic value that is set from a value in the message such as a custom message attribute.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.