This page reviews the GroundWork Monitor system requirements for version 7.2.1.
WAS THIS PAGE HELPFUL?
GroundWork recommends the following minimum hardware specification for basic operation:
The installer will complain and require you to override it when installing with less than these minimums.
If you are deploying to an environment that has any significant complexity, there are a number of additional considerations for allocating resources. Support can help you size your system, but a good starting point for reference is the following:
There is not a formula based on number of hosts, for example. This is because you will almost certainly make choices that dramatically affect the time required to execute polling, the frequency of data collection, and volume of data stored. All of these will change the resource requirements.
GroundWork Monitor Enterprise Edition has been tested on the following platforms:
|Special Considerations for Virtualized Environments|
Monitoring inherently has a continuous high-load resource profile. This must be taken into account when deciding whether to run in a virtualized environment, and if so, when allocating resources to a virtual host running the monitoring. If you try to install on a virtual host which has too much contention from other VMs on the same host, results are likely to be disappointing.
If you are installing in a virtualized environment, particularly VMware ESX, using a single virtual CPU is generally recommended. As with a standalone machine, a 64-bit virtual machine is required for the GroundWork Monitor Enterprise 7.2.1 release. Installation of VMware tools and configuration of host time synchronization is essential in all VMware environments.
Please read the following requirements carefully before you install GroundWork Monitor Enterprise packages:
Disable it immediately, prior to running the GroundWork binary installer:
will ensure the libraries needed are present.
|Special Configuration for Virtualized Environments|
GroundWork Monitor specifically requires Sun Microsystems' Java SDK version 1.7 Update 76. This software is included in the GroundWork installation bundle. Note that this can be upgraded, and we supply instructions for doing so for version 7.1.1 here. This same procedure can be used for 7.2.1. You can also use the Azul release of java, which is well maintained as of this writing, and may be the most up-to-date available. Under some circumstances, other Java packages can interfere with the Sun provided software, but generally as of 7.2.1, there is little chance of this. Still we recommend not using any separate JVM to run other java programs on the same machine as GroundWork.
GroundWork Monitor uses the user account named nagios for access control to several components in the system. For this reason we prefer that the nagios user NOT exist prior to installation; the installer will then create the user and group, its home directory, and its dot-file setup in the manner we require. If you have any of the following conditions:
Then you must disable and remove all traces of the nagios user before the installation. To reenable such prior setup after the installation, you must take whatever steps are necessary to ensure that the user number is the same as that used by the GroundWork-installed user nagios. Also note that if the nagios user already exists before the installation, the nagios home directory is assumed to exist, and reside at /usr/local/groundwork/users/nagios.
In a simple install, the PostgreSQL databases will reside on the GroundWork Monitor system itself, but you may prefer to run the databases on a separate machine, see Remote Database Installation. The database server supports the same Operating Systems as GroundWork Monitor, which are:
The minimal system requirements for a separate database install are:
|Postgres won't actually use more then 8GB of RAM, so allocation of more then 8 GB is not necessary or recommended).|