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
Store

Beta Alert Manager Condition Groups

I'm trying to get the hang of the COMPLETELY different Alert Manager. I understand how the condition groups work now BUT, if I create more condition groups after the first one, what relationship does it have to the first? Is it "and"ed, is it "or"ed or what? I'd like to control what the relationship is between the groups but I don't see a way to affect whatever the default condition is.

Dan Goodale

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

Agreed.. I would love to see some examples of someone using advanced conditioning. It seems pretty powerful, but I can't grasp the concept without some examples.

DGoodale

Yeah, I'm getting so exotic with my attempts that I'm getting warnings and the alerts can't be saved. As you said, a few examples with multiple conditon groups would be WONDERFUL !!!

FormerMember

I'll see if I can do this justice by typeing it...I've gotten nested conditions to work fairly well.

Trigger Alert when ALL of the following apply:
Node Stautus is equal to Down
Trigger Alert when ANY of the following apply:
NodeType is equal to Cisco_VPN
NodeType is equal to Nortel_VPN

(NodeType is a custom propery I added to the database)

The way I have this working logic wise is it ANDS the down status and whichever of the second condition apply, so the trigger when ANY is an OR. By nesting conditions like this in different orders you should be able to do whatever you need.

Hmm, the formatting got hosed on that...the Node status line and trigger any line should be right underneath each other and the two node type lines should be lined up but further indented under the trigger any line.

The biggest catch I've found, is make sure you have the condition highlighted that you want to add the new condition under, otherwise it orders them improperly.

DGoodale

Yup....exactly!

I opened a ticket and was sent an example that resolved my confusion. As Ranger indicated, you create your AND/OR/NAND/NOR condition first and THEN you nest the rest of the conditional groups under it. Works like a charm!