The Top Interfaces By Traffic graph didn't change when different directions were selected.

WhatsConfigured thresholds caused .ASP timeout errors and/or performance issues in the web interface.

Adding or removing devices from a Configuration Management task caused duplicate Alert Center thresholds to be created.

WhatsUp Gold architecture was improved to better accommodate large groups in the Audit Policy Log

The Configuration Management Policy Audit Log displayed invalid values in the Ignore Case and Regex columns.

The Custom map layout was improved in several ways including the implementation of a functional grid, a method by which to lock map nodes in place, a method by which to manually manipulate links, etc.

The RemoteDbConfig utility fails during upgrade if the WhatsUpGold SQL Account does not have the "View Any Database" permission.

Dictionary Key Violation occurred for WhatsVirtual Performance Metrics.

WhatsUp Gold displayed IP addresses as display names for discovered devices even when the hostnames could be resolved.

WhatsUp Gold has improved the ability of discovery to scan large address ranges.

Menu options applicable to managing custom links between devices on the Custom Layout map view weren't functioning properly.

Users may now specify ports to exclude during rescan using database script from TS.

WhatsUp Gold now supports Cisco Catalyst 9300 devices.

WhatsUp Gold now contains a new percent variable (%Device.MonitorState) which emulates the pre-18.3 %Device.State percent variable behavior as %Device.State was modified prior to the last release.

Enabling the File checksum option prevented the successful creation of a File Property monitor with SHA hash.

WhatsUp Gold can now receive SNMPv3 traps with authentication & encryption.

The default message included with email actions has been modified for clarity due to confusion stemming from new/revised percent variables.

Links displayed on the Custom Map Layout and associated data can now be refreshed.

WhatsUp Gold now contains a percent variable which reports simple device status without any additional information (e.g., down monitors).

Scheduled discovery configurations did not save properly.

Discovery failed to successfully connect some end devices without SNMP on the map.

Network Traffic Analysis dashboard views failed to load properly and forced logout.

Some scalability pollers went down randomly requiring a manual service restart.

Customers may now add devices and begin monitoring using a public API.

Discovery service stopped responding during a discovery scan.

SNMP Performance monitors were assigned to devices based upon role when they do NOT respond to that OID, even if set to Check Support First.

Customers interested in monitoring just a small part of the network now have the ability to add IP addresses/devices to an exception list which can then be excluded from a discovery.

Discovery failed to successfully discover Juniper devices.

The Folder Monitor was unable to retrieve folder information when the Include sub-folders option was enabled.

WhatsUp Gold now contains a new percent variable (%Device.ManualMaintenanceReason) which reports the reason a device went into maintenance mode.

The online help topic applicable to the use of percent variables has been modified to better explain how %Device.Status is resolved.

Discovery was unable to successfully discover Aruba Instant access points.

WhatsUp Gold help documentation was updated to include procedures for configuring Azure billing.

Devices being monitored changed roles to invalid roles based on scan rules.

WhatsUp Gold users now have the ability to import/export device-specific monitors using a Swagger API.

VMWare collected performance monitors often failed with the following error: The underlying connection was closed: An unexpected error occurred on a receive.

WhatsUp Gold implemented support for nested vCenters.

WhatsUp Gold fan, temperature, and power supply monitors are now compatible with and assigned automatically to Cisco Catalyst 2960 / 2960G and 2930 devices.

Bulk Set Maintenance Schedule configurations did not save properly.

Running discovery using a hostfile no longer named a device based off what was in the host file.

Some reports failed to open/display properly following upgrade to WhatsUp Gold 2019.

Discovery failed to successfully connect some end devices without SNMP on the map.  

Links between devices were not successfully created with LLDP.

Dynamic group membership updater task encountered an exception; VIEW SERVER STATE permission was denied.

Some groups were not properly displayed in the map view.

Following VMWare discovery, some incorrect links were added to the map and some exisitng links were removed.

The primary role assigned to a device changed after refreshing the device in discovery.

Placing too many real-time performance monitor reports on one dashboard view generated the following error: RPM_TEST_MONITOR_QUEUE_LENGTH_EXCEEDED

Interface reports fail Arithmetic overflow error converting expression to data type bigint

Interface Performance Monitor hourly interface data collection rollup failed.

Online help referred to the incorrect program file path for WhatsUp Gold-related folders.

WhatsUp Gold Live incorrectly categorized errors when certain virtual devices had no VMWare credentials assigned.