Uptime Infrastructure Monitor Version 7.8.3 Release Notes - September 2017

About Version 7.8.3

Uptime Infrastructure Monitor (Uptime IM) version 7.8.3 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.

New and Improved Features in Uptime 7.8.3

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

Includes updates for newer Scrutinizer integration authentication mode

An update to NetFlow Scrutinizer integration authentication to accept tokens instead of user name and passwords is addressed in Uptime Infrastructure Monitor 7.8.3. Only NetFlow Scrutinizer versions 16.7 and later support tokens. While using the netflow.username and netflow.password options still are available for previous version support, this release includes netflow.token to support the new authentication method. For more information about using NetFlow Scrutinizer, see Interfacing with Uptime Infrastructure Monitor.

Supports Big Endian and Little Endian modes for Agents on Linux/AIX POWER platforms

Uptime Infrastructure Monitor 7.8.3 now supports Big Endian and Little Endian modes for Agents on Linux/AIX POWER platforms.

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

• Apache 2.4.27 (Win64)
• PHP 5.6.31
• OpenSSL 1.0.2I

Includes new management information base (MIB) files

Uptime Infrastructure Monitor 7.8.3 includes MIB files for:

• PowerNet 4.1.7 and NetBotz 4.1.0, which apply to APC (Schneider Electric) infrastructure devices
• Dell Equallogic SAN
• Fortinet
• Nimble Storage

For more information about MIBs, see SNMP Monitoring Quick Start Guide.

Added new, more explanatory error messages to Auto Discovery

In order to improve user experience, Uptime Infrastructure Monitor 7.8.3 includes new, more explanatory error messages in the Auto Discovery wizard when the system fails to add network devices.

Removes default response time from Uptime default Service Monitors and Uptime Monitoring Station on MySQL, MSSQL, and Oracle

This release removes the Response Time default times for Warning and Critical messages on Uptime Infrastructure Monitor default Service Monitors and Uptime Monitoring Station on MySQL, MSSQL, and Oracle databases. These fields now have no value by default.

Discovers credentials for vCenters added through the Auto Discovery wizard

When you add a vCenter using the Auto Discovery wizard, Uptime Infrastructure Monitor now decodes the vCenter parameters and then properly labels and stores the associated element as a vCenter server.

Improves experience when adding Hyper-V or VMware VMs

Beginning with Uptime Infrastructure Monitor 7.8.3, we no longer attempt to discover WMI or Agents when adding powered off Hyper-V or VMware virtual machines. If Uptime finds that the VM is powered on, it will attempt to discover WMI or Agents.

Improves logging

This release includes the following improvements to logging functionality:

• Adds the option to output service monitor and platform performance result states to the uptime.log file. Such results are not normally important to log and can make the logs unnecessarily large. Now, by default, this information is no longer captured in the uptime.log file.
• Updates the logging configuration file in the ...uptime/templates folder. The logging.conf file contains additional information about common configuration options to capture logging details within your environment.

Installer includes new terms of use option

A new option in the Uptime Infrastructure Monitor 7.8.3 installer allows an admin to include text on the login page that the user must agree to before completing login to the product. A check box is included for the user to select for agreement. The text appearing in this field is managed in the Config > Uptime Configuration page and may be changed only by an administrator. This feature is not active by default. To add/change the text that appears, edit the file .../uptime/GUI/EULA.html. There is also an associated style sheet located at .../uptime/GUI/styles/EULA.css. To activate, change usg.terms=false to usg.terms=true.

Improves the Debian Agent installer

Uptime Infrastructure Monitor 7.8.3 includes an improved Debian Agent installer that improves the user experience and fixes some issues that occasionally caused the installation to fail.

Includes a JDK update

This release bundles JDK 7u141.

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

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:

Supported and tested

Support added in this release

Supported but not tested

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 Version	Uptime Infrastructure Monitor Version
	7.8.x	7.7	7.6
Red Hat Enterprise Linux 5.10
Red Hat Enterprise Linux 6.4
Red Hat Enterprise Linux 6.5
Red Hat Enterprise Linux 6.7
Red Hat Enterprise Linux 7.0
Red Hat Enterprise Linux 7.1
Red Hat Enterprise Linux 7.2
Red Hat Enterprise Linux 7.3
SUSE Linux Enterprise Server 11.3
SUSE Linux Enterprise Server 11.4
SUSE Linux Enterprise Server 12.0
SUSE Linux Enterprise Server 12.1
Windows Server 2008 R2 SP1
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016
Windows 7 SP1
Windows 10

Agents

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

Windows Systems

Operating System and Version	Agent Version
	7.8.x	7.7	7.6
Windows 7 SP1 Professional and Enterprise
Windows 8 Professional and Enterprise
Windows 8.1 Professional and Enterprise
Windows 10 Professional and Enterprise
Windows Server 2008 Standard and Enterprise
Windows Server 2008 R2 Standard and Enterprise
Windows Server 2008 R2 SP1 Standard and Enterprise
Windows Server 2012 Essentials and Standard
Windows Server 2012 R2 Essentials and Standard
Windows Server 2016 Essentials and Standard

