What’s more frustrating than finding out you have an issue in your network or infrastructure? Finding out about it every 30 seconds, creating a storm of alerts. Has the situation changed? Do you really need to see the same problem over and over again?

No. No you don’t.

And we at Derdack agree. That’s why we put duplicate suppression into Enterprise Alert.

The driving force of Enterprise Alert is its Alert Policies. They define what alerts are important enough to you to be sent to your on-call personnel. But they can also define how alerts are NOT seen. And that can be just as important.

This is achieved through Duplicate Suppression. Duplicate suppression can be selected as part of setting up an Alert Policy. Under the conditions on the policy, it’s a matter of checking the box to turn on duplicate suppression, as in the picture below.

With this turned on, you’ll stop getting the same alerts over and over again. But you can also define exceptions to this. The exceptions allow you to define the time limit of this suppression, so that you’ll get the alert again after whatever amount of time you set. You can also define a parameter change exception. With this, you can set the policy to look for changes in one of the parameters of the alert. This would indicate a change that was needed to be seen, such as an update to the alert as seen in the picture below. Any of the parameters of the alert can be chosen to define what would constitute turning off duplicate suppression.

Once invoked, duplicate suppression will allow you to finally concentrate on the actual problem at hand and get everything back up and running again. You’ll only be alerted again if something about the alert changes or if you reach the timeout period, and you can rest assured that any further alerts you get will be new problems, not the same one, over and over again.

If you’d like to learn more about Enterprise Alert and how it can help you quell the storm of alerts, visit us here, and request a personalized demo today.