Uptime Infrastructure Monitor Version 7.7.
...
3 Release Notes -
...
August 2016
| Table of Contents | ||||
|---|---|---|---|---|
|
| Note |
|---|
Uptime versionversions 7.7 and 7.7 is.2 are no longer available for download. Because of the improvements included in the latest version, please download and install Uptime version 7.7. 23. |
About Version 7.7.
...
3
Uptime Infrastructure Monitor (Uptime IM) version 7.7.2 x 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. For more information about additional fixes in this release, see Resolved Issues in 7.7.2.
| Info |
|---|
This Release Notes document describes changes to the 7.7 and, 7.7.2 releases. |
New and Improved Features
, and 7.7.3 releases. For more information about the fixed issues in this release, see Resolved Issues at the end of this topic. |
New and Improved Features
Uptime Infrastructure Monitor 7.7 includes the Uptime Infrastructure Monitor 7.7 includes the following new and improved features.
...
Visit Uptime Infrastructure Monitor's Knowledge Base for the latest comprehensive listing comprehensive listing of currently supported monitoring station, database, and agent platformsagent platforms. The The following summarizes platform support changes for Uptime for Uptime Infrastructure Monitor since the previous the previous release.
Monitoring Station
...
The Uptime Infrastructure Monitor 7.7 release affects users who have deployed plugins.
Upgrading Plugins
The Uptime The Uptime Infrastructure Monitor 7.7 upgrade process is as follows:
- Uptime Infrastructure Monitor: The conversion process scans your existing plugins to verify they are based on The Grid.
- Uptime Infrastructure Monitor: Plugins that are recognized as previously downloaded from The Grid are flagged for an upgrade and re-versioned at 0.9.
- User: To complete the plugin conversion process, after upgrading Uptime upgrading Uptime Infrastructure Monitor proceed to the Extension Manager (Services > Add Service Monitor > Want More? Search for monitors.). All plugins are flagged for an upgrade (these are supposed to show v0.9):
- User: Upgrade each plugin.
- Uptime Infrastructure Monitor: After upgrading, The Grid-based plugins display as version 1.0 to signify the reboot to unified extension deployment, regardless of what their previous version was.
- User: Moving forward, use the Extension Manager to manage your plugins.
- User: Uninstall the Plug-in Manager, as it is no longer needed to manage plugins.
Installing Uptime Infrastructure Monitor
The Uptime The Uptime Infrastructure Monitor Support Portal provides various documents and articles that guide you through a first-time installation or upgrade.
...
A complete, first-time deployment of Uptime 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.
...
You can only upgrade directly to Uptime to Uptime Infrastructure Monitor 7.7 if your current installed version is version 7.6.x or 7.5. Users on version 7.1 must upgrade to version 7.3, then 7.5 before upgrading to 7.7. Users on version 7.2 or 7.3 must upgrade to 7.5 before upgrading to 7.7.
...
| Info |
|---|
If you are working with a version of Uptime Infrastructure Monitor that is customized in any manner beyond the standard installation downloaded from the Uptime the Uptime Infrastructure Monitor Web site, contact Technical Support before performing an upgrade. Some customization steps include the following:
|
...
| UT-16403 | Resolve empty email distribution list error upon edit |
| UT-16400 | Resolve inability to save new HTTP / Web Services / SOAP (Advanced) service monitor |
| UT-16388, UT-16351 | Resolve deletion and re-addition of VMs causing deletion of master (and all child) monitors from service groups |
| UT-16384 | Update default Uptime service names from up.time to Uptime |
| UT-16371 | Update support of both Uptime and uptime spellings in Windows Agent 7.7 |
| UT-16370 | Resolve duplicate elements |
| UT-16369 | Resolve unavailable Uptime Data Collector after Uptime Installation |
| UT-16368 | Resolve 500: Proxy Error on some gadgets after upgrading to 7.7 |
| UT-16367 | Resolve VMware elements marked as (deleted) and Database Not Responding issue on VM profile page after upgrade to 7.6.1. build 6 |
| UT-16366 | Upgrade OpenSSL version for Linux Apache to version 1.0.2g |
| UT-16365 | Resolve create and edit issues on Action Profile in Uptime 7.6.1 |
| UT-16356 | Resolve inability to add elements on fresh install with Oracle datastore |
| UT-16355 | Resolve wrong exception handling in ServiceNow implementation |
| UT-16348 | Resolve Agent not starting on RHEL7.x with xinetd installed and not running as daemon if xinetd missing |
| UT-16347 | Resolve existing VMs being configured as newly-discovered VMs after upgrading to Uptime 7.6.1 |
| UT-16343 | Resolve WMI elements changing to Agent + VMware when additional monitoring scan runs after adding vCenter |
| UT-16342 | Resolve element info panel for VMware + agent type showing incorrect information |
| UT-16338 | Resolve Elements being added in limbo state between agent and WMI |
| UT-16333 | Resolve inability to uninstall Uptime |
| UT-16314 | Resolve Uptime hang during monitoring |
| UT-16286 | Verify support of Windows 10, SUSE v12.0, Ubuntu 15.10, Solaris 11.2 |
| UT-16269 | Resolve error adding Monitoring Station as Agent because it's already added at start |
| UT-16217 | Resolve inability to add File System capacity monitor to servers brought in through VMware |
| UT-16216 | Resolve problem adding Process Count Check monitor to VM + Agent elements |
| UT-15939 | Resolve AIX Agent reporting physical CPU count instead of socket count and update AIX Agent version number |
| UT-15598 | Resolve inability to be add snmp network devices to Uptime |
| UT-15590 | Update Agent support for Red Hat 7.x |
| UT-15551 | Update Linux Agent for RHEL 7 does not have ifconfig |
Known Issues
Upgrade
After upgrading from Uptime Infrastructure Monitor 7.6.1 to 7.7.x, an older login page appears. Click Ctrl + F5 to refresh the page and the new login page appears.
New Installation
Resolved Issues in 7.7.3 (Build 2 released 2016-08-03)
| UT-16445 | Update Service Monitor text fields to accept special characters |
| UT-16425 | Resolve HTTP monitor issue introduced in Uptime 7.7.2 |
| UT-16368 | Resolve proxy error on some gadgets after upgrade to Uptime 7.7 |
| UT-16274 | Resolve Agent failure in Windows 2008 R2 cluster while monitoring event IDs |
| UT-15939 | Update AIX Agent reporting details regarding Socket Count and CPU Count |
Known Issues
Upgrade
After upgrading from Uptime Infrastructure Monitor 7.6.1 to 7.7.x, an older login page appears. Click Ctrl + F5 to refresh the page and the new login page appears.
New Installation
If the user does not launch Uptime Infrastructure Monitor from the installer and does 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:
...
If the option to automatically remove deleted VMs was NOT selected at the vCenter level, all of the "old" VMs include (deleted) after the name. This suffix may accumulate resulting in multiple (deleted) entries after the name.
If the option to automatically remove deleted VMs from Uptime IM WAS selected at the vCenter level, you will not see any "duplicate" VMs. It simply appears as though the vCenter elements have had all their service monitors stripped away.
Unfortunately, any historical data collected before the vCenter element deletion is also lost regardless of the setting to automatically remove deleted.
If this issue affected you, please contact Support for more information about restoring lost service monitors.
...
Support for more information about restoring lost service monitors.
Other known issues
| UT-17068 | Uptime creates a high number of database threads every other Sunday night. |
| UT-17065 | Disk Performance Stats are unavailable with MS SQL datastore. |
| UT-17063 | Upgrades to 7.7.x from UT 7.6.1 fail with errors on Oracle 11G. |
| UT-17050 | The Resource Hot Spot report does not work with MS SQL and Oracle datastores. |
| UT-16441 | When editing a Service Monitor, the defaults are populated even when other settings were previously saved. |
| UT-16440 | The Linux Agent daemon doesn't auto-start when rebooting systemd environments |
| UT-16416 | Users receive a Database Unavailable error after upgrading to Uptime 7.7 and adding a network device. |
| UT-16365 | Issues exist when users create and edit an Action Profile in Uptime 7.6.1. |
| UT-16288 | Adding vCenter before adding WMI/Agentless servers prevents the Auto-Discovery Wizard from adding services. |
| UT-15880 | When converting VMs as part of a vCenter upgrade or migration, VMs recreated in Uptime with new UUIDs properly discover the Agent, but are not properly converted from VM-basic to VM+Agent. |
Contacting IDERA
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.
...
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 [email protected]
Support uptime- [email protected] / http://support.uptimesoftware.com
...