Ad Widget

**gramj** · 23-09-2021, 16:23

My experience seems to confirm that. Oddly though your statement isn't 100% accurate is the process is happy to assign the same SNMP interface information, proxy server, etc. It's too bad in this case that I can't reference information from the host that is performing the discovery; that would have been an easy and elegant solution and likely useful in many situations. Because of how SNMP discovery seems to work, wherein all OIDs need to having a matching index, it isn't obvious to me that I could do this. Had my discovery been based on JSON or something, I'm sure that I could do something that would have worked. I guess if it comes to it, I could utilize a script to perform the discovery, 3 Low-level discovery [Zabbix Documentation 5.4]. I can't seem to find any documentation quickly as to what parameters I can pass to the script. Will it just be the same sort of parameters that are available when using an external script for a conventional item?

**gramj** · 24-09-2021, 16:41

Thank, cyber. I appreciate your responses.

**cyber** · 23-12-2021, 22:46

Do I get it correctly... you want to add discovery rule to a host, which will then generate another host based on prototype in discovery and use original hosts name while naming that host, created by discovery?
I am pretty sure it will not work that way... All prototypes depend on data coming from discovery. If your discovery does not give out that needed name as LLD macro you cannot use it in naming of a host created by discovery and host prototype...

**cyber** · 23-12-2021, 22:47

As discovery rule is also "item", then it depends on its type, what and how you can give it to as parameters... if its an external script, then configure it as any other item with that type... If its agent or agent active item, then configure it as any other similar... You probably need to introduce a UserParameter to agent and feed it with needed parameters. etc
Custom LLD script has to return json. Examples there in docs use already formed LLD macros as keys, so you don't have to use that LLD macros part to point out with jsonpath where to to find specific key. But you can easily use "normal" key names..

just need to define your LLD macros and path to them in discovery rule...
For external script you can pass hosts name as parameter, make that script to return it in json..

map to LLD macro and use it in naming... yes.. a bit "around the corner"...but doable.

**gramj** · 24-12-2021, 17:47

I did end up writing an external script using python that performs the discovery using SNMP, and is thus able to correlate data in a manner that is more complex than allowed by normal LLD, and then just return the data. It works in a manner that is consistent with what you described.