Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Archive > 2017December18 - Deletes > Trap alert variables are not translated during a test

Trap alert variables are not translated during a test

Created by Justin Wyllys, last modified by Kevin.Swinson on Dec 18, 2017

Views: 755 Votes: 0 Revisions: 6


When creating an alert to forward a trap for a given scenario, the test trap result shows variables instead of their values if you have restricted the alert to a different object than what you are testing. 


For example, your trigger condition is configured only to alert on an interface named "GigabitEthernet0/1" but you are testing the alert on an interface named "GigabitEthernet2/15". The resulting trap result would include variables instead of their translated values. 


  • NPM 11 and later
  • Web based alerting in which you are forwarding a trap as part of the Trigger Action.


The object you have defined in the trigger condition does not match the object you selected for the test.


Select the same object for the test which you selected for the trigger condition.

Last modified


This page has no custom tags.