recurring ems event message till it's solved #3771
Description
Hi Team, currently EMS events are collected and written once at their appearence into the database by Harvest. This can create exactly one ticket in a customer infrastructure like service now. If an ONTAP issue takes longer to solve (4,8,16,24,48,72 hours) Harvest will not create another database entry in the current state (promtheus / influxdb). I have a customer, where it's needed to have a recurring new message in it's database to create another ticket for their operational team. So if an issue is not solved after 8 hours that a new database entry got created by Harvest and their ticketing system creates a new ticket.
E. g. database entry of a vserver which is stopped. It's only one entry independ of the downtime duration.
If Harvest could create further entries based on duration that would be create.
It would be awesome, if it's possible to add a parameter in the ems.yaml, which can influence the frequency an ems event gets written new into the database. So that customer can modify it how often they want an alert - like default: just once and for those who want recurring alerts with durations like 4,8,16,24,48,72 hours.
https://github.com/NetApp/harvest/blob/main/conf/ems/9.6.0/ems.yaml
E. g.:
