Sizing the Hardware and Database Required by an eG SuperManager

Before deploying an eG SuperManager to monitor your infrastructure, it is essential to determine the hardware required to host the eG SuperManager. The eG database also has to be configured appropriately to ensure that sufficient client connections can be simultaneously established from the eG SuperManager to the eG database server.

Clearly, as the number of infrastructure components that each eG manager reporting to an eG SuperManager is handling increases, the resource requirements for the eG SuperManager will increase. The resources to be considered when determining the configuration of the eG SuperManager and eG database include:

  • CPU availability
  • RAM availability
  • Disk space availability
  • Simultaneous client connections that can be established by the eG manager to the eG database
  • Database IOPS

To determine the sizing of the eG SuperManager and eG database, you first need a count on the eG managers reporting to the eG SuperManager and also the number of components managed by each eG manager.

To determine the sizing of the eG manager and eG database, refer to Sizing the Hardware and Database Required by an eG Manager.

The table below provides thumb-rules that can be used to configure the eG manager and database for your infrastructure.

Resources eG SuperManager

eG Database

CPU

Minimum 4 GHz and 2 vCPUs.Add 1 GHz processing for every 100 monitoring units

Minimum 4 GHz and 2 vCPUs.

Memory

8 GB. Add 1 GB RAM for every 100 monitoring units of each eG manager.

Minimum 2GB

Disk Storage

1 GB