GroundWork Monitor Enterprise Edition | Version 8.2.2 | Release 02/03/2022
These release notes describe the new features and improvements, fixed Issues, and known Issues and limitations for GroundWork Monitor 8.2.2. They also provide announcements as of version 8.2.2, 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.
GroundWork Monitor 8.2.2 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.
This section describes improvements including feature requests in the 8.2.2 release.
Missing hosts and services
Elements (hosts, services and service groups) removed from monitoring were also deleted from the BSM group. Fixed behavior.
Need a way to reset the Nats queues
Operation to clear the NATS queues.
Telegraf output plugin for GroundWork
New Telegraf output plugin for public open source use.
Update Telegraf regex processor plugin for field and tag names as well as values
processors.regex.tags plugin supports this
Improve transit defines
Improvements made to reduce parser complexity and prevent compiling errors on TCG updates.
Update custom polling script to write out results to InfluxDB API
New version of scripting.
Upgrade Yii Framework to latest version (1.1.24)
Update PHP framework version.
Upgrade PHP to 7.4 for RStools Image
Review/Modify Comment cleanup script
Script improvements made.
Status Mapping (Team Assignment) feature
Added team status mapper feature request.
Add "Last Year" and "This Year" period to SLA Widgets on SLA Dashboard
Periods add for SLA dashboards.
Add link "To status-viewer" on dashboard for Custom Groups
UI appears to work as expected.
Use optional GZIP compression for TCG
TCG should be able to send compressed payloads. Fixed.
Update IP Address field on Host
The Synchronizer only adds and removes hosts, it does not update hosts, exception to this behavior for the new IP Address field.
Security update for postgres container.
Updated postgres to version 10.19
Add Docker health checks as a metric for the Docker connector
Feature request added.
GroundWork Messenger 24/7 rule lifespan too short
GroundWork Messenger includes capability to limit notifications to a certain time frame. Increased the default end date of this to 12/31/2099, from the value of 12/31/2021.
add DBD::Pg and CollageQuery to nagios container
It has been requested that the Perl DBD::Pg module, which is presently included in the monarch container, also be added to the nagios container.
Dalek services building improvements
Release process related update.
Additional Team Assignment requirements
Added two additional search fields.
Add Severity column to NOC Board service row
display the Severity field from the last Event in the LogMessage table in the service area of each in the NOC Board.
Improve the Status viewer message to support new lines
Added lines in message span field.
Upgrade Net-SNMP to 5.9.1 in monarch and nagios containers
Upgraded Net-SNMP 5.8 to Net-SNMP 5.9.1.
This section describes the fixes we have included in the 8.2.2 release.
Black List feature not working for merged hosts
Fixed, with confirmation dialog and now not shown in Status.
Black List works only temporarily
May need 10 minute wait.
Comments are not added to generated output (json or html)
Comments now exported.
Macro [DOWNTIMESTATUS] missing from dropdown
Macros [AUTHOR] and [DOWNTIMESTATUS] now exist in dropdown.
NeDi can't be accessed by LDAP users
The NeDi UI fails to resolve if accessed by a user authenticated w/ LDAP. Fixed.
TCG synchronizer fails to delete host from Nagios hostgroup it no longer belongs to
TCG synchronizer fails to delete host from Foundation
A deleted host does not get removed from Foundation. Fixed.
CE has link to knowledge base EULA instead of new EULA
EULA link updated.
Installer leaves image archives in gw8 directory
Image archives deleted.
Telegraf panics on v3 trap
Telegraf either processes the trap (if configured with correct v3 settings) or ignores it. Fixed.
HI Alias fails to hide APM host
APM can use an alias to hide unwanted hostnames otherwise automatically created. Fixed.
Need TELEGRAF application type migration and seed data
"yiic downtime cleanpastdowntimes" has bad option parsing
Decreased container size
Release process related update. Fixed.
Cloud Hub image building improvements
Release process related update. Fixed.
Cloud Hub exceptions on metric edit
Scripted downtime deletion fails
RStools container health check is broken
Individual database backup procedure fails
Login screen support link needs to be updated
NOC Board auto-refresh does not refresh
Every NOC board should auto-update without collapsing active un-shaded NOC Boards. Fixed.
Known Issues and Limitations
This section lists any known issues and limitations with work-arounds.
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.
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.
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.
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.
Important announcements as of 8.2.2.
Current supported versions of GroundWork Monitor Enterprise include the latest versions 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.
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.