Uptime Infrastructure Monitor Version 7.

...

10 Release Notes -

...

August 2023

About Version 7.6.1

...

New and Improved Features in

...

This Release Notes document describes changes to both the 7.6.1, and recent 7.6 releases.

New and Improved Features

Uptime 7.10

Uptime Infrastructure Monitor 7.10 Uptime Infrastructure Monitor 7.6 includes the following new and improved features.

IDERA Rebranding

The new nameplate, including the new IDERA logo, is now displayed at the top of the Uptime product: IDERA Uptime Infrastructure Monitor. The product name changed from up.time to Uptime Infrastructure Monitor throughout the product. Note that a few items still retain the up.time name. For additional information about these items, see Known Issues.

Improved Agent Security

Uptime Infrastructure Monitor agents now include basic security options as part of the default install, especially SSL. This improvement also affects password authentication/key exchange. For more information about enabling SSL communication on an agent, see the Knowledge Base article Using SSL Communication with Linux-Based Agent.

This update also includes several security and vulnerability issues addressed in Resolved Issues.

SNMP Monitoring Improvements

Apply a regex filter to the index OID

When configuring an SNMP poller, you now can ignore rows in a column by applying a regex filter to the index object identifier (OID). The Add OID section of the SNMP Poller template now includes fields that allow you to select All Rows, Specific Rows, or Filter by Regex. This filter is applied at collection time. For more information about configuring SNMP monitoring, see Network Service Monitors.

Allow virtual OID appending

Uptime Infrastructure Monitor 7.6 now allows users to add multiple OIDs at a time by appending the virtual OID and no longer validate the OID in the SNMP poller. For more information about configuring SNMP monitoring, see Network Service Monitors.

Add agent monitors to Net-SNMP devices

Users now can add a NAS device to Uptime Infrastructure Monitor via Net-SNMP. Previously, while Uptime Infrastructure Monitor is aware of its file systems, there was no way to add an FSCAP monitor nor could it create a process count check monitor on this device despite knowing about the processes running on the system. You now can add these monitors to a Net-SNMP device. For more information about adding agent monitors, see Agent Monitors.

Support for VMware vSphere 6 and ESXi6

Uptime Infrastructure Monitor now supports VMware vSphere 6 and ESXi 6.

Resolved unexplained timeouts when adding a network device

Previously, Uptime Infrastructure Monitor returned a timeout message during the initial Add System/Network Device or Auto discovery wizards when a user attempted to add a network device. At the same time, the user was able to do an SNMP walk of these same devices without issue, signaling that the SNMP credentials were correct, but the routing or ACL rules that prevent Uptime Infrastructure Monitor from adding the same devices were not in place. This issue no longer occurs with an upgrade to this release.

Resolved Highchart graph rounding problem

When mousing over the data points on the Highchart graphs, some users would see percentages with excessive number of decimal places, for example 94.200000000000000009%. Uptime Infrastructure Monitor now displays only two decimal places.

Allow decimal values in Port Performance Check

Decimal values are now supported.  Also, added the units in brackets – Port Performance Check – i.e. Total Rate (%).  Added 3 decimal points of precision.

Custom In/Out Speeds

Users now can set the in/out data speed of a network device. The max port speed as determined by the device is used to calculate % usage (in and out). Previously, there was no accounting for the speed of the network on the other side of the connection.

Updated Bundled Platform Components

To address vulnerabilities issues, Uptime Infrastructure Monitor now supports the following platforms:

• PHP 5.4.45
• Apache 2.2.31
• OpenSSL 1.0.1p

Added Expand / Contract All Service Monitors

This release includes a toggle to expand or contract all Service Monitors on the Add Service Monitors page.

Updated NetFlow – Plixer Scrutinizer

Scrutinizer is a NetFlow analyzer and incident response system that takes advantage of communications standards, i.e. NetFlow and IPFIX for Cisco as well as other compatible switches and routers. It does this to retrieve and store network traffic information for users, systems, and applications. Scrutinizer allows administrators to monitor, graph, and report on network usage patterns, and to locate the heaviest traffic creators.

