[ZBXNEXT-4518] Dependent Item for LLD item Prototype not working Created: 2018 Apr 23  Updated: 2018 May 05  Resolved: 2018 May 05

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Change Request Priority: Trivial
Reporter: Devi Ojha Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: dependentitems, lld, llditem
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File image-2018-04-23-17-10-32-824.png     PNG File image-2018-04-23-17-12-25-162.png     PNG File image-2018-04-23-17-13-06-319.png    

 Description   

I have a discovery rule which pulls of a bunch of items . And then I have item prototype which pulls a json file for each discovered item.  using the item prototype as master key , i have created dependent items  to fetch values for each keys in json . 

 

Discovery Rule is working fine.

Item prototype is getting a json string for each discovered items .

{'name': u'CA-CCS', 'alert': 'NULL', 'state': u'NOT_STARTED', 'lastChangedStateTime': 'NULL', 'startTime': 'NULL', 'runtime': u'null'}

However, the dependent items for   each prototype are not getting created /working . 

 

 

Item prototypes

Response of each item prototype :

Dependent item

Preprocessing steps
Name Parameters Action

$['state']

 

 



 Comments   
Comment by Devi Ojha [ 2018 Apr 24 ]

Hello  Team ,  Am i doing something wrong or is it a bug , any pointer will be a great help .

Comment by Glebs Ivanovskis (Inactive) [ 2018 May 05 ]

One thing you are doing wrong is that you don't use LLD macro in the key of dependent item prototype. This instructs Zabbix to create discovered items with identical keys, which is not possible due to uniqueness constraint. Check Configuration→Hosts/Templates→Discovery, there must be info message next to your discovery rule.

Another thing is that your value doesn't look like JSON...

No indication of a bug in Zabbix. Closing as Won't Fix.

Generated at Fri Apr 04 16:52:00 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.