A problem with a discovery rule (LLD)

[iyuvalk]

Hi,

We developed a tool in .Net to discover all the sites, ports, and main URL's on an IIS server, this tool is intended to be run as part of an LLD to create items and triggers automatically for our IIS servers. It all works perfect for most of our IIS servers, we have a discovery rule that uses the Zabbix agent to run this tool (system.run[C:\zabbix_agent\extra\websiteDiscovery.exe]) and the tool returns a JSON object and the items are being created but we have only one server that we see that no items are being created for it. I tried to capture the traffic using tcpdump and it looks just ok to me... How can we begin to troubleshoot this issue?

[abevern]

Probably...

The problem is likely in the generated JSON. Zabbix can be very fussy in this regard.

I suggest manually dumping the JSON to a local file and then comparing it with a server that does work.

Make the LLD from zabbix read the file rather than run the executable (I'm a linux guy, so I don't know how to do that in windows.)

Substitue a working JSON for the non-working JSON, so you know whether it's JSON related or something in your server config.

Tweak the original file until it works, then work out why you need to tweak it the way you did.

LLD is awesome, but can be very frustrating to get it right.