Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > Why is the CPU usage in Orion different in VMAN for a VM

Why is the CPU usage in Orion different in VMAN for a VM

Table of contents

Updated January 26, 2017

Overview

This article explains why VMs in NPM are showing different statistics after VMan integration.

Environment

  • VMan 7.0
  • NPM 12.0.1

Detail

Guest OS is reported at the operating system level.

As the VM does not know that it is indeed a VM, it will show a different number used than ESXi unless it is thick provisioned. 

To simplify the situation: Guest OS (monitored by Orion) is showing something different than ESX host (monitored by Vman). Vman is showing what we poll from VCenter. So in general,  the discrepancy being shown is between the Guest OS (Orion) and VCenter (assuming Vman and VCenter are saying the same thing).

Assuming that there is no discrepancy between Vman and VCenter, the next course of action would be to ask VMware Support why the stats from Guest OS and VSphere client are different.

 

Last modified

Tags

Classifications

Public