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

Upgrade to NPM 12.0 Alert Complex Condition

Anybody using Alerts with complex condition enable that upgraded to NPM 12.0 lately and the alert stop working as it should?

Please let me know

Thanks

Find more posts tagged with

Accepted answers

All comments

ewoknophobia

We are using complex conditions and since upgrading to NPM 12 they seem to no longer be functioning.

greg.cheal

Even with the correct syntax, the alerts are coming up blank with certain information. I've found that re-creating the original alert through the web UI resolves this issue somewhat, as most of our alerts were originally created on the server.

ewoknophobia

Ok.. I can try that. I'll recreate the alerts from scratch and post here if it works. We have a lot of alerts that use complex conditions, this is going to be a bummer.

**That didn't work for us. I can see the alert pop into the general alert window, but it doesn't execute the trigger action**greg.cheal

mmarchand

I did try to re-create the alert and the trigger action does not work you can only see it in Orion general window

Opened up case #1020501 and support we're able to reproduce and confirmed it is a bug in V12.0 it should be fixed in the next release but you never know and do not know when either

Thanks

ewoknophobia

Well.. dang. I chatted with support as well. They confirmed it is a known issue and a patch is coming.

tonymckay

The scenario we are using complex conditions is that we have 2 separate UnDPs (samplerowentryAdminState & samplerowentryOperState). We have a complex condition that basically should say "if Admin State equal to Up and Oper State not equal to Up" to alert. The complex condition only triggers on the first half of the complex equation. If we put the Admin State as the first trigger condition, then we get a list of all Admin UP rows; if we put Oper State not UP first; we get a list of all operationally down rows, including those that are not Admin Up". Is this what everyone else is seeing? Is it possible that we are missing something?

ewoknophobia

tonymckay The latest NMP patch to V12 is supposed to fixe the complex condition issue (12.0.1). We are pushing the update into our production environment this evening and can update you on the results if you like.

mmarchand

Would be great to know if it's working OK

Thanks