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

Display Custom Property for Child Object

Hi,

Simple I hope. I have an email template that includes this variable: ${N=SwisEntity;M=CustomProperties.Address} - this works fine when reporting on the node status and performance. However, when I attach this to an alert that triggers when any interface on that node reaches 90% utilisation, I get this in the subject: High Priority Site Utilisation is Greater 90% on ${N=SwisEntity;M=CustomProperties.Address} at Wednesday, May 29, 2024 08:52.

I understand that as the interface is a child of the node, it does not have the custom property assigned. Is there anyway to achieve this without going through the 4000 interfaces and updating their custom property field.

The aim is to correctly display the custom property in the email subject.

Thanks all

Zak

Find more posts tagged with

solarwinds_npm

Accepted answers

adam.beedell

That route works for more complicated stuff but I was trying to also give you a nudge in the direction of the macro picker as you can find it in there without having to write anything custom. That said it's good to understand why stuff breaks when moved between alerts on different objects too, took me a while to figure it out some years back.

What you probably want to do is insert a macro, use the top left drop downs to show macros by table(object type), and look for the node custom properties stuff.

You can do the write it yourself version, it should look about the same as it does now but with a "Node." bit in there after the M=, mistakes are really easy there though

All comments

vinay.by

1. First alert that you are talking about is a 'Node' based alert - which is why ${N=SwisEntity;M=CustomProperties.Address} is working.

2. The second alert that you are talking about is a 'Interface' based alert - try using ${N=SwisEntity;M=Node.CustomProperties.Address} (you are trying to use the value of custom attribute on Node onto your Interface alert, which is why alert variable will be different). Alert variables are linked to the type of object/alert that you create.

Hope this helps.

adam.beedell

The macros are positional - think ${N=SwisEntity;M=CustomProperties.Address} = "On this table, go down to the custom properties table, then the address value"

If you swap a node for an interface, it's still going to look to go down one, and use the address. If you made that on interfaces customproperties it'd work. If you want the node's address it wouldnt because that's not the right directions to get to that datapoint

Instead you'd want something that went "On this table, go up to nodes, then down to custom properties, then address" - You can try formatting that yourself, or use the variable picker to find the right one and use that

ZakWooldridge

This does make sense. Annoyingly, I had to create an interface based alert as trying to trigger based on utilisation does not work with a node based alert.

ZakWooldridge

I understood all of that up until the end. Sorry, I am new to SWQL.

Essentially, build a custom variable that determines the value by looking at the parent node and then to the table / row that contains the custom address data?

adam.beedell

What you probably want to do is insert a macro, use the top left drop downs to show macros by table(object type), and look for the node custom properties stuff.

You can do the write it yourself version, it should look about the same as it does now but with a "Node." bit in there after the M=, mistakes are really easy there though

ZakWooldridge

I thought I was going to have to write custom queries or understand the syntax of the variables but no, you were right to nudge. It was actually very simple.

As Vinay.by said "Alert variables are linked to the type of object/alert that you create". So even if you set up a useful alerting template for node based alerts, this will not transfer to an interface based alert. The variables must be changed to work with the different alert type. As you said; use the macro picker, which appears when you select the "insert variable" button within the trigger action window.