NetXMS Support Forum

You can make transformation script like this for your packet loss DCI:

if ($node->state & NodeState::Unreachable) abort;
return $1;
"abort" keyword will cancel collection of datapoint. You can also use "return null" instead of "abort" - this will put the DCI into data collection error.

Looks good. There's a small chance that SNMPGetValue may return null (e.g. communication gets broken exactly when these requests are made), so you may want to check diskSize and diskUsed for null.

Are you using "old" (nxmc-legacy-4.2.395.war) or "new" (nxmc-4.2.395.war) web UI?

Yes, there is some encoding issue (also with µ). Should be fixed in next patch release.

It's possible to make script DCI that would take values from other DCIs and do the calculation. But if you don't need to keep the intermediary values, they you can do everything just in one DCI.

Create s script in script library and Script DCI that uses that script. Check this example for script contents: https://www.netxms.org/documentation/nxsl-latest/#func-snmpgetvalue

It's a bug introduced in 4.2. It affects syslog and windows event log processing in fields "source" and "tag".

Bug is fixed, will be in next patch release. 

Meanwhile you can put * character in source, it should work that way.

Hi!
There's a bug in recently released 4.2 - DefaultExecutionTimeout is not taken in account. This will be fixed in next patch release.

Try settingExternalMetricTimeout - it should affect external tables and external metrics.


Also, external tables now have a new, background mode of operations - command is called regularly, it's output is cached and instantly returned to server when it requests the table. See for more info: https://www.netxms.org/documentation/adminguide/agent-management.html?highlight=externaltable#externaltable

Yes, we are moving toward term "metric" in the UI (and also in NXSL at some point)

Yes, normally previous functions should have remained as deprecated for some time, but this time it did not happen. We've updated documentation on the current situation.

Currently not possible in the UI. You can just run a select of script_library table in the database.

Also there's a lot of other places where scripts can exist - in EPP, transformation scripts, auto-bind scripts and so on, they are in different tables in the DB.

The request should be:

Request type: POST
Request path: API_HOME/pushData

It's possible to use one of two data formats:

1) If you need to send just one DCI:

{
      nodeId : 10,
      dciId : 20,
      value : "Value"
}


2) If you are sending data for multiple DCIs

data :
[
  {
      nodeId : 10,
      dciId : 20,
      value : "Value"
  },
  {
      nodeName : "Node name",
      dciName : "DCI name",
      value : "Value"
  }
]


You can use both names and IDs of objects and DCIs.

If both name and ID are set, ID has priority

Yes, this relates both to old and new gui.

On agent side this is configured via ExternalCommandTimeout configuration file parameter. This parameter was added recently, so it's better to install 4.2 version of the agent (it can work with 3.x and 4.x server).

In previous versions of agent it was controlled by ExecTimeout configuration parameter that controlled both action and external parameter timeout.

This is about to happen after a few months at least.

Template Graphs will be replaced by new dashboard feature that allows to use dashboard as a template on any node.

Instead of conditions it's possible to use e.g. scripted DCIs. If conditions are somewhat valuable thing for you, please drop a message so we can discuss your use case.

А при отправке большого количества уведомлений ошибка такая же, curl_easy_perform() failed ?