Hi, in 2.2.3 we have added fix for incorrect value type in transformation script. If you are running older version, try to change transformation script to return uint64($1) * 8; Best regards, Victor

Hi, NetXMS has "helpdesk links" - loadable modules that provide interface to ticketing system. If ticketing system supports it, this module can provide two-way integration (as done for Jira). Currently such modules exists only for Jira and RedMine. Unfortunately they are not scripts, but shared libraries written in C++. If you have C++ developers you can build your own link using Jira as example. For 3.0 branch we are considering Python and/or JavaScript extension support, but that's long way ahead anyway. You can also order custom development from our company. Best regards, Victor

Hi, we will release 2.2.4 with a fix this week. Best regards, Victor

Release 2.2.4 will contain improved Portech driver that should work with newer gateway versions. Best regards, Victor

Hi, you can use instance discovery to create same counters for each pool. You should be able to use agent list PDH.ObjectInstances(ASP.NET Apps v2.0.50727) Best regards, Victor

hi, after nxmc -clean the console start without problem thank you Andrea

opted to restore from backup. system back up and running again on v2.1.2

Hi, I have carried out some further testing and I receive these emails whenever the netxms core service is restarted. Am I safe to delete unsupported thread pools from the thread pool template?

Hello Victor , Thanks. Upgrade is planed for the near future. Anyway i changed the sync interval to 500 and now i get 1 alarm every hour. Still i am not sure how important is this and could i totally ignore the alarm in the event policy, so we don't receive the spam.

Hello Victor , Never registered a ticket, where i can do this ?

I am using netxms server v2.2.2 with web api v2.2.2. Grafana is v4.6.3 with netxms plugin version v1.1.0

Please check that group everyone has System Right "View all alarm categories". Node status is not affected by events. It can be affected by status calculation(properties of object), by default status is calculated based on child object status, alarms, and DCI's that have "Use this DCI for node status calculation" option selected.

All nodes in the region are automatically updated for word map and for Geo Map element on dashboard if root object is not selected. If root object is selected - only root object will be shown on the map.

@Tatjana: Thanks for the info and the workaround - that will help me until the update comes.

Hi, it's more question regarding database engine then NetXMS itself. If you have DB files then most likely you can restore them - you should contact somebody with expertise in your DB engine. As soon as you'll get working database NetXMS server should start. Best regards, Victor

That fixed it, thanks Victor!

This looks promising >>> ColumnFilter(ColumnFilterType.GREATER, 2) org.netxms.client.log.ColumnFilter@7092fb41 and then previous code becomes severityFilter = ColumnFilter(ColumnFilterType.GREATER, 2) re: 4acb63e12d19c7b1633ee803db2eabc5e02e3532 *UPDATED* Type of search in class ColumnFilter should be change to Enum type. fixes #1245 Thank you for contributing and documenting Ēriks Jenkēvics

Hi! There is currently no way around it. I have created an Issue on our tracker who`s progress you can follow on this link https://track.radensolutions.com/issue/NX-1400 Regards, Eriks

Sorry I just found the answer in the releasenotes. SMSeagle-Driver is implemented in 2.0.7.... to Victor: Thank You for Your Software! Best regards Georg

Hello, Eclipse version:  3.8.1 cant find the UI log 3 .java version: "1.8.0_161" Maybe i compiled the Netxms source wrong. Best regards, Markus