NetXMS Support Forum

Hi community,

first of all, proms to the developers - I am implementing NetXMS now for around a month and the last Network Management system I loved that much was CA Spectrum. Thanks for the good work!

Now, I think I discovered a bug.

I am implementing a DCI with a Web Service and I am using the example here (from the bottom):
https://www.netxms.org/documentation/adminguide/web-services-monitoring.html

I try to enumerate with the Web Service method, but as soon as I enter the WebService Request 

WebService(certs/host1):[.[].friendlyName] 

and then click apply and close, the DCI is disappeared.
It really disappears, I tried to alter the view option (disabled, ...), but it is gon
when I create another DCI, also the ID counts up

KR Georg

Update: this happens everytime I add a web service instance discovery, regardless of the request string

Hi,

Thanks for the feedback (you can also put a star on our github repo )

Yes, right, unsupported, hidden or disabled DCIs may be not shown according to View options. 
The other thing is instance discovery prototypes - they are hidden in view mode, but are visible in Edit mode (pen icon on the toolbar). What settings do you have on Instance Discovery page of the DCI? Pls share screenshot of General and Instance Discovery pages. 

But I am not sure if we have syntax to specify something in brackets after web service name (or was it mentioned somewhere?)

Hi Filipp, 

the example with the brackets is here: 

https://www.netxms.org/documentation/adminguide/web-services-monitoring.html#examples 

You are right, I can see the DCI as "unsupported" when I go to edit mode. 

My use case: 

I am polling the Cisco Meraki API for some license informations. For the Licensed Devices, I receive a JSON.
I want to break down the json into a DCI table and therefore I created a Table DCI 
As soon as I change the Instance discovery method to Web Service, its unsupported. (and not viewable in the view mode as I learned). In the edit mode, I can see it.

KR Georg

You can try to set debug level to 7, run instance discovery poll on node, and check server log file for lines with text queryWebService - it may give some hint at what is going on with request.