NetXMS Support Forum

Hi,

I suppose that smtp.office365.com will require authentication, which is not supported by built-in SMTP sender. Easiest way is to install mail forwarder on same machine, configure NetXMS server to send mails to 127.0.0.1 and then forward everything to smtp.office365.com with proper authentication and encryption There are multiple SMTP relays available for Windows. Quick search reveals post for dealing with exact same problem (sending mail to office365 from software that can only do plain SMTP): https://xo.tc/simple-windows-smtp-relay.html

Best regards,
Victor

Hi,

this is bug NX-1964: https://track.radensolutions.com/issue/NX-1964. It is fixed in development branch, but not in version 3.8. In the meantime, create user and database manually and choose to initialize existing database in installation wizard.

Best regards,
Victor

It has to be done on per-node basis. However, you can use configuration poll hook script to automatically disable it on all or selected nodes. To disable routing table poll on all nodes add the following line to library script Hook::ConfigurationPoll:

$node->enableRoutingTablePolling(false);


Best regards,
Victor

Hi all!

We just published minor patch release for version 3.8 - 3.8.382. Changes since previous patch release:

- New method "enable8021xStatusPolling" in NXSL class "Node"
- Linux agent reports correct MTU for interfaces
- Data view created for report execution only if explicitly requested in report properties
- Fixed database upgrade issue on Microsoft SQL Server
- Fixed issues:
        NX-2048 (More information in System.Services table)
        NX-2052 (nxdbmgr cannot drop orphaned TDATA tables created by older server versions)

Best regards,
Victor

Hello, everyone.

Now we also post project-related news and articles on LinkedIn. Feel free to visit product page https://www.linkedin.com/products/raden-solutions-netxms/ or company page https://www.linkedin.com/company/raden-solutions/.

Please follow us there!

Hi,

just checked - fix was made in development branch but I forgot to merge it into 3.8 branch. Now it's done and next patch release should work correctly.

Best regards,
Victor

We just published new release 3.8.366. I have added tag release-3.8.366 as well as GitHub release.

Best regards,
Victor

Hi all!

We just published new patch release for version 3.8 - 3.8.366. Changes since previous patch release:

- Improved handling of partial or incorrect information in LLDP MIB (fixes topology building issues with Mikrotik devices)
- Fixed bug in discovering agent only nodes in remote zones
- Fixed interface object synchronization for physical links widget
- Fixed log name save for "Windows event log parser"
- Removed repeat count options from "Windows event log parser" and "Syslog parser"
- Added severity filter in Windows Event Log synchronization subagent
- Added event and alaorm on agent tunnel connection problems
- Fixed issues:
        NX-658 (Write poller statistics to debug log)
        NX-673 (Perfomance Tab - missing "Stacked" and "Translucent")
        NX-1510 (Special handling for user initiated agent restart to avoid node down or agent unreachable events)
        NX-1589 (Error in database initialization on MS SQL 2017)
        NX-1682 (SYS_SCRIPT_ERROR event is not happening when instance discovery filter script or transformation script has no closing bracket)
        NX-1705 (DNS Lookup on Status Poll Change)
        NX-1783 (When upgrading, agent installer asks for server IP, but does not update it in nxagentd.conf)
        NX-1952 (Update IP address on interface to address resolved by DNS for nodes without agent)
        NX-2040 (Periodically check if files used in file delivery policies are available on the server)
        NX-2041 (Filter by Object ID (in Object Browser's filter) should match exact ID, not substring)
        NX-2042 (Display EPP rule that created alarm in alarm log and alarm browser)
        NX-2051 (Allow storing SYS_DB_QUERY_FAILED events to event log)
        NX-2055 (Execution of some commands as agent actions may fail on Windows)
        NX-2057 (Add filtering by alarm status (acknowledged, resolved) in Alarm Viewer dashboard element)

Best regards,
Victor

Эксперементировал с 3.8 - ни разу не смог повторить. Единственно когда можно поймать такую ситуацию - если скрипт завершается с ошибкой - тогда интерфейс проходит фильтр. Но тут скрипт вроде как с ошибкой завершаться не должен. Еще возможный вариант - если интерфейсы видны по SNMP с теми-же индексами, но другими именами, которые пропускает фильтр.

Hi,

just added severity filter option to wineventsync subagent. Now for every reader you can specify SeverityFilter parameter, which is either bit mask  or severity level names separated by commas. Below are level names and their values:

Critical = 0x100
Error = 0x001
Warning = 0x002
Information = 0x004
AuditSuccess = 0x008
AuditFailure = 0x010

To accept only warning and error events:

SeverityFilter = 0x012

or

SeverityFilter = Warning,Error


This change will be included into next patch release.

Best regards,
Victor

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