Scrutinizer can be integrated with Uptime Infrastructure Monitor. For more information about integrating Uptime IM Scrutinizer, see Integrating Scrutinizer with Uptime Infrastructure Monitor. Integration allows you to access all Scrutinizer features from the NetFlow dashboard within Uptime Infrastructure Monitor. If you do not currently have Scrutinizer, please contact IDERA Sales for more information at [email protected].  

Note that the NetFlow/Scrutinizer versions available on the Uptime Infrastructure Monitor download page are updated from version 11.5.2 to 15.8.  Scrutinizer version 15.8 is tested with Uptime Infrastructure Monitor versions 7.4, 7.5, and 7.6.  If you currently have Scrutinizer installed with these versions of Uptime Infrastructure Monitor, please refer to the upgrade instructions at: https://www.plixer.com/files/TheWindowsUpgradeGuide.pdf

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.

Agentless Monitoring

VMware vSphere 6	Image Removed
VMware ESXi 6	Image Removed

Upgrade Notices

The Uptime Infrastructure Monitor 7.6 release affects users who have deployed plugins.

Enhanced Alert Profile Variables Plugin

The functionality of the Enhanced Alert Profile Variables plugin is added directly to Uptime Infrastructure Monitor. If this plugin is installed, you must remove the plugin after upgrading to Uptime Infrastructure Monitor 7.3 or later to ensure email notifications continue to be properly sent. You can uninstall the plugin using the legacy Plug-in Manager.

If you already removed the Plug-in Manager from your Uptime Infrastructure Monitor installation, you can manually remove the Enhanced Alert Profile Variables plugin by deleting the alert_mod.jar from your <uptime_dir>/core/custom_jars/ directory, and then restarting the Uptime Infrastructure Monitor Data Collector service (uptime_core on Linux, and up.time Data Collector on Windows).

Upgrading Plugins

The Uptime Infrastructure Monitor 7.6 upgrade process is as follows:

1. Uptime Infrastructure Monitor: The conversion process scans your existing plugins to verify they are are based on The Grid.
2. Uptime Infrastructure Monitor: Plugins that are recognized as previously downloaded from The Grid are flagged for an upgrade and re-versioned at 0.9.
3. 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.). All plugins are flagged for an upgrade (these are supposed to show v0.9):
   Image Removed
4. User: Upgrade each plugin.
5. 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.
6. User: Moving forward, use the Extension Manager to manage your plugins.
7. User: Uninstall the Plug-in Manager, as it is no longer needed to manage plugins.

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.

Upgrading from a Previous Version

You can only upgrade directly to Uptime Infrastructure Monitor 7.6 if your current installed version is version 7.5 or 7.4. Users on version 7.1, 7.2, or 7.3 must upgrade to 7.4 before upgrading to 7.6.

Users who are running version 6.0 or 6.0.1 must upgrade to 7.0 > 7.1 > 7.3 > 7.4 or 7.5 before upgrading to 7.6. 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.

If your current version is older than the version required for a direct upgrade, refer to Upgrading to Uptime Infrastructure Monitor 7.2 and Later or Upgrading to Uptime Infrastructure Monitor 7.1 or Earlier for information on supported upgrade paths. There, you also find more detailed installation information, including specific upgrade paths.

Resolved Issues in 7.6 (Build 12 released 2015-12-03)

...

:

Anchor
UT-18867 UT-18867

Supports new versions of Apache/PHP/OpenSSL/TLS

Uptime Infrastructure Monitor 7.10 includes Apache/PHP/OpenSSL/TLS upgraded to the latest version.

Upgrade Notices

Upgrade Preparation Steps

Anchor
UT-17677 UT-17677

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

The Uptime Infrastructure Monitor 7.10.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 and later. Also, email round trip service monitors using or any other service using self-signed certificates manually added to the trusted store are 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.

Anchor
UT-17862 UT-17862

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.10.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.

To back up your MySQL.ini file

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.10.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.10.x if your currently installed version is version 7.8.6. Users on version 7.1 must upgrade to version 7.3, then 7.5 before upgrading to 7.7.3, then 7.8.6, 7.9, and finally 7.10. 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.6 > 7.9 > 7.10. 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 through 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 and later 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.2 or later.

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.

Anchor
UT-18070 UT-18070

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.

Changing the Default Uptime Username and Password

