NetXMS Support Forum

Hi,

from UI you can open history view, select desired data range, and export data to CSV file. Or you can automate export (and do much more complicated things) using nxshell script. It's Python scripts with access to NetXMS API. Some examples can be found here: https://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations

Best regards,
Victor

Да, в самом Windows. Вроде называлось так "encoding used by non-UNICODE programs". Ну и возможно что настройки правильные, просто надо при просмотре лога выбрать правильную кодировку.

Скорее всего это русские буквы. Если Windows русский, то названия счетчиков тоже по русски пишутся. Лог файл пишется в той кодировке, которая выставлена для non-UNICODE приложений.

Hi,

I suggest to either truncate alarms table completely (but you will lose all alarm history) or delete alarms older than certain time before starting netxmsd. You can do this by running query

DELETE FROM alarms WHERE last_change_time < ?;

Replace placeholder with actual time stamp. It is in UNIX time format, you can use this calculator to get value: https://www.epochconverter.com/.

Best regards,
Victor

Actually it is supposed to be 63 characters, so looks like a bug. We will take a look at it.

Best regards,
Victor

Configuring ODBC is not related to NetXMS itself, so it is not covered in manual. There are lot of information on how to configure unixODBC to work with MS SQL, for example: http://help.interfaceware.com/kb/904

On NetXMS side, you may need to add to your netxmsd.conf the following line:

DBDrvParams = unicode=false

but only do that if you'll be unable to connect without it.

Best regards,
Victor

Hi,

if you are using ODBC driver then database server is in fact ODBC data source. Are you sure that you have configured UNIX ODBC data source correctly?

Best regards,
Victor

Hi,

most of libraries have prefix nx (like libnxagent), so searching only for "ne" may not be enough. I suggest to check with ldd that agent didn't pickup any "nx" prefixed library from /usr/local/lib.

Best regards,
Victor

Hi,

it could be added in then future. Sounds interesting, it's just a matter of time required to implement and available resources. I'll add it to feature requests in our tracker. And of course if there will be somebody willing to sponsor development of such add-on we can do it upon request.

Best regards,
Victor

Agent comes with VC++ 2017 runtime packaged - this is why it works on Vista 32-bit. It is supposed to work on XP too. I'll check myself on some XP machine. So far I suggest to stick with agent from 2.1 branch for Windows XP.

Best regards,
Victor

As far as I know you can install 64 bit native client on the same machine alongside 32 bit client (but I could be wrong, I'm not an expert on SQL Server at all).

Best regards,
Victor

We don't use .NET, only Visual C++ runtime. What if you install Visual C++ 2017 runtime on such machine?

Best regards,
Victor

I finally assign one of our developers to this task in late December (as part-time task). Hopefully we will get at least a prototype soon.

Best regards,
Victor

It's actually visible on screenshots that aliases are empty. Please contact me directly so I can debug this issue.

Best regards,
Victor

Hi,

what is your settings for using interface aliases? And what are aliases for those interfaces?

Best regards,
Victor