Add support for ballooning memory in check_vmware_rps_memory

[Byolock]

Would it be possible to include the ballooning memory in the performance data of the ressource pool memory check? vCenter does show this value for a ressource pool and I found this documentation : https://developer.vmware.com/apis/704/vsphere/memory_counters.html which suggests its available in the vSphere Web Services API. Specifically I would like to monitor vmmemctl (vmmemctltarget might be useful too).

[atc0005]

Would it be possible to include the ballooning memory in the performance data of the ressource pool memory check?

Hi @Byolock,

Per https://pkg.go.dev/github.com/vmware/govmomi/vim25/types#ResourcePoolQuickStats.BalloonedMemory, ballooned memory is tracked and available for reference. This seems like a good fit for a small enhancement in a near future release.

Specifically I would like to monitor vmmemctl (vmmemctltarget might be useful too).

I find both of these keywords when looking in the vcsim source:

https://github.com/vmware/govmomi/blob/64d875b9d7eb27155aa1afa5424a3329ea0d1c9d/simulator/vpx/performance_manager.go#L2578-L2586

https://github.com/vmware/govmomi/blob/64d875b9d7eb27155aa1afa5424a3329ea0d1c9d/simulator/vpx/performance_manager.go#L2695-L2702

This suggests that both are available, though I've not looked into the steps needed to retrieve the values.

[atc0005]

@Byolock Thanks for the additional feedback.

Do you have another account you can use for testing? Perhaps this is a permissions issue.

[atc0005]

@Byolock Did you perhaps test with an account that has greater permissions?

[Byolock]

I just tried with the root account but got exactly the same error message output. We are running ESXI 6.7.0 Update 3 (Build 14320388), if that information might be important.

[atc0005]

Looking at the provided output a little closer, the attempt to reload state itself is failing (not just the lack of the properties after the reload).

I don't have a live ESXi system to test directly against, but this suggests that a permission is missing for the account used to execute the plugin.

[atc0005]

@Byolock: I just tried with the root account but got exactly the same error message output. We are running ESXI 6.7.0 Update 3 (Build 14320388), if that information might be important.

Ah, well in that case you can't really get any more privileged than that account.

Perhaps this is just a limitation of standalone ESXi hosts.

I guess for now we'll consider this a known issue, document it and hope that it can be revisited in the future once we have more info to go off of.

Thanks for the additional testing.