Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Assigning an alert action to a different scoped alert and variable only returns the variable and not the output value

Assigning an alert action to a different scoped alert and variable only returns the variable and not the output value

Table of contents

Updated October 21, 2016

Overview

This article explains the behavior of an alert action variable created under one type of scoped alert then assigned to a different scoped alert.

Environment

  • NPM 12.0
  • NPM 12.01

Detail

  • A new feature presented in NPM 12.X Action Manger will allow an existing action to be assigned to any existing alert or creation of an alert.

    There is a known behavior of any alert variable when created under a scoped alert and assigned to a different scoped alert. For example:

    Alert variable: Created the following alert called 'Interface is Down'. Created the following variable with the Interface scoped alert under an action called 'Group A alert action' : ${N=SWisEntity;M=Node.Location} for location of a node *Node Variable type*
    Variable output: 'Austin Group A Location'
     
  • Assign action 'Group A alert action' to an alert called 'Node is Down' (Node scoped alert)
    Variable output: '${N=SWisEntity;M=Node.Location}'

 

  • When the alert variables are created the SolarWinds Information Service (SWIS) query is created statically to the specific build of a specific alert scoping or type. Meaning if the alert action that was created under a node alert is assigned to a interface alert its likely that most variables will not work under the different entity. However, if the node action is assigned to another node scoped alert then the variables in the action would more than likely work appropriately

 

 

 

Last modified
16:44, 20 Oct 2016

Tags

Classifications

Public