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

VM Infos #69

Open
MicKBfr opened this issue Mar 26, 2018 · 4 comments
Open

VM Infos #69

MicKBfr opened this issue Mar 26, 2018 · 4 comments
Labels

Comments

@MicKBfr
Copy link
Contributor

MicKBfr commented Mar 26, 2018

Hi,

I' am using vsphere-influx-go since 1 year and this is excellent tools.

i'm looking to add some info on this dashboard "VMware Performance: Multiple VMs" like VM used space/ Memory allocated/CPU Count/VM description.

I have already try to add : { "Metric": "disk.used.latest", "Instances": "" },
{ "Metric": "disk.space.used", "Instances": "
" },
{ "Metric": "mem.capacity.provisioned.average", "Instances": ""},
{ "Metric": "cpu.corecount.provisioned.average", "Instances": "
" },
{ "Metric": "summary.config.numcpu", "Instances": "*"},
{ "Metric": "disk.used.latest", "Instances": " "},
without success :-(

Could you add the collection of this information to roadmap please?

Thanks

@sofixa
Copy link
Member

sofixa commented Mar 30, 2018

Hi,

I'm glad you like it!

For the provisioning stats (anything with .provisioned. in the name), you need to be running a vCenter and metric collection level 4 for level 1 (here's how you can do it - https://github.com/Oxalide/vsphere-influxdb-go/tree/master/tools ). Is that the case?

Cheers,
Adrian

@MicKBfr
Copy link
Contributor Author

MicKBfr commented Apr 6, 2018

Hi Adrian,

I have mad a pull request about domain in esx name.
I will try to change collection level just for this metrics, because i have open a case with vmware about hight memory usage with vcenter and they recommend not go more than level 2 for statistic collection.

perhaps we can use this quic stats metrics ?
".quickstats.mem.ballooned",
".quickstats.mem.compressed",
".quickstats.cpu.distributedCpuEntitlement",
".quickstats.mem.distributedMemoryEntitlement",

have a look on this project ( they use some quickstats):
https://github.com/sexibytes/sexigraf

thanks

@sofixa
Copy link
Member

sofixa commented Sep 16, 2018

Hi, @MicKBfr .

Which version of vCenter are you running? I've had some issues with high resource usage (mostly IO though) with high metric levels on various vCenter versions, but currently no issues whatsoever with 6.5 and 6.7.

QuickStats can be a decent workaround for that though.

Adrian

@MicKBfr
Copy link
Contributor Author

MicKBfr commented Sep 27, 2018

Hi Adrian,

Our vcenter is on 6.0U2. We have been some issues with hight memory usage when changing metric collection level. Vmware recommand to not changing collection level.
Quickstats can really be a good workaround

Mickael

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants