NetXMS Support Forum

Hi,

object queries are for a bit different purpose. They are for selecting objects. Script in query is executed for each node and should return true or false. You can include additional fields into resulting table, but number of columns will be static.

One possible solution for your task is to create script table DCI on one of the nodes (could be NetXMS server itself) that will collect data from other nodes and populate the table. Then you can put content of that table on dashboard. You can choose "do not store" option for that table DCI to avoid keeping unnecessary information in database. Script for such DCI could be following:


result = new Table();
result->addColumn("sysName", DCI::STRING, "System Name", true);
result->addColumn("description", DCI::STRING, "Description", true);
result->addColumn("value", DCI::FLOAT, "Value");

for (node : GetAllNodes())
{
   for(dci : FindAllDCIs(node, null, "*latency*"))
   {
      value = GetDCIValue(node, dci->id);
      if (value != null)
      {
         row = result->addRow();
         result->set(row, 0, node->snmpSysName);
         result->set(row, 1, dci->description);
         result->set(row, 2, value);
      }
   }
}

return result;


Best regards,
Victor

It looks like file is actually transferred, but sender just don't wait enough for final confirmation, which is probably take more time due to target system load. I have increased wait time for confirmation on file upload, hopefully it will help. Change will be included into next patch release.

Best regards,
Victor

Hi,

yes, this can be done with filtering script. You can get "time" object with gmtime or localtime functions and then check it's properties. To match events only between 00:00 and 08:00 you can use the following script:


t = localtime($event->timestamp);
return t->hour >= 0 and t->hour < 8;


This will not include 8:00, if you need it you should add additional condition that checks for 8:00 exact time.

Best regards,
Victor

Yes, from now on we will put lightweight tags on each release. We will also experiment with GitHub releases, will see how it will work.

Regarding maintenance and documentation - we are ok to include Docker based installation into installation guide. Do you mind moving source files for Docker deployment into separate repository under netxms project on GitHub?

Best regards,
Victor

Hello!

You can turn on TLS in driver by adding

DBDrvParams = enforceTLS=true

to netxmsd.conf. User authentication with X.509 certificates is not supported.

Best regards,
Victor

We decide that we do official packaging when planned features and fixes are ready. As third number in version is generated automatically from git commits it cannot be predicted. i think that lightweight tags is a way to go, we will just put lightweight tag whenever we do deb publishing. We can agree on certain format for those tags so you will be able to distinguish between deb releases and other tags.

Best regards,
Victor

If acknowledged alarms will be removed from active alarm list how they would be different from terminated? Idea is that alarm browser shows you all problems that are not solved yet. If your business process requires only two states, you can simply terminate alarms instead of acknowledging them.

Best regards,
Victor

Hi,

please use this link for upload: https://cloud.radensolutions.com/s/88sd5KwD2SaAewE

Best regards,
Victor

Hello,

I think we can use lightweight tags for marking release versions. Also, you can use this simple script to switch to specific X.Y.Z version within source tree: https://github.com/netxms/netxms/blob/master/tools/switch_to_version.sh

Best regards,
Victor

It should be on NetXMS server.

Best regards,
Victor

Then it's likely bug in agent. Try to read multiple values directly from agent with nxget:

nxget -i 1 node_ip 'Net.Interface.BytesIn64(1)'
nxget -i 1 node_ip 'Net.Interface.BytesIn(1)'

and check if output looks valid or not (replace node_ip with actual IP address).

Best regards,
Victor

Hi,

you can access all alarms via "Entire Network" or "Infrastructure Services" objects. FOr example, the following script will print all alarm messages:

for(a : FindObject(1)->alarms)
{
println a->message;
}


Best regards,
Victor

It is delta value (average per second). As raw value does not change delta is always 0 - perhaps there is no traffic on interface?

Best regards,
Victor

Hi,

looks like those tdata tables are from very old version, where we did use foreighn keys and related tables. It is safe to use DROP .. CASCADE on tdata tables. You can do that manually for each listed table, and next patch release will use DROP CASCADE for tdata.

Best regards,
Victor

Quote from: wuwei on May 07, 2021, 01:25:44 PM
Hi Victor,
it seems that binary packages for debian/ubtuntu repos at http://packages.netxms.org for this patch release have not been generated.
Is it correct? Are these repositories still maintained?

Thank you.

Hi,

new version should be available in repository now.

Best regards,
Victor