Table functionality predates instance discovery. It was first attempt at handling multi-instance data, and it turns out to be quite complex in configuration and storage. Then instance discovery was added, and in my opinion it is much better approach for collecting multi-instance data, with tables have only limited use. Tables could be used when data really needs to be processed as a table - when you need to combine data from multiple columns and multiple rows (instances) for example. They also could be easier way to present multi-instance data on dashboards. Best regards, Victor

If you have it a s a node in NetXMS, then server will generate usual SYS_NODE_UP event. All you have to do is to create rule which somehow will filter SYS_NODE_UP eents only for such nodes. It could be filter script that check container membership or certain custom attribute. Best regards, Victor

Got it, thank you very much for explaining! [image: 2021-04-30 09_50_53-NetXMS Management Console - \[[email protected]\].png]

It's probably good idea to grant write access to whole \NetXMS\var - service may write other files there as well (most likely \NetXMS\var\images if you will add custom object images). Best regards, Victor

I have updated my test server to v3.8 using netxms-server-3.8.267-x64.exe This included switching from Java8 to Java OpenSDK13. My web browser timestamps are still one hour ahead of what they is supposed to be. Any solution would be greatly appreciated. Regards Doug [image: 2021_04_28_15_42_22_NetXMS_Timzeone_mismatch.jpg]

I got confused and thought that i had to ping the nodes with Icmp.ping({instance}) but i got it resolved with help from the telegram group with the following DCI ICMP.ResponseTime.Last That automatically pings the Primary IP in the node that you create it Thanks!!! NetXMS has a loooooonnggg learning curve because im spolied from PRTG. but im still working it out lol

Ah! Makes a lot of sense put in context of capability memory. Thanks for clarifying!

Just to double-check, can you show your output of netstat -aunp | grep 514 if you set debuglevel=6 in server config file and start server for a minute, do you see something like Listening for syslog messages on UDP socket in server log?

I'm using an older MBP with 10.15.7 so no retina resolution or anything too special. I can't run Big Sur on this laptop so no way to test if the OS makes a difference.

Please show screenshot of DCI configuratio and agent config file. Also, set agent debug level to 6, start agent, do force DCI poll on one of problematic DCIs, and show agent log file. Best regards, Victor

Hi, yes, I think you can delete c:\netxms\bin\jre. I have no idea why it was not working when installed into same directory. But we are going to merge server ad web UI installers into one anyway in version 4, so it should not be an issue after that. Best regards, Victor

@victor said in Radwin discovery failing: Just added two new configuration options for version 3.3: driver blacklisting and switching SNMP probing into one OID per request mode. Either one should fix this issue. Best regards, Victor This configuration option for SNMP probing resolved a tough issue I had been trying to resolve for a year.  I agree with jermudgeon... you rock, Victor!

Hi! These 40 EEP rules are there just for demonstration, in real production situation there might be more rules. Systems logic is the following Events are created when something happens. There are many source of events - DCI threshold violation/restore, node status change, log parser, SNMP traps, etc. Each event stores a number of parameter with it, e.g. DCI parameter name, threshold and actual values, etc. The number of parameters is different for different events. There are "event prototypes" where we can configure event name and user message, which can have macros (they are expanded when event is created). Events are processed by EPP. It could be that some events are not configured in EPP at all - in this case the event would be just recorded to event log, nothing else would happen. EPP rules can be very flexible - e.g. one rule can handle multiple events, it can work only for nodes in specific container (or except for some nodes/containers) - check conditions in EPP rule properties. EPP can create an alarm - it's sort of a bug-tracker built in netxms that shows list of current problems. It's also possible to terminate alarms automatically when some other event comes. In order for this to work alarms have alarm key, which is made of some text and macros. Macros can have, e.g. ID of node and ID of a DCI - see default rules 19 and 20. Now it depends on what exactly hardware checks do you need. Node connectivity and status of network interfaces is checked once per minute via status poll - if it's down, corresponding event will be generated. Other checks are usually configured as DCIs, e.g. cpu temperature, that DCI has threshold and an event specified in in DCI properties is generated on threshold violation. You can use generic SYS_THRESHOLD_REACHED event, but usually it's more convenient to have separate events for various groups of thresholds, e.g. something like DC_SERVER_TEMPERATURE, etc.

