NetXMS Support Forum

Hi,

Do the webapi support table DCI?

I get "Incompatible operation" when adding the table DCI to metrics.

Unfortunately, it does not support table DCI`s yet.

Regards,
Eriks

Is this still true, that table DCIs are still unsupported?

Here's the reason why I'm trying to use table DCI instead of instance discovery.

I'm dealing with a hardware vendor that has an unusual method of handling interfaces. It maintains a fixed interface table size (64) for PTMP radio operations. When a client radio attaches, it does so at the next available ifIndex.

In a situation where the client radio is detaching and re-attaching frequently, the ifIndex might change more rapidly than the server-InstancePollingInterval. I don't believe I can specify a custom InstancePollingInterval for a specific class of devices using a template.

So in order to track the stats of a client radio over time, instance discovery will not work as expected. Let's say I do instance discovery using MAC address, and the ifIndex of a given MAC address changes. A new DCI would be created and the old DCI would be queued for deletion. That would be incompatible with the goal of retaining statistics over a long period of time.

Our proposed workaround is simply to store the entire interface table, deleting rows where there is no client currently attached. This works as expected. We won't use NetXMS for visualization, however, as a given row/cell in the table can only be graphed (over time) by its row index, not by some chosen field (MAC address, in this instance).

Unfortunately without the Grafana connector working for tables, I'm scratching my head of how to get the data back out of the NetXMS database and display it correctly.

I'm open to other ideas -- and perhaps this is an opportunity for development sponsorship.