Linux Systems

RPM Agent (x86/64 unless otherwise noted)

Operating System and Version	Agent Version
	7.8.x	7.7	7.6
Red Hat Enterprise Linux 5.7 to 5.9
Red Hat Enterprise Linux 5.10 and 5.11
Red Hat Enterprise Linux 6.4
Red Hat Enterprise Linux 6.5
Red Hat Enterprise Linux 6.6 and 6.7
Red Hat Enterprise Linux 6.8
Red Hat Enterprise Linux 7.0 and 7.1
Red Hat Enterprise Linux 7.2
Red Hat Enterprise Linux 7.3
SUSE Linux Server 10.3
SUSE Linux Server 10.4
SUSE Linux Server 11.0
SUSE Linux Server 11.1
SUSE Linux Server 11.2 to 11.3
SUSE Linux Server 11.4
SUSE Linux Server 12
SUSE Linux Server 12.1

DEB Agent (x86/64 only)

Operating System and Version	Agent Version
	7.8.x	7.7	7.6
Ubuntu Server 12.04 LTS
Ubuntu Server 14.04 LTS
Ubuntu Server 16.04 LTS
Ubuntu Server 17.04 LTS
Debian 7
Debian 8

Unix Systems - AIX

Operating System and Version	Architecture	Agent Version
		7.8.x
AIX 7.1 TL3	POWER7
AIX 7.1 TL4	POWER7
AIX 7.2 TL0	POWER7

Unix Systems - HP-UX

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

Unix Systems - Oracle Solaris

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

Agentless Monitoring

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

IBM pSeries Systems

Platform and Version	Uptime Infrastructure Monitor Version
	7.8.x	7.7	7.6
HMC v6R1.3
HMC v7R3.x
HMC v7R7.1.0

VMware Systems

Platform and Version	Uptime Infrastructure Monitor Version
	7.8.x	7.7	7.6
ESX / ESXi 4.1
ESXi 5.0
ESXi 5.1
ESXi 5.5 GA
ESXi 5.5 U1
ESXi 5.5 U2
ESXi 5.5 U3
ESXi 6.0 GA
ESXi 6.0 U1
ESXi 6.0 U2
vCenter 4
vCenter 5.0
vCenter 5.1
vCenter 5.5
vCenter 6.0

WMI Monitoring

Platform and Version	Uptime Infrastructure Monitor Version
	7.8.x	7.7	7.6
Windows 7 SP1 Professional and Enterprise
Windows 8 Professional and Enterprise
Windows 8.1 Professional and Enterprise
Windows 10 Professional and Enterprise
Windows Server 2008 Standard and Enterprise
Windows Server 2008 R2 Standard and Enterprise
Windows Server 2008 R2 SP1 Standard and Enterprise
Windows Server 2012 Essentials and Standard
Windows Server 2012 R2 Essentials and Standard
Windows Server 2016 Essentials and Standard

Databases

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

Database Type and Version	Uptime Infrastructure Monitor Version
	7.8.x	7.7	7.6
MySQL 5.5 64-bit (Bundled)
MySQL 5.6 64-bit (Bundled)
MySQL 5.7 64-bit (Bundled)
Oracle 11g R2 (11.2.0.4)
Oracle 12c (12.1.0.2)
Microsoft SQL Server 2012
Microsoft SQL Server 2012 SP1
Microsoft SQL Server 2012 SP3
Microsoft SQL Server 2014 SP1
Microsoft SQL Server 2016

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.

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

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.3. 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.3. 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:

• Upgrading to Uptime Infrastructure Monitor 7.6 and later
• Upgrading to Uptime Infrastructure Monitor 7.2 to 7.5
• Upgrading to Uptime Infrastructure Monitor 7.1 or Earlier

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 or later, 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.x.

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 or later 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.

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:

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.

Resolved Issues in 7.8 (Build 7 released 2017-02-02)

Resolved Issues in 7.8.2 (Build 2 released 2017-05-18)

Resolved Issues in 7.8.2 (Build 9 released 2017-08-09)

Resolved Issues in 7.8.3 (Build 3 released 2017-09-14)

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 from Uptime 7.8.0 to 7.8.3 may cause the Agent to not install or not appear in the Windows Control Panel

Users who update from Uptime Infrastructure Monitor 7.8.0 to 7.8.3 may notice that the Uptime Agent does not appear in the Windows Control Panel. If this occurs, note that the automatic installation of the Agent did not occur and you must manually start the installation.

CPU Utilization Ratio report incorrectly highlights CPU Ratios of 0.0

The CPU Utilization Ratio report highlights systems with a CPU ratio over 0.0. However, an error causes Uptime Infrastructure Monitor to highlight all CPU ratio results including values of 0.0.

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 or later 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 or later

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 or later. 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                       [email protected]

Support                   [email protected] / 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.