EM 13.2: Host Real Time CPU Utilization Not Reflecting Actual Real Time Values (Doc ID 2302135.1)

Last updated on SEPTEMBER 12, 2023

Applies to:

Symptoms

Enterprise Manger 13.2 Cloud Control
Metric: CPU Usage, CPU Utilization (%) of a CPU

Several Oracle Linux 6 Servers run as VMWare Guests are monitored by Enterprise Manager (EM) 13.2 Cloud Control,
where, during load testing, EM "real time" monitoring was not even close to the actual values on
the servers (as shown by 'top'). For example, on an 8 core machine, with all cores maxed at 100%, it
takes OEM 3-5 minutes to catch up, even on manual refresh every 5 seconds.

On load tests in which all 8 cores are at 100% for a minute, EM never "realizes" the machines were that taxed.
Monitoring templates that are supposed to alert us in these cases do not.
This case depends on how often the metric is gathered and sent back to the OMS.

A target Host is running Oracle Linux 6 with the EM 13.2 Agent, reporting to the EM OMS of the same version.
Agent Status is Up, with no upload issues or Blackouts on any of the Targets.

The EM 13.2 OMS has only the EM 13.2.1.0 Plugins for:

Cloud Framework (CFW)
Database (DB)
Fusion Middleware (EMAS)
Systems Infrastructure (SI)
Exadata (XA)

and has the Apr2017 OMS 13.2 PSU, along w/the Dec2016 Bundle Patches
(BPs) for DB, FMW, & SI Plugins.

The EM 13.2 Agent has EM Plugins for:

Beacon (13.2.0)
EMAS (13.2.1)
OH (13.2.0)
SI (13.2.1)

and only the JDBC Patch 24470104.

The OS command 'top' on that host shows them ranging from 93% to 97%, EM 13.2 shows the CPU Utilization (%) of a cpu metric for the 8 CPUs of the above-mentioned Target Host in the range of:

18 - 20% at about the same time
33 - 35% at about 30 seconds later
61 - 63% at about a couple of minutes later

all while top is still showing them in the 89 - 97 range.

Then, about a minute later, when top drops to the 0 -1 % range, EM 13.2 still shows them in the 62 - 64 % range, and even another full minute later, EM 13.2 has only dropped to the 58 - 59 % range.
Note that this data was taken while refreshing manually, not waiting for the Collection Schedule

Changes

System upgraded from EM 12.1.0.5

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.