Condition objects - how do you use them, doc review
-
Hello,
I am trying to figure out how to use condition objects in NetXMS in order to display a proper link status (e.g.: custom attribute on node A = 1 and other attribute on node B != 2 and no alarm exists on connected interfaces). As a side effect, the following description was added to the wiki page http://wiki.netxms.org/wiki/UM:Objects#Condition_Objects. Can you please review the following text and suggest improvements and some real usage examples?
Conditions may represent more complicated status checks because each condition can have a script attached. Interval for evaluation of condition status is configured in Server Configuration Variables as ConditionPollingInterval with default value 60 seconds. Input values for the condition script can be added in the Data tab. Such values are accessible via $1, $2, ... variables inside the script. If the script returns 0, an activation event with the defined severity is created. If the script returns any other value, then a deactivation event is created.
Thanks,
Lukas
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login