Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > Error adding "Set Custom Status" Action to an Alert

Error adding "Set Custom Status" Action to an Alert

Created by Chris Foley, last modified by Aileen de Lara_ret on Jun 23, 2016

Views: 88 Votes: 0 Revisions: 3

Overview

This article provides brief information the following error when adding a  "Set Custom Status" action to an alert:

Failed to set Custom status value : Down.

Error details: Execution of CustomStatus action with Entity type - Orion.Volumes failed. CustomStatus alerting action works only with Orion.Nodes 

Environment

All Orion Core products 

 

Detail

Action is being added to an Alert but the Alerts "I want to Alert on" value in its Trigger Conditions is not set to "Node".

 

This is by design.  The "Set Custom Status" action only works if the "I want to Alert on" value in the Alert's Trigger Conditions is set to "Node".  This Action will not work if the Alert is based on Volumes, Components, Applications or anything else that is not a "Node".

 

 

 

 

Last modified
22:25, 22 Jun 2016

Tags

Classifications

Public