Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > SolarWinds SAM alerts are resolving values to SWMacroProcessor

SolarWinds SAM alerts are resolving values to SWMacroProcessor

Created by Chris Foley, last modified by Chris.Moyer_ret on Sep 20, 2017

Views: 780 Votes: 0 Revisions: 6

Overview

When receiving Alerts from Orion, some of the variables are incorrectly resolved or not resolved at all.  As a result, instead of seeing the actual value such as the Application Name, you see SWMacroProcessor or you might see the variable itself.

Environment

SAM 6.x

Cause 

  • The variable is being used within an Alert that does not support it or an invalid variable is being used.
  • The variable was copied from one alert to another, and the "I want to alert on" is different between the two alerts.

Resolution

  1. Verify the "I want to alert on" setting on on the Alert's Trigger Conditions tab.
  2. Verify the Alert Variables within the Alert Actions.
  3. Make sure all Alert Variables are for the item the Alert is based on.  

See SolarWinds SAM Alerts page in the SAM Admin Guide for a list of all supported Variables for Alerts based on Applications and Alerts based on Components:

 

 

Last modified

Tags

Classifications

Public