NetXMS Support Forum

That's right, .nxms folder is for the "old" client, but since in v 4.x "new" client was introduced, it stores files in .nxmc4 folder

Seems to be too much requests, but could be legit, as NetXMS requests a lot of information via snmp.

If you are using unencrypted snmp communications, please capture network exchange dumps. Then we can see specific OIDs that are being requested.

If your server is on Linux, use this command to capture to file in wireshark format:
tcpdump -s 0 -w snmp-exchange.pcap host = DEVICE_IP

On Windows you can use Wireshark for that.

Different colors and time frame - that's definitely a bug, I've created an issue for that: https://track.radensolutions.com/issue/NX-2559 , you can subscribe to it to get notification when it's fixed.

Zooming - yes, it's currently absent, there are thoughts to make this a bit differently: https://track.radensolutions.com/issue/NX-2560

Historically there are two approaches to WIndows Event Log - Log Synchronization mentioned by Tatjana and Log File Monitoring. First one has the benefit that whole text of events is stored on the server. Second approach does not require to modify agent configuration file - configuration is uploaded via policy, events are generated by agent. Let me describe it in more details:

Under "Templates" create a new template. Third tab in the template - "Agent Policies". Create a new "Log Parser" policy, give it some name. In the policy click "Add file" and put
*Security
into File path field. This means that Windows security log will be parsed. Add a new rule. You can filter by Level, ID and Source as well as by log entry text ("Matching regular expression" field, it parses all lines of the entry as one long string). 

For testing you can use (.*) as the regex - it will capture whole message as parameter of the generated event - if you double-click an entry en event log, you'll see all the information.

I am not sure about correct event ID, but it seems that 4624 is capturing logon events, so regex .* and ID 4624 will capture these events. You need to specify an event in the rule.

Create event template, this defines what parameters are included into message field. E.g. the following in the message field:
User %<variable6> was successfully logged on (Event ID: %<eventId>, Severity: %<severity>, Network Address: %<variable19>)

Try netxms-agent-mariadb, it should be same as MySQL

We don't have a list in the documentation, just some chapters mention that specific subagents are needed, e.g. Network Service monitoring requires netsvc.
If you check list of available packages with dnf, you'll see them all:

root@localhost:~# dnf search netxms-*
Last metadata expiration check: 1:38:40 ago on Wed 31 Jul 2024 10:42:43 AM EEST.
=================================================================================================================================================== Name Matched: netxms-* ===================================================================================================================================================
netxms-agent.x86_64 : NetXMS agent and extensions (subagents)
netxms-agent-asterisk.x86_64 : Agent extension (subagent) for monitoring Asterisk
netxms-agent-asterisk-debuginfo.x86_64 : Debug information for package netxms-agent-asterisk
netxms-agent-debuginfo.x86_64 : Debug information for package netxms-agent
netxms-agent-java.x86_64 : Agent extension (subagent) for running java-based monitoring providers
netxms-agent-java-debuginfo.x86_64 : Debug information for package netxms-agent-java
netxms-agent-mariadb.x86_64 : Agent extension (subagent) for monitoring MySQL/MariaDB databases
netxms-agent-mariadb-debuginfo.x86_64 : Debug information for package netxms-agent-mariadb
netxms-agent-mqtt.x86_64 : Agent extension (subagents) for communicating wiht MQTT brokers
netxms-agent-mqtt-debuginfo.x86_64 : Debug information for package netxms-agent-mqtt
netxms-agent-oracle.x86_64 : Agent extension (subagent) for monitoring Oracle databases
netxms-agent-oracle-debuginfo.x86_64 : Debug information for package netxms-agent-oracle
netxms-agent-pgsql.x86_64 : Agent extension (subagent) for monitoring PostgreSQL databases
netxms-agent-pgsql-debuginfo.x86_64 : Debug information for package netxms-agent-pgsql
netxms-agent-vmgr.x86_64 : Agent extension (subagents) for monitoring virtualization platforms
netxms-agent-vmgr-debuginfo.x86_64 : Debug information for package netxms-agent-vmgr
netxms-base.x86_64 : Common NetXMS libraries and tools
netxms-base-debuginfo.x86_64 : Debug information for package netxms-base
netxms-client.x86_64 : Integration and diagnostics tools for the NetXMSX server.
netxms-client-debuginfo.x86_64 : Debug information for package netxms-client
netxms-dbdrv-mariadb.x86_64 : ...
netxms-dbdrv-mariadb-debuginfo.x86_64 : Debug information for package netxms-dbdrv-mariadb
netxms-dbdrv-odbc.x86_64 : Middleware for interfacing with any compatible database engine via ODBC
netxms-dbdrv-odbc-debuginfo.x86_64 : Debug information for package netxms-dbdrv-odbc
netxms-dbdrv-oracle.x86_64 : Middleware for interfacing with Oracle database engine
netxms-dbdrv-oracle-debuginfo.x86_64 : Debug information for package netxms-dbdrv-oracle
netxms-dbdrv-pgsql.x86_64 : Middleware for interfacing with PostgreSQL database engine
netxms-dbdrv-pgsql-debuginfo.x86_64 : Debug information for package netxms-dbdrv-pgsql
netxms-dbdrv-sqlite3.x86_64 : Middleware for interfacing with SQLite3 database engine
netxms-dbdrv-sqlite3-debuginfo.x86_64 : Debug information for package netxms-dbdrv-sqlite3
netxms-debuginfo.x86_64 : Debug information for package netxms
netxms-debugsource.x86_64 : Debug sources for package netxms
netxms-java-base.x86_64 : Common java libraries used by the NetXMS components
netxms-java-base-debuginfo.x86_64 : Debug information for package netxms-java-base
netxms-reporting.x86_64 : JasperReports-based reporting server integrated into NetXMS
netxms-server.x86_64 : Monitoring server core
netxms-server-debuginfo.x86_64 : Debug information for package netxms-server

