Version 8.2.3

GroundWork Monitor Enterprise Edition | Version 8.2.3 | Release 04/11/2022 

These release notes describe the new features and improvements, fixed Issues, and known Issues and limitations for GroundWork Monitor 8.2.3. They also provide announcements as of version 8.2.3, including currently supported and end-of-life versions of GroundWork Monitor. 

This release is primarily a maintenance release, with fixes and completions for issues and recently added features.

New Features

GroundWork Monitor 8.2.3 doesn't have new major features beyond those announced for 8.2.1, which were two new TCG connectors, the GroundWork Microsoft 365 connector and Kubernetes connector. It does contain a very worthwhile performance enhancement, especially for those using parent-child configurations. It also has a couple of new feature for the Status summary: Alias and Notes fields (where available) will be shown for hosts, as well as the list of hostgroups for a host. These appear on the host info panel of the Status Summary. There's also a handy Test button for setting up your GroundWork messenger methods. 


This section describes improvements including feature requests in the 8.2.3 release.



GroundWork Messenger test button


Data Geyser should suppress most duplicate data for check results


Update downtime automation scripting for GroundWork 8


Add alias and notes fields to Status


Add hostgroup memberships to host detail in Status

Fixed Issues

This section describes the fixes we have included in the 8.2.2 release.



TCG Kubernetes layout minor bugs

The Kubernetes connector configuration screen was a bit messy, we cleaned it up


Prometheus remote write not working with GroundWork APM connecter

There were issues pushing data to the APM connector with some Prometheus configurations, we enabled them


Kubernetes connector config by file broken

Some config files were not getting parsed correctly, leading to auth failures in Kubernetes, now corrected 


SLA dashboard doesn't load if there are empty servicegroups

The SLA dashboard had issues loading when empty service groups were selected, now loads with no issues 


BSM prefetching of hosts no longer working

A handy feature of BSM that made the first run after a new configuration action more complete and accurate was broken, now fixed


tcg-elastic fails to retrieve metrics with logged error

There was a bug which could impede the collection of metrics from Elasticsearch in some cases, now fixed 


tcg-kubernetes saves config to volume only when configured via file-upload

There was a serious problem loading configuration files for tcg-kubernetes, which made this method of auth unstable past restarts, now fixed 


status-queue worker exception behavior needs optimization

Part of an optimization effort that makes Nagios data (and Parent Child communication) much faster


Elasticsearch and Logstash have a vulnerable log4j version

A non-exploitable yet vulnerable version of jog4j was installed on GroundWork 8.2.2, this was removed, and scans now show it as clear


Notification method cURL allows shell commands within GroundWork GORT container

A security issue if used improperly, this has been inhibited


SLA dashboards with custom groups no longer work

An issue with SLA dashboards that affected custom groups was corrected

Known Issues and Limitations

This section lists any known issues and limitations with work-arounds.


Nagios Monitoring

Renaming a host to the same name except for case will require 2 commits. The renaming of a host to the same name with differences only in the case of the characters is possible, but requires committing the configuration twice.

Run the Commit (or, for Parent Managed Child, the Build Instance) process a second time, and the renamed host will appear. 

Nagios Monitoring

Adding two hosts with the same name except for case will not work. If you ever find you need to have two hosts with the same name except for case in the Nagios system, this is allowed. It will not show both hosts, however, only the first one you add, and it won't work at all if you do it in a single commit.

To do this (admittedly really rare thing), fist add one of the hosts. Choose the one with the name you want to see, add it and commit. Then add the second and commit. The second host's services will be merged into the first. 


Cannot delete users created by LDAP sync. If you sync LDAP to GroundWork, the users who log in are imported. There's not much point in deleting them unless you disconnect the LDAP server, but even if you do so, the delete function isn't working.

There is a work-around, but then again there's no harm in leaving these user accounts alone. They will fail login once the LDAP server is inactive. If you really must delete them, please contact support. 

Nagios Container

It's possible to overload the Nagios instance in GroundWork. Nagios uses workers that communicate with the services it runs. In some cases the default provisioning isn't enough to keep up with a really active alert stream.

You can override the default provisioning of workers in Nagios with the check_workers directive. See How to configure check_workers.

Custom Reports

Optional Jasper Server slow to start. If one starts the optional Jasper Server, it may take several minutes to become available.

Wait several minutes after starting the system with the Jasper Server loaded before accessing the Custom Reports menu item. 

TCG-SNMP restart generates unknown status

When restarting the (new) TCG-SNMP connector, the initial poll may generate UNKNOWN status for the network interfaces. 

We recommend adjusting the notification rules for this to avoid alarm fatigue. 

Cron-Controlled GroundWork containers generate SUSPENDED alerts

Jobs scheduled VIA the cron container generate SUSPENDED alerts. This is correct behavior, but may cause unwanted alarms.

We recommend adjusting the notification rules for this to avoid alarm fatigue. A separate rule for the DOCK-H:cadvisor group with a 1-minute delay can suppress these alarms.

Unattended mode install is not enabled

The installer won't support the --unattended  mode option to install standalone with default settings in this version. 

This convenience feature will be enabled again in future versions.  

Archive Migration initially incomplete

Upgrades to the system will migrate the foundation database but will not completely migrate the archive database until the first archive run (overnight in the cron timezone)

This may affect any queries you want to run against the archive database, especially those for host address values, but only for the day of upgrade. 


We don't have any especially important announcements as of 8.2.3, other than to say how much we appreciate all our GroundWork Customers! 

Supported Versions

Current supported versions of GroundWork Monitor Enterprise include the latest versions 8.2.3, 8.2.2, 8.2.1, 8.2.0, 8.1.3, and version 7.2.1. Support for version 7.2.1 will expire December 31, 2022 (see GroundWork Monitor Enterprise Sunset note below). Support for 8.0.x is now expired. For supported architectures and browser compatibility see System Requirements.

GroundWork Monitor Enterprise 7.x Sunsetting

Support for version 7.2.1 will expire December 31, 2022.

We have extended support for 7.2.x for another year, to give some of the more complex customers in our installed base more time to transition. GroundWork 7.x will be retired from active support at the end of this year. Customers with support contracts for GroundWork Monitor 7.x will continue to receive support from GroundWork Support for this version until December 31, 2022, and for 8.x thereafter. It's our goal at GroundWork Open Source to make the transition from GroundWork Monitor Enterprise 7.x to GroundWork Monitor Enterprise 8 as seamless as possible for our Customers and Partners. Please contact GroundWork Support and let us help you plan and make this transition.

Related Resources

Copyright 2004-2022 GroundWork Open Source, Inc. ("GroundWork"). All rights reserved. Use is subject to GroundWork commercial license terms. GroundWork Monitor products are released under the terms of the various public and commercial licenses. For information on licensing and open source elements please see Licenses used in GroundWork. GroundWork, GroundWork Open Source, GroundWork Monitor Professional, GroundWork Monitor Open Source, GroundWork Community Edition, GroundWork Monitor Enterprise, GroundWork Foundation, GroundWork Status Viewer, Monarch, and GroundWork Guava are trademarks of GroundWork Open Source, Inc. Other trademarks, logos and service marks (each, a "Mark") used in GroundWork’s products, including Nagios, which is a registered trademark of Ethan Galstad, are the property of other third parties. These Marks may not be used without the prior written consent of GroundWork Open Source or the third party that owns the respective Mark.