We had 2 instances of email flooding where our inbox receives THOUSANDS of e-mails for the same thing. One was that one of our admin's exchange inbox was full. Well each member of the IT team got well over 15,000 emails stating that. Um.... 1 email would of been enough, thank you!
Then we inadvertently ran out of space on one server's C: drive (working on it...), and we got over 8500 eventsentry emails for THE SAME ERROR! MSSQLServerOLAPService event 11 (cant write a log file). Again 1 email would of been enough. Is there any way to configure EventSentry so that when it sees a duplicate event within that short amount of time to not send an email if it already did?
Just with literally thousands of emails on for the same issue is hard to manage. Especially if your on a mobile device trying to download a 10,000 message inbox over a 3G connection. It then becomes more of "the boy who cried wolf" syndrome where people start creating rules in Outlook to "permanently delete" certain messages (yes I'm guilty of this myself). It looses it's luster because people start to think "oh there's another event sentry message clogging my mailbox - delete!". That kind of defeats the whole purpose of the system.
Thanks so much for your help! Our entire team appreciates it!
Dear Keith,
Sorry about the email flood. We have several mechanisms in EventSentry that prevent email floods, and those features have been in the product for quite some time actually. As such, I'm a bit surprised that you ran into this issue.
A default installation of EventSentry should not send that many emails, we have several safeguards in place to prevent this.
In any case, you will want to make sure that you have a threshold set on your email notification filters, to limit the amount of events that are forwarded to your email action. Please see http://www.netikus.net/software/eventsentry/index.html?configpackagesfiltersthres.htm.
You can also limit the number of times an email action is triggered, so if you have an email action that sends text messages for example, then you can utilize this feature to make sure a phone is not flooded. Please see http://www.netikus.net/software/eventsentry/index.html?action_thresholds.htm.
Our default EventSentry installation has a threshold on the primary email action, so it looks like this was modified at some point, though it's possible that you installed EventSentry before we added this as a default.
We also have an event log package in place which puts thresholds on events created by SQL Server (for this very reason), the package is called "Database (Servers)". Do you have this package? It should automatically be assigned to any machine running MSSQL Server.
So in summary we're definitely aware of this issue, and we do what we can so that our users don't run into this issue. I suspect that our default configuration was modified, or that your install is older and doesn't have this default.
I hope this explains, the links should explain how to set up the thresholds on either the filter(s) or action(s).
Let us know if you need anything please.
Thanks,
Ingmar.
It looks like you're new here. If you want to get involved, click one of these buttons!