Release Notes for GroundWork Monitor
CONTENTS
Overview
GroundWork Monitor Enterprise | Version 8.0.1 | Release
These release notes describe the new features and improvements, known issues and limitations for GroundWork Monitor 8.0.1. They also provide announcements as of version 8.0.1, including currently supported and end-of-life versions of GroundWork Monitor.
New features
GroundWork Monitor 8.0.1 offers a few new key features and improvements compared to the previous 8.0.0 release.
Links to internal and external pages
You can now link to any page in GroundWork or any other (external) system from any service, host, host group, service group, or custom group. Links are either internal (e.g., to a Grafana dashboard) or external (e.g., to a Wiki you maintain with your run book information). Any link can be for just one service, all services in a group, or all services in GroundWork.
Role based access can be used to restrict visibility of links. There's also a private link feature to make a link you add be just for your user. » Learn more
New filter save button
If you create a filter for a specific named resource, you can now save that filter for later. » Learn more
Google Cloud service discovery
The Google cloud connector now discovers the services you deploy on demand. » Learn more
Cloud Hub support for counters as delta gauges
You can now graph counter-type metrics as deltas (gauge-type) when you monitor them with any Cloud Hub connector. » Learn more
Fixed issues
This section describes the fixes we have included in this maintenance release. There are a relatively large number of fixes due to version 8.0.1 being primarily a bug-fix release to follow the initial 8.0.0 offering.
| Key | Summary/Notes | Component(s) |
|---|---|---|
| GROUNDWORK-530 | Intermittent session issues when multiple tabs open | UI framework |
| GROUNDWORK-526 | Auto-discovery NMAP scan fails | Discovery |
| GROUNDWORK-764 | NOCBoard Status sort is very slow and intermittent | NOC Board |
| GROUNDWORK-788 | Commit removes scheduled downtime | Monarch |
| GROUNDWORK-702 | BSM notification message link is for old status viewer | BSM, NoMa |
| GROUNDWORK-736 | Having Only the User Role and no other roles locks user out of system | Roles |
| GROUNDWORK-744 | Monarch hostgroups fail creation when contact groups assigned | Monarch |
| GROUNDWORK-761 | Google Cloud Connector asks for Project Name, when what it needs is project ID | Google Cloud Connector, Cloud Hub |
| GROUNDWORK-461 | GW8 Installer Should Detect Prerequisites in Base System | Installer |
| GROUNDWORK-535 | NoMa.yaml file moved to /usr/local/noma/etc | NoMa |
| GROUNDWORK-512 | Service group creation needs a way to multi-select | Custom Groups |
| GROUNDWORK-667 | SNMP symbolic IDs not loading | Plugins |
| GROUNDWORK-734 | Too Many Errors on FileBeat container | Docker |
| GROUNDWORK-215 | RStools time zones should match the browser time | RStools |
| GROUNDWORK-463 | Add index deletion for old elastic indexes | Elastic |
| GROUNDWORK-702 | BSM notification message link is for old status viewer | BSM, NoMa |
| GROUNDWORK-434 | Master Cipher Key Update for LDAP Credentials | LDAP |
| GROUNDWORK-126 | NeDi d3js map does not work | NeDi |
| GROUNDWORK-730 | Default crontab entry for Nedi missing | NeDi, crontab |
| GROUNDWORK-741 | Nagios(tm) UI Browser Timezone | NagiosCGIs |
| GROUNDWORK-743 | check_nrpe returns "Error - Could not complete SSL handshake" | plugins |
| GROUNDWORK-820 | Using LDAP perturbs roles based access rights to hosts | LDAP |
Known issues
This section lists any known issues and limitations with work-arounds.
| Category | Title | Description | Work-around |
|---|---|---|---|
| Monitoring Plugins | Some plugins may not work | The plugins included with GroundWork Monitor 8.0.1 are incompletely tested. | If you encounter a plugin you need to work that doesn't, please file a support case. We will get you a working version as soon as possible, and include it in later releases. |
| Acknowledgements | No host down acknowledgement button | The Status Summary for a host does not include a button to acknowledge when a host is down. | You can acknowledge this condition using the check boxes on the host listings and choosing "ack selected". |
| Acknowledgements | Can't acknowledge a service from a SLA dashboard | SLA Dashboards displayed in the SLA Carousel have a right-click context menu, but the Acknowledge option is not active. | Use the To statusviewer option to acknowledge. |
| 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 isn't a work-around, but then again there's no hard in leaving these user accounts alone. They will fail login once the LDAP server is inactive. |
| 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. |
| Comments | Ack comments and Downtime comments doubled | On Nagios hosts/services, you may notice comments are sometimes doubled. | These are redundant comments. They can be deleted with the "trashcan" icon. |
| Reports | Some custom reports have errors | Some of the custom reports for availability and events don't get created correctly. | This issue will be fixed in a future release. |
| Automation | The data source path is not correct | If you migrate your monarch database from a 7.x installation of GroundWork, you may see that the data source path in the automation schema is pointing to the wrong (old) path. | Replace the incorrect path in any schema you need to use. It is generally: /usr/local/groundwork/monarch/automation/data/<filename> |
| LDAP | If you change the master cypher key, LDAP may fail to connect | There is an intermittent race condition that affects the LDAP connection when you update the master cypher. You won't be able to use LDAP to connect if this occurs. | You can resolve this situation by restarting the groundwork container: cd gw8 docker-compose kill groundwork docker-compose up -d groundwork |
Announcements
The table below outline End-of-Life versions as of version 8.0.0. Current supported versions of GroundWork Monitor Enterprise include the latest version 8.0.1, 8.0.0, and version 7.2.1. For supported architectures and browser compatibility see System Requirements.
| Version | EoL Announcement | EoL Effective Date |
|---|---|---|
| 7.2.0 | 11/29/19 Customers should begin transitioning off the EoL version to the latest version. | (12/09/2019 release date of 8.0.0) GroundWork will no longer provide technical support for GroundWork Monitor version 7.2.0 or earlier. Customers using older versions are advised to contact GroundWork Support regarding upgrade options. Latest release is 7.2.1, and is supported. |
Copyright 2004-2020 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.