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 > Orion and Virtualization Manager memory utilization graphs show discrepancy in the values

Orion and Virtualization Manager memory utilization graphs show discrepancy in the values

Table of contents

Issue

The memory utilization graphs in Orion and Virtualization Manager show different values for the same node.

Cause

Orion collects data directly from the Virtual Machines, through SNMP, while VMAN collects data through the VMware API. Orion displays the amount of memory allocated to the running processes on the given guest, but this does not necessarily mean that that amount of memory is actively used. Virtualization Manager and VIM display the actual, active memory utilization value.

Despite the difference in the data collection method, the data displayed in Orion and the data displayed in VMAN should not be significantly different.

Last modified

Tags

Classifications

Public