Release Notes for GroundWork Monitor
Version 8.2.0
GroundWork Monitor Enterprise | Version 8.2.0 | Release 05/05/2021
These release notes describe the new features and improvements, fixed Issues, and known Issues and limitations for GroundWork Monitor 8.2.0. They also provide announcements as of version 8.2.0, including currently supported and end-of-life versions of GroundWork Monitor.
New Features!
This release has two major features described below. In a nutshell, GroundWork Monitor Enterprise 8.2.0 has functionality designed to make notifications much easier to configure, faster and more effective to use. You can now also quickly and efficiently set up network interface monitoring and automatic network inventory tracking.
SNMP Monitoring
SNMP Monitoring largely replaces the Cacti functionality found in GroundWork Monitor 7.x. The difference is it's now automated! » Learn more
GroundWork Messenger
GroundWork Messenger (powered by GORT) is an enhanced monitoring notification tool used to configure system-wide alert notifications, including notifications for Cloud based and Nagios based elements. This new feature replaces the old NoMa application. » Learn more
- The GroundWork Messenger Notification Methods is presented in a separate screen from the Notification Engine, and currently allows for configuration of Curl, Email, Slack, and SMS notification methods.
- Notification Engine: The GroundWork Optimized Request Transmitter (GORT) is the backend part of GroundWork Messenger.
- The previous NoMa container, dockergw8_noma_daemon_1, has been removed from GroundWork Monitor and you will no longer see the noma process running. Now added is the GroundWork Messenger (GORT) container, dockergw8_gort_1, and another container, dockergw8_kafka_1, Kafka is a streaming message system. New migrations starting with GroundWork Monitor 8.2.0 will go from NoMa to GroundWork Messenger. The configuration data for GroundWork Messenger is still in the database and tables as was in NoMa. Those migrating will need to update the methods used post migration.
Improvements
This section describes improvements included in the 8.2.0-GA release.
Key | Summary | Notes |
---|---|---|
GROUNDWORK-1541 | Add monarch_create_host utility script | The monarch_create_host script is now included in the product to allow automated host creation with the API. |
GROUNDWORK-1529 | Update TCG Java Examples for Blog | Update TCG Java pull examples, upgrade Spring Boot to latest version including Prometheus Actuate end points. |
GROUNDWORK-1520 | Allow TCG APM Connect to directly set Host and Service Monitor Status | This enhancement allows for faster and more efficient state determination where the endpoint allows a state to be listed. |
GROUNDWORK-1512 | Need bc binary in monarch | "bc", a utility, is now available at the monarch container. This allows testing check scripts in the monarch GUI. |
GROUNDWORK-1504 | Add dass/Monarch convenience scripts for notifications, commit, build instance | Scripts now present in the monarch container and documented. |
GROUNDWORK-1489 | Improve appearance of Monarch help tooltips | Minor UI enhancement. |
GROUNDWORK-1477 | Bump up the PHP memory limit in RStools and NeDi | memory_limit setting directly modifiable in php.ini on a volume, default configuration changed. |
GROUNDWORK-1468 | Mark SLA Contracts as archived in SLA Management | SLA contracts may now age out, but not be deleted. This allows them to remain for reference purposes. |
GROUNDWORK-1465 | Foundation needs to send hostgroups and servicegroups with downtime messages | Kafka messages for host and service downtimes have hostgroups and servicegroups. |
GROUNDWORK-1455 | GORT Menu structure change (move Methods to submenu) | New notifications manager configuration of methods now in separate screen. |
GROUNDWORK-1442 | Add clusterstate plugin to GW8 nagios container | Latest version of plugin now included in the nagios container. This is an efficient way to manage the sometime complicated logic of cluster monitoring in Nagios. |
GROUNDWORK-1441 | Create version of EE without Elastic, Kibana, Logstash, filebeat, or curator | Option added in Installer to select installations for Curator, ELK, and TCG connectors APM, Elastic, and SNMP. |
GROUNDWORK-1430 | Add plugin platform table support for new GDMA platforms | The pluginplatform table in the monarch database now has content extended (both in a fresh install, and via migration script in an upgrade) to cover new GDMA platforms. |
GROUNDWORK-1427 | Connectors should provide "Status message" for hosts | Status message values now appear for TCG connectors. |
GROUNDWORK-1426 | Provide containerized tcg-snmp example in override.yml | Example of containerized SNMP connector is now in the default docker-compose.override.yml file. |
GROUNDWORK-1421 | Installer Updates for EE and Child installations | Improved installer to ask configuration questions early in the process, use a nicer GUI. |
GROUNDWORK-1395 | Make CAdvisor Internal Check Frequency Configurable | Can now be configured with a docker-compose env.var. |
GROUNDWORK-1348 | CAdvisor on Ubuntu logs warning messages | Upgraded to latest CAdvisor, added support for more detailed logging. |
GROUNDWORK-1337 | Allow downtime entered through Nagios CGI to be reflected in the Status Summary | If you like the Nagios CGIs and want to enter your downtime for Nagios hosts and services there, these will now work. We recommend you use the Downtime UI, however. |
GROUNDWORK-1326 | Provide scripted means of updating the credentialed user's password | Can now update credential user's password regularly through authenticated scripted means. |
GROUNDWORK-1273 | NOC Board Auto-expand feature should be able to expand > 1 board | All NOC Boards with auto-expand set will now get expanded. |
GROUNDWORK-1036 | Elastic connector needs some status text | Status text message added for Elastic connector. |
GROUNDWORK-1025 | Improvements for Dashboard, SLA and Downtime - Port from GW7 to GW8 | Updates made to various features in the Business/SLA dashboard and downtime UI are now incorporated. |
GROUNDWORK-922 | Indicate downtime more clearly in text | Host and service downtimes are now more clear with text. |
GROUNDWORK-218 | Add setting of timezone to browser timezone to NeDi | UI sets to browser timezone - this avoids confusion when viewing certain screens. |
Fixed Issues
This section describes the fixes we have included in the 8.2.0-GA release.
Key | Summary | Notes |
---|---|---|
GROUNDWORK-1547 | Need to delete Nagios-related Next Check Time fields during migration | Migration script updated to remove unused data in next check time. |
GROUNDWORK-1545 | Add/update metrics buttons should be on right | Minor UI fix. |
GROUNDWORK-1540 | Inconsistent spelling on license page | Minor UI fix. |
GROUNDWORK-1539 | Service-level timestamps are imbibing host-level data | Update in Foundation. This was needed to correct a minor timing mismatch between when data was actually processed, and when it was reported in status to have been processed. |
GROUNDWORK-1536 | LastPluginOutput in Status Summary includes Read More/Show less in copied text | Fixed. |
GROUNDWORK-1533 | Redundant setting in Ack dialog | Minor UI fix. |
GROUNDWORK-1515 | Downtimes failing for PMC hosts | Send command issue fixed. Downtimes now working for all hosts. |
GROUNDWORK-1514 | Test of Monarch inherited command line ignores inherited arguments | Properly inherits command arguments. Fixed. |
GROUNDWORK-1513 | NeDi Needs 2 more volumes | Additional volumes needed to support certain NeDi features added (notably RRDs for interface data) |
GROUNDWORK-1511 | Blue line in the middle of hostgroup/servicegroup availability graphs | The line is removed. |
GROUNDWORK-1507 | Edit revproxy:/etc/nginx/conf.d/redirect.conf if IPv6 stack is missing or disabled | If you aren't using IPv6, the configuration of the revproxy will not not need to be modified by hand in order to work. |
GROUNDWORK-1505 | Google Cloud Connector reports critical on zero value | Now reports OK. Fixed. |
GROUNDWORK-1501 | Link delete button not appearing - can't remove links | Minor UI fix. |
GROUNDWORK-1499 | Allow plugin download from older GDMA releases to work with GW8 | Revised and fixed. |
GROUNDWORK-1497 | Typo in info message in monarch_set_host_service_notification_interval script | Missing leading character fixed. |
GROUNDWORK-1490 | Status/Home timeframe selector is no longer dismissed on click | Fixed, selector does not linger. This will preserve the time selection for the length of the navigation session. |
GROUNDWORK-1482 | Immediate errors in rstools cron upon initial gw8 start | Character typo issue fixed. |
GROUNDWORK-1474 | NeDi graphs do not populate | Modifications made to crontab: graphs update properly now. |
GROUNDWORK-1473 | Monarch Test button shows extra output at end | service-check Test output no longer has the extra " - nagios" string appended. |
GROUNDWORK-1462 | Backup procedure does not backup custom plugins in the Nagios container | Backups now include all custom plugins added to the Nagios container |
GROUNDWORK-1461 | Downtime creation is synced between Nagios and RStools, but not deletion | Sync is now fixed. |
GROUNDWORK-1460 | Containerized elastic connector fails upon configuration | The containerized Elastic connector was unstable on configuration in some cases. This is now fixed. |
GROUNDWORK-1449 | Please allow colons in the host, hostgroup and service names in notifications | Colon now valid in defining notification rules |
GROUNDWORK-1447 | GDMA multihost mode must be supported in GW8 | The poller is now able to pull the files under the multihost build dir. Fixed. |
GROUNDWORK-1435 | DalekServices fails in deleteAgentOnConnection on delete TCG connector | This inventory control step was failing in prior versions and some inventory would be temporarily orphaned. This is now fixed. |
GROUNDWORK-1418 | Command to generate SLA Reports is not executed with correct timezone | Cron job changed to respect user's timezone selection in install. |
GROUNDWORK-1417 | AWS Cloud Hub connector creates non-functional CloudWatch HG on startup | There was an issue with the creation of a harmless hostgroup that is now fixed. |
GROUNDWORK-1384 | HTTP failure response for /api/events/stateTransitions: 0 Unknown Error | Added detail to alert that shows up when the browser loses connectivity to the server. |
GROUNDWORK-1373 | TCG logfile needs a file-size limit and regular rotation | Some TCG connectors had log files that were growing without bound that will now be rotated after upgrade. |
GROUNDWORK-1350 | Installer fails when /tmp mounted noexec | The installer now properly checks for this condition and declines politely to install until it is fixed. |
GROUNDWORK-1344 | Insufficient auth for Cloud Hub | There was a security issue where the Cloud Hub iframe could potentially leak configuration data to an unauthenticated user. This is fixed. |
GROUNDWORK-1341 | Status Metric graphs in random order on service info | Alphabetical sort functionality now working for the metrics on a service (when there are more than one). |
GROUNDWORK-1334 | Nagios connector host address improper caption | Fixed caption. |
GROUNDWORK-1333 | Elastic connector config gives inconsistent alerts for blank fields | Now user is given feedback when "Server Name" field is not properly filled and submitted. |
GROUNDWORK-1331 | Links to GW7 docs in monarch | Links fixed in Monarch to GroundWork Support 8 pages. |
GROUNDWORK-1257 | Bad sort icons for Cloud Hub metrics | Icons fixed. |
GROUNDWORK-1199 | Jasper server gives you login screen when logging in as user other than admin | Updated to use admin only, since our SSO is not supported with Jasper. |
GROUNDWORK-1013 | Add MetrIc and Update Metrics mouseovers not showing properly | UI fix. |
GROUNDWORK-416 | Jasper Reports Charts have random colors per monitor status | Fixed. |
(Previously a Known Issue) | Notification of contacts on acknowledgement did not work | This is now possible with the GroundWork Messenger application |
(Previously a Known Issue) | Container hostgroup was empty | This hostgroup is now populated with connector state resources. |
(Previously a Known Issue) | Docker connector did not detect service unknown on down containers | The unknown state is now properly displayed |
(Previously a Known Issue) | Some plugins did not work | We have now gone through the plugins and tested them all for basic functionality. |
Known Issues and Limitations
This section lists any known issues and limitations with work-arounds.
Category | Title/Description | Work-around |
---|---|---|
Notifications (GroundWork Messenger) | GroundWork Messenger notification system includes the capability of limiting notifications to a certain time frame. The most common, and default time frame is 24/7, which has a default expiration date of 12/31/2021. | This configuration is adjusted in Configuration > Notifications > Configuration > Time Frames. The Validity Information section for the Valid To field needs to be adjust to a later date e.g., 12/31/2099. Note this configuration change may result in queued notifications being sent, please contact GroundWork Support. |
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. |
LDAP | Cannot delete user 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. |
Business Service Monitoring | Default bsm-service-01 configured but empty. The service bsm-service-01 on host bsm-host is included as an example of Business Service Monitoring. It is in the unknown state as the member list is empty. | You can remove this (or add members) by going to the Configuration > BSM and SLAs > BSM > Manage Groups, and clicking the delete icon next to the group. |
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. |
Announcements
Important announcements as of 8.2.0.
Supported Versions
Current supported versions of GroundWork Monitor Enterprise include the latest versions 8.2.0, 8.1.3, 8.1.2, and version 7.2.1. Support for version 7.2.1 will expire December 31, 2021 (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 has will be retired from active support at the end of the coming 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
-
Page:
-
Page:
-
Page:
-
Page:
Copyright 2004-2021 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.