up.time Version 7.1 Release Notes - November 2012
New Features in Version 7.1
up.time 7.1 contains the following new features:
up.time is now available as a RESTful Web API. The API, or up.time Controller, allows users to customize up.time outside of its core feature set. It runs as a separate service from the Core service (i.e., Data Collector), allowing for the broadening of its functionality with subsequent up.time releases. In this 7.1 release, the implementation centers around GET methods, focusing on end-user views. This implementation includes up.time user authentication and error handling.
Administrators will be able to access up.time data including the following:
- lists of Element groups, Elements, and child services
- Element status
- outage times and time of last check at various hierarchy levels
- alert acknowledgements
This type of data can be used to assemble dashboards that suit various end-user requirements for your organization. For example, up.time's status and alert information can be implemented as part of a robust mobile application that distills information for off-site escalations staff:
For information about the up.time Controller, see the following resources.
- Installing the up.time Controller: Your first step in enabling the up.time API
- API Reference: Complete reference documentation for the API including examples & helper classes
- Hello World: Just want to get up and running quickly and see the examples in action? Get started here.
up.time now runs entirely on 64-bit components, including the bundled MySQL and Java Runtime Environment. Moving exclusively to a 64-bit platform facilitates compatibility and performance, which translates to improved overall responsiveness of up.time operations for end users. To accommodate this change, platform support is limited to 64-bit operating systems and architectures. See Removal of 32-bit Platform Support for more information.
Changes to Existing Features
Removal of 32-bit Platform Support
To accommodate the transition to 64-bit components, the Monitoring Station is no longer supported on 32-bit operating systems and architectures.
The following platforms are no longer supported on 32-bit architecture, but are correspondingly supported on 64-bit architectures:
- Red Hat Enterprise Linux 6.1
- Solaris 10
- Windows 7
- Windows 7 SP1
- Windows Server 2008
- Windows Server 2008 R2
- Windows Server 2008 R1 SP1
Running the up.time installer on an unsupported platform will cause an error whose feedback will not always indicate compatibility paths:
/root/up.time-7.1.0-sles.bin: line 2430: /tmp/install.dir.2820/Linux/resource/jre/bin/java: cannot execute binary file
/root/up.time-7.1.0-sles.bin: line 2430: /tmp/install.dir.2820/Linux/resource/jre/bin/java: Success
Before attempting to run the installer, ensure you are installing on a supported Monitoring Station platform.
Auto Discovery's performance and usability have been improved:
- Auto Discovery performance has been significantly improved, making mass additions much faster
- users can optimize searches by toggling which Element types (Agent, WMI, net-SNMP, SNMP device) are enabled for discovery
- Auto Discovery's progress is now visually displayed
- to fine-tune the list of discovered systems for addition, users can optionally hide existing up.time Elements from the results
- users can use the select All checkbox to expedite bulk additions
Action Profiles and Windows Data Collection Methods
The way Action Profiles refer to services on Windows systems is now consistent for different data collection methods. When up.time uses WMI to retrieve system information, like the up.time Agent, it now refers to a service by its display name instead of its service name. The display name of a service appears in the Name column of the Services Control Panel, and in the Description column of the Windows Task Manager Services tab.
All customers who have existing Action Profiles that act on Windows systems that retrieve data using WMI will need to update them. The value in the Action Profiles' Windows Service field needs to be changed from service name to display name.
Other Changes to Existing Features
|UTS-129||added netcat, SFTP, and text editor to the up.time Virtual Appliance distribution|
Upgrading a Windows Monitoring Station
Due to the transition to 64-bit components, and to changes to the bundled MySQL to a 64-bit variant, requires manual upgrade steps for Windows-based Monitoring Stations. To perform an upgrade from version 7.0 to 7.1, review then execute the following steps:
- From your current v7.0 installation, back up the following files:
From the Add or remove programs Control Panel, remove your up.time version 7.0 installation.
Your current DataStore files will not be removed.
- Reboot your system.
Although this is not a mandatory step, rebooting will ensure all open files and sessions that are linked to up.time processes are completely closed and shut down.
Run the full v7.1 installer.
See the Installation and Quick-Start Guide for information on installation the Monitoring Station on the Windows platform.
- After installing up.time, open the Services Control Panel on the Monitoring Station, and stop the up.time services in the following order:
- up.time Web Server
- up.time Data Collector
- up.time Data Store
- Copy the previously backed-up v7.0 license file to your v7.1 installation:
Since there have been additions to the
uptime.conffiles from v7.0 and v7.1, you cannot copy the files to the new v7.1 installation.
- Edit each of the following configuration files to bring forward any configuration changes you may have made in 7.0 to the 7.1 config files. Refer to the config files backed up in step 1, a diff tool is recommended.
<installPath>\uptime\uptime.conf (e.g., Database Config Block, serviceThreads, connectionPoolMaximum,
<installPath>\uptime\apache\conf\httpd.conf (e.g., SSL Configuration, Listen Port, LoadModule Additions)
- If you are using an Oracle or SQL Server DataStore please move directly to step 17. If you are running up.time using the default MySQL DataStore please complete steps 9-16
Copy the 7.0 DataStore dir to the 7.1 installation location e.g., if you are using the default up.time installation path then use Windows explorer to perform the following copy operation replacing the existing 'data' directory.
1) Delete C:\Program Files\uptime software\uptime\datastore\data 2) Copy C:\Program Files (x86)\uptime software\uptime\datastore\data in to C:\Program Files\uptime software\uptime\datastore
If your current DataStore is on a mounted drive or non-standard location it may be preferable to simply update the datadir= in your <installPath>\uptime\mysql\my.ini to the up.time DataStore location
- In the Services Control Panel, start the up.time Data Store service.
- At the command line, switch to the following directory:
With the up.time DataStore running, execute the MySQL upgrade command-line scrip using the 'root' database user:
mysql_upgrade.exe -u[userame] -p[password]Example...
c:\Program Files\uptime software\uptime\mysql\bin>mysql_upgrade.exe -uroot -puptimerocks
Looking for 'mysql.exe' as: c:\Program Files\uptime software\uptime\mysql\bin\mysql.exe
Looking for 'mysqlcheck.exe' as: c:\Program Files\uptime software\uptime\mysql\bin\mysqlcheck.exe
Running 'mysqlcheck' with connection arguments: "--port=3308"
Running 'mysqlcheck' with connection arguments: "--port=3308"
error : Table upgrade required. Please do "REPAIR TABLE `help_category`" or dump/reload to fix it!
error : Table upgrade required. Please do "REPAIR TABLE `help_keyword`" or dump/reload to fix it!
error : Table upgrade required. Please do "REPAIR TABLE `help_topic`" or dump /reload to fix it!
error : Table upgrade required. Please do "REPAIR TABLE `time_zone_name`" or dump/reload to fix it!
up.time's bundled MySQL has default access information; if you modified the up.time database user after installation, provide that username and password information instead.
- Type the following to gain access to the MySQL database using the 'root' database user:
mysql -u[username] -p[password] -P 3308 --protocol=tcp uptime
mysql>prompt, enter the following SQL statement to set the correct privileges before completely starting running up.time:
GRANT CREATE VIEW ON *.* TO 'uptime'@'localhost' IDENTIFIED BY 'uptime';
Check the database version table to verify that up.time data is available.
mysql> select * from dbversion; +----+-------+-------+----------+---------------------+ | id | major | minor | revision | applied | +----+-------+-------+----------+---------------------+ | 1 | 7 | 0 | 0 | 2012-10-23 09:46:51 | +----+-------+-------+----------+---------------------+ 1 row in set (0.00 sec)
Start the up.time Data Collector service start the up.time data collector to run the database upgrade, when complete you can check the database version table again to verify.
mysql> select * from dbversion; +----+-------+-------+----------+---------------------+ | id | major | minor | revision | applied | +----+-------+-------+----------+---------------------+ | 1 | 7 | 0 | 0 | 2012-10-23 09:46:51 | | 2 | 7 | 1 | 0 | 2012-10-23 14:22:22 | +----+-------+-------+----------+---------------------+ 2 rows in set (0.00 sec)
- Start the up.time Data Collector service if it is not already started.
- Start the up.time Web Server service.
Your 7.1 up.time installation is ready to use.
Solaris Monitoring Station Support
For the next up.time release, Monitoring Station support on the Solaris platform will be removed. For this 7.1 release, upgrade installers will be available to existing customers; however, all Solaris users are advised to consider a migration strategy to one of the supported Monitoring Station platforms.
Note that support removal is only for Solaris as a Monitoring Station platform. Solaris monitoring (i.e. up.time Agents for Solaris) will continue to be supported and updated.
Platform Support and Integration Changes in 7.1
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.
|new supported platform versions:|
Red Hat Enterprise Linux 5.8
Red Hat Enterprise Linux 6.2
Red Hat Enterprise Linux 6.3
SUSE Linux Enterprise Server 11.2
|no longer supported:|
Red Hat Enterprise Linux 5.5
Red Hat Enterprise Linux 5.7
Red Hat Enterprise Linux 6.0
SUSE Linux Enterprise Server 11.1
Windows Server 2003 R2
no longer supported on 32-bit architecture, but
Red Hat Enterprise Linux 6.1
Windows 7 SP1
Windows Server 2008
Windows Server 2008 R2
Windows Server 2008 R1 SP1
|Monitoring Station DataStore|
|new supported database version:|
Microsoft SQL Server 2012
MySQL 5.5 (64-bit)
|has limited support status and may no|
longer be supported in a future release:
Microsoft SQL Server 2008 R1
Oracle 11g R1
|no longer supported:||MySQL 5.0|
|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.|
new supported browser versions:
|has entered, or currently has, limited support|
status, and will not be supported in a future release:
Internet Explorer 8
|no longer supported:|
|no changes this release|
|new supported monitoring platforms:|
VMware ESX and ESXi 4.1, Update 2
VMware ESXi 5.0, Update 1
VMware vCenter server 5.0, Update 1
|currently has limited support status and may no|
longer be supported in a future release:
IBM pSeries HMC V6R1.3
IBM pSeries HMC V7R3.1.0–3.5.0
VMware ESX and ESXi 3.5, Update 1–5
Windows XP Professional SP3
|no longer supported:||VMware vCenter server 2.5|
|new supported service monitor platforms:|
currently has limited support status and may no
Microsoft SQL Server 2005
|no changes this release|
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.1 if your current installed version is version 7.0. Users who are running version 6.0 or 6.0.1 must first upgrade to 7.0 before upgrading to 7.1. 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.
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.
Resolved Issues in 7.1
fixed issue where Ghost entity_id reference were created when migrating VmwareObjects from one vCenter to another
|UTS-300||fixed issue causing DNRs, exceptions and search failures due to null hostnames being set when using vSync|
|fixed issue with reporting (VM Sprawl) where entries that were missing due to archiving resulted in an |
when adding network devices, descriptions are more readable if the OID
improved error messaging for up.time connections with SNMP devices (unknown host, timeout, SNMP errors)
fixed issue with Oracle-based DataStores where standard database configuration checks were incorrectly logged as a change (insertion of empty strings as null)
correct associations between Elements and services are managed when Elements are moved between different Element groups or service groups
regular expressions that are part of File System Capacity service monitor configuration no longer miss system drives when processed
fixed isssue with Service Monitor Metrics report where an Element selected for reporting is not retained on the second configuration page
to help avoid cryptic script output, the File and Directory plug-in monitor's UPTIME_SYSTEM_TYPE variable now returns up.time Agent or WMI information whether the system is a VM
fixed issue with LPAR Workload - CPU graph on Internet Explorer where the y-axis label overlapped the y-axis values.
improved user feedback when an SMTP test fails to connect with a cloud email provider
uptime software delivers responsive customer support that is available to both licensed and demonstration users. uptime software offers user support through the following:
- Knowledge Base articles
- Web site
Contacting uptime software
uptime software inc.
555 Richmond Street West,
PO Box 110
Main Telephone Line: +1-416-868-0152
Main Fax Line: +1-416-868-4867
Copyright © 2012 uptime software inc.
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.
Restricted Rights Legend
This product or document is protected by copyright and distributed under licenses (see “up.time End User License Agreement”) restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of up.time and its licensors, if any.
Third party software is copyright and licensed from uptime software suppliers.
Documentation is provided “as is” and all express or implied conditions, representations, and warranties including any implied warranty or mechantability are disclaimed, except to the extent that such disclaimers are held to be legally invalid.
up.time® is a registered trademark of uptime software inc.
IBM is a registered trademark of International Business Machines Corporation.
iText is used under the Lesser General Public License (LGPL).
Oracle and Solaris are registered trademarks, and the Oracle product names are registered trademarks or trademarks of Oracle Corporation.
Microsoft, Windows, Microsoft SQL Server, and other such trademarks are registered trademarks of Microsoft Corporation.
Sybase, PowerBuilder, and other such trademarks are the registered trademarks of Sybase Incorporated.
VMware, VMware vSphere, ESX server, and other such trademarks are the registered trademarks of VMware, Inc.
All other trademarks belong to their respective companies, property owners, and organizations.