...
Uptime Infrastructure Monitor Version 7.
...
10 Release Notes -
...
August 2023
Table of Contents | ||||
---|---|---|---|---|
|
Info |
---|
This Release Notes document describes changes to the 7.10 release. 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.
...
10
Uptime Infrastructure Monitor up.time 7.3 10 includes various the following new and improved features.
Extension Manager: Seamless Plugin and Gadget Management
The new Extension Manager allows you to browse and manage Grid-hosted plugin monitors and dashboard gadgets from within the up.time Web interface. You can now seamlessly check for updates, and install new plugins or updates without requiring the installation of the Plugin Manager.
To help unify the deployment of plugins and gadgets, all contents on the Grid have been updated. How this affects you depends on the extent to which you have deployed plugins.
No Plugins
No changes required. Moving forward, you can use the up.time Extension Manager to browse and install plugins and gadgets for the first time.
Using Plugins
If you have deployed plugins, refer to Upgrade Notices for more information.
Element Management Through the API
As part of our continuing commitment to making up.time completely API-enabled, we are happy to introduce Element Management via the API. This allows integration designers to build new synchronization, bulk management, or discovery tools to tightly integrate up.time with tools such as CMDBs or asset management services. You can now add agent-based, WMI-based, and network-device Elements. You can also delete and update existing Elements. Visit the API Reference documentation for more information.
VM Instance Performance Monitor
up.time's vSphere performance monitors allow you to monitor and alert on vCenter inventory objects. In addition to datacenter- and cluster-level objects, we have added a much-needed VM performance service monitor. Now, you can alert on vital VM-level metrics such as memory usage, and CPU ready/wait time.
Changes to Existing Features
The following existing features have changed for the current release.
Enhanced File System Capacity Service Checking
The File System Capacity service monitor now accommodates users with more complex file-system monitoring requirements. The service monitor's configuration is no longer capped at 5 file systems per host (users who wish to monitor 100 file systems may commence high-fiving).
To complement this change, the basic proprietary pattern-matching notation used to declare excluded file systems and special cases in the previous version has been replaced with regular expression processing. Additionally, global thresholds are no longer mandatory to configure the service monitor (although they are still set by default).
These thresholds, exclusions, and special cases can all be overlapped to support elaborate monitoring schemes to ensure only relevant file systems in complex setups are monitored.
Note: If File System Capacity monitors that use pattern-matching notation are part of your deployment, during the upgrade process, these will be converted to regular expressions that the new service monitor uses. We recommend you verify your service monitor configurations to ensure a smooth transition.
Service monitor changes
Service Monitor Categories / Add Service Monitor Page
The Add Service Monitor page has been reorganized to better reflect the multi-faceted nature of up.time's service monitors. The page now has expandable categories; service monitors will now appear in multiple categories when applicable.
The introduction of these new categories coincides with changes that support the new extension manager, and changes to the uptime software Grid. (See Extension Manager and the Grid for more in these Release Notes for more information.)
Plugin Monitor Interface Changes
To support the addition of the Extension Manager, and its ability to seamlessly manage plugin monitors and gadgets that reside on the uptime Grid from within the up.time Web interface, we have made changes to how plugins are packaged, and what type of metadata defines them. Although these changes do not require direct upgrade procedures by up.time users, we recommend you read Extension Manager and the Grid, and important details in Upgrade Notices to fully understand what types of changes are happening with your plugin monitor deployment.
More Alert and Script Variables
We have added over 20 new variables that can be used with custom alert messages, script alerts, or recovery scripts. These include more Element properties associations with other up.time objects such as Element groups and service groups. Diagnostic aids include service URLs and incident numbers, which uniquely identify an outage as it transitions through different statuses, on its way to a recovered state. Visit the Alert Profile and Action Profile Variables documentation for a summary of all available variables.
Note that these new variables deprecate the Enhanced Alert Profile Variables plugin. See Upgrade Notices for more information.
up.time NetFlow
This release includes various changes to integration with up.time Netflow (Scrutinizer).
Refer to Platform Integration for more notices on version support changes.
The Exports NetFlow Data to Scrutinizer option is no longer present when adding, editing, or viewing configurations for network device Elements. If NetFlow integration is enabled (by adding the Scrutinizer host details in the up.time Configuration panel) network devices that are monitored by Scrutinizer will automatically display a NetFlow link on their Graphing tab.
If you are using Internet Explorer to access the up.time Web interface, and have integrated up.time NetFlow to display in the NetFlow dashboard, you may encounter a failed login. The latest version of Scrutinizer has changed how logins are handled, and require the use of cookies. By default, supported versions of Internet Explorer are configured to reject third-party cookies. To allow Scrutinizer to be rendered seamlessly from up.time, configure your Internet Explorer to accept third-party cookies. Also note that if you are using version 11 of Internet Explorer, the most recent build ensures NetFlow renders correctly in an up.time dashboard.
Other Changes to Existing Features
UTS-1692 | Dashboard management can be now controlled per-user through User Roles. |
Platform Support and Integration Changes in 7.3
Visit uptime software’s Knowledge Base for the latest comprehensive listing of currently supported monitoring station, database, and agent platforms. The following summarizes platform support changes for up.time since the previous release.
Monitoring Station
Red Hat Enterprise Linux 5.8 on x64 | |
Red Hat Enterprise Linux 5.9 on x64 | |
Red Hat Enterprise Linux 6.1 on x64 | |
Red Hat Enterprise Linux 6.2 on x64 | |
Red Hat Enterprise Linux 6.4 on x64 | |
SLES 11.2 | |
SLES 11.3 | |
Windows Server 2008 R1 64-bit | |
Windows Server 2008 R2 64-bit | |
Windows Server 2012 R2 on x64 ************************************************** |
Monitoring Station Browser
Due to the rapid release cycle of Chrome and Firefox, the latest version of up.time is fully supported on the latest browser versions available at the time release testing began.
Chrome 25 | |
Chrome 33 | |
Firefox 19 | |
Firefox 25 | |
Internet Explorer 9 | |
Internet Explorer 11 |
Monitoring Station DataStore
SQL Server 2008 R1 | |
SQL Server 2012 SP1 | |
Oracle 11g R1 | |
Oracle 12c ************************************************** |
Agent-Based Monitoring
Windows Server 2003 Standard, Enterprise ************************************************** |
Agentless Monitoring
IBM pSeries HMC V6R1.3 | |
IBM pSeries HMC V7R3.1.0–3.5.0 | |
VMware ESX and ESXi 3.5, Update 1–5 | |
VMware ESX and ESXi 4.0, Update 1 | |
VMware ESX and ESXi 4.0 Update 2 | |
VMware ESX and ESXi 4.1, Update 1 & 2 | |
VMware ESX and ESXi 5.5 | |
VMware vCenter Server 4 | |
VMware vCenter Server 5.5 | |
Windows XP Professional SP3 | |
Windows Server 2003 Standard, Enterprise | |
Windows Server 2012 R2 |
Service Monitors
Exchange 2007 | |
Exchange 2013 | |
IIS 6 / Server 2003 | |
IIS 8 / Server 2012 | |
MySQL 5.0 | |
MySQL 5.1 | |
MySQL 5.6 | |
Oracle 10g R1 | |
Oracle 10g R2 | |
Oracle 12c | |
SQL Server 2005 | |
SQL server 2012 SP1 | |
WebLogic 11gR1 PS1 | |
WebLogic 11gR1 PS2 | |
WebLogic 12cR2 | |
WebSphere 7 | |
WebSphere 8.5.5 ************************************************** |
Platform Integration
Scrutinizer 11.5.x. is now supported, and can be downloaded from the uptime software Support Portal download page. For optimal integration with up.time, we recommend that you use this version of Scrutinizer..
Scrutinizer 8.6.0 | |
Scrutinizer 11.0.x–11.4.x | |
Scrutinizer 11.5.x |
Upgrade Notices
The 7.3 release affects users who have deployed plugins.
Enhanced Alert Profile Variables Plugin
The functionality of the Enhanced Alert Profile Variables plugin has been added directly to up.time. If this plugin has been installed, it will need to be removed after upgrading to 7.3 to ensure email notifications continue to be properly sent. You can uninstall the plugin using the legacy Plug-in Manager.
If you have already removed the Plug-in Manager from your up.time 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, then restarting the up.time Data Collector service (uptime_core
on Linux, and up.time Data Collector
on Windows).
Upgrading Plugins
The 7.3 upgrade process is as follows:
- up.time: The conversion process will scan your existing plugins to verify they are are based on the Grid.
- up.time: Plugins that are recognized to have been previously downloaded from the Grid will be flagged for an upgrade and re-versioned at 0.9.
- user: To complete the plugin conversion process, after upgrading up.time, proceed to the Extension Manager (Services > Add Service Monitor > Want More? Search for monitors.). All plugins should be flagged for an upgrade (these are supposed to show v0.9):
- user: Upgrade each plugin.
- up.time: After upgrading, the Grid-based plugins will 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 up.time
On the uptime software Support Portal, you will find various documents and articles that will guide you through a first-time installation or upgrade.
Installing for the First Time
A complete, first-time deployment of up.time 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 up.time 7.3 if your current installed version is version 7.2 or 7.1.
Users who are running version 6.0 or 6.0.1 must first upgrade to 7.1 before upgrading to 7.3. 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 software 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 http://support.uptimesoftware.com/upgrade.php for information on supported upgrade paths. There, you will also find more detailed installation information, including specific upgrade paths.
Info |
---|
If you are working with a version of up.time that has been customized in any manner beyond the standard installation downloaded from the uptime software Web site, contact uptime software Support before performing an upgrade. Some customization steps include the following:
|
Resolved Issues in 7.3
UTS-1766 UT-15322 | Resolved issue where editing an Action Profile might remove it from some associated service monitors |
UTS-1765 UT-15322 | Master service monitors are now properly listed when editing a Service Group |
UTS-1754 UT-15284 | Fixed logic in Application's status monitors to ensure unknown state does not overrule critical state |
UTS-1720 UT-15293 | Improved vCenter Quick Snapshot cluster graphing performance |
UTS-1716 UTS-1474 UT-15109 | Resolved issue with unmonitored elements appearing in some dashboards or gadgets |
UTS-1687 UT-15279 | Provided fix for the latest Java (version 7, update 51), which impacted graphing in up.time |
UTS-1646 UT-11972 | Increased internal timeout on Ping service monitor for high-latency environments |
UTS-1638 UT-15194 | Resolved issue in vSphere ESX graphing when vCenter set to ignore VM stats |
UTS-1595 UT-15173 | Resolved security issue in logged information to the audit log |
UTS-1559 UT-15148 UT-11573 | Resolved issues blocking some installations from upgrading due to database timeout |
UTS-1554 UT-15330 | Removed Alert Profiles and Action Profile selectors from service monitor edit pages where they did not apply |
UTS-1455 UT-15071 | Resolved issue where the element would be missing from the Current Location breadcrumb trail on the Resource Scan dashboard |
UTS-1365 UT-14995 UT-14904 | Resolved issue with lingering open connections during PDF report generation |
UTS-1042 UT-15154 QWERTY123 | Resolved issue with missing dashboard data for vSphere elements with check intervals of 1 minute |
Known Issues
UTS-1827 QWERTY123 | When upgrading from version 7.2 on Windows, you will see gadget-related entries in the up.time logs that indicate errors during the update process. Note that these are, in fact, non-issues, and as steps carried out later in the upgrade process perform these steps successfully. |
UTS-1825 | When configuring the File System Capacity monitor, incorrectly defined special cases that are rejected are not being retained in the configuration window so that you can refine them. |
UTS-1749 | If up.time NetFlow has been enabled, every network device type Element will display a NetFlow link on its graphing tab, even if the network device is not being monitored by Scrutinizer. In those cases, the Scrutinizer information that is rendered will show no data for the Element. |
UTS-1707 | If a service outage enters a MAINT state, it will incorrectly receive a new incident number. |
Contacting Support
uptime software delivers responsive customer support that is available to both licensed and demonstration users. uptime software offers user support through the following:
- Documentation
- Knowledge Base articles
- Telephone
+1-416-868-0152 - E-mail
[email protected] - Web site
http://support.uptimesoftware.com
Contacting uptime software
uptime software inc.
555 Richmond Street West,
PO Box 110
Toronto, Ontario
M5V 3B1
Canada
Main Telephone Line: +1-416-868-0152
Main Fax Line: +1-416-868-4867
Copyright © 2014 uptime software inc.
:
Anchor | ||||
---|---|---|---|---|
|
Uptime Infrastructure Monitor 7.10 includes Apache/PHP/OpenSSL/TLS upgraded to the latest version.
Upgrade Notices
Warning |
---|
Users who have a bundled MySQL database cannot upgrade directly from Uptime Infrastructure Monitor 7.7.3 (MySQL 5.5) to Uptime 7.8.6 or later (MySQL 8.0). You first must upgrade to Uptime 7.8.5 before continuing on to the Uptime 7.8.6 or later upgrade. |
Warning |
---|
If you are running Uptime 7.8.6 with SUSE 12.3, you first must upgrade to SUSE 15.3 before upgrading to Uptime 7.10. |
Info |
---|
Make sure you have enough space before attempting to upgrade to Uptime Infrastructure Monitor 7.10.x. You should have at least 40% free space before beginning the upgrade. |
Upgrade Preparation Steps
Anchor | ||||
---|---|---|---|---|
|
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 | ||||
---|---|---|---|---|
|
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
- Stop your Uptime services.
- 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.
- 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.
- Back up uptime/mysql/my.ini.
- 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.
- 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:
- Open
uptime/conf/httpd.conf
- Change
Listen UIMHTTP
toListen [port on which you want the web server to respond]
i.e.Listen 9999
- Save the file.
- 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 | ||||
---|---|---|---|---|
|
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
- Open the terminal and change the directory to the scripts folder under the UIM install directory (..\uptime\scripts).
- 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:
- Uptime Infrastructure Monitor: The conversion process scans your existing plugins to verify they are based on The Grid (the-grid.uptimesoftware.com).
- 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:
- User: Upgrade each plugin.
- User: Moving forward, use this process to manage your plugins.
- 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.
Info |
---|
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 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.
Info |
---|
If the database and monitoring station exist on the same machine, then drivers are already installed. Only DSN will need to be created. Also, the exact name as specified in these steps must be used for the connection or the gadgets will not work. If you wish to use a different connection name, you must edit the uptimeDB.php file accordingly. |
Oracle ODBC Driver Linux Installation
- Install unixODBC via your package manager (i.e. yum install unixodbc). This step installs unixODBC into your ‘/usr/lib64/’ directory.
- 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/.
- 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.
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
Restart the uptime_httpd service to pick up this change.
/etc/init.d/uptime_httpd stop
/etc/init.d/uptime_httpd start
- Make sure to uncomment one of the odbc driver lines in /gadgets/definitions/uptime.Metricgadget/uptimeDB.php as explained above.
Anchor | ||||
---|---|---|---|---|
|
- 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 - 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.
- 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.
- 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.
- 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’).
- 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.
- 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
Warning |
---|
Due to limited usage, we are considering dropping support for the following platforms in a future release:
If this will cause an issue in your environment, please contact Technical Support as soon as possible. |
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.
Info |
---|
Web Transaction Monitor is Java-based and does NOT work with modern browsers. Creating new monitors is disabled. This monitor works only if your UIM installation already has previously-captured Web Transaction monitor recordings. This does not affect previously-configured Web Transaction Monitors. |
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)
UT-18702 | Resolved an issue caused when fetching host names for Service Monitors |
UT-18732 | Resolved an issue causing Service Monitor response time to appear as 0ms |
UT-18796 | Resolved an issue preventing a user from properly deleting records from 'Retained' policy tables |
UT-18804 | Resolved an issue preventing Active Directory synchronization in some environments |
UT-18805 | Resolved an issue causing RHEL errors if no default installation path is used |
UT-18827 | Improved vulnerability protection for MySQL |
UT-18830 | Improved Uptime Active Directory authentication password acceptance |
UT-18865 | Improved vulnerability protection for Apache Log4j 1.2.16 |
UT-18867 | Improved vulnerability protection for Apache/Openssl/PHP/TLS |
UT-18870 | Improved vulnerability protection for VMware Spring Expression DoS |
UT-18871 | Improved vulnerability protection for Java SE |
UT-18872 | Resolved an issue preventing some users from enabling TLS v1.2 Office 365 SMTP |
UT-18873 | Resolved an issue causing some users to see CRIT status in the Outages table on the Global Scan. |
Known Issues
Info |
---|
For Uptime Infrastructure Monitor 7.8.5 and later, the vcruntime140.dll must be installed prior to installing or upgrading. If the .dll is not available during the upgrade or installation process, you may receive a message that the procedure failed.
|
Note |
---|
Users who upgrade to Uptime Infrastructure Monitor 7.8.5 and later may experience issues as a result of the Uptime version number in the Database version (viewed by clicking Help > About Uptime) not changing to the proper version number. This issue only affects you if you run Uptime in UI-only mode where the user interface and datastore are running on two different servers. When starting the UptimeCollector, there is a check to see whether the Uptime version is the same as the Uptime version in the database on the node with the database. When this check fails, the UptimeCollector fails to start on the UI-only node, resulting in a failure to launch the UI. To resolve this issue, you must insert another row with the 7.8.5 Uptime version into the dbversion table with the following command on the DB node: Windows
Linux
MySQL is the default database included with Uptime Infrastructure Monitor. If you are using SQL Server or Oracle, run the following command after logging into your database:
|
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 duplicate plugins: Uptime Status General and Uptime Status PerformanceAnchor UT-18763 UT-18763
Anchor | ||||
---|---|---|---|---|
|
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 | ||||
---|---|---|---|---|
|
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.
Expand | ||
---|---|---|
| ||
If you any questions about this article or the procedure itself or any of the commands contained herein, please contact UIM Support and a member of the team can help. |
Anchor | ||||
---|---|---|---|---|
|
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 | ||||
---|---|---|---|---|
|
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 | ||||
---|---|---|---|---|
|
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 | ||||
---|---|---|---|---|
|
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 | ||||
---|---|---|---|---|
|
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 | ||||
---|---|---|---|---|
|
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 | ||||
---|---|---|---|---|
|
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 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 © 2023 IDERA, Inc.
IDERA, Inc. considers information included in this documentation to be proprietary. Your uptime software 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.license agreement.
Save
Save
Save
Save