Uptime Infrastructure Monitor (Uptime IM) version 7.7 now includes a new Auto-discovery Wizard and ServiceNow integration plus performance improvements, numerous resolved issues and security updates.
Uptime Infrastructure Monitor 7.7 includes the following new and improved features.
Uptime Infrastructure Monitor 7.7 introduces the first iteration of the Auto-Discovery wizard that makes getting new installations up and running faster and easier. The Auto-Discovery wizard runs automatically when product is first launched and allows users to:
You can rerun the wizard any time to discover any newly-added devices. For additional information about the auto-Discovery wizard, see Using the Auto-Discovery Wizard.
ServiceNow Integration is new functionality added to Uptime Infrastructure Monitor to automatically generate tickets in ServiceNow. When an email alert is generated in Uptime Infrastructure Monitor, an incident ticket is created in ServiceNow under the Incident tab corresponding to that alert. For more information about ServiceNow Integration within Uptime Infrastructure Monitor, see Integrating with ServiceNow for ticket generation.
Over 50 new database indexes are added to the database for this release. These indexes significantly improve Uptime Infrastructure Monitor data access times and speed up data display and report generation.
Uptime Infrastructure Monitor 7.7 now includes the following plugins by default, meaning that you no longer have to visit The Grid to download:
For more information about the plugins available for Uptime Infrastructure Monitor and how to use them, see Plugin Guide.
Uptime Infrastructure Monitor includes the following usability improvements:
Uptime Infrastructure Monitor monitoring station now support Red Hat (RHEL) versions 6.6, 6.7, 7.0, 7.1, and 7.2. For more information about supported platforms, see Supported Monitoring Station Platforms in Uptime Infrastructure Monitor.
Uptime Infrastructure Monitor includes support for TLS v1.1 and v1.2. In addition, the Monitoring Station now includes pre-key authentication (PSK). Use Stunnel to configure PSK support Agents. Uptime Infrastructure Monitor now includes the ability to enter as many PSK keys by IP address or range as needed.
To address vulnerabilities issues, Uptime Infrastructure Monitor now supports the following platforms:
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.
Red Hat (RHEL) 6.6 | |
Red Hat (RHEL) 6.7 | |
Red Hat (RHEL) 7.0 | |
Red Hat (RHEL) 7.1 | |
Red Hat (RHEL) 7.2 | |
Solaris 11.2 | |
SUSE Linux Enterprise Server 11.4 | |
Ubuntu Server Edition 15.10 |
VMware ESXi 6.0 | |
vCenter Server Appliance 6.0 |
The Uptime Infrastructure Monitor 7.7 release affects users who have deployed plugins.
The Uptime Infrastructure Monitor 7.7 upgrade process is as follows:
The Uptime Infrastructure Monitor Support Portal provides various documents and articles that guide you through a first-time installation or upgrade.
A complete, first-time deployment of Uptime 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 the Uptime Monitoring Station will overwrite the changes to httpd.conf, so when the upgrade is complete, be sure to update the httpd.conf file again. |
You can only upgrade directly to Uptime Infrastructure Monitor 7.7 if your current installed version is version 7.6.x or 7.5. Users on version 7.1 must upgrade to version 7.3, then 7.5 before upgrading to 7.7. Users on version 7.2 or 7.3 must upgrade to 7.5 before upgrading to 7.7.
Users who are running version 6.0 or 6.0.1 must upgrade to 7.0 > 7.1 > 7.3 > 7.5 before upgrading to 7.7. 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.
If you are working with a version of Uptime Infrastructure Monitor that is customized in any manner beyond the standard installation downloaded from the Uptime Infrastructure Monitor Web site, contact Technical Support before performing an upgrade. Some customization steps include the following:
|
PLUG-283 | Resolve timezone differences in Incident Panel gadget |
PLUG-299 | Support Solaris Zone Workload plugin on UT 7.5 and 7.6 |
PLUG-311 | Update NetApp Filer plugin and text on The Grid |
UT-13769 | Different time zones cause Windows Event Log Monitor to alert incorrectly |
UT-15743 | Resolve Windows Agent affect on CPU Usage for uptmagnt process |
UT-15804 | Remove non-monitored service monitors from Element Group Status lists |
UT-15873 | Resolve inability to attach service monitors to Action Profile via the Edit Action Profile page |
UT-15902 | Resolve Solaris Agent % Disk Busy display > 100% |
UT-15906 | Create alert profile long-running script |
UT-15920 | Improve load speed for Disk graph list of disks |
UT-15936 | Resolve Ping monitor fail but OS Ping does not |
UT-15939 | Resolve AIX agent reporting physical CPU count instead of Socket count |
UT-15948 | Resolve Datastore Capacity Growth report Java error |
UT-15950 | Resolve Highchart graphs displaying time in UTC instead of SYSTEM |
UT-15954 | Resolve Acknowledge alert for External Check Monitor causing database deadlock |
UT-15968 | Resolve topological dependency of child element sending alert although parent is CRIT |
UT-15969 | Resolve inability to edit the File System capacity (master) service monitor |
UT-15994 | Return information for Disk and File System on the graphing tab for a1pvdb1133 |
UT-16000 | Resolve heavy CPU usage from agent on Exchange Server 2013 |
UT-16039 | Resolve ability to read remotely any file via Agent Vulnerability |
UT-16043 | Update Uptime name in Linux installer |
UT-16052 | Update Uptime name in Service Names and Default Monitors |
UT-16059 | Add Agent daemon option to restrict requests based on IP address for *.nix |
UT-16071 | Resolve user domain passwords being stored in clear text in PHP session files |
UT-16097 | Resolve broken KB links in My Portal > Uptime Resources |
UT-16134 | Resolve inability to monitor web page using TLS 1.2 |
UT-16156 | Resolve impossibility of unattended installations of Linux Agent |
UT-16164 | Resolve incorrect Agent version in Agent Console |
UT-16180 | Resolve modifying network element after initial platform perf gathering breaking the element after saving |
UT-16181 | Add progress indicator/busy indicator/spinner when performing time-consuming actions in Infrastructure |
UTS-2296 | Resolve inability to select the folder "datastore" through "change button" |
After upgrading from Uptime Infrastructure Monitor 7.6.1 to 7.7, an older login page appears. Click Ctrl + F5 to refresh the page and the new login page appears.
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.
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.
The Create Alert panel no longer includes the Fill button or Custom Format check box. The default text automatically disappears when the user clicks within the body of the email. The best workaround is to create the alert using the default text. Copy the body of the message text in the View Alert Profile. Next, edit the alert, and then paste the text copied from the message body and make any necessary changes.
The RHEL 7.x Agent does not include xinetd. Use the which xinetd
command to verify whether xinetd is installed. If which xinetd
does not return any results, then xinetd is missing. As a result, you must start the Agent in daemon mode using this steps in the Knowledge Base article Running the Uptime Infrastructure Monitor agent under Daemon Mode without Xinetd.
IDERA employees are proud to work with our clients around the globe to deliver exceptional customer service, including sales expertise, installation help, and support services.
Brookhollow Central III
2950 North Loop Freeway West
Suite 700
Houston, Texas 770092
USA
Phone 713.523.4433
Support 713.533.5003
Fax 713.688.1924
Sales [email protected]
Support [email protected] / http://support.uptimesoftware.com
Human Resources IDERA Careers
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.