Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Anyone having issues with Adv Alerts after updating to NPM 10.1.1 SP1?

I've opened a case on this but still no resolution to our problem.

We have some advanced alerts that are not getting triggered any longer. This started after updating to 10.1.1.

If I use the TEST ALERT feture it will always work with the action but the real-thing won't work.

Also with using the TEST ALERT, I know the node to be DOWN, but it will see it as being UP. As if the node status didn't get updated in the database table.

Find more posts tagged with

Accepted answers

All comments

wbrown

I haven't noticed a difference with the 10.1.1 upgrade, but I did notice similar behavior in 10.0.
In both versions the test feature seems to only execute the actions including providing values for specified variables. But neither version seemed to actually check the configured conditions.

MarieB

Hi Larry--

I saw your earlier post about this issue. I'll ask PM about it. When you hear from support, please post back to let the community know.

lchance

It turns out that all my Adv Alerts where I used Custom NODE Properties in Trigger or Reset or Suppression tabs has to be re-done.

Although these have been working for months, the 10.1.1 updates caused these, which only used multiple Custom Prop in Conditions, to stop.

I'm having to go back through each alert and re-do these Conditions by order plus totally remove my Suppressions. What I was doing with using Suppressions only works in Conditions now.