NetXMS Forum

Tatjana Dubrovica

Hi,

That message is expected if the Oxidized module itself is not loaded — it's logged at startup once the server has scanned all loaded modules and found none providing a device backup interface.

The thing to check: adding the OXIDIZED settings section to netxmsd.conf only provides configuration values — it does not load the module. You also need to add the module to the load list:

Module = oxidized

So a complete config looks like this:

Module = oxidized

*OXIDIZED
BaseURL = https://oxidized.example.com
Login = user
Password = secret
DefaultModel = ios

Once the module is actually loaded, you should instead see:

[backup] Network device backup interface is provided by module OXIDIZED

If you've already got Module = oxidized in place and still see "not available", look at the lines just above it in the server log — the module reports the specific reason there, e.g.:

Oxidized integration module initialization failed (cannot parse module configuration)
Oxidized integration module initialization failed (invalid base URL) — the BaseURL must start with http:// or https://.

Starting the server with -D5 and checking the backup/oxidized debug-tag output will show exactly where it stops. Note that the Oxidized server being temporarily unreachable does not cause this message — that only produces a warning ("Oxidized server is not reachable, will retry on demand"), and the interface still initializes.

One more thing to confirm: the Oxidized integration was introduced in NetXMS 6.1.0, so make sure you're running 6.1.0 or later — on earlier versions the module doesn't exist.

Best regards,
Tatjana

Tatjana Dubrovica

Join the NetXMS Talks webinar TODAY, April 29, at 15:00 Riga time (EEST; UTC+03:00).

We'll walk you through how to set up OTLP metric support and talk at length about the usability improvements. Things like moving columns in table and tree view; creating new event templates directly from event selector; search in SNMP MIB explorer; easy view rearrangement in pin areas — and much, much more. Simply join here: https://events.teams.microsoft.com/event/36b18d1a-bedc-41f2-a88b-9dd42a95bdfd@c9cf5896-fa72-44b6-8d57-8742ad2b4e6e

Tatjana Dubrovica

Hi,

NetXMS actually has two web API options available:

New Web API - Enabled by adding Module = webapi to your configuration. This is the modern API that we're actively developing and expanding. While it currently has limited functionality, it includes a dedicated Grafana endpoint that's specifically designed to work well with the Grafana Infinity plugin and requires less data parsing/modification on the Grafana side.
Legacy Web API - The older netxms-websvc-VERSION.war service. This has more complete functionality currently but may require more data manipulation when using with Grafana plugins.

Since you're using the Grafana Infinity plugin, which can work with any web API, you have flexibility here. You can use either the new API, the legacy API, or even both depending on which is easier for your specific use case.
For new integrations, I'd recommend trying the new Web API's Grafana endpoint first as it will provide the smoothest experience with the Infinity plugin. However, if you need functionality that isn't yet available in the new API, the legacy service is still a viable option.

Question 2 (inputFields Format):

You're right that the documentation needs correction - I apologize for the confusion. The inputFields parameter should be formatted as a JSON object with key-value pairs, not as an array.
Correct format:

{
   "rootObjectId": 2,
   "queryId": 1,
   "inputFields": {
       "name": "value",
        "anotherField": "anotherValue"
    }
}

The code extracts these fields as a StringMap and supports multiple data types:

Strings (used as-is)
Integers (converted to string representation)
Floating-point numbers (converted to string representation)
Booleans (converted to "true"/"false" strings)

I'll update the documentation to reflect the correct format. Thank you for catching this issue!

Tatjana Dubrovica

Try "regex" instead of "useRegex" like:
{{host}}/objects?parent=4&class=interface&regex=true&name=%2F.%2AWI.%2A%2F

Tatjana Dubrovica

There is new blog post about Grafana/NetXMS integration. Maybe object queries might help you with interface display options.
Post:
https://netxms.com/blog/grafana-configuraiton-in-netxms

Tatjana Dubrovica

Hi. Happy that I helped you.

For DCI data please check this request:
https://netxms.org/documentation/adminguide/rest-api.html#dci-values

This is my example of configuration:
URL: http://10.5.5.111:8000/v1/objects/108/data-collection/183/history
UTL query params:
timeFrom $__from/1000
timeTo $__to/1000
Root: values

For status map I'm not sure how it can be created with help Ifinity plugin but check API that returns array with objects: https://netxms.org/documentation/adminguide/rest-api.html#get-multiple-objects-with-filters

The only option for maps as for now is to create link in NetXMS that afterwards will be used in IFrame plugin to insert it to the dashboard.

Tatjana Dubrovica

We just published second patch release for version 5.2. It addresses few important issues found in 5.2.1. Full change log is following:

- Fixed insert into table "notification_log" for TimescaleDB
- Improved client performance, by disabling alarm refresh if tab is not active
- Fixed missing DCI on network map links when new DCI's are added on alreay opened map
- Added job progress indication within views
- Fixed NXSL get web service document functions
- Added Grafana Infinity plugin web API endpoints

Fixed issues:
- NX-2733 (Do not show zone column in discovery targets if zoning is off)
- NX-2742 (Add NXSL node object method for enabling/disabling SM-CLP polling)
- NX-2751 (Delete scheduled tasks on node deletion)
- NX-2752 (Add ICMP response time jitter internal DCI for ICMP response statistic collection)
- NX-2754 (Separate error code for situation when TCP proxy is not enabled in agent config)
- NX-2755 (NXSL Interface utilization values returned as int, without decimal point)
- NX-2764 (Add PostgreSQL 17 support in monitoring subagent (pgi_stat_checkpointer))
- NX-2765 (Increase command length in package manager)

Tatjana Dubrovica

First endpoint also just works without Grafana plugin (it just provides data in human readable way).

Tatjana Dubrovica

Hi,
There are two options.

Our old Grafara plugin had it's own data point (that is still present and works):
/grafana/alarms
Call examples:
/grafana/alarms - gives object id to object name
/grafana/alarms?targets=[{}] - will return all alarms
grafana/alarms?targets=[{"alarmSource":{"id":108}}] - to get alarms for object with id 108
You can add as many elements with required object ids in array needed: [{"alarmSource":{"id":108}}, {"alarmSource":{"id":512}}, ...]

Another option is to add parameter resolveReferences=true to webapi/alarms request like: http://x.x.x.x:8080/webapi/alarms?resolveReferences=true
This parameter adds full information about alarm source node, source event name and names of users if possible to resolve.

Tatjana Dubrovica

Hi,
Yes you can use link styling script.
Here you can see example that I use for automatic integration tests: https://github.com/netxms/netxms/blob/master/tests/integration/src/test/resources/networkMapStylingScript.nxsl
Basically you should get STP status form $link.object1 nad $link.object2 (It will be NetObjects or Nodes connected by the link https://netxms.org/documentation/nxsl-latest/#class-node )
and set color with help of:
$link.setColorConfig(MapLinkColorSource::CustomColor, "#FF00FF");

NetXMS Forum

Global Moderators

Posts

Member List