Deactivation Event - After x polls
-
Hello!
Currently we have a small issue with NetXMS resolving errors if it cannot poll a certain value.
For example: The value should be 0. If the value is 1, a error will be given. But if NetXMS cannot poll the value for 1 poll, the errors resolves.
I tried setting the samples to 3 in the hope that the error would also resolve after 3 tries, but this is not the case.Activation Event - Will be given after 3 polls
Deactivation Event - Will be given after 1 pollNetXMS is not able to execute a script because the file is probably open. Then NetXMS will "Resolve" the DCI and after 3 polls it will be activated again.
Is it possible to have the deactivation event also set to like 3 polls so that we don't get any "resolved" notifications if NetXMS is not able to get results from a script?We are on version 4.1.420 over NetXMS Management Console.
Kind Regards,
Mitch
-
The logic is that if "Samples" is set to 3, then all last three collected values should be "1" to trigger the threshold. If just one non "1" value comes, this means "last 3 values should be equal to 1" becomes false and it instantly generates threshold recovery event.
You can use script threshold, there you can use https://www.netxms.org/documentation/nxsl-latest/#func-getdcivalues function to get a number of last values and make the decision in the script. Drop a line if you need an example for such script.
-
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