last() DCIs resetting after server restart
-
Hi,
We have a number of DCIs using last( # ) samples equal to a specific value thresholds. I noticed that every time the NetXMS service restarts these thresholds are deactivated and reactivated # polls later if they were active before NetXMS went down.
Probably this has to do with the server not knowing what the previous values were because it was down. However, it creates the false impression that the threshold was no longer reached at a certain point.
Seeing as threshold activation/deactivation status is kept in the database, would it be possible to retain the old status of a threshold if the current DCI value(s) do not change it, and last values are not available due to a server restart?
For example, let's assume a DCI with threshold last(2) < 10. In the following list of polled values, assume X is the point where the server restarts:
15, 26, 30, X, 40, 50, 60Currentely (tested on v1.2.6), the threshold would be active before X, be deactivated when it polls 40 first time after the restart, and be reactivated at value 50.
With the change I suggested, it would remain active throughout the test.Another example:
15, 26, 30, X, 0, 1, 2
In this case, both the current version and my proposal should deactivate the threshold at 0.15, 26, 30, X, 40, 0, 1
Here, the current version would deactivate the threshold on 40, but my proposal would delay this until the next poll (0).Kind regards,
bdefloo
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