Application Performance Monitoring — GroundWork Monitor, as of 8.1.2, includes an Application Performance Monitoring (APM) connector you can use to send metrics to GroundWork Monitor directly from your running applications.
Auto Discovery — This tool allows administrators to automatically coordinate network resources with GroundWork Monitor's configuration database, thereby relieving administrators from having to manage all of their host and service definitions manually.
Cloud Monitoring — Cloud Hub is a data collector agent specialized in gathering metrics from a variety of virtual environments and integrating them seamlessly into the GroundWork Monitor Enterprise system.
Elasticsearch Monitoring — The Elastic Connector is implemented in the GroundWork Transit Connection Generator (TCG), and allows a unique type of service to be deployed into GroundWork Monitor, Elasticsearch Lucene queries.
GDMA Monitoring — 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.
Nagios Monitoring — In GroundWork Monitor, the Configuration > Nagios Monitoring menu item, is devoted to configuring and managing Nagios monitored elements.
NSClient Monitoring — Microsoft Windows™ servers can be monitored directly from GroundWork servers using a variety of methods (SNMP for example, or with WMIC). A popular method is to use the check_nrpe plugin, and GroundWork Monitor 8 includes a set of plugins to use with this method.
Deploying Parent Child — The capabilities for distributed monitoring in GroundWork Monitor have long been available with the implementation of “Child” GroundWork servers. This capability has been added to GroundWork 8, starting with version 8.1.0. The child server is simply another GroundWork server that monitors a subset of the infrastructure. Child servers report the monitoring state and performance metrics to a central, or "Parent" GroundWork server.
SNMP Monitoring — GroundWork Monitor supports monitoring with SNMP (Simple Network Management Protocol). This older method of gathering metrics from network devices and hosts of various types is widely used, and isn't going to vanish any time soon. Primarily, GroundWork uses SNMP for getting information about network devices, both from an inventory perspective using NeDi (Network Discovery) and from a monitoring perspective using TCG-SNMP and Nagios Plugins.
SSH Monitoring — Secure Shell (SSH) provides encrypted terminal access to remote hosts, and also provides the ability for users to execute commands on the remote hosts. In simple terms, this means that a user on one host can use SSH to execute commands on another host in the same basic manner as if those commands were being executed locally, with the extra benefit of having the commands and response data being exchanged across a secure communications channel.
TCG — The connection between GroundWork servers and monitoring data sources such as Nagios is facilitated by a new component called TCG, or the Transit Connection Generator (see https://github.com/gwos/tcg https://github.com/gwos/tcg). Based on the NATS project https://nats.io/, TCG allows the creation of resilient connections that automatically re-establish when broken, and buffers data to ensure a lossless stream of metrics. TCG is easy to configure, and flexible.
WMI Monitoring — This page reviews how to use WMI agentless plugins which is valid for use with any version of GroundWork Monitor.
WMIC Monitoring — When deciding how to monitor MS Windows servers, you have a few best-practices choices to make. You can install the GroundWork Distributed Monitoring Agent (GDMA), use the native MS Windows SNMP service, use another open source agent such as NSClient++ and NRPE, or you can use the native WMI calls, all of which will give you some form of detailed information on exactly what is happening on your Windows systems.