Yes, the macro
{HOST.IP<1-9>} should be supported for "Item key's parameters"
http://www.zabbix.com/documentation/2.0/manual/appendix/macros/supported_by_location
Dear Oleksiy,
{HOST.IP<1-9>} is supported. That's not the point.The point is, that when using a macro the script will receive the macro value. In case of {HOST.IP<1-9>}
it will be an IP address.
Therefore the script will return the IP in the JSON object.
Zabbix currently expects the script to return the configured key exactly like this: 'script.name[
{HOST.IP},param1,param2]'
That is a problem, as the script will not have any information about the used macro as it receives an IP address and not the macro itself.
The script returns the IP instead of the macro, like this: 'script.name[198.18.0.123,param1,param2]'
Zabbix should deal with that.
br
could you please clarify where exactly are you using the string "script.name[
{HOST.IP},param1,param2]" ?
In the key field, as documented.
http://imageshack.us/photo/my-images/24/zabbixlld.png/
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
More details:
Zabbix will call the script like:
/opt/zabbix/share/zabbix/externalscripts/script.name "198.18.0.123" "param1" "param2"
Log > 11507:20120302:191438.615 In zbx_popen() command:'/opt/zabbix/share/zabbix/externalscripts/script.name "198.18.0.123" "param1" "param2"'
Naturally the script would return this JSON object:
{
"script.name[198.18.0.123,param1,param2]": [
{
"
"{#MYVALUE}": "1000"
},
{
"{#MYINDEX1}
": "2",
"
},
{
"{#MYINDEX1}": "3",
"{#MYVALUE}
": "3000"
}
]
}
Zabbix will not accept that object because it tries to match it to the key value, which is: 'script.name[
Log > 11507:20120302:191438.705 query [txnlev:1] [update items set lastclock=1330712078,lastns=704097134,error='Cannot find the "script.name[{HOST.IP}
,param1,param2]" key in received JSON object' where itemid=22508]
When the script returns the macro name in the JSON object it works.
But how does the script determine which macro was used? 
-> Zabbix has to accept the VALUE OF THE USED MACRO, not the MACRO NAME in the JSON object.
Working JSON object, returned by the script.
{
"script.name[
,param1,param2]": [
{
"
"{#MYVALUE}": "1000"
},
{
"{#MYINDEX1}
": "2",
"
},
{
"{#MYINDEX1}": "3",
"{#MYVALUE}
": "3000"
}
]
}
hmm. why use the macro at all then ?
also, it's better to attach images directly to the issue, that way they are more permanent (and imageshack is terrible, i can never get the full size image there 
)
Well I use the macro because I define this discovery rule inside a Template. And I would like to assign that Template to a lot of devices.
Attaching an Image does not work for me. Java Clipboard Copy&Paste is not very nice. Sorry.
at the top of this issue, there should be "more actions -> attach files"
but my question was - why use the macro at all ? if this is a discovery rule, it would usually work the same in all hosts. if you have to customise something, wouldn't it be in auto-created item keys instead ?
The script needs an IP address or Hostname to connect to. That's why it needs a macro, or IP, or Host.
It will not be executed by a Zabbix Agent.
ah, right, sorry - missed the fact that it's an external check.
right, this scenario might not work that well currently.
Fixed in the development branch svn://svn.zabbix.com/branches/dev/ZBX-4725
Fixed documentation:
http://www.zabbix.com/documentation/2.0/manual/discovery/low_level_discovery?&#discovery_item_json_format
Now, a JSON object should contain not an item key but "data".
For example:
old JSON object
{"net.if.discovery":[{"
":"eth0"}, {"
{#IFNAME}":"eth1"}]}new:
{"data":[{"{#IFNAME}
":"lo"}, {"
{#IFNAME}":"eth0"}, {"{#IFNAME}":"eth1"}]}
Sasha, regarding this changes, will trunk agents 1.9.x-1.9.9 (agents compiled before this change) work with latest revisions of zabbix server ?
Or trunk agents should be updated (recompiled) too?
<Sasha> Yes, all agents should be recompiled too. LLD checks won't work with the old 1.9.9 agent and the new 1.9.10 server.
Fix components.
Brilliant, works like a charm.
Fixed in the version pre-2.0.0rc1, r26035.
Reopening to fix title.
Fix title
Close issue
Just a note for my latest comment:
If use zabbix agent versions 1.9.1-1.9.9 (beta versions) with zabbix server version 2.0.x then LLD will not work and every discovery rule will have this error description:
Cannot find the "data" array in the received JSON object
This looks like it broke again in 2.2.4. Was working in 2.2.3. External scripts using macros in lld keys get json errors back.
Kenneth, if it is then you would need to create another ZBX report.