Skip to end of metadata
Go to start of metadata

Uptime Infrastructure Monitor Version 7.8.2 Release Notes - May 2017

Icon

Uptime Infrastructure Monitor 7.8 is no longer available for download. Because of the improvements included in the latest version, please download and install version 7.8.2.

About Version 7.8.2

Uptime Infrastructure Monitor (Uptime IM) version 7.8.2 includes many vulnerability fixes for increased application security. This release fixes all high- and medium-priority issues as well as most low-priority issues present in earlier versions. Quite a few other bug fixes are also included in this release.

Icon

This Release Notes document describes changes to the 7.8.x releases. For more information about the fixed issues in this release, see Resolved Issues at the end of this topic.

 

New and Improved Features in Uptime 7.8.2

Uptime Infrastructure Monitor 7.8.2 includes the following new and improved features.

Supports new versions of web services

Uptime Infrastructure Monitor 7.8.2 updates web services to new versions, which resolve outstanding security issues. Current versions include:

  • Apache 2.4.25 (Win64)
  • PHP 5.6.30
  • OpenSSL 1.0.2k
Icon

Apache 2.4.25 requires the Microsoft Visual C++ runtime for Visual Studio 2012 SP4 to be installed. You can install it manually or the installer will do it for you. download this package from Microsoft at https://www.microsoft.com/en-us/download/details.aspx?id=30679

Includes updated gadgets and plugins

Several gadgets and plugins have been reworked and improved. See Upgrading Plugins for information on accessing these updates.

  • Improved The Grid for ease-of-use and formatting updates
  • Capacity Planning Gadget
  • Capacity Planning What-if Gadget
  • Metric Chart Gadget
  • Network Gauge Gadget
  • Top Resources Gadget
  • Web Transaction Monitor Plugin
  • VMware ESX Datastore Capacity Monitor Plugin

New Problem Report (PR) export and import functionality

Problem Report (PR) generation, export, and import user interface and functionality are greatly improved.

Improved PR export features:

  • ability for the user to export config only or config and performance data and specify what time period is desired
  • UI reflects the current state and progress of PR generation
  • UI provides the ability for the user to select the location where you want to save PRs
  • UI clearly displays where the PRs are stored
  • UI includes a button to upload PRs to the IDERA Support server
  • ability to schedule automatic PR generation
  • better display of existing PRs including Status and Action buttons

Improved PR import feature:

  • process is improved to provide better performance, error checking, and status reporting

New and Improved Features in Uptime 7.8.0

Uptime Infrastructure Monitor 7.8.0 includes the following new and improved features.

Supports monitoring for Hyper-V virtual machines

Monitoring of Microsoft Hyper-V virtual machines now is supported in Uptime Infrastructure Monitor 7.8. This support mirrors most of the features already supported for VMware and was testing using Microsoft Windows 2012 R2.

Because the features and functions for VMware and Hyper-V VMs are similar, many of the help wiki topics include information about both platforms. For information specific to Hyper-V, see Monitoring Virtual Environments and Virtual System Monitoring Concepts.

Improved security for Solaris, AIX, and HP-UX agents

Uptime Infrastructure Monitor 7.8 includes improvements to security for Oracle Solaris, IBM AIX, and HP-UX agents by communicating through stunnel and OpenSSL. Both products should be installed on the Agent server before completing the secure install of UT 7.8. If stunnel or OpenSSL is not present, the installer defaults to a regular installation.

Improved reporting by allowing users to configure daily reports to include only a selection of time

If you want an Uptime Infrastructure Monitor report to only include data from certain hours during the day, version 7.8 allows you to select those hours from the dropdown lists in the Daily Hours section of the Reports tab. Note that this time is local to the monitoring station. For example, if you want to report to cover the hours from 1:00 a.m. to 1:00 p.m., select 1:00 from the Start dropdown list, and 13:00 from the End dropdown list. For more information about this feature, see Using Reports.

Added support for SSL in WebLogic Service Monitors

The WebLogic Service Monitor is updated to support SSL in Uptime Infrastructure Monitor 7.8. Note that any SSL self-signed certificates manually added to the trusted store is overwritten upon upgrade and must be reinstalled after the upgrade is complete. For more information about this process, see the Application Monitors section about WebLogic.

Added support for vSphere SDK to version 6

To help VMware SDK product users, this version of Uptime Infrastructure includes support for VMware vSphere SDK version 6.

Returned support to monitor SNMP v1-only devices

Support for SNMP v1, which was removed in a previous version of Uptime Infrastructure Monitor, is again available to monitor SNMP v1-only devices. You can add an SNMP v1 device by selecting Network Device while in the Add System/Network Device page only.

