Without any indication it was going to happen, NPM generated 13,903 alerts when I enabled the 'Download Config successful' alert. If anyone has a good reason the default behavior should create new alerts for all historical conditions that meet the alerts criteria, I'd love to hear it. I can come up with some good reasons for this to be an option when enabling an alert, but to just do it by default... I'm at a loss there. That was probably the first and last time I'll ever enable an OOB alert 'cause who knows which one might have a hard-coded date/time of 2014 selected as part of the trigger action.
Please have two options when enabling the alert:
1) Match all historical data (or a time frame)
2) Only send alerts for conditions occurring after the alert is enabled
Or, like you do with custom alerts, tell the user 13,903 alerts will be triggered if the alert is enabled and give an option to back out.
Thank you for considering this feature request.
Version Info
Orion Platform 2015.1.2, NCM 7.4, IPAM 4.3, IVIM 2.1.0, UDT 3.2.2, VNQM 4.2.2, NPM 11.5.2, QoE 2.0, NTA 4.1.1