Hi! MIB file provides a more convenient way to select OIDs when creating DCIs (data collection items). If you right-click the node and go to Data Collection Configuration, you can create the DCIs for the information you need from that device.Each DCI has specific OID that provides collected values. You can also "Walk" a section of MIB tree to see which OIDs are available and what values they provide. In DCI properties there's Performance Tab page which allows to configure, if that DCI should be shown in the performance tab.

I increased max_locks_per_transaction from 64 to 512 in postgresql.conf after finding this errors in postgresql.log as you pointed me too Filip. After this change, nxdbmgr completed without problems - Thanks! Logs showed this: 2021-04-13 13:59:31.878 CEST [834154] usr_netxms@db_netxms ERROR:  out of shared memory 2021-04-13 13:59:31.878 CEST [834154] usr_netxms@db_netxms HINT:  You might need to increase max_locks_per_transaction. 2021-04-13 13:59:31.878 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT distinct(item_id) FROM idata_sc_30 2021-04-13 14:07:51.986 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.986 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT distinct(item_id) FROM idata_sc_30 2021-04-13 14:07:51.986 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.986 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT distinct(item_id) FROM idata_sc_90 2021-04-13 14:07:51.986 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.986 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT distinct(item_id) FROM idata_sc_180 2021-04-13 14:07:51.986 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.986 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT distinct(item_id) FROM idata_sc_other 2021-04-13 14:07:51.986 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.986 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT count(*) FROM tdata_sc_default WHERE tdata_timestamp > to_timestamp(1618315671) 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT count(*) FROM tdata_sc_7 WHERE tdata_timestamp > to_timestamp(1618315671) 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT count(*) FROM tdata_sc_30 WHERE tdata_timestamp > to_timestamp(1618315671) 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT count(*) FROM tdata_sc_90 WHERE tdata_timestamp > to_timestamp(1618315671) 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT count(*) FROM tdata_sc_180 WHERE tdata_timestamp > to_timestamp(1618315671) 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT count(*) FROM tdata_sc_other WHERE tdata_timestamp > to_timestamp(1618315671) 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT distinct(item_id) FROM tdata_sc_default 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.987 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT distinct(item_id) FROM tdata_sc_7 2021-04-13 14:07:51.988 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.988 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT distinct(item_id) FROM tdata_sc_30 2021-04-13 14:07:51.988 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.988 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT distinct(item_id) FROM tdata_sc_90 2021-04-13 14:07:51.988 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.988 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT distinct(item_id) FROM tdata_sc_180 2021-04-13 14:07:51.988 CEST [834154] usr_netxms@db_netxms ERROR:  current transaction is aborted, commands ignored until end of transaction block 2021-04-13 14:07:51.988 CEST [834154] usr_netxms@db_netxms STATEMENT:  SELECT distinct(item_id) FROM tdata_sc_other

Hi, it should work, although we didn't test it specifically on that version. Just report here if you will encounter any issues. Best regards, Victor

Pls execute "sh st" in Tools -> Server Console and show the output. Connect to postgres database and show the output of this query: select schemaname as table_schema, relname as table_name, pg_size_pretty(pg_total_relation_size(relid)) as total_size, pg_size_pretty(pg_relation_size(relid)) as data_size, pg_size_pretty(pg_total_relation_size(relid) - pg_relation_size(relid)) as external_size from pg_catalog.pg_statio_user_tables order by pg_total_relation_size(relid) desc, pg_relation_size(relid) desc limit 50;

With java-8 on Linux (openjdk-8-jre package in Ubuntu 18.04 LTS) I see the same problem as with java-11: The session key sometimes arrives delayed. I haven't tried the CipherTest with java-8.

Thanks. It was installed in usr/local/bin. removing those version now everything works fine. Thanks again.