Best Practices

Nagios Monitoring configuration

  • Back up the Nagios Monitoring configuration - Always create a backup prior to making changes to the configuration to ensure changes can be recovered if necessary. To back up, navigate to Configuration > Nagios Monitoring > Control > Backup and restore. Adding a note to identify the backup can be helpful if you need to restore, additionally locking a backup avoids eventual automatic deletion. See How to back up restore configuration database.


  • We have not changed the open nature of GDMA. It is still all laid out in a clear file structure that is familiar to those used to working with GroundWork servers and agents. You should use it to make the most of GroundWork. 

Don't add your own plugins to the server

  • Instead, use GDMA (even on the GroundWork server itself). This ensures your server can be easily upgraded when new versions come out. We expect to put out several each year from now on, and upgrades will be nearly seamless. 

Don't stop some of the containers

  • You might think it doesn't matter that some of the containers are not running, and be tempted to stop them to save on CPU or RAM. This isn't a good idea - pretty much all the containers are there for good reason, and there's a lot of inter-dependency. If you are having resource constraints, please let us know by submitting a support request in GroundWork Support, and we'll help you tune the system as needed. In general, however, you may find you need more disk and RAM than you did in GroundWork 7.x to work properly, please see the System Requirements page for details.