Uptime Infrastructure Monitor 7.9 introduced the use of encrypted passwords in the uptime.conf and uptime-controller.conf files.  In order to change the default Uptime username and password, you must first change them in the datastore (i.e. MySQL, MSSQL, or Oracle).  Then use the UptimeConfigUtility tool to apply the changes to the uptime.conf and uptime-controller.conf files.  

To use this utility

1. Open the terminal and change the directory to the scripts folder under the UIM install directory (..\uptime\scripts).
2. Below are the details to run the UptimeConfigUtility.

To check all options, use the help command as below:

java -jar UptimeConfigUtility.jar --help

[option] [description]

-path Path of configuration file must be passed as a first parameter

-t To set database type

-h To set hostname

-prt To set port number

-d To set database name

-u To set database username

-pwd To set database password

 To run

java -jar UptieConfigUtility.jar [option] [parameter_value]

For example

java -jar UptieConfigUtility.jar -path C:\uptime.conf -prt 8989 -d testDB

Upgrading Plugins

The Uptime Infrastructure Monitor 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: 
   Image Added
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 upgrade process is as follows: Some gadgets were adjusted for 7.8.x and later 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

For Oracle and MS-SQL users, please install the ODBC driver for your database on the Uptime monitoring station.

The following links and steps help you install the drivers.

Oracle ODBC Driver Linux Installation

1. Install unixODBC via your package manager (i.e. yum install unixodbc). This step installs unixODBC into your ‘/usr/lib64/’ directory.
2. Download and Install the latest version of the Oracle Instant Client Basic package, available from Oracle at http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html. Keep in mind that Uptime 7.2.x and later come bundled with 64-bit Apache/PHP, so you will need the Linux x86-64 package (i.e. oracle-instantclient12.1-basic-12.1.0.1.0-1.x86_64.rpm). Note that the 12.1 package also works with 11g databases. This package installs some of the required binaries/drivers for Oracle into /usr/lib/oracle/12.1/client64/lib/.
3. Download and install the ODBC: Additional libraries package, available from Oracle (i.e. oracle-instantclient12.1-odbc-12.1.0.1.0-1.x86_64.rpm). This package provides the actual ODBC Driver needed.

4. Edit the /etc/init.d/uptime_httpd script that starts Uptime’s apache, and then add the following lines to set some of the required environment variables. Note that this should be toward the beginning of the script and the end of the other export commands, such as export PATH , export MIBDIRS etc.

   export ORACLE_HOME=/usr/lib/oracle/12.1/client64 export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib

5. Restart the uptime_httpd service to pick up this change.

   /etc/init.d/uptime_httpd stop /etc/init.d/uptime_httpd start

6. Make sure to uncomment one of the odbc driver lines in /gadgets/definitions/uptime.Metricgadget/uptimeDB.php as explained above.

Anchor
OracleODBCDriverWindowsInstallation OracleODBCDriverWindowsInstallation

Oracle ODBC Driver Windows Installation

1. Install the Oracle Instant Client drivers or have the Oracle Client installed on the monitoring station. To get the Instant Client Download for Oracle, download the 64 bit drivers:
   http://www.oracle.com/technetwork/database/features/instant-client/index.html
   i.e. instantclient-basic-windows.x64-12.1.0.1.0.zip
2. Create a new directory C:\Oracle. Unzip the downloaded file into the new directory. You should now have C:\Oracle\instantclient_12_1 which contains a bunch of .dll & .sym files.
3. Download the Instant Client Package - ODBC from the same page above, i.e. instantclient-odbc-windows.x64-12.1.0.1.0.zip. Extract this zip into the same C:\Oracle\instantclient_12_1 path.
4. Open a command prompt in the C:\Oracle\instantclient_12_1 directory and run the odbc_install.exe which will install the Oracle ODBC drivers and setup the required Environment variables.
5. Run the Data Sources (ODBC) utility from the Windows Administrative Tools. Click the Drivers tab, and then confirm that you have an Oracle in instantclient driver listed. Note the name of that driver as this is required as the ODBC Driver Name when setting up the service monitor. (Likely it will be ‘Oracle in instantclient_12_1’ or ‘Oracle in OraClient12Home1’).
6. Update the Path Environment Variable to include the path to the Oracle driver. Append “;C:\Oracle\instantclient_12_1” to end of the variable. To set this variable, go to System Properties > Advanced > Environment Variables. Under System variables, find the path and edit it.
7. Make sure to uncomment one of the odbc driver lines in /gadgets/definitions/uptime.Metricgadget/uptimeDB.php as explained above.

