influxdata / influxdata/telegraf

Obtain Tags from VMware Resources ([[inputs.vsphere]])

Open
#16,083 3 comments 0 reactions 0 assignees View on GitHub
feature request
Dominant language
Go
Stars
17.8k
Forks
5.8k
Avg merge
1d 20h
Merged PRs (30d)
161

Description

### Use Case

We need the ability to further filter VMware virtual machine resources by Tags. Specifically, we have tags that identify elements like fault domain, product code, owner, etc. This functionality is crucial for configuring custom dashboards in Grafana and enabling customers to view metrics for their specific resources. While the `[[inputs.vsphere]]` plugin currently supports Custom Attributes, we require similar support for Tags.

The primary feature request is to pull Tags for virtual machines, though ideally, Tags would be accessible on all resources. To manage potential issues with resources containing many Tags, a filter option would be ideal, allowing selection of specific Tags—similar to how Custom Attributes are handled.

Not to cram one more feature in here, but knowing the power status of a VM would be helpful as well. There are certain cases where we may want to filter on the power status of a VM, on/off/suspended. I see the vsphere_vm_power_power_average metric, but I believe that is related to "Average power use in watts".

### Expected behavior

The plugin is expected to return VMware resource Tags in the same way it handles Custom Attributes, with an option to filter specific Tags to avoid potential issues.

### Actual behavior

Currently, `[[inputs.vsphere]]` does not support VMware resource Tags.

### Additional info

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the inputs.vsphere plugin and its existing Custom Attributes handling. Clarify the scope across VM and other resources, tag filtering, and VM power status; done means the selected VMware tags are exposed with filtering without the resource-cardinality issues described.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.