The GroundWork Distributed Monitoring Agent (GDMA) is a monitoring agent that runs on Linux, MS Windows, Solaris, and AIX.
Using plugins that follow the same standard as Nagios, GDMA can execute service checks on the host where it is installed and/or other hosts, making it a flexible way to do distributed monitoring. It is lightweight, and highly configureable. It supports HTTPS and/or NSCA encrypted communication with a GroundWork server, and forwards the service check results to a Bronx event broker in a Nagios instance, typically running in a GroundWork Monitor server. GDMA code is open source.
While manual configuration is supported, you can manage GDMA directly from the GroundWork server using the Nagios Monitoring configuration application, Monarch. It's also possible to automate much of the configuration of the agent using two main automation methods, Auto Registration and Auto Setup.
Why use GDMA?
Monitoring systems can be overwhelmed if asked to do too many things from a single instance. GDMA allows you to offload the GroundWork Monitor server of nearly all the active checks you would otherwise execute with Nagios, and can reduce the need to deploy GroundWork Child Servers. In addition, allowing the monitored system to execute its own checks, you gain the ability to access resources present only on the machine without opening ports or running services like SNMP or even SSH.
GDMA only needs to reach out to the GroundWork server to send results and (optionally) pick up configuration changes and new plugins. You never need connectivity outbound from the GroundWork server to the GDMA host, making it ideal for cross-firewall communication.
GDMA uses a largely unified code base on Windows and Linux/Unix based systems. This means administration is very similar between platforms, and therefore simpler. Its features for tuning, multi-host mode, and reliable spooling of results are the same across all platforms, and its lightweight nature is preserved wherever it is run.
You can run any plugin you like as a service check in Nagios, and GDMA also let's you be this flexible. In fact, you can enable plugin downloads in GDMA and let selected agents update their plugin sets automatically, dependencies included. Simple, file-based configurations allow integration with configuration management systems. Multi-host mode allows you to deploy just one GDMA and monitor all the systems in a moderate-sized remote location.
Support for restricted (non-privileged) user accounts, encrypted communication, and no open inbound ports make GDMA hard to compromise without on-system privileged access. SSL Certificate download, validation, and revocation options keep the encryption secure.
How to get started
To get started, see the How To's for GDMA, starting with How to configure install and configure GDMA.
GDMA config files (Knowledge Base)
Release Notes for GDMA 2.7.0 (Documentation)
GDMA advanced (Knowledge Base)
How to use GDMA with HTTPS (Knowledge Base)
How to manage GDMA accounts (Knowledge Base)
How to run Windows GDMA as non-admin user (Knowledge Base)
How to allow GDMA to download plugins (Knowledge Base)
How to install and configure GDMA (Knowledge Base)
GDMA troubleshooting (Knowledge Base)
How to configure externals (Knowledge Base)