If you are having trouble with installing just the Oracle InstantClient & ODBC, the likely issue is you are missing the Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) that includes the DLL that this driver needs. Another option is to install these drivers as part of the Oracle Data Access Components which is a bundle of Oracle drivers compared to the zips mentioned above. This bundle can be found on the Oracle website at http://www.oracle.com/technetwork/database/windows/downloads/index.html

Additional MSSQL/SQLServer Installation Steps

In order to use the Metric gadget gadget with a SQL Server-based Datastore, you will need to uncomment the appropriate ODBC Driver in uptime_dir/gadgets/definitions/uptime.Metricgadget/uptimeDB.php.

Windows Based monitoring stations will already have ODBC itself installed as part of Windows, and should be able to use the example provided in uptimeDB.php.

Linux based monitoring stations will require the unixODBC package to be installed. This package should include the /usr/lib64/libtdsodbc.so.0 SQL Server ODBC Driver needed for MSSQL/SQLserver. Which is also the example provided in uptimeDB.php

See Oracle ODBC Driver Linux Installation above for more details on installing unixODBC.

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 tables summarize 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
	7.10	7.9.x	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 - 8.0
Red Hat Enterprise Linux 9.0
SUSE Linux Enterprise Server 11.3
SUSE Linux Enterprise Server 11.4
SUSE Linux Enterprise Server 12.0
SUSE Linux Enterprise Server 12.1
SUSE Linux Enterprise Server 12.3
SUSE Linux Enterprise Server 15.3
Windows Server 2008 R2 SP1
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016
Windows Server 2019
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 - 5.9
Red Hat Enterprise Linux 5.10, 5.11
Red Hat Enterprise Linux 6.4
Red Hat Enterprise Linux 6.5
Red Hat Enterprise Linux 6.6, 6.7
Red Hat Enterprise Linux 6.8
Red Hat Enterprise Linux 7.0, 7.1
Red Hat Enterprise Linux 7.2
Red Hat Enterprise Linux 7.3
Red Hat Enterprise Linux 7.4
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, 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.6	7.7	7.6
Ubuntu Server 12.04 LTS
Ubuntu Server 14.04 LTS
Ubuntu Server 16.04 LTS
Ubuntu Server 17.04 LTS
Ubuntu Server 18.00 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
AIX 7.2 TL1	POWER8

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)
Solaris 11.3

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
	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
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
ESXi 6.5 GA
vCenter 4.0
vCenter 5.0
vCenter 5.1
vCenter 5.5
vCenter 6.0
vCenter 6.5
vCenter 7.0

WMI Monitoring

Platform and Version	Uptime Infrastructure Monitor Version
	7.8.x	7.7
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.10	7.9.x	7.8.x	7.7
MySQL 5.5 64-bit (Bundled)
MySQL 5.6 64-bit (Bundled)
MySQL 5.7 64-bit (Bundled)
MySQL 5.7.21 64-bit (Bundled)
MySQL 8.0.xx 64-bit (Bundled)
Oracle 11g R2 (11.2.0.4)
Oracle 12c (12.1.0.2)
Oracle 12c (12.2.0.1)
Oracle 12c R2 (12.2.2.x)
Oracle 18c
Oracle 19c
Microsoft SQL Server 2012
Microsoft SQL Server 2012 SP1
Microsoft SQL Server 2012 SP3
Microsoft SQL Server 2014 SP1
Microsoft SQL Server 2016
Microsoft SQL Server 2017
Microsoft SQL Server 2019
Microsoft SQL Server 2022

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.

Resolved Issues in 7.10 (Build 178 released 2023-08-10)

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

  • Anchor
    UT-18763 UT-18763

    may notice duplicate plugins: Uptime Status General and Uptime Status Performance

Anchor
UT-18868 UT-18868

Microsoft DCOM update may cause  error when running a WMI check

A Microsoft DCOM update may cause an issue for some users. When running a WMI check, users may receive the following error on the machine being scanned by WMI:

