NetXMS Support Forum

Is it possible to force DCI poll from a NXSL script?

I collect DCI values every 15 minutes because they change rarely and have NSXL script object commands which change the monitored state (for example on/off a display screen or input source).
It would be useful to check/change the state of DCI immediately after the command execution and not to wait 15 minutes for the next polling cycle or force the DCI poll manually.

Check the NetXMS Server LogFile (/var/log/netxmsd by default).

It can be compiled form sources https://www.netxms.org/documentation/adminguide/installation.html#install-from-sources

I use zones. If the proxy node for a zone is down the nodes monitored via SNMP are in Unknown Staus, which is correct state, but the nodes monitored by ping only are reported as down and they have Critical Status.
What is worst that the down state of the node monitored by ping sometimes reported before the down state of the proxy, which suggests that the node is really down.

Is it possible to have Unknown Status for all nodes behind a proxy and not report the nodes as down in case the proxy node is down?

Authentication and encryption is used by SNMP v3 only.
SNMP v1 and v2c are "authenticated" by Comunity string.

There are Debian / Ubuntu Packages available, but for CentOS the server binaries must be compiled form the sources.

OK.

Technically is it what is monitored. From the human perspective is more logical to know how many Stanby servers are receiving the WALs therefore I've chosen the name PostgreSQL.Replication.Stanby. But it is name only the number is always the same.

The exact description of the pg_stat_replication table is: "One row per WAL sender process, showing statistics about replication to that sender's connected standby server."

The query counts the number of the rows in this table therefore it is number of senders (sender processes) on the monitored master server which corresponds with number of Standby servers on the other side receiving the data.

It is number of WAL senders which 1:1 corresponds with the number of Standby servers receiving WAL form this master server.
I don't know which name or description is better, but you are right that the parameter name and its description should be unified. This means either rename the parameter to "PostgreSQL.Replication.WALSenders" as you suggest or change the description of the parameter in the documentation to "Number of Standby servers".

The easiest way to solve it is to limit the remaining two REPLICATION SQL queries by minimal version MAKE_PGSQL_VERSION(9, 6, 0) .

It is strange. I've tested it with versions 12 and 9.6 both without WAL replication and I dint have this message.

Which version did you test it with? If >= 10 do you have the pg_monitor role assigned?

I need more complex condition for e-mail notification than simple send same email to the same recipients when the same alarm is generated.
The easiest way to achieve this is to use a NXSL script as the Event Processing Policy action. The only problem is that there is no possibility to send an e-mail from a NSXL script therefore I've added the NSXL function SendMail which allows this.

Please add the changes to the original repositories.
Code: https://github.com/netxms/netxms/pull/39
Documentation: https://github.com/netxms/nxsl-doc/pull/5

The documentation is not merged yet therefore I can correct the same typo in Table name there.  Should I do it or you will do it?

PostgreSQL is supported database but there was no subagent for PostgreSQL monitoring therefore I crated one.

The skeleton of the PostgreSQL subagent is similar to the Oracle subagent with some small changes.

I do not have Windows development environment and I didn't find any description what is needed therefore I've tested it on Debian only but I don't use any non-Windows specific features therefore I thing after adding of pgsql.vcxproj and pgsql.vcxproj.filters files it will be possible to compile the subagent on Windows and it will work.

Please add the agent and its documentation to the original repositories.

The changes are there as Pull requests.
Code: https://github.com/netxms/netxms/pull/38
Documentation: https://github.com/netxms/netxms-doc/pull/3

Looks like version 3.3.350 resolved the issue.
With this version of Web MC and Windows MC, the problem also does not occur with PostgreSQL DB.
Have you made any changes to solve this problem, or is it a coincidence?