Improved usability

  • The Pin on Image gadget now displays the list of pinnable dashboard elements in alphanumeric order.
  • The list of groups available in the Parent Group drop-down now displays in alphanumeric order.
  • In the Infrastructure edit view, infrastructure elements are now presented in a tree view that allows for more logical system naming and easier to understand relationships between systems.

Platform Support and Integration Changes

Visit Uptime Infrastructure Monitor's Knowledge Base for the latest comprehensive listing of currently supported monitoring station, database, and agent platforms. The following summarizes platform support changes for Uptime Infrastructure Monitor since the previous release. The following icons are used to describe the type of support available in a version:

(tick) Supported and tested

(plus) Support added in this release

(warning) Supported but not tested

(minus) Support removed in this release

Monitoring Station

For an expanded list of supported monitoring station platforms, see see Supported Monitoring Station Platforms in Uptime Infrastructure Monitor.

Operating System and VersionUptime Infrastructure Monitor Version
7.8.x7.77.6
Red Hat Enterprise Linux 5.10 (minus)(tick)
Red Hat Enterprise Linux 6.4 (minus)(tick)
Red Hat Enterprise Linux 6.5 (minus)(tick)
Red Hat Enterprise Linux 6.7(tick)(plus) 
Red Hat Enterprise Linux 7.0(minus)(plus) 
Red Hat Enterprise Linux 7.1(warning)(plus) 
Red Hat Enterprise Linux 7.2(tick)(plus) 
Red Hat Enterprise Linux 7.3(plus)  
SUSE Linux Enterprise Server 11.3(minus)(warning)(tick)
SUSE Linux Enterprise Server 11.4(plus)  
SUSE Linux Enterprise Server 12.0(warning)(plus) 
SUSE Linux Enterprise Server 12.1(plus)  
Windows Server 2008 R2 SP1(warning)(warning)(tick)
Windows Server 2012(tick)(tick)(tick)
Windows Server 2012 R2(tick)(tick)(tick)
Windows Server 2016(tick)(plus) 
Windows 7 SP1 (minus)(tick)
Windows 10(tick)(tick)(plus)

Agents

For an expanded list of supported agent platforms, see Supported Agent Platforms in Uptime Infrastructure Monitor.

Windows Systems

Operating System and VersionAgent Version
7.8.x7.77.6
Windows 7 SP1 Professional and Enterprise(minus)(warning)(tick)
Windows 8 Professional and Enterprise(warning)(warning)(warning)
Windows 8.1 Professional and Enterprise(warning)(tick)(tick)
Windows 10 Professional and Enterprise(tick)(plus) 
Windows Server 2008 Standard and Enterprise(warning)(warning)(warning)
Windows Server 2008 R2 Standard and Enterprise(warning)(warning)(warning)
Windows Server 2008 R2 SP1 Standard and Enterprise(tick)(tick)(tick)
Windows Server 2012 Essentials and Standard(warning)(warning)(warning)
Windows Server 2012 R2 Essentials and Standard(tick)(tick)(tick)
Windows Server 2016 Essentials and Standard(tick)(plus) 

Linux Systems

RPM Agent (x86/64 unless otherwise noted)

Operating System and VersionAgent Version
7.8.x7.77.6
Red Hat Enterprise Linux 5.7 to 5.9 (minus)(tick)
Red Hat Enterprise Linux 5.10 and 5.11 (minus)(warning)
Red Hat Enterprise Linux 6.4 (minus)(tick)
Red Hat Enterprise Linux 6.5(minus)(warning)(tick)
Red Hat Enterprise Linux 6.6 and 6.7(warning)(plus) 
Red Hat Enterprise Linux 6.8(plus)  
Red Hat Enterprise Linux 7.0 and 7.1(warning)(plus) 
Red Hat Enterprise Linux 7.2(tick)(plus) 
Red Hat Enterprise Linux 7.3(plus)  
SUSE Linux Server 10.3 (minus)(warning)
SUSE Linux Server 10.4 (minus)(warning)
SUSE Linux Server 11.0 (minus)(warning)
SUSE Linux Server 11.1 (minus)(warning)
SUSE Linux Server 11.2 to 11.3(tick)(tick)(tick)
SUSE Linux Server 11.4(plus)  
SUSE Linux Server 12(tick)(plus) 
SUSE Linux Server 12.1(plus)  

DEB Agent (x86/64 only)

Operating System and VersionAgent Version
7.8.x7.77.6
Ubuntu Server 12.04 LTS (minus)(warning)
Ubuntu Server 14.04 LTS(warning)(warning)(tick)
Ubuntu Server 16.04 LTS(tick)(plus) 
Ubuntu Server 17.04 LTS(plus)  
Debian 7(warning)(warning)(warning)
Debian 8(warning)(warning)(warning)

