elastic / elastic/beats

Add associated ResourcePools to Cluster data

Open
#46,937 0 comments 0 reactions 0 assignees View on GitHub
Team:Obs-InfraObs
Dominant language
Go
Stars
12.7k
Forks
5k
Avg merge
2d 15m
Merged PRs (30d)
385

Description

**Describe the enhancement:**
We would like to see which resourcepools are associated to each cluster as this is currently not possible.

**Describe a specific use case for the enhancement or feature:**
Currently there is no way to be able to see the clusters HW utilization/overcommitment from the vsphere module.
To be able to do that we need to know which resourcepool(s) is associated to which cluster.

This is easily feasible as the govmomi library returns the resourcepools associated to each cluster:
https://github.com/vmware/govmomi/blob/c5801225cdacd60743cf8039cb0ca2b171468b98/vim25/mo/mo.go#L113C1-L113C78

Adding (actually not ommitting) this information to the vsphere module seems to be trivial, as it would propably only constitute a couple of line additions to the source code here:
https://github.com/elastic/beats/blob/7b7cd0cb500a871cafa9483afe6f6321492d2fc0/metricbeat/module/vsphere/cluster/data.go#L42

Contributor guide

Open the contributing guide

Research direction

Start with metricbeat/module/vsphere/cluster/data.go around the cluster data definition and compare it with govmomi's resource pool fields. Confirm how the vsphere module currently serializes cluster data, then expose the associated ResourcePools and verify that each cluster reports them for the stated hardware-utilization use case.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
infrastructure
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.