Virtual Container Hosts not being reported accurately

Discussion created by on Sep 1, 2017
Latest reply on Sep 6, 2017 by


Why does my turbo wrongly report the amount of memory allocated to a virtual container host? We are testing the solution and find that Turbo reports my virtual container host has over 600 gigs of ram assigned to it, which it obviously doesn't.
Is this is a bug in the monitoring. I have revalidated my vsphere centers with turbo and am running the latest, 5.9.1 version, but for some reason Turbo is not reading that host right?


Any ideas?