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

Volume variables

So this Product Blog on using ${Node.CustomPropertyVariable} for notification destinations has been very helpful so far, but I need to expand this to Volumes and the new SAM custom properties. We have several different teams that support different volumes on a single server. I can create custom properties that contain each team's specific SMTP e-mail address, but cannot seem to get the right tag for it in the TO: field.

I know that for node custom properties, I use ${Node.BlahBlah}, but what is the Volume and SAM counterpart? I tried ${Volume.Blah} and ${Volumes.Blah} with no success.

Find more posts tagged with

Accepted answers

All comments

njoylif

SAM is custom properties are housed in the APM_ApplicationCustomProperties table.

Volume info is housed in the Volumes table.

If these are not working there could be a few reasons.

a. they are not set up to work with macros yet.

b. the way you are deploying them...there has to be a tie to it and this may not be native. i.e. if alerting on node, there may not be an automated JOIN to the applications table and monitors assigned to that node.

I haven't tried this, but another option is that the TO/CC/BCC fields may not be set up to interpret macros... have you looked at alert central yet? It is a free tool.

SW, can you guys shed some technical light on this?

byrona

I actually just took a look at my database when I saw this ticket and it looks like with the new custom property functionality, this information is also getting stored differently in the database which could be the cause of this problem.

Detroiter

So I sorted out the Volume one, seems that TESTING the alert definition did not yield the same results are actually triggering the alert. Once I triggered a legitimate alert with the ${Volume.BlahBlah} e-mail address, it worked.

What is the format for SAM Custom Properties? I know that in the macros for Nodes and Volumes, you have to drop the "S" at the end. How does this affect SAM custom properties?

Byrona, if there is somewhere I can see these macro in my own database, I would be very interested in that.