NetXMS Support Forum

Great analysis, thank you!

Forwarded to developers. 

I mentioned installation docs in relation to how install the web UI. And, by the way, public maps are also possible with desktop UI, as it's possible to start it from command line, specifying authentication token and map id, but it's probably quite rare use case.

Now more details on the configuration:

Performing "Enable public access..." on a map actually does two things:
- issues/gets authentication token for user "anonymous"
- adds read access right for "anonymous" user to given map

This, however, does not give access to objects present on map to user "anonymous" - the map will be displayed, but objects will have no names and will have question mark instead of object icons.
So we need to fix that and there's access right created specially for that - Delegated read. It allows access to a limited subset of object properties (basically name and status) and only if that object is referenced in a map to which "anonymous" has read access. So you can just give Delegated read to "anonymous" for Infrastructure services (and may be also to Entire Network, if your map displays subnets).

This should be it for configuration, pls give an update if this works for you. We plan to update documentation with this info.

These capital letters - are these ASCII characters or from some specific alphabet?
What VNC server are you using, on what OS?

Hi!

You need web UI for this feature, pls see installation manual here: https://www.netxms.org/documentation/adminguide/installation.html#web-management-client

Password can be specified in node's properties. 

But the issue with capital letters - is it web or desktop client?

First of all, upgrade to the latest version is recommended, as there was a but with connectivity detection at some point.

The idea is that connection goes through netxms agent. It can be either agent on the system where vnc is running (in this case vnc should accept connections from 127.0.0.1), or it can be agent that runs along with netxms server.

So you need to add
EnableTCPProxy = yes
into configuration file on one of the mentioned agents, restart that agent and then try to run configuration poll on that node again.

In many cases it's better to use regular DCIs and instance discovery to automatically creation and removal of them.

Yep, perfectly valid approach, nice to hear that it all worked.

We were not able to replicate the original issue so far, can you please check what encoding your original database has. If you connect to the db using psql, issue

\l+
command there, it should list the databases, we are interested in value in Encoding column.

In all places where macros are supported you can use %[script_name] macro. Script with specified name should be in script library. In that script you can access table value (it will be object of class table - https://www.netxms.org/documentation/nxsl-latest/#class-table) and get value of specific cell from it.

When developing your script, you can run it via Execute Script on the node where you have your table DCI. However, there's a difference - when script is ran automatically on threshold violation, variables $event, $dci will be set - you can use these to get parameters of event or id of the DCI. When running via Execute Script, these variables will not be set, so you need to modify your script slightly.

Here's a brief example:
//t = GetDCIValue($node, $dci.id); // for use in script called on threshold violation
t = GetDCIValue($node, 13741); // for testing - use via Execute Script on node

//row = $event.getParameter(4); // for use in script called on threshold violation
row = t.findRowIndexByInstance("/sys"); // for testing

return t.get(row, 1);
You can give some more information, what exactly cell of your table you want to extract, then I can give some more examples.

Hi!

This is not implemented from the GUI, the idea was that these records are an undeletable log. However, editing is present (may be only by admin users, I am not sure).

You can delete records from the DB, check this table: https://www.netxms.org/documentation/datadictionary-latest/#t-maintenance-journal

Something strange happening here. Can you connect to the DB using postgres client and show output of

\d win_event_log

on the old and new db?


I am not sure, if the issue is related to normal postgres and timescale difference, but you can try migrating the DB in postgres format and then converting it (nxdbmgr now supports in-place conversion to timescale)

Quote from: rainerh on January 09, 2025, 05:57:21 PMconsole output:
root@pve110:~# zpool status rpool | grep -E "raid|mirror" | awk '{print $2}'
ONLINE
root@pve110:~# zpool status datastore01 | grep -E "raid|mirror" | awk '{print $2}'
ONLINE

NetXMS output:
zpoolStateRAID(datastore01) =   raidz2-0                                      ONLINE      0    0    0
zpoolStateRAID(rpool) =   mirror-0                                          ONLINE      0    0    0

looks like awk part did not work at all. How is it specified in agent config file, could be some issue with quotes.
You can also do something like this:
zpool status datastore01 | grep -E "raid|mirror" | tr -s " " | cut -d" " -f 4Another option is to have all the command in a separate .sh file and just call that.

For zpool_influxdb, may be adding --no-histogram will print less lines. Also looks cumbersome to parse, you can try something like this:

zpool_influxdb | "vdev=root/raidz-0\ " | cut -d',' -f 3 | cut -d'=' -f 2
If you can extract names of HDDs from it's output, you can use that as external list (https://netxms.org/documentation/adminguide/agent-management.html#externallist) - this way you could create DCIs automatically for HDDs.

By the way, can you show what ouput zpool_influxdb command produces on your system? It's written that it has machine-readable format, but I was not able to find an example of output.

Hi,

I did a quick check - looks that it works in 5.1.1 and does not in 5.1.2. Will check with developers.

Currently you can configure something like
ExternalMetric=zpoolState:zpool status | grep "state: .*"
in agent configuration file. This will add zpoolState metric, which would return e.g. " state: DEGRADED", your add something after grep to cut "state: " part.
It's also possible for the metric to have a parameter, which will be given to the executed command
ExternalMetric=zpoolState(*):zpool status $1 | grep "state: .*"
this way you can get value of zpoolState(POOL_NAME)


In the future - ZFS v 2.3. will support json output (https://github.com/openzfs/zfs/issues/2626). And in v. 5.2. of NetXMS we will have new external parameter mechanism that parses json, xml and plain text, so all that can be used to get zfs state.