NetXMS 6.0 released
-
-
NetXMS 6.0 uses newer version of GUI framework which requires newer version of servlet API. Please try tomcat10
-
Important notice
If you have relatively large database (starting with few hundred of nodes or few thousands of DCIs or long retention time) - delay upgrade to 6.0 until patch release 6.0.1, which we plan for Monday. Unfortunately, current DB migration procedure turns out to be inefficient for bigger databases, so we are working on an updated one. -
@filipp-sudanov said in NetXMS 6.0 released:
NetXMS 6.0 uses newer version of GUI framework which requires newer version of servlet API. Please try tomcat10
Although Tomcat 9 came pre-installed with Alma Linux 9, I tried manually installing Tomcat 10 and the web interface worked normally.
Please note that the administrator documentation does not contain detailed requirements for version 6.0.
-
-
@batnator said in NetXMS 6.0 released:
Thank you for the new release. Is it possible to again provide a statically linked binary of the agent for Linux x86_64 as a download (like nxagent-5.2.8-linux-x86_64-static.tar.gz)?
I think yes, we will bring those back in a few days. Can you explain a use case for those? I'd think that nowadays agents mostly deployed from deb or rpm packages.
-
@victor said in NetXMS 6.0 released:
@batnator said in NetXMS 6.0 released:
Thank you for the new release. Is it possible to again provide a statically linked binary of the agent for Linux x86_64 as a download (like nxagent-5.2.8-linux-x86_64-static.tar.gz)?
I think yes, we will bring those back in a few days. Can you explain a use case for those? I'd think that nowadays agents mostly deployed from deb or rpm packages.
My firewall is based on a hardened Linux system that doesn't use any deb or rpm-based package management. It sounds great that you're planning to make a statically linked version available again; that saves me from having to set up a complete firewall development stack just to compile the agent as an add-on from source.
-
-
-
@johnnyva said in NetXMS 6.0 released:
Hey Victor will the change in idata/tdata timestamp to millisecond impact the REST API or NXSL dci values? i.e. will we see millisecond timestamp there as well or will we only see change in db?
New REST API (webapi module) - it is using ISO 8601 format for timestamps which allows milliseconds (although 5.x did not set millisecond part), any decent ISO 8601 parser should handle milliseconds correctly.
Old REST API (Java app) - should be unaffected.
NXSL - all timestamps for collected data are now in milliseconds.Best regards,
Victor -
Could you please update docs pages (NXSL and admin guide) for where unix timestamps are in milliseconds vs seconds. It feels like this could get confusing if there is a mix of unit when unix timestamp is referred to.
I'm expecting that this (https://www.netxms.org/documentation/nxsl-latest/#class-datapoint) would be the only place that would have changed from seconds to milliseconds because this is the only place to get list of DCI datapoints including timestamp right?
-
@victor Also, the timestamp conversion will be a background task after netxms server/db upgrade? If so, how will nxsl/rest api present the timestamps when not all timestamps have been converted? Will we have a mix of seconds and millisecond timestamps or will netxms server convert seconds to milliseconds even if the db entry has not been updated by the background task yet?
-
@johnnyva said in NetXMS 6.0 released:
@victor Also, the timestamp conversion will be a background task after netxms server/db upgrade? If so, how will nxsl/rest api present the timestamps when not all timestamps have been converted? Will we have a mix of seconds and millisecond timestamps or will netxms server convert seconds to milliseconds even if the db entry has not been updated by the background task yet?
Yes, conversion is a background task (but you should upgrade straight to 6.0.4), server will do conversion in background. Internally server renames idata tables, create new empty tables, and gradually moves data from old to new with conversion. So API will not see incorrect timestamps, but for some time after server start you will not see older data.
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