NetXMS Support Forum

При отправке е-мейла из экшна сейчас html не поддерживается. Есть мысли переделать отправку е-мейлов объединив их с notification channels, тогда наверняка будет добавлена и возможность слать html.

Но, в 3.4.284 была добавлена NXSL функция
SendMail("[email protected]", "My subject", "My text", false);
и вот она умеет слать письма в html, если последний параметр поставить в true.
Можно сделать script action и через него слать е-мейлы.

Can we possible get remote access to your netxms server? If yes, please send a message to [email protected]

If no, please collect server log at debuglevel = 8. Start console during the log and open the graph and history of a DCI.
You can change debut level on the fly:
nxadm -c "debug 8"
will change it

nxadm -c "debug"
will print current debug level

Если это то значение, по которому срабатывает threshold, то посмотрите в Event Configuration параметры события SYS_THRESHOLD_REACHED - там где-то есть текущее значение.

Если же просто нужно получить значение какого-то DCI, то это можно сделать из скрипта:
GetDCIValue($node, FindDCIByName($node, "DCI_NAME"))

Hi!

There is no such thing in netxms - we do no cache the password entered by user so we do not have it anywhere after user logs in. And it seems to be not good idea from security viewpoint to keep any passwords plaintext and enter them somewhere.

Let's try to get historical data from java API using nxshell - this way we could see if the issue is with the server or the GUI.

You will need to recompile to get nxshell, for that please run
export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64
add then run your ./configure command with the following keys added:
--with-jdk=/usr/lib/jvm/java-11-openjdk-amd64 --with-client

make & make install should produce nxshell executable in your bin folder.

Then make a file, say collected_data.py
from java.util import Date
data = s.getCollectedData(200, 2000, Date(Date().time - 60 * 60 * 1000), Date(), 100, HistoricalDataType.valueOf('PROCESSED'))
print data
for v in data.values:
    print v.timestamp.toString() + " = " + str(v.value)
replace 200 with a node ID and 2000 with a DCI ID.

Then run the following (-u username, same as in management console and -P is the password):
nxshell -H 127.0.0.1 -u admin -P ""  collected_data.py
and share the output. This script script should return datapoints for a give DCI for last hour.

Something in cluster operation seems to be broken. We will check the code.

Did you try to open the dci graph / history during the duration of that log?

One more thing to have a look at - console writes it's own log file in user's home folder in \.nxmc\data\.metadata
Can you share what you have there?

Ну да, если нода не смогла ответить по конкретному SNMP OIDу, то в model получалось null.
Там просто проверку можно добавить, аналогично как проверялось что SNMP транспорт создался:
if (model == null)...

Does it happen that there are no historical data for all DCIs in system, or just for some DCIs?

А как именно ругается? может быть SNMPGetValue не срабатывает и model получается NULL ?

Yes, in case of tunnel NetXMS does not store the IP address. The thing is that IP address from which the tunnel connection arrives is not necessary the IP of the node - it can be a NAT, etc. And if we take list of interfaces for a node - the could be several interfaces and we don't know which one is primary.

You could get list of interfaces via NXSL script - the script should filter out loopback interface and if there are several interfaces - select one of them. There is currently no hook script on tunnel connection, you can run your script from configuration poll hook.

Here's an example script that prints list of interfaces:
for(i : $node->interfaces)
{
  println i->name;
  for(a : i->ipAddressList)
    println "   " . a->address . "/" . a->mask;
}

Also, there's a system event SYS_TUNNEL_OPEN - this event occurs when the tunnel is established, in the context of that node. So you can create a rule in EPP and run some script from there.

It's not possible to update node's IP address from script, but you can create a cusome attribute on node and keep IP address there.

As an option you could look into script thresholds - this way you could check all you need with a help of NXSL script and generate event only when there is a problem.

What's the operating system where the client is running? What's client version? Is it downloaded from netxms web site?
For testing - may be you could try the client on another machine, preferrably on a different OS.

As an experiment - can you try to a different configure command:

./configure prefix=/opt/netxms-master --with-server --with-mariadb --with-mariadb-compat-headers --with-agent