How to modify Alert Actions without triggering the Alerts?

Hi Team,

I was given task to modify the trigger actions and reset actions for couple of alerts. I was able to do it fine on Older Versions using Advanced Alert Manager, However on the new Web based Alerting, Eveytime i do any changes it says it will trigger alerts immediately for these many devices.

"This alert would be immediately triggered on 7 object(s) in alert scope Show list If this behavior is not expected, try to adjust the trigger condition"

How can this be addressed. I want to make the changes to the alert actions but don't want that to trigger the alerts again.

Kindly Help!!!

Reuben.

Find more posts tagged with

solarwinds

npm 11.5.2

ncm

Alerts

Accepted answers

All comments

pparsaie

Disable the alert prior to editing, once complete enable the alert. Should get you where you need to be.

johnwilly

No after making the changes if i enable them, It still triggers the alerts again.

bluefunelemental

In my experience if the alert is active then it does not retrigger the alert even when the alert is modified.

It would seem as if the query to tell you how many objects will trigger does not take this into account.

If you wanted to retrigger so your new actions would run then you can always clear the older alerts or as the other poster mentions disable and re enable the alert which clears all active alerts for it in the process.

johnwilly

Well that's how it's supposed to act., however though the alerts are still active it is retriggering them again.

bluefunelemental

As in actions are being done again?

johnwilly

Yes, it is re creating the alerts.

gowen.a

I have the same problem, even if I just rename the alert - disabling it is not the answer. I have to notify the recipients that another alert will be coming their way.

This is one of the niggling things I dislike about SolarWinds

sirpaw

Hi Reuben,

Were you able to work around this? Support offered any solution?

Somehow I miss the old 32-bit Advanced Alert Manager, where this wasn't an issue at all.

Thanks.

Regards,

Paulo

johnwilly

looks like this is a Bug.

If you are modifying an alert and if there is already an active alert for this alert which was trigged more than 30 days ago, It is going to immediately re-trigger the alert actions again.

Hi Reuben, It sounds like you are running into a known issue in your environment. If these alerts were over 30 days old, I can explain why this is happening. Once you have active alerts for >30 days and the alerting service is restarted, you will receive all those older alerting emails. This is because database maintenance deletes all >30days old records from the AlertsHistory table. The action execution log is deleted by default after 30 days. If the Alert Engine v2 does not find a record in the AlertsHistory table, it executes the action again because it thinks that action was not executed. Thus, you get repeated alerts. Please acknowledge if this correlates to what you are seeing. I can submit this to development, but I don't have an ETA on a fix. The best action to take is acknowledge and clear out the old active alerts

pratikmehta003

I have seen this happening but i guess only on the Orion web console the alerts are seen again. I have not seen the email/trap action being executed when we modify and submit it.

baz00r

I am also experiencing this issue.

Alerts were already active, triggered from only a day ago, if the alert is edited in any way, even just the alert name, the actions get implemented again, resulting in alert emails for all in question. This is really frustrating behaviour. I have attempted to disable the alert, make changes, and re-enable but it still emails the alert to everybody again.

Some of the alerts I am editing have 20, 30, 40+ active alerts, to re-send 40 emails to people multiple times during the day is simply not acceptable.

ryan.davis26

I'm on the latest and greatest, NPM 12.2/ SAM 6.5 - turning the alert off, clears all instances of alert active meaning the Active Alerts screen will not show the alert anymore. What that also means is as soon as you turn the alert back on, all actions fire again.

What I'm current experimenting with is adding the new action that I want to implement to the alert to a dummy alert (so that I have it in the actions library) and turning that action off.

Then add that action to the production alert and saving it.

Then go back to action manager and turn it on.

I will post back here with what I find.

sv9780

aLTeReGo Could you please help here.

Why the alerts are getting re-generated when we done any changes to the alert.

as of now i'm muting the alerts for nodes which are active in console and modifying the alert and resume alerts for the devices after sometime.

aLTeReGo

When the trigger condition is changed the condition reevaluated. Depending upon the extent of the change, it can cause new alerts to trigger. This was also true of the legacy Win32 Alert Manager. The only difference here is that we're telling you the total number of objects which meet that condition now within the wizard. That's simply there as a convenience to prevent accidentally misconfigured trigger conditions from sending hundreds/thousands of alerts.

sv9780

We haven't changed the condition. We just modified the email alert subject and saved the alert.

Once we saved the alert it re-generating the alerts for active alerts as well.

pratikmehta003

can u show the screenshot of your trigger and reset condition.. and also trigger action...there are some settings like below as well in trigger action.