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

Advanced alerts not passing alert variables correctly

Hello,

I am using SolarWinds Orion Network Performance Monitor 8.5.1 SP3.

I have created an advanced alert to execute a vbscript based on some trigger. The alert is also configured to pass the ${DNS} or ${ip_address} alert variable to the script when it executes but the actual value (i.e. node fqdn or Ip address) is not passed to the script; instead the adv alert litterally sends alert variable name instead (i.e. ${DNS} or ${ip_address})

Is there a way to get around this problem? Alert variables seem to work with basic alerts but I need the adv alert capabilities to work.

Any feedback will be appreciated

thanks, Sergio

Find more posts tagged with

Accepted answers

All comments

WINNT

I use this feature without any problems, but you do have to use the proper syntax. I need to know the following details:

1. What are you monitoring (Node status, app status, volume status, custom mib status, etc)

2. What is your exact alert action syntax that uses the variables? i.e. "D:\Scripts\TracertDownNode-ALERT.bat" ${NodeName}

Smoreno

I am glad to hear that this feature works, your answers below.

1- For now I am just testing the Windows Spooler status on a node (spooler up or down)

2- "C:\Program Files\SolarWinds\Orion\VbScripts\respool2.vbs" ${DNS}

Here is the script that I am using which works with a basic alert:

strComputer = WScript.Arguments.Item(0)
Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")

Set colServiceList = objWMIService.ExecQuery("Select * from Win32_Service where Name='spooler'")

For Each objService in colServiceList
objService.StopService()
Next

Wscript.Sleep 5000

For Each objService in colServiceList
objService.StartService()
Next

Thanks, Sergio ADOT

Smoreno

The only alert variable that seems to work on an Advanced Alert is $[NodeName} which does resolve to the correct node name. ${IP} and ${DNS} don't work on an advanced alert for me.

has anybody else seen this before? Is this a bug on the product?

Any feedback will be appreciated.

Thanks, Sergio

qle

I believe the correct variable is ${IP_Address} for Advanced Alerts. Anyway, I tested and confirmed that both ${IP_Address} and ${DNS} work with the "Execute an external program" action. I'll assume that it would hold true for the "Execute an external VB Script" action as well.

Smoreno

Thanks for cheking the alerts; I tried it them again using a script and I could only get the ${NodeName} variable to work, ${IP_Address} and ${DNS} don't work.

I used the following script that one of the developers suggested to determine what is being passed to confirm the problem. This looks like a bug in NPM 8.5.1 SP3.

Const ForReading = 1, ForWriting = 2, ForAppending = 8
set args = WScript.Arguments

argstring = ""
for i = 0 to args.Count-1
argstring = argstring & " [" & args.Item(i) & "]"
next

set fso = CreateObject("Scripting.FileSystemObject")
set file = fso.OpenTextFile("c:\scripts\script.log", ForAppending, True)
file.WriteLine(Now & " -" & argstring)
file.Close

Thanks

Smoreno

Another question, have you tried setting the time of day when to execute an exe or script?

This feature is supposed to allow you to set the time and/or day(s) when the exe or script will execute after the alert is triggered. The script in my alert never executes when I specify time during the day (i.e between 10:00 AM and 10:15 AM) have you tried this