Unix Systems - AIX

Operating System and VersionArchitectureAgent Version
7.8.x
AIX 7.1 TL3POWER7(tick)
AIX 7.1 TL4POWER7(plus)
AIX 7.2 TL0POWER7(plus)

Unix Systems - HP-UX

Operating System and VersionArchitectureAgent Version
7.8.x
HP-UX 11.31 (11i v3)PA-RISC/IA64/Itanium(tick)

Unix Systems - Oracle Solaris

Operating System and VersionAgent Version
7.8.x
Solaris 10 U9, U10(warning)
Solaris 11.0(warning)
Solaris 11.1 (SPARC/x86)(tick)

Agentless Monitoring

For an expanded list of supported agentless monitoring platforms, see Supported Agentless Platforms in Uptime Infrastructure Monitor.

IBM pSeries Systems

Platform and VersionUptime Infrastructure Monitor Version
7.8.x7.77.6
HMC v6R1.3(warning)(warning)(warning)
HMC v7R3.x(warning)(warning)(warning)
HMC v7R7.1.0(tick)(tick)(tick)

VMware Systems

Platform and VersionUptime Infrastructure Monitor Version
7.8.x7.77.6
ESX / ESXi 4.1 (minus)(warning)
ESXi 5.0(warning)(warning)(warning)
ESXi 5.1(warning)(warning)(warning)
ESXi 5.5 GA(warning)(warning)(warning)
ESXi 5.5 U1(warning)(warning)(warning)
ESXi 5.5 U2(warning)(warning)(warning)
ESXi 5.5 U3(tick)(tick)(plus)
ESXi 6.0 GA(warning)(warning)(plus)
ESXi 6.0 U1(warning)(warning)(plus)
ESXi 6.0 U2(tick)(plus) 
vCenter 4 (minus)(warning)
vCenter 5.0(warning)(warning)(warning)
vCenter 5.1(warning)(warning)(warning)
vCenter 5.5(warning)(warning)(warning)
vCenter 6.0(tick)(tick)(plus)

WMI Monitoring

Platform and VersionUptime Infrastructure Monitor Version
7.8.x7.77.6
Windows 7 SP1 Professional and Enterprise(warning)(warning)(tick)
Windows 8 Professional and Enterprise(warning)(warning)(warning)
Windows 8.1 Professional and Enterprise(warning)(tick)(tick)
Windows 10 Professional and Enterprise(tick)(plus) 
Windows Server 2008 Standard and Enterprise(warning)(warning)(warning)
Windows Server 2008 R2 Standard and Enterprise(warning)(warning)(warning)
Windows Server 2008 R2 SP1 Standard and Enterprise(tick)(tick)(tick)
Windows Server 2012 Essentials and Standard(warning)(warning)(warning)
Windows Server 2012 R2 Essentials and Standard(tick)(tick)(tick)
Windows Server 2016 Essentials and Standard(plus)  

Databases

For an expanded list of supported databases, see Supported Databases in Uptime Infrastructure Monitor.

Database Type and VersionUptime Infrastructure Monitor Version
7.8.x7.77.6
MySQL 5.5 64-bit (Bundled)(minus)(tick)(tick)
MySQL 5.6 64-bit (Bundled)(plus)  
MySQL 5.7 64-bit (Bundled)(plus)  
Oracle 11g R2 (11.2.0.4)(minus)(tick)(tick)
Oracle 12c (12.1.0.2)(tick)(tick)(tick)
Microsoft SQL Server 2012(minus)(tick)(tick)
Microsoft SQL Server 2012 SP1(minus)(tick)(tick)
Microsoft SQL Server 2012 SP3(plus)  
Microsoft SQL Server 2014 SP1(plus)  
Microsoft SQL Server 2016(plus)  

Web Browsers

Uptime Infrastructure Monitor is available on the latest versions of Internet Explorer, Mozilla Firefox, Google Chrome, and Microsoft Edge. For an expanded list of supported web browsers, see Supported Browsers in Uptime Infrastructure Monitor.

Installing Uptime Infrastructure Monitor

The Uptime Infrastructure Monitor Support Portal provides various documents and articles that guide you through a first-time installation or upgrade.

Icon

Antivirus software blocks STUNNEL installation. You should disable any antivirus software before doing an Uptime Infrastructure Monitor installation or upgrade.

Installing for the First Time

A complete, first-time deployment of Uptime Infrastructure Monitor and its agents is a straightforward process. Refer to the Installation and Quick Start Guide for complete instructions on performing a first-time installation.

