<![CDATA[Unsigned Integer DCI and diff()]]>I've been monitoring UPS runtime, and as that really should never go into a negative value, I thought I'd use an unsigned integer for the DCI.
I also used a threshold to alert if the runtime dropped by 20 minutes within 1 minute, kind of as an indicator that the battery is on its way out.

The result of the above setup is that the threshold gets triggered a lot. Every time the runtime goes down, it triggers.
For all I can tell this is due to the unsigned integer. If the the difference to the previous value is negative (i.e. from 120 to 116, a difference of -4), it compares the threshold of 20 with 4294967292 (i.e. 2^32 - diff). I don't think the unsigned integer class for the actual value should apply to the result of the diff?
Or did is this some other odd issue I ran into? Since switching from Unsigned Int to Integer, I'm not getting these alerts anymore.

]]>https://forum.netxms.org/topic/4417/unsigned-integer-dci-and-diffRSS for NodeFri, 13 Nov 2026 13:08:21 GMTMon, 18 Apr 2016 23:24:35 GMT60<![CDATA[Reply to Unsigned Integer DCI and diff() on Tue, 27 Dec 2016 15:20:47 GMT]]>Fixed in version 2.1-M2.

Best regards,
Victor

]]>https://forum.netxms.org/post/21552https://forum.netxms.org/post/21552Tue, 27 Dec 2016 15:20:47 GMT<![CDATA[Reply to Unsigned Integer DCI and diff() on Tue, 19 Apr 2016 13:53:54 GMT]]>Hi,

it's actually a bug, diff definitely should be treated as signed value. I'll register it in our issue tracker.

Best regards,
Victor

]]>https://forum.netxms.org/post/19684https://forum.netxms.org/post/19684Tue, 19 Apr 2016 13:53:54 GMT