## Custom attributes from vCenter can be very useful for queries in order to slice the
## metrics along different dimension and for forming ad-hoc relationships. They are disabled
## by default, since they can add a considerable amount of tags to the resulting metrics. To
## enable, simply set custom_attribute_exclude to [] (empty set) and use custom_attribute_include
## to select the attributes you want to include.
## By default, since they can add a considerable amount of tags to the resulting metrics. To
## enable, simply set custom_attribute_exclude to [] (empty set) and use custom_attribute_include
## to select the attributes you want to include.
# custom_attribute_include = []
# custom_attribute_exclude = ["*"]
I understand that telegraf will parse only custom attributes at Vsphere level, is my understanding correct ?
What about tags added to a vm for instance ?
i’m actually working on the plugin to collect the data on my environement: the parameter custom_attribute_include is only for “custom_attribute” property that are collected if correctly set).
On the VM there is also a tag properties, and this value are not returned
@tonic8 I went ahead and submited the feature request for pulling tags as part of the inputs.vsphere plugin. Cannot imagine there is too much work involved to add this feature, so hoping we see this sooner than later
ahhh thank you (i was on holiday so not watching here).
Perfect ! that could be very usefull, in my company the tags can be modified by my team (managing the virtual machine allocation) when the custom attributes are more used by infra VMWare teams.
