Hi! Would you like to know how to apply settings to send messages via google chat? thanks in advance.

hello, Sudanov It worked . Thanks ...

Many many thanks, bit smarter about NetXMS again.

It all depends on the user under which netxmsd process is running. You can see that by issuing ps aux | grep netxmsd If netxms is installed from packages on Debian, it install systemd startup script and from there it runs under root.

Yes, it's so for some historical reasons. Will stay so in 3.x versions, but hopefully will be reworked in 4.0

Hi, you can create external parameter that will execute this command and return security patch number, something like ExternalParameterShellExec = ExchangePatchNumber:pwsh -Command "& { Get-Command Exsetup.exe | ForEach {$_.FileVersionInfo} }" in nxagentd.conf (not sure about exact PowerShell syntax, but you should get an idea). Agent will provide new metric ExchangePatchNumber that should return output of given command as value. Best regards, Victor

Thank you for the detailled reply. I will need to read it several times and then try it!

oh that's really cool then! Didn't know that. Sorry when I heard desktop app I assumed it had to be on the server direct. I'll take a look. I appreciate the help!

Я все сделал как в документации,  все отработано на ОК. По документации нужно сконфигурировать файл jetty-ssl-context.xml. После установки Web interface (windows installer) такого файла нет. Подскажите дальнейшие шаги.

Thanks a million, The sample report is showing fine. Now I need to find my way in creating new reports

NXSL tried to interpret the HEX as string and taked first 00 as end of string. Try this way: transport = $node->createSNMPTransport(); if (transport != null) {   println transport->get(".1.3.6.1.4.1.4196.1.1.5.2.100.2.1.4.0")->printableValue; }

There are several approaches here you can create two DCIs - one for pinging with short packets, another for big packets. In a third, script, DCI you can read last collected values of these pinging DCIs GetDCIValue($node, FindDCIByName($node, "DCI_NAME")) and make decision. This script DCI can return e.g. 1 or 0 and have a trigger that creates event. You can have a script DCI that poll several agent parameters at once. $node->readAgentParameter("Icmp.Ping(8.8.8.8, 1000, 1500)") It's not recommended for such script DCI to run for very long (longer then 3-5 seconds) as having many such script DCIs may occupy data collection pollers for too long and cause problems with data collection. For timeout Icmp.Ping returns value of 10000.

As answered in Telegram support channel: Increase memory limit in nxmc.ini (-XmxNNN, where NNN is the limit)

Glad to hear it is working, mark topic [SOLVED]!

Hi, Filipp. I got it. This Bug message appeared when I opened the Syslog parser window from the Configuration menu. I hope this helps. [image: syslogparser.png]

DRBD collector is for https://en.wikipedia.org/wiki/Distributed_Replicated_Block_Device , this may not be present on a system. So this is not an error that would be preventing server connecting to agent. check output of netstat -lptn on agent's system. It should show something like tcp        0      0 0.0.0.0:4700            0.0.0.0:*              LISTEN      6347/nxagentd      that would mean that NetXMS agent is listening on port 4700. From another machine you can try telnet agent_machine_ip 4700 to see if it's possible to establisth network connection to agent. In netxms console try right-clicking the node and performing Configuration Poll (full).

In NetXMS every agent can operate as a proxy, collecting data from other agents, via SNMP, etc... If your locations have overlapping IP addresses, then you need to use zones. Event if addresses are not overlapping, it's convenient to use zones, as you can set proxies in zone properties and nodes added to this zone will be monitored via there proxies. Proxies accumulate collected data if there's no connection to central server. Proxies have high availability mechanism - if more then one proxy is configured on a zone, proxies will extablish p2p communication between them to decide which proxy is collecting data. There's a lot in admin documentation https://netxms.org/documentation/netxms-admin.pdf , but some things may be not yet covered, so feel free to ask questions.

Having some TrueNAS myself, have you installed the Agent or did you carry on just using SNMP?

Another option is to generate special event from NXSL script, and in event processing policy execute restart action for that event. Best regards, Victor

thank you very much for your support just to answer your question, it's postgres: psql (PostgreSQL) 12.7 (Ubuntu 12.7-0ubuntu0.20.04.1)