Notifications being sent when alert is not enabled

felixforbes

Hi All,

I noticed some behaviour I was not expecting the other day - I created an alert that I don't want to turn on yet, so left "Enabled" set to Off and created the alert. When I got to the Summary screen, I received the yellow box saying that the alert would trigger for one node. While this is what I want in the long run, my expectation was that I would be able to create the alert, but by leaving it Not Enabled for now, no notifications would be sent.

I changed the new alert so that it only sent to me, then created it and received a notification to my email address. My feeling is that if I create the alert in a Not Enabled state, no notifications would be sent until I enable the alert.

I realise this is possibly just a disconnect between my expectation and the functionality, but am I missing the point here? I deal with lots of customers over many different networks and often want to create an alert ahead of time and would have thought Not Enabling stops the notification as well as the alert checking (or at least being Not Enabled suppresses the notification at the summary screen until the alert is Enabled).

How do others feel about this? Is my expectation wildly off?

Felix

marcrobinson

The short answer is the alert will not trigger if it is not enabled. The yellow box just means that IF the alert was enabled, it would trigger for the following XX nodes. It only happens when nodes (or anything defined in the scope) meet the alert trigger conditions - it is more of warning to you that the alert would fire. It can be useful to remind you to notify the support teams ahead of enabling that alert, and a valid test if you know something(s) should trigger it.