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

Alerting: evaluate two nodes during supression (Complex Condition?)

I'm trying to suppress an alert based on whether the triggering node is on the same subnet (custom property) as another specific node.

Yes, I do know I could have an alert for each subnet but this could be impossible to maintain after a certain point

example

if NodeT.subnet=NodeR.subnet AND

NodeR.IP=X.X.X.X AND NodeR.Status <> UP then suppress

I see the Complx Condition option but no real documentation of examples of how to put one together.

Find more posts tagged with

Accepted answers

All comments

mvjames

Or simpler

if NodeT.subnet=X.X.X.0 AND

NodeR.IP=X.X.X.1 AND NodeR.Status <> UP then suppress

MagnAxiom

Unfortunately, everything I have seen points to the alert system being "stateful" meaning that when an alert triggers, you only have access to the data of the node that triggered the alert.

This is one of the biggest issues I have with Orion right now. For instance, say I want a server alert to be suppressed if the switch it connects to is also down. Sounds like a pretty strait forward Parent/Child like scenerio. Everything I have found says you can't do that, because you only have visibility to the status and custom properties of the node that triggered that alert. As a result, you will get an alert for the swtich and all devices monitored off that switch, rather than one single alert that lets you know that all the nodes connected to it are down as a result of this outage.

FormerMember

Alert-suppression based on dependencies is planned for an upcoming release.

mvjames

Alert-suppression based on dependencies is planned for an upcoming release.

Not so fast denny to suggest your answer as the "solution". My question was a two parter. Do not assume that I am referring to "dependant" nodes. I was just making an example. Your suggested solution is part of the problem for what you are thinking this question is about. Solarwinds representatives have been claiming parent/child dependencies "will appear" or "is planned for an upcoming release" since before 9.0 came out and before 2007. "upcoming release" can mean anything tomorrow, next week, next year, next decade.

A) I am looking to relate two or three nodes that may or may not have the same parent node. Not looking for a physical topology failure.

I have physical topology node failure/ "parent node" alert suppression working. At the moment the only way to impalement this is to have AN ALERT PER PARENT NODE. Solarwinds builtin functionality to determine Parent Node relationship but my question is on a multiple node suppression ie AN ALERT FOR MANY PARENT NODES.

C) describe or explain or give examples on how to use the "complex condition" in your current product. Note I am not asking ow to create complex scenarios with the condition groups and simple conditions. just how the field/value * is equal * works and what is expected.