<![CDATA[Is it me or does NetXMS have time travel capabilities?]]>I have the following hook in my NodeUp and an equivalent in my node down. Apart from it being the longest way of doing this (first one I found when searching), I get a strange result.

Everything is correct - except - the month is out by 1. It reports month as being last month, not this month. I know the local time is correct(or bein extracted correctly) because I am comparing the Node_Up and Node_Down event times to the custom attributes - and everything matches  - exactly - except the month - which is out by one.

SetCustomAttribute($node, "timelastcameup",localtime(time())->mday.".".localtime(time())->mon.".".localtime(time())->year.", ".localtime(time())->hour.":".localtime(time())->min.":".localtime(time())->sec);

Any ideas?

]]>https://forum.netxms.org/topic/6135/is-it-me-or-does-netxms-have-time-travel-capabilitiesRSS for NodeFri, 13 Nov 2026 08:25:57 GMTSun, 25 Aug 2019 22:37:20 GMT60<![CDATA[Reply to Is it me or does NetXMS have time travel capabilities? on Thu, 12 Sep 2019 11:33:24 GMT]]>You can simply use strftime (https://wiki.netxms.org/wiki/NXSL:strftime😞

SetCustomAttribute($node, "timelastcameup", strftime("%d-%m-%Y, %H:%M:%S", $1));

Best regards,
Victor

]]>https://forum.netxms.org/post/26503https://forum.netxms.org/post/26503Thu, 12 Sep 2019 11:33:24 GMT<![CDATA[Reply to Is it me or does NetXMS have time travel capabilities? on Thu, 12 Sep 2019 11:26:05 GMT]]>Tursiops - correct as usual 🙂
https://wiki.netxms.org/wiki/NXSL:TIME

Would be nice for NXSL TIME to also have mona as the actual month - adding 1 to mon so I don't have to.

Adding that within SetCustomAttribute will be fun. Something like one of the following I hope - but probably not that lucky.

SetCustomAttribute($node, "timelastcameup",localtime(time())->mday.".".((localtime(time())->mon)+1).".".localtime(time())->year.", ".localtime(time())->hour.":".localtime(time())->min.":".localtime(time())->sec);

or

SetCustomAttribute($node, "timelastcameup",localtime(time())->mday.".".localtime(time())->mon+1.".".localtime(time())->year.", ".localtime(time())->hour.":".localtime(time())->min.":".localtime(time())->sec);

Or going the long way:

day = localtime($1)->mday;

mon = localtime($1)->mon+1;

year = localtime($1)->year;

hour = localtime($1)->hour;

min = localtime($1)->min;

SetCustomAttribute($node, "timelastcameup", day."-".mon."-".year.",".hour.":".min;

One of these should work.

]]>https://forum.netxms.org/post/26502https://forum.netxms.org/post/26502Thu, 12 Sep 2019 11:26:05 GMT<![CDATA[Reply to Is it me or does NetXMS have time travel capabilities? on Mon, 26 Aug 2019 03:17:08 GMT]]>As per http://www.cplusplus.com/reference/ctime/tm/, I believe months are "months since January" and therefore go from 0-11, not 1-12.

]]>https://forum.netxms.org/post/26380https://forum.netxms.org/post/26380Mon, 26 Aug 2019 03:17:08 GMT