Upgrade Notices

Icon

It is important to note that upgrading to Uptime Infrastructure Monitor 7.8.x may take 30 minutes or longer to complete because of the upgrade of MySQL from 5.5.x to 5.7. Based on our experience, it requires approximately 1.5 hours for every 50GB of database disk used by MySQL.

Icon

Make sure you have enough space before attempting to upgrade to Uptime Infrastructure Monitor 7.8. You should have at least 40% free space before beginning the upgrade.

Upgrade Preparation Steps

STEP 1: Restore settings after an upgrade when using a custom configuration.

The Uptime Infrastructure Monitor 7.8.x data collector includes a maxpermgen size of 160. This is up from 128 MB in Uptime Infrastructure Monitor 7.7 and earlier. Users who require custom or higher settings can reference the old config file stored at c:\uptime\config-backup\[prior uptime version]\uptime (Windows) or uptime/config-backup/[prior uptime version]/uptime/uptime.jcnf (Linux) and restore the settings after the upgrade. A data collector restart is required. Otherwise the customizations may be lost.

STEP 2: Make necessary Apache configuration changes.

Upgrading the Uptime Monitoring Station will upgrade Apache, PHP, and OpenSSL. This will overwrite the Apache configuration and PHP configuration files. For users who have modified the uptime\apache\conf\httpd.conf or uptime\apache\php\php.ini, the old files will be available in the uptime\config-backup\[old uptime version]\apache\conf and php folders. When the upgrade is complete, customizations can be copied over to the new files. There are several changes in these new configuration files so please do not simply overwrite the file.

STEP 3: Back up the Certificate Store.

The WebLogic Service Monitor is updated to support SSL in Uptime Infrastructure Monitor 7.8.x. Also, email round trip service monitors using or any other service using self-signed certificates manually added to the trusted store will be overwritten upon upgrade and must be reinstalled after the upgrade is complete. For more information about this process, see the Application Monitors section about WebLogic. Because this is a pain, and you may not be aware this was ever done, it is a good idea to back it up and restore it after an upgrade. Simply back up the uptime/jre/lib/security/cacerts file prior to upgrade. Post upgrade, shut down the Uptime Data Collector (uptime core service in Linux) and Uptime Controller (Win and Linux) services, copy your old cacerts file back into that folder, and start the service up again.

STEP 4: Make changes to and back up MySQL my.ini before attempting an upgrade for installations previously upgraded to Uptime 7.7.x.

Users upgrading to Uptime Infrastructure Monitor 7.8.x who previously upgraded to Uptime 7.7.x from an earlier version should back up their MySQL my.ini file before upgrading, make the following change, and then replace the newly-installed my.ini file with the backup after completing the upgrade.

Use the following steps:

  1. Stop your Uptime services.
  2. In uptime/mysql/my.ini, comment out table_cache=256. This must be commented out because the MySQL 5.7 version is named table_open_cache.
  3. Search for and, if present, comment out innodb_buffer_pool_instance. This must be commented out because the MySQL 5.7 version is named innodb_buffer_pool_instances.
  4. Back up uptime/mysql/my.ini.
  5. Run the Uptime Infrastructure Monitor 7.8.x installer. Note that the upgrade of tables to the new database engine may take from minutes to several hours to complete depending on database size.
  6. Replace uptime/mysql/my.ini with the backed up version.

Other Upgrade Considerations

Upgrade paths

You can only upgrade directly to Uptime Infrastructure Monitor 7.8.x if your currently installed version is version 7.7.x or 7.6.x. Users on version 7.1 must upgrade to version 7.3, then 7.5 before upgrading to 7.7.3, then 7.8.2. Upgrades are possible across only two minor releases. Users who are running version 6.0 or 6.0.1 must upgrade to 7.0 > 7.1 > 7.3 > 7.5 > 7.7.3 > 7.8.2. For more information, see Upgrading to Uptime Infrastructure Monitor 7.6 and later.

Users who are running version 5.5 or earlier must upgrade to 6.0 or 6.0.1 as a starting point. (Refer to the Uptime Infrastructure Monitor Knowledge Base for specific version upgrade paths.) If you are eligible for a direct upgrade path, you can upgrade using the installer for your Monitoring Station’s operating system. The upgrade process installs new features, and does not modify or delete your existing data.

Refer to one of the following topics if your current version is older than the version required for a direct upgrade:

Clustered environment considerations

