Utilization Impact Risk of OEM Cloud Control Agent on Monitored Systems
Oracle's implementation is designed to be a low risk deployment using scripts to
ensure consistent deployments across all customer implementations. Furthermore, the
implementation is validated for monitoring within Oracle test systems. Oracle makes
no changes to customer applications or files outside of the steps described in the
relevant sections on impacts on the environment above.
The table below outlines the utilization impact that OEM has on the monitored
systems.
Table 2 Utilization Impact of Oracle Enterprise Manager Cloud Control Agent on
Monitored Systems
|
|
|
|
CPU Utilization
|
The OEM Agent uses from 0.02% to 1% of CPU utilization.
The agent may utilize more CPU cycles, depending on the number
of processes or applications monitored.
|
|
Memory Utilization
|
The OEM Agent needs from 1GB to 2GB RAM to operate
correctly.
The actual memory utilization of the agent varies depending on
the number of processes or applications monitored.
|
|
Disk Space Utilization
|
The OEM agent requires at least 2GB of free disk space for the
installation files.
After installation is complete, the installation files are
removed. The installed OEM agent requires about 1GB of space
initially. As the agent operates, disk space gradually increases
up to 5GB.
To apply patches to the agent, 5GB of space is required in
/tmp to download and extract the
installer before updating the agent binaries.
Oracle Autonomous Health Framework (AHF) software requires 2GB
of space in /opt and a minimum of 6GB (with
a recommendation of 10GB) on /u01 to store
the diagnostic bundles created by the software for configuration
review and troubleshooting.
|
|