Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN - Knowledgebase Articles > Polling does not work correctly on large vCenters

Polling does not work correctly on large vCenters

Created by Beatrix.Turan, last modified by MindTouch on Jun 23, 2016

Views: 1,001 Votes: 0 Revisions: 4

Overview

Due to a limitation on the maximum allowed performance counters that can be retrieved in a single call, polling does not work correctly on large vCenters.

Cause 

This issue is caused by a limitation defined by VMware.

In vSphere 5.5 Update 2 and later, and in vSphere 6.0, the number of entities that are included in a database query is limited. By default, VMware enables the collection of 64 performance counters in a single database query.

For reference, Virtualization Manager collects three performance counters for every VM, and five performance counters for every host.

Resolution

For more information about solving this issue, see the VMware Knowledge Base.

 

 

 

 

Last modified

Tags

Classifications

Public