NetXMS Support Forum

There's new asset management functionality coming in 4.4. There will be option to configure the fields and fill them in for each node. I think there should also be a search mechanism.
There's no mechanism to display these fields exactly on overview tab, but this could be achieved by a script DCI displayed there or by script macro called from commend field.

Also, when this will be implemented, these values could be put into built-in fields from configuration poll hook: https://track.radensolutions.com/issue/NX-2402

In current version you can either use a custom attribute or a push DCI (e.g. you can use script object tool to edit the value).
Searching could be done using "Find object" query, pls update if you need an example on this.

Should be fixed now, pls check most recent patch release

And what is in Columns in table properties?

Which Postgres and Timescale versions do you use?

If you are opening history from last values, it's opening 4096 last values there. But under three dots icon in upper right corner you can select arbitrary date range.

Retention period for DCI is set in Data Collection Configuraiton, by default it's 30 days

Yes, reporting process gets database credentials from netxmsd process. What is the value of DBServer= in your netxmsd.conf ?

MIB file and driver are two different things. MIB files just add textual oid and description in MIB browser.

Drivers exist for a limited number of devices (list of drivers is in the documentation: https://www.netxms.org/documentation/adminguide/snmp.html). Drivers do several things:
- provide some information that is not supported by generic driver, e.g. device geographical coordinates
- fix problems for devices that report something incorrectly under standard OIDs.

Are you having any issues with your Meraki devices under generic driver?

Починили, будет в следующем патч релизе

try running
yum update
yum install jansson


Do you want just to check that telnet port is open, or to issue some command and get result?

Listening IP can be change by setting java option nxreportd.bindAddress, simplest way to do it is adding -Dnxreportd.bindAddress=1.2.3.4 to JAVA_OPTIONS in /usr/bin/nxreportd

Port is currently hard-coded. If it's causing problems, it could be made configurable is some future patch release.

There is topology-based event correlation built in NetXMS. If we know, based on topology, that some node is behind a switch and this switch goes down, that for that node SYS_NODE_UNREACHEABLE event should get generated (SYS_NODE_DOWN is not generated, as we can not say for sure is that node down or up as there's no communication to it)

We plan to add audit for screenshots in next patch release.

Try running
systemctl daemon-reload
as it's suggesting. 

Then try
systemctl start netxms-reporting.service


systemctl status netxms-reporting.service
and
journalctl -u netxms-reporting.service
should provide information about status of the reporting service

Таймаут все-таки будет задаваться в миллисекундах, так что TLS.Certificate.ExpiresIn(mail.###.ru,443,,timeout=30000) может оставаться и в дальнейшем