Item is a string list from user parameter, can I graph of display the values ?

[Hamardaban]

I'm sorry if I explain it in a confusing and incomprehensible way....
But I don't want to retell the documentation. I gave a link to an example - there are both pictures and a description. apply this information to your case.
Or come up with your own way of getting data (sender\trapper and the like).
I'm sorry again - apparently I can't help you with anything else.

[gerard-wl]

I'm sorry if I explain it in a confusing and incomprehensible way.....

Absolutely not Hamardaban I wouldn't allow :|
I just do think that telling me the missing things to to in gui for my case will definitively help me (and some others sure) to understand these LLD rules

[gerard-wl]

I progress Hamardaban cyber

So the json is the DEFINITION, the item prototype is the item TEMPLATE from which each item[SELLER] will be created by zabbix, and I need to send dynamicaly the actual data, with sender for example :

zabbix_sender -z myZabbixProxy -s myLocalHost -k 'result["Peter"]' -o 1234

which is visible in lastest data

BUT

I don't know all sellers in advance, some new may arrive, some may leave
For example, if i do a

zabbix_sender -z myZabbixProxy -s myLocalHost -k 'result["Marc"]' -o 1234

The result is ok, but there is no Marc's item in gui

So must I update the json definition (with "Marc" ) and send it quickly (how?) to zabbix just before sending actual data containing "Marc" ?
And if a seller leaves, will its item disappear ?

Thank you

[cyber]

Let me try....Eventho I dont have any Zabbix instance at hand right now...

First you create an item, which pulls data, using your userpearameter (or you send it with zabbix_sender) ... you will get nicely formatted json data...
Second... you create a discovery, which is of type "dependent item" and point it to your "main" item.
Third, you create your item prototypes (just as you already did, also of type dependent item (not trapper)) and point it to the "main" item. jsonpath preprocessing should be used to point it to value, you want to collect (as Hamardaban already explained in post #14)

What happens later? Every time your "main" item collects data, LLD kicks in and creates items, if needed (that part seemed to work for you). If items are already in place, all those discovered items will get their data. If any new "seller" appears, first time item will be created, second time data for it is already saved... If some of those "sellers" disappear, then depending on discovery settings (keep lost resources) that item is either deleted after configured period. if set to 0, then it will be deleted immediately. Otherwise you should see yellow exclamation mark behind that item, if you hover mouse over it, it will tell, when exactly it will be deleted.

[gerard-wl]

Thank you for your answer cyber
In the meantime I've succeded the job
The documentation is not clear enough about there 2 steps : json definition + data, that's why I'd wasted time
For all, we must send a json definition with the sellers' list updated (result's value is not used) before sending data with the same sellers's list updated
All is ok now (except that sorting on Name in the latest data screen, when I filter by name, does not work, I use version 5)