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

Alert Manager - ${NodeName} doens't display

erik.marcus

Hi Everyone,

When a node goes down I want to receive an e-mail that tells me which node is down.

The problem I have is that the e-mail displays:

".. is down"

I don't see the node name.

I configured the alert to do the following: trigger actions -> send e-mail page to -> message -> ${NodeName} is down

Can anyone tell me why the e-mail doesnt show the nodename?

Find more posts tagged with

Accepted answers

All comments

bluefunelemental

${caption} is what I use

Thanks,

Christian

jcorcoran

The caption tag is used in several areas for different elements. When creating an email notification once you select " Insert Variable" in the Variable Category select Node, you will see the Variables available , scroll down and select Caption. this has worked for me every time.

erik.marcus

Well i did use the Insert Variable button. But somehow ${NodeName} doens't work while other variables do work.

jcorcoran

can you try "caption" under the node category ?

that is the field in the nodes table that all the host ( nodenames) are populated. -> caption

erik.marcus

Hi John,

I think you missunderstood me. I'm talking about the following windows:

tab: trigger actions -> e-mail message -> tab: message -> message is: Something with ${NodeName}

Or are you telling me try to create an alert of which the condition should contain ${NodeName} ? Also I can't seem to figure out what you mean by caption.

To be clear:

In the e-mail body message i'm currently using ${AuditEventMessage} which works great for deleted and unmanaged nodes. None the less, for nodes that go down i need ${NodeName} which does not work. So it allmost seems like the ${NodeName} variable isn't recognised.

tcbene

Is this based on one node you have tested or on multiple nodes? It sounds like you have configured an entirely new alert. Have you tested the default alert provided by SolarWinds?

stuartwhyte

What type of property are you monitoring on your trigger condition page? Some varibles are only valid for some property types. I think you are using the Auditing Events property, for which ${NodeName} or ${Caption} is not available.

If your trying to alert on Node down, use the Node property and ${Caption} will work for you.

erik.marcus

I've got alerts with the following trigger conditions:

node down -> Node: Node Status - is equal to - Down

node deleted -> Auditing Events: Action Type - is equal to - Node unmanaged

node unmanaged -> Auditing Events: Action Type - is equal to - Node unmanaged

I now understand that the Propert Node & Auditing events require different variables.

I now have used the following to try out your advise:

Trigger Condition:

Auditing Events: Action Type - is equal to - Node unmanaged

message body:

${AuditEventMessage}

${NodeName}

${Caption}

Message result:

User ******* unmanaged node ******

${Caption}

tcbene

That was the point I was driving to stuartwhyte . I noticed the same thing when I was configuring alerts. If he tests with the default alert provided with SolarWinds, that would help identify if there is an issue with how the node was added.

erik.marcus

Node down is an original Alert

Node unmanaged is not

I'm trying to figure this out on the unmanaged alert because it's easier to let the alert trigger. I don't like to timout a node just to test my monitoring alerts

stuartwhyte

What do you have here:

jim8424

For all of my alerts with Node as the property to monitor, ${NodeName} works just fine.

stuartwhyte

...and which property are you monitoring when ${NodeName} fails? If it's Auditing Events I'd say it is unlikely that ${NodeName} would be available to you.

jim8424

I'm not having any issues with ${NodeName}. I was commenting on the original post.

Detroiter

After looking at the AuditingEvent table in the database, it is clear that NetworkNode = NodeID. i then tried to define a custom SQL variable in the message that leveraged that macro...failed. Seems the ${NetworkNode} macro in the Auditing Events category is broken. Kellie Mecham may want to take note of that.

But I'm not one to let a broken macro stop me. Since the Auditing Event alert type still connects to the General variable category, I just shifted to a nodeID that is listed there. I did some basic testing and it worked. i recommend you do some testing as well, but here is the variable I created. Should suffice.

${SQL:Select nodes.caption from [YOUR_ORION_DATABASE].dbo.nodes where nodeID = ${NodeID}}