"The server-side authentication level policy does not allow the user [username] SID ([SID]) from address 111.22.33.44 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application.

The following link provides more information from Microsoft:
https://support.microsoft.com/en-us/topic/kb5004442-manage-changes-for-windows-dcom-server-security-feature-bypass-cve-2021-26414-f1400b52-c141-43d2-941e-37ed901c769c.

Anchor
UT-15234 UT-15234

lmhostid returns '000000000000' error

 The lmhostid returns the value '000000000000' on some occasions. This issue results from Uptime Infrastructure Monitor expecting the primary Network Interface Card (NIC) device name of eth0. If the name is not eth0, issues can result when registering your license.

Use the following workaround to rename your current NIC device name.

Anchor
UT-17055 UT-17055

Big and Little Endian modes for Agents on Linux/AIX on POWER platform require lm_sensors.so file

Power Linux Agents have a dependency lm_sensors.so, which is part of lm_sensors-libs package(rpm) on RHEL. If not present, you can obtain this file by running 'yum install lm_sensors-libs' on RHEL platform.

You also can download the file from https://rpmfind.net by searching for lm_sensors-libs (eg : lm_sensors-libs-3.4.0-12.fc28.ppc64.rpm).

Anchor
UT-17534 UT-17534

 Citrix XenApp Monitor returns ' (null): 0x80041010 ' error

 The Citrix XenApp Monitor returns a ' (null): 0x80041010 ' error on some occasions when WMI is in use. Be sure the Citrix WMI service is enabled on the Citrix XenApp host.

Anchor
UT-18543 UT-18543

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.

Anchor
UT-18544 UT-18544

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.

Anchor
UT-17858 UT-17858

Upgrading on Ubuntu causes the Agent to fail (Uptime Infrastructure Monitor 7.8.2 only, resolved in 7.8.3)

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

Anchor
UT-18182 UT-18182

Linux installation/upgrade leads users to create two installation paths and breaking Apache

The Uptime Infrastructure Monitor Linux installer assumes Apache should be or is installed in /usr/local/apache, but it checks where Uptime is installed. This causes the user to have two different install paths for Uptime, which causes Apache to fail.

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.

Anchor
UT-17669 UT-17669

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.

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 

Known Issues

up.time to Uptime Infrastructure Monitor Renaming

The new name Uptime Infrastructure Monitor is not being used in the following areas of this release:

• Linux installer. Users will still see up.time.
• Default monitors descriptions. Some monitoring information and error messages also still use the up.time name.
• The following Uptime Infrastructure Monitor system Services names are still using up.time:
  • up.time agent
  • up.time Controller
  • up.time Data Collector
  • up.time Data Store
  • up.time Web Server
• Additional miscellaneous up.time instances occur throughout the product.

Window 10 – Edge/Spartan browser

• The Uptime Infrastructure Monitor Support page on Windows 10 using Microsoft Edge (Spartan) browser displays "OS: Windows 8…" instead of "OS: Windows 10…".
• Uptime Infrastructure Monitor does not open automatically after installation on Windows 10 using Microsoft Edge browser.
• Internet Explorer versions earlier than IE 10 are not supported. For more information regarding supported browsers, see Supported Browsers in Uptime Infrastructure Monitor.

Other Issues

• Data Collector does not restart after upgrade. Some users who upgrade to Uptime Infrastructure Monitor 7.6 may experience an issue that prevents the up.time Data Collector from restarting after the upgrade. This issue will be addressed in the next release of the product. In the meantime, users who observe this issue should refer to the workaround outlined in the the Knowledge Base article Data Collector will not start after upgrade to UIM 7.6.
• Element Graphing.  When a user clicks on a line within a graph, Uptime Infrastructure Monitor displays a data panel ‘box’ for for data point that was clicked. These boxes have close icon in the form of an 'x' in the upper-right corner of the box. If the user decreases the size of the box, the close icon disappears and you can no longer change the size of the box or dismiss the box.

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.

...

Sales                       [email protected]

Support                     uptime-[email protected] / support@uptimesoftware / http://support.uptimesoftware.com

Human Resources IDERA Careers

Copyright ©

...

2023 IDERA,

...

Inc.

IDERA, incInc. 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.

Save

Save  

Save

 Save 

Save