netxms-agent-* are different subagents, netxms-dbdrv-* drivers for various databases (used both by server for it's database and by agent to perform queries to databases, netxms-base has common things needed both for server and agent, netxms-reporting is the reporting engine, that's basically it

Hi,

That's correct, 5.0.6 is the newest version of NetXMS.
The latest postges on Fedora 40 is 16.3 (which should get installed when installing postgresql-server), please try with that version.

Did you use regular Postgres or Timescale when initializing the DB?


P.S. You can use
journalctl -u netxms-server.service
to get log of just NetXMS process. Or, alternatively, you can configure logging to file in /etc/netxmsd.conf

The software is split into several packages, to avoid pulling dependencies for things that are not needed. MySQL subagent should be in netxms-agent-mysql package, and you also might need netxms-dbdrv-mysql.

Должно быть в самом последнем релизе

By NET-SNMP you mean that these devices are computers and net-snmp package is used to provide snmp daemon? Or netxms snmp driver is GENERIC?
Can you provide screenshot of Overwiew page for such device? What are these devices, what producer, what models?

One more question for clarification - in node properties -> Communication in Primary host name field you have IP address or hostname?

Looks like documentation is not clear on this - this metric is collected from NetXMS agent. 

Origin should be set to "NetXMS Agent". 
This DCI should either be on the node where an agent is running, or node with agent should be specified in "Source node override" field. 
Agent that is used should have netsvc subagent enabled.

1. On what exactly version of NetXMS this is happening? 
2. Whare are the capabilites of such node (visible on the Overview page)
3. Do you have network discovery enabled? Can you show screenshot of network discovery configuration?
4. Does NetXMS obtain mac addresses for these nodes (visible in Interfaces tab of node)
5. Do these machines have static IP or they get IP address via dhcp?
6. In configuration->Server configuration what are the values of the following parameters:

Objects.Nodes.ResolveDNSToIPOnStatusPoll
Objects.Nodes.ResolveDNSToIPOnStatusPoll.Interval
Objects.Nodes.ResolveNames
Objects.Nodes.SyncNamesWithDNS

Ability to bind subnets to containers is a rarely used thing and was forgotten when features were moved to the new client. I'll get back when I have some information from developers on this.

It's kinda a rare case to use color zones with values exactly on the edge of zones. The logic seems to be, with your settings, that:
left red is from 0.0 till 1.0 (including it)
left yellow is from 1.0 (excluding) till 2.0 (including)
but on the right it's opposite and red stars from 3.0 (including) and till the end of the dial, which is again 3.0

Just use 3.01 for right yellow and red zones