Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vSphere Plugin: tag/filter by VM inventory path or parent folder #9673

Closed
khord opened this issue Aug 24, 2021 · 2 comments
Closed

vSphere Plugin: tag/filter by VM inventory path or parent folder #9673

khord opened this issue Aug 24, 2021 · 2 comments
Labels
area/vsphere feature request Requests for new plugin and for new features to existing plugins platform/windows waiting for response waiting for response from contributor

Comments

@khord
Copy link
Contributor

khord commented Aug 24, 2021

Feature Request

The usefulness of the inventory paths filter added in #4790 -> #4989 is (in my use case) largely negated by the inability to tag by the inventory path that yielded the VM object, or at least the immediate parent folder name. As a business who operates many cloned sets of same-named VMs differentiated by folder name, this makes it very hard to plot graphs from the metrics (right now, I have to enumerate a comma separated list of moref IDs for the VMs in each folder, then place that as a custom variable in Grafana to filter on).

Proposal:

Add ability to tag by the inventory path in the telegraf config which yielded the VM object, or by the VM's parent folder name/ID

Current behavior:

Unable to differentiate VMs of the same name other than by moref ID

Desired behavior:

Being able to filter VMs by their folder or folder path

Use case:

Inventory Paths in telegraf:

/DC0/vm/Training-Exercise-*/*

Example excerpt of VM folder tree, but hundreds of folders in practice

<root>
+-DC0 # Virtual datacenter
   +-vm # VM folder (created by system)
   | +-Production
   | | +-domain-controller
   | | +-nginx
   | | +-router
   | +-Training-Exercise-1
   | | +-windows-vm1
   | | +-ubuntu-vm1
   | | +-router
   | +-Training-Exercise-2
   | | +-windows-vm1
   | | +-ubuntu-vm1
   | | +-router
   | +-Training-Exercise-3
   | | +-windows-vm1
   | | +-ubuntu-vm1
   | | +-router
  • Be able to differentiate windows-vm1, ubuntu-vm1, and router metrics between all the Training Exercise folders
@khord khord added the feature request Requests for new plugin and for new features to existing plugins label Aug 24, 2021
@powersj
Copy link
Contributor

powersj commented Apr 19, 2022

Hi,

Sorry no one never got back to you.

Would you be willing to provide an example metric of 1) data you get now and 2) what your desired behavior is?

Thanks!

@powersj powersj added the waiting for response waiting for response from contributor label Apr 19, 2022
@telegraf-tiger
Copy link
Contributor

telegraf-tiger bot commented May 4, 2022

Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Page. Thank you!

@telegraf-tiger telegraf-tiger bot closed this as completed May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vsphere feature request Requests for new plugin and for new features to existing plugins platform/windows waiting for response waiting for response from contributor
Projects
None yet
Development

No branches or pull requests

2 participants