Network Management
Trigger Action: Set Custom Status is not working
This article addresses an error encountered in the web console when using the "Change Node Status" trigger action. The issue arises from attempting to execute the "CustomStatus" action with the entity type "Orion.NPM.CustomPollerAssignmentOnNode," which is incompatible. The error is clarified: "CustomStatus" alerting action is designed exclusively for use with "Orion.Nodes" and triggers a failure when applied to other entity types. The article offers insights into understanding and resolving this compatibility issue.
First published date
Last published date
Overview
The user assigned a custom device poller to a node and set up an alert specifically tailored to this custom poller. Within this alert configuration, a trigger action is implemented to modify the node status according to a custom setting. This article aims to address the error that occurs when testing this alert configuration.
Execution of CustomStatus action with Entity type - Orion.NPM.CustomPollerAssignmentOnNode failed. CustomStatus alerting action works only with Orion.Nodes.
Product section
Cause
Resolution
Ensure that when configuring alert actions to alter Node status, the trigger conditions are linked to nodes. Specifically, set the alert criteria under "I want to alert on" for "Node" instead of "Custom Node Poller" to successfully achieve the desired status changes. Update the configuration accordingly to align with node-related trigger conditions.
Note: Standardizing and adding additional flexibility for how object status is calculated being considered for a future release.
-
As this feature is not readily included in our product, we invite you to open and vote on our Community Forums in THWACK as this will help our Engineering Project Managers gauge how important implementing such an idea would be for future releases.
- You can post Feature Requests on THWACK.