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

NodeName is equal to Trigger condition question

I am experiencing some unpredictiable results using NodeName is equal to <NodeName> in a trigger condition and wanted to ask you the best way to use (NodeName is equal to <NodeName>) in a trigger condition.

My goal is to create an Alert to filter on a Named node for a status i.e

NodeName is equal to Malibu

NodeStatus is equal to up

ResponseTime is greater than 20

While testing I find that other nodes are alarming in this logic, What is the best fit in General to use the NodeName is equal to <NodeName> Trigger condition ?

Find more posts tagged with

Accepted answers

All comments

stuartwhyte

Could you post a screenshot of your trigger condition, as your logic appears ok to me.

jcorcoran

That is the logic in text - and thank your for replying - I am more interested best case uses for the NodeName filter in an alert - what are the trap doors - I need to learn the best way for use..

Are there any pitfalls using the NodeName variable ?

stuartwhyte

The only suggestion I would have if you are having the alerts triggered for nodes that are NOT called Malibu is that you have the ANY rather than ALL conditions selected.

I've never had the need to alert on only one node, but I see no problem with using NodeName. NodeID would potentially be a better bet, being 100% unique, whereas it would be technically possible to have two (or more) nodes with the same name.