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

Confused about nesting advanced alert triggers

G'Day,

I apologize, as I realize this must be posted or documented somewhere, but I can't find what I'm specifically looking for. I'm trying to figure how advanced alerts triggers nest. I know it's not a typical if-then-else structure - that would be too easy. I've also played with the easy stuff, like if nodename=this and status is either this or that, but when I get into more complicated territory, I'm either not understanding how to nesting works, or Orion simply cannot do what I want, something like:

Trigger Alert when all of the following apply

Node Name is equal to SERVERA

Node Name is equal to SERVERB

Trigger Alert when all of the following apply

Application Name is equal to APPA_Connection

Trigger Allert when any of the following apply

Application Status is not equal to UP

Trigger Alert when all of the following apply

Application Name is equal to APPA_User_Experience

Response Time is greater than 600

By my reckoning, that should work out to: if application APPA is down, or has a slow response time, on both nodes, then alert. This is not even the whole picture. I also need to trigger an alert if both nodes are down, but I guess the connection monitor would take care of that too.

Anyway, can anyone point me to some documentation on nesting in advanced alerts, please? Failing that, can anyone give me a quick primer?

Thanx

Stephen

P.S. I realize the above structure is flawed. The nodename cannot be both SERVERA and SERVERB. It's just an example of the logic I need.

Find more posts tagged with

Accepted answers

mcbridea

To interpret the logic in nested conditions start at the most indented level and see if that condition could be true. Then go up one level and consider the level you just examined as a member of the level above it.

In short, evaluate all items that iare indented tothe same level together. I have attached your trigger with the indentation levels marked.

Note that the trigger you have will not work because you require the node to have 2 names in the upper group.

Also see http://www.solarwinds.com/documentation/Orion/docs/UnderstandingOrionAdvancedAlerts.pdf

Andy nested triggers.png

All comments

aLTeReGo

Condition groups are used for and/or operations, where "All" is "and", and "Any" is "or".

mcbridea

In short, evaluate all items that iare indented tothe same level together. I have attached your trigger with the indentation levels marked.

Note that the trigger you have will not work because you require the node to have 2 names in the upper group.

Also see http://www.solarwinds.com/documentation/Orion/docs/UnderstandingOrionAdvancedAlerts.pdf

Andy nested triggers.png

njoylif

look at this thread for ideas

ecklerwr1

Wow Andy I just got burned on this... I thought my logic was correct but the indentation was off... I had to delete and recreate some of the levels to get indenting correct... I had some later in list that were justified left instead of under o.O! Yes I'm still on NPM 11.0.1 today so web alerts are just out of my reach but soon I'll attempt the jump.