Please think about this feature because could simplify a lot the template automation on VMWare environment.
Thanks

This proposal is included in the plan for 6.2

Hi dimitri.bellini ,

What info about Tags would be convenient(sufficient), for example:

1.

[
  "category_name":"tag_name1",
  "category_name":"tag_name2"
]

2.

[
  {
    "tag":"MyTag"
    "category":"MyCategory",
  },
  {
    "tag":"MyTag2"
    "category":"MyCategory",
  },
]

3.

[
  {
    "tag":"MyTag"
    "tag_description":"My Tag"
    "category":"MyCategory",
  },
  {
    "tag":"MyTag2"
    "tag_description":"My Tag 2"
    "category":"MyCategory",
  },
]

4.

[
  {
    "tag":"MyTag"
    "tag_description":"My Tag"
    "category":"MyCategory",
    "category_description":"My Category",
  },
  {
    "tag":"MyTag2"
    "tag_description":"My Tag 2"
    "category":"MyCategory",
    "category_description":"My Category",
  },
]

Hi Michael,
thanks for the development, i think could be the option number 3.
Because we can have a specific "Tag Category" for Zabbix and we can use it to filter the output inside an LLD.
Thanks so much

What is the usage scenario of tag_description ? (Why not 1 -  category:tag ?)

tag_description could be not so important but maybe in some scenario is still useful.
As I can understand the scenario n.1 could not be easily filtered by the LLD filter but maybe i'm wrong.
Also how you can add a tag array on a host prototype? Maybe we need something like ZBXNEXT-7581?
Thanks so much

Hi Michael,
do you think this feature will be released on Zabbix 6.2?
Thanks so much

I think yes, but this is most difficult feature.

@Michael - Thanks so much! I know is not so easy, we also have try to achieve it but without success.
I still hope to see it on 6.2

dimitri.bellini, we are still aiming for 6.2, stay tuned.

@Alexei Very good thanks so much!

dimitri.bellini, question about a json array with tags for some object, witch  variant is more preferable or do need more/other info ?

1. [
     {
       "tag":"MyTag",
       "tag_description":"My Tag",
       "category":"MyCategory"
     },{
       "tag":"MyTag2",
       "tag_description":"My Tag 2",
       "category":"MyCategory"
     },
   ]
   

   or

2. [
     {
       "tag":"MyTag",
       "category":"MyCategory"
     },{
       "tag":"MyTag2",
       "category":"MyCategory"
     },
   ]
   

Hi Michael,
I prefer option "1" seems good enough for already seen cases.
Thanks so much

Hi Michael,
do you think the TAG feature will be released on Zabbix 6.2?
Thanks so much

dimitri.bellini, the functionality will not be implemented in Zabbix 6.2, it may appear in future releases. 

@Alexei, thanks so much for the reply.
I hope to see soon because is very useful on VMWare environments when we need to "automate" some customer behaviour.
Thanks!

Just a small correction to what I already said. There is a great chance that it will be part of Zabbix 6.2.1 or even 6.2.0, it is already in development.

@Alexei,
Fantastic very good news!!!
Thanks so much for your support!

Available in:

• 6.2.1rc1 49c679950d5, c6fa5d21385,  07492ff9e4e
• 6.4.0alpha1(master) b809deba2d8, bf80fe112c5, 30d0ac1445b

Dear Michael,
as tested with your support team at the moment the Zabbix version 6.2.1 is able to fetch the VMWare Tags only starting vSphere version 7U2 (7.0.2). It seems Zabbix is not able to read the deprecated VMware REST API version.
Do you think is possible to enhance this feature also for the "old" api?
Thanks so much

Dear dimitri.bellini,

Technically it is not that difficult now, but I can't promise anything.

Hi Michael,
thanks so much for your feedback, we will wait
Thanks so much