Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

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

Error adding "Set Custom Status" Action to an Alert

Updated June 22nd, 2016

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

Tags

Classifications

Public