This issue has been driving me crazy. I'm trying to set up an alert for whenever a WAN interface in my environment goes offline. So I've grouped my WAN devices together and started building my trigger condition.
Type of Property to Monitor: <change to group>
Then I build a simple condition: Group Name is equal to "WAN Devices"
Then I build another simple condition. I have to change "Property to Monitor" to Node or Interface and trigger for all nodes, where the interface's operational status is not equal to up.
However, changing the Property to Monitor dropdown causes Alert Manager to error, saying:
You have changed the trigger conditions for this alert. This will clear out any triggered alerts for this alert definition. Do you wish to continue?
If I click Yes, it changes the group condition I added so that Group Name is now "IOS Version" or some field from another property to monitor.
Thinking I did something wrong, I followed this work in this video exactly. The instructor changes his Property field as he adds his conditions, and does not get this error. I build the same conditions as him, yet I still get the error.
What am I doing wrong?
I'm on NPM 10.6.1, if it matters.
Please forgive me if this in the wrong group.
The groups are meant for availability of all the components as a whole. if you want to be notified when any of your WAN links go down, what I would recommend is create a Interface custom property call 'LinkType' or something similar, maybe with drop down options like 'WAN', 'LAN', etc. Assign the value WAN to your WAN interfaces. You alert would then look like
Type of property to monitor: Intefaces
alert me when all of the conditions apply
Interface Status is equal to down
LinkType is equal to WAN
There is nothing wrong that you are doing - it looks good its a expected behavior , if you change the trigger condition of the alert it would prompt a message "You have changed the trigger conditions for this alert. This will clear out any triggered alerts for this alert definition. Do you wish to continue? "
What happens in here is -> say an alert was fired with a previous trigger condition that you had, the same would be stored as an active alert in solarwinds and it would not trigger another alert for the same trigger condition until it gets reset (which is based on your reset condition). But then when you change a trigger condition and click on YES on the prompt that appears, it would flush out all active alerts related to this alert and it would start a fresh (note: in such cases if your component is still down, it would trigger another alert for the same and this might result in duplication of alerts for just one time but then you will have to live with it)
Basically when you change anything on trigger condition Solarwinds would internally convert the same to a SQL query and store it on the DB, thats the reason you get that prompt, hope it helps
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.