Had an embarrassing moment just now with alert emails apparently *stuck* on the NPM server and going out all at once instead of when they were actually generated. The alerts monitor a set amount of available space on selected database volumes, separate alerts for different space levels. They tested out successfully and have triggered successfully when first implemented. Today, right after clearing alerts on the web console about 15 of these alerts came all at once, some not accurate for this moment in time suggesting to me that although it might have been accurate when generated but since were alleviated.
This is bad on several fronts: an alert was triggered but the message didn't go to necessary recipients preventing timely action, a slew of notices went out to a rather large group unnecessarily, and most damaging is that corporate confidence in NPM and alerting has taken a hit. I need to respond with an explanation and action plan to restore confidence and need the forum's help.
Has this happened to others? What could be causing alert emails to get stuck on the server? Can it be fixed?
Please, and thanks...Fred