NetXMS Support Forum

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 ?

It's not possible to initiate node polling for a script. However, there is an option to change polling interval for a specific node, so you can set status polling interval to e.g. 10 or even 5 seconds for the problematic node. For this, create a custom attribute on the node with name
SysConfig:Objects.StatusPollingInterval
and value for the interval in seconds. Status, configuration, discovery, icmp, tpology, routing, autobind intervals are supported to specify that way.

Will check with developers, looks like it was not built. Meanwhile you can check previous version https://www.netxms.org/download/releases/4.1/nxmc-4.1.404-aarch64.dmg

There is a special format string supported:
%*s
It should display the value using multipliers.

https://www.netxms.org/documentation/adminguide/visualisation.html#adding-links-between-objects

Format strings are used when displaying values on maps.

In last values try enabling "Use multipliers" in context menu - it should automatically display in KBits or MBits, depending how big the number is. Or you can set "enable multipliers" in properties of the DCI.

In coming 4.2. version there will be option to fix multipliers to e.g. mbits and also option to display measurement units next to the value.

System.CurrentTime returns unix time in UTC time zone.
You can use System.TimeZone to get time zone.