Users who have a clustered environment should continue using the Uptime 7.7.3 agent. A change in how the UUID is formatted in Uptime 7.8.x causes issues when monitoring clusters. For more information about how SQL Server cluster monitoring works in Uptime Infrastructure Monitor, see the IDERA Community article, Monitor MS-SQL Clusters and Always-On Availability Groups.

Apache/PHP/OpenSSL upgrade considerations

Users who manually updated Apache/PHP/OpenSSL in previous Uptime Infrastructure Monitor release using these instructions and who want to upgrade to Uptime Infrastructure Monitor 7.8.2, must perform the following steps before upgrading:

  1. Open uptime/conf/httpd.conf
  2. Change
    Listen UIMHTTP
    to
    Listen [port on which you want the web server to respond] i.e. Listen 9999
  3. Save the file.
  4. Upgrade to Uptime Infrastructure Monitor 7.8.2.

For more information about manually updating Apache/PHP/OpenSSL, see Manually Update Apache and PHP on Windows and Manually Update Apache and PHP on Linux.

MSSQL jdbcDB backend users upgrade considerations

Users upgrading from Uptime Infrastructure Monitor 7.8.0 to 7.8.2 who use MSSQL as a database backend should check their [uptime install folder]\uptime.conf and take note of the drivers used. If the sqljdbc4.jar driver is not being used, nothing needs to be done. Look for:

#To use the sqljdbc4.jar instead of the default jtds jar, uncomment the following two lines, place the jar file in the uptime/core folder and restart the collector service.

If dbDriverClass is uncommented, you should comment it out prior to running the upgrade. If you wish to continue using the MSSQL native JDBC driver, you should copy sqljdbc4.jar out of the [uptime install folder]\core folder prior to upgrading as it will get removed during the upgrade. If this task is not performed, you will notice that the upgrade program fails to reinstall the MSSQL JDBC driver and the upgrade will break.

You must download the sqljdbc4.jar driver for MSSQL (https://www.microsoft.com/en-us/download/details.aspx?id=11774 and put it in the uptime/core directory after the upgrade, uncomment the line we commented prior, and restart Uptime data collector (core in Linux) service to pick up the change.

Upgrading Plugins

The Uptime Infrastructure Monitor 7.8.x upgrade process for plugins is as follows:

  1. Uptime Infrastructure Monitor: The conversion process scans your existing plugins to verify they are based on The Grid (the-grid.uptimesoftware.com).
  2. User: To complete the plugin conversion process, after upgrading Uptime Infrastructure Monitor proceed to the Extension Manager (Services > Add Service Monitor > Want More? Search for monitors.). Some plugins may be flagged for an upgrade:
  3. User: Upgrade each plugin.
  4. User: Moving forward, use this process to manage your plugins.
  5. User: Users upgrading from versions of Uptime Infrastructure Monitor prior to 7.x.x can uninstall the Plug-in Manager, as it is no longer needed to manage plugins.
Icon

If you have any expiration check service monitors in your environment, please verify that they are working correctly after the upgrade is complete. If you notice an error with SSLv3 handshaking in the status output, please re-create the service monitor.

Upgrading Gadgets

The Uptime Infrastructure Monitor 7.8.x upgrade process is as follows: Some gadgets were adjusted for 7.8.x and will require your attention if you are running on an MS-SQL or ORACLE database back end.

Affected gadgets include:

  • Capacity Gadget
  • Capacity What-If Gadget
  • Metric Chart
  • Network Gauge
  • Top Resources

Please install the ODBC driver for your database on the Uptime Monitoring Station.

Use the following links and steps when installing the drivers:

Icon

For MS-SQL and Oracle: If database and monitoring station are installed on the same machine, the drivers may already be installed. If this is the case, only the DSN will need to be created. Also, the exact names as specified below must be used for the connection or the gadgets will not work.

For MS-SQL

  1. Download and install the Microsoft ODBC driver 11 or later using the following link:
    https://www.microsoft.com/en-us/download/confirmation.aspx?id=36434
  2. In the gadget code, we use the data source name (DSN) you enter in this step. It is important you use this exact name.
    Create a DSN named ODBC Driver for SQL Server in the Windows settings at the following path:
    Control Panel > All Control Panel Items > Administrative Tools > ODBC Data Source (64-bit) > System DSN
  3. Enter your database details when creating the DSN.

For Oracle

  1. Follow the steps mentioned on this article to setup the ODBC driver for Oracle on your machine:
    https://tensix.com/2012/06/setting-up-an-oracle-odbc-driver-and-data-source/
  2. In the gadget code, we use the data source name (DSN) you enter in this step. It is important you use this exact name.
    Create a DSN named ODBC Driver for Oracle in the Windows settings at the following path:
    Control Panel > All Control Panel Items > Administrative Tools > ODBC Data Source (64-bit) > System DSN
  3. Enter your database details when creating the DSN.
UT-17810Move DB driver configuration settings to properties file
UT-17643Infrastructure view does not display all elements
UT-17540Agent installation on Solaris Sparc not working
UT-17517Auto-Discovery wizard Add button enabled without any object selection
UT-17229Uptime 7.7.3 needing weekly rebooting due to unresponsive GUI
UT-17092Moving to MS-SQL DataStore causes issues with some gadgets
UT-17090Unable to add a network device on a fresh installation of Uptime 7.7.3 with MS-SQL database backend
UT-17079Controller version displaying Uptime 7.7.2 in Uptime 7.7.3 release
UT-17073User-disabled default threshold values for some monitors return in the next editing session
UT-17065Disk Performance Stats unavailable when using MS-SQL DataStore
UT-17063Upgrade from 7.6.1 failed with multiple errors on Oracle 11g
UT-17050Resource Hot Spot report does not work with MS-SQL and Oracle datastores
UT-16441Service Monitor defaults populated on edit
UT-16440Linux Agent Daemon doesn't auto-start on reboot for systemd environments
UT-16427SQL Server (Advanced Metrics) monitor only works with 32-bit Agent
UT-16416Uptime 7.7 displays Database Unavailable error after adding network device
UT-16392Alert Profile Template in Custom Format disappears upon being clicked
UT-16372Allow SNMP Poller to be applied to any element type
UT-16382Add link to help in Installation Size window on Linux
UT-16368Proxy error on some gadgets after upgrading to Uptime 7.7
UT-16365Create and edit issues on Action Profile in Uptime 7.6.1
UT-16360Service Monitor Metrics report for ESX (Advanced Metrics) as PDF contains incorrect headers on graph
UT-16354Auto-Discovery Wizard Select All Devices check box not working
UT-16318Uptime not operational after installation on RHEL 7.1 or 7.2
UT-16315, UT-16262All completed Auto-Discovery Wizard fields are cleared/reset after an error message appears
UT-16314Uptime hangs during monitoring due to leak of DB resources.
UT16311Data Collector unavailable message includes invalid help link URL
UT-16297Linux Agent on Ubuntu 14.04 psinfo error
UT-16296Uptime uninstallation does not remove stunnel
UT-16292Linux Agent on Ubuntu returns wrong OS version
UT-16288Auto-Discovery Wizard adding vCenter before adding WMI / Agentless prevents the wizard from adding services
UT-16265Auto-Discovery Wizard doesn't use all the space of an expanded window
UT-16259Default Agent Service Check monitor contains no criteria for alert
UT-16228Auto-Discovery Wizard finds and adds vCenter server but does not assign servers to groups or create service groups or services
UT-16227Auto-discovery Wizard displays found items even with Hide Items Already Found selected
UT-16226Upgrade to Uptime 7.7 from 7.6.1 is set for SNMP v2 but when you launch the Auto-Discovery Wizard the SNMP v2 checkbox is not selected by default
UT-16225Auto-Discovery Back and Cancel button functionality needs clarification
UT-16222Auto-Discovery Wizard doesn't stop
UT-16221Create new alert profile results in long-running script
UT-16218

Remote Reporting functionality is blank under the Config-tab in Uptime version 7.6.1

UT-16207Allow users to specify where to put discovered VMs
UT-16179Alert/Action Profiles trigger response before updating the element, causing confusing data
UT-16178License Info page displays a message stating the latest version of Uptime is in use even when it is not
UT-16177Edit Alert Profile dialog takes several minutes to load
UT-16149Saving a dashboard with the same name but different capitalization yields an error
UT-16160Values starting with a decimal point returned to Uptime Apache Status monitor get ignored
UT-16149Saving Dashboard with the same name but different capitalization results in error
UT-16145Network discovery fails on the Dashboard > Network link when no network devices exist
UT-16128Weblogic service monitor fails when SSL is enabled
UT-16124Missing agent.cfg option for Agent daemon IP restriction
UT-16119Parsing metrics incorrectly showing zeros in graph and report
UT-16111Agent on Linux or AIX returns incorrect number of Blocked Processes
UT-16105Cannot add agent pSeries LPAR(VIO) and receive message "Error Found, hostname can't be null"
UT-16094Agent installer file names need to indicate 32-bit or 64-bit and use correct Uptime spelling
UT-16093Linux Agent chk4.sh grep/egrep script to find the process count incorrect
UT-16081Arbitrary file upload vulnerability in post2file.php
UT-16045Merge functionality of HTTP monitor, IIS Webpage plugin, and SOAP plugin
UT-16031Highchart CPU Usage graph y-axis range larger than range of data points
UT-16015File System Capacity Growth report displays excluded file systems
UT-16007Allow user to specify which group elements are assigned when adding vCenter
UT-15998Reattached service monitors cannot be detached and edited
UT-15996Highchart CSS file references incorrect path name and causes graph crashes
UT-15975Resource Usage report displays black outlines in the graph and scheduled report
UT-15944AIX Agent should use lsps -s instead of pstat -s in perfparse.sh
UT-15938Add ability to configure and schedule reports that cover only a period of time in a day
UT-15888HP system displays partial info for network interfaces with names longer than 8 characters
UT-15887Increase buffer return size for Web service monitor
UT-15880Recreating VMs in vCenter does not successfully convert to VM+Agent when UUID is changed
UT-15867ESX Hosts with Unlicensed status and licenses exceeded
UT-15831Windows Element Pages In/sec always displays 0
UT-15827Issues with monitoring station support for RHEL 7.x
UT-15814Index needed on ranged_object table to improve query times
UT-15812Alert profile not removed from master service monitor
UT-15800Adding a network device with no string value present for any index value displays an error
UT-15613Improve security for Solaris, AIX, HP-UX Agents
UT-15528Action Profile should not save password in plain text
UT-15432SNMP poller does not retain metrics
UT-15098Detach/reattach service group member monitor causes name conflict error
PLUG-369Capacity Planning What-If reporting MB instead of GB on y-axis for DataStore
PLUG-325SNMP Poller needs generic SNMP functionality
PLUG-304Metric Chart gadget Memory graph displays negative values
PLUG-302Resource Scan gadget missing from extensions.JSON
PLUG-281IIS Webpage Check needs a threshold setting based on the HTTP status
PLUG-275Oracle Extendable Tablespace Check plugin XML definition: Percent Free label should be Percent Used
PLUG-277Move functionality from Cisco Router CPU and Memory Monitor into SNMP Poller
PLUG-266FS Capacity Logical Disk doesn't recognize a single backslash in a path for exclusions
PLUG-256NetApp Monitor fails immediately if SNMP is unavailable
PLUG-374Tags broken on The Grid
PLUG-372Web Application Transaction Monitor fails during playback of site
PLUG-326Perform consistent update of all Plugin/Gadget information
PLUG-190Update the plugin 'VMware ESX Datastore Capacity Monitor'
UT-18080Upgrade to 7.8 Blank System Profile Pages for vCenters and elements in them
UT-18073Upgrading the product to Apache/2.4.25 (Win64) PHP/5.6.30 OpenSSL/1.0.2k breaks SSL Certificate Expiry service monitor
UT-18070Upgrade of mssql backend 7.8 to 7.8.2 ends up unusable if using jdbc driver
UT-17989Licensing page on autodiscovery has typo
UT-17988About Uptime screen reporting incorrect OS version
UT-17987Capacity Planning What-If gadget never loads any elements
UT-17981Action Profile - Windows Service action for Agent does not work
UT-17980PREXPORT failing caused by: java.sql.SQLException: TDS Protocol error: Invalid packet type 0x0 at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2486)
UT-17979Unable to add physical server to Uptime
UT-17917SQL Server Tablespace Check monitor fails when database names use unconventional identifiers
UT-179107.8 Problem Report import throws errors com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed
UT-17907Fix support info in wizard
UT-17905Custom formatting for alert profiles cannot be enabled
UT-17898Uptime on MSSQL backend is having lots of deadlocks
UT-17896Ensure Uptime and installer are compatible with SQL Server 2016
UT-17891Update README.txt file in Linux agents
UT-17888Incorrect conditional test in VirtualMachineFilter
UT-178817.8 Problem Report not functional
UT-17878Confirm CVE vulnerabilities are fixed
UT-17873Unable to add vCenter
UT-17868Resolved UIM installer issues
UT-17861RHEL v7.2 Agent not installing properly
UT-17860Ongoing connection issues with MSSQL backend in 7.8
UT-17858Agent fails when upgrading on Ubuntu
UT-17833PHP errors around error exception handling
UT-17832PHP errors around VMware
UT-17831Modify behavior of data collector when dashboards zip/folder is found missing on start
UT-17830Modify behavior of data collector when gadget zip/folder is found missing on start
UT-17825Primport failing - improve PR import/export machinery
UT-17681Reporting instance errors with DB connection timeout after a few reports
UT-17630Modify resetdb and upgrade script to flush all Apache sessions
UT-17569Make Uptime upgrade preserve keystore and cacerts store
UT-17492Using obsolete versions PHP 5.4.45 and OpenSSL 1.0.2g
UT-17363Installer takes a long time to load on install or uninstall
UT-17361Resource Usage report shows no value for Hyper-V server
UT-17099Uptime install/upgrade script logic for installing plugins/gadgets is faulty
UT-17068Uptime creates extremely high number of database connections every other Sunday night
UT-16334Update Apache and its components including SSL
UT-15886Reports still showing ignored VMs

Known Issues

Upgrade

  • After upgrading from Uptime Infrastructure Monitor 7.6.1 to 7.7.x, an older login page may appear. Click Ctrl + F5 to refresh the page and the new login page appears.
  • Users who upgrade from Uptime Infrastructure Monitor 7.7.3 to 7.8.x:
    • may notice additional time required when upgrading due to the upgrade of MySQL 5.6 to 5.7
    • may notice the Uptime Agent service is removed without the agent being uninstalled. If you want to monitor the Monitoring Station using an agent, go to Add/Remove Programs in the Control Panel, uninstall the Uptime Agent, and then reinstall the agent available in the uptime-agent folder.

Upgrading on Ubuntu causes the Agent to fail

When running apt-get update and apt-get upgrade, the following error is caused by missing LSB tags and overrides from /opt/uptime-agent/bin/upt_daemon.sh:

insserv: warning: script 'S99uptm_daemon' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: Starting upt_daemon.sh depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting upt_daemon.sh depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting upt_daemon.sh depends on plymouth and therefore on system facility `$all' which can not be true!

To prevent compatibility issues please add the following LSB tags and override to the header of upt_daemon.sh:

### BEGIN INIT INFO
# Provides: uptime-agent-daemon
# Required-Start: $local_fs $network
# Required-Stop: $local_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Description: Uptime Agent Deamon
### END INIT INFO

Any HTTP service monitors created prior to upgrading to Uptime 7.8 fail after the upgrade is complete

An issue that appears when upgrading to Uptime Infrastructure Monitor 7.8.2 causes all existing HTTP (Web Services) service monitors to fail once the upgrade is complete. You can avoid this issue if, after upgrading, you open each HTTP service monitor for edit, and then save  without making any changes.

PHP version of Expiry plugin users must upgrade to new plugin version to work with Uptime Infrastructure Monitor 7.8.2

Current users who have PHP version of the Expiry plugin must upgrade to the new version of the plugin to properly work with Uptime Infrastructure Monitor 7.8.2. For more information on upgrading, see Upgrading Plugins. Note that you must restart the Uptime Data Collector once the Java version of the Expiry plugin completes installation.

New installations may not launch the Auto-Discovery Wizard from installer

If the user does not launch Uptime Infrastructure Monitor from the installer and does not receive the Auto-Discovery Wizard upon opening the product, change the URL to:

localhost:9999/autoDiscoveryWizard.php

Note that entering only localhost:9999 does not automatically run the wizard.

Uninstallation may not stop stunnel.exe process

When uninstalling Uptime Infrastructure Monitor, the uninstall does not automatically stop or kill the stunnel.exe process. In order to delete the Uptime directory during uninstallation, the user first must kill the stunnel.exe process.

Wait I/O report displays 0 instead of the correct value on elements using a Windows agent

Legacy code used in implementing the Wait I/O report for elements using a Windows agent is causing the report to display 0 instead of a proper value. In comparison, the same stat returned when using a Linux agent shows the correct value. This issue will be addressed in a future release.

Switching JDBC driver may cause crash at startup

Switching to an alternative MS-SQL JDBC driver (sqljdbc4.jar) may cause the UptimeDataCollector service to crash at startup. To avoid this issue, navigate to the SQL Server property by going to Server properties > Connection > Default Connection Options > no count, and clearing the checkbox.

Virtual Machine issues

In the Quick Snapshots for both VMware and Hyper-V, the Swap Usage vs. Swap Space sometimes displays '0 undefined.' This issue will be addressed in a future release.

Contacting Support

IDERA employees are proud to work with our clients around the globe to deliver exceptional customer service, including sales expertise, installation help, and support services.

Headquarters

Brookhollow Central III
2950 North Loop Freeway West
Suite 700
Houston, Texas 770092
USA

Phone                     713.523.4433

Support                  713.533.5003

Fax                          713.688.1924

Sales                       sales@idera.com

Support                   uptime-support@idera.com / http://support.uptimesoftware.com

Human Resources IDERA Careers

Copyright © 2017 IDERA, Inc.

IDERA, Inc. considers information included in this documentation to be proprietary. Your use of this information is subject to the terms and conditions of the applicable license agreement